You must re-emerge every package that links to openssl after you have
merged openssl 0.9.7 This is becuse packages that links against
openssl 0.9.7 links against the full version. Also, if you don't have the
sources for the packages you need to re-emerge you should download
them with emerge -f prior to the installation of openssl 0.9.7 This is
becuse wget may be linked against openssl 0.9.7 To generate a list of
packages that links against openssl 0.9.7 you can download and run the
script from http://cvs.gentoo.org/~aliz/openssl_update.sh If
you are using binary packages you need to rebuild those against the
new version of openssl 0.9.7.

But after I read this warning, I updated openssl!

OK let's start

Code:

cd /usr/portage/dev-libs/openssl/
emerge -u openssl-0.9.7b.ebuild

After this you have to run the script openssl_update.sh

Code:

sh openssl_update.sh > liste1

Now we have a file with all packages that needs an update after openssl is updated.

After this emerge the biggest problem is to emerge the packages that you have to update in the right order.
For this I coded I small perl script

Code:

#!/usr/bin/perl

open (IN,"<liste1"); # the file where the output from the given script
# is. http://cvs.gentoo.org/~aliz/openssl_update.sh
@in = <IN>;
close IN;

Reading this I think qpkg should have two extra options; One to sort its output dependency-wise and another to list only the packages. I mean, why an extra script, if qpkg -I -q openssl does nearly the same?

You have to update much more packages than "qpkg -I -q openssl" find.
The script http://cvs.gentoo.org/~aliz/openssl_update.sh find every package that links again openssl.
"qpkg -I -q openssl" only finds the packages what have DEPEND="openssl" in the ebuild.

I'm currently running openssl 0.9.7b, and I didn't have to run this script at all. I just reinstalled packages depending on openssl and everything seems to be working. Now granted I've only been doing this for a few days, so problems might arise in the future, but it should be a simple matter to fix them. Just make sure you have the wget sources first, since you'll need that to fetch any other sources.

For people getting an empty list after running openssl_update.sh, you have to run the script *after* you update OpenSSL. I had the same problem at first (Be sure to emerge -f wget before emerging OpenSSL!)

Posted: Thu May 22, 2003 4:44 pm Post subject: How long does that script take?

Hello Everyone,
Thanks for the HOWTO Muchos appreciated!
I was wondering how long that script takes.
This could be a cut n' paste issue. So if someone could post a working file to ensure it isn't it would also be appreciated.
When I attempt to sort, the output returned is (something like)
65 packages to sort
^[[55 packages left to sort
^[[55 packages left to sort
^[[55 packages left to sort
^[[55 packages left to sort
^[[55 packages left to sort
^[[55 packages left to sort

which you don't really need because there aren't going to be any apps that rely on libssl and libcrypto that will relink themselves.
elementary actually it's so easy i am surprised no one else has posted this

emerge openssl just didn't compile the libs, just docs and headers...
instead of compiling it gave me a very very long list of "coloured" errors... like he was doing a "cat" on the configure and/or the Makefile instead of *running* them.

so my problem is BEFORE re-emerging the packages linked to libssl/libcrypto or whatever.

I compiled openssl 0.7.9 by hand (it worked fine.. so i think there are some problems with the ebuild...?)

after i emerged openssl 0.7.9 again... and didn't work at all (same thing as before).. but i had my libssl.so.0.7.9 in /usr/lib from manually installed openssl.

i tried to emerge wget.. and magically it just "compiled" docs and unuseful stuffs but it didn't actually compiled any code.