Updating packages breaks wget/libssl

[jdkruzr]

now, anything that depends on libssl fails.

libopenssl - 3.0.8-2a

Caelum: ~/ opkg remove libopenssl
No packages removed.
Collected errors:
 * print_dependents_warning: Package libopenssl is depended upon by packages:
 * print_dependents_warning: 	libcurl
 * print_dependents_warning: 	git
 * print_dependents_warning: 	git-http
 * print_dependents_warning: 	wget-ssl
 * print_dependents_warning: These might cease to work if package libopenssl is removed.

 * print_dependents_warning: Force removal of this package with --force-depends.
 * print_dependents_warning: Force removal of this package and its dependents
 * print_dependents_warning: with --force-removal-of-dependent-packages.
Caelum: ~/ wget
wget: error while loading shared libraries: /usr/lib/libssl.so.1.1: internal error

among other things this means I can't opkg update anymore because it uses wget-ssl. git is broken, etc. I would imagine there's some way to get applications that expect SSL 1 and SSL 3 to coexist?

[Eeems]

This is a bug with entware and not toltec. They have an issue with the order that packages are upgrading. You can solve this by doing the following steps:

opkg remove wget-ssl
wget http://toltec-dev.org/thirdparty/bin/wget-v1.21.1
# This next step is important. If it errors, something changed the file as it was downloaded. Either it corrupted,
# or something modified in in transit. I highly recommend not using it if this is the case.
# Instead you can try manually downloading it on your computer with https and validate that it doesn't get changed.
# Then you can copy it to your device.
echo "8798fcdabbe560722a02f95b30385926e4452e2c98c15c2c217583eaa0db30fc  wget-v1.21.1" | sha256sum -c -
chmod +x wget-v1.21.1
mkdir -p /home/root/.local/bin
mv -f  wget-v1.21.1 /home/root/.local/bin/wget
ln -s /home/root/.local/bin/wget /opt/bin
opkg update
opkg upgrade
opkg install --force-reinstall wget-ssl
rm /home/root/.local/bin/wget

Edit: Updated steps based on feedback later in the thread.

[Eeems]

Entware/Entware#913 is the upstream issue for this. It looks like the official solutions are just workarounds similar to ours.