| Summary: | sys-apps/portage-2.1.11.50: openssl:0.9.8 is installed but libssl.so.0.9.8 and libcrypto.so.0.9.8 are preserved | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Peter Asplund <azpegath> |
| Component: | [OLD] Library | Assignee: | Portage team <dev-portage> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | esigra, pacho |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 240323 | ||
|
Description
Peter Asplund
2013-01-27 13:17:10 UTC
Don't you have openssl:0.9.8 installed? dropbox-1.4.23 is RDEPENDing on dev-libs/openssl:0.9.8, so that /usr/lib64/libssl.so.0.9.8 should not even be preserved-rebuild target. I seem to have both 0.9.8x and 1.0.1c installed.
root@skare$ eix openssl -I
[I] dev-libs/openssl
Available versions:
(0.9.8) 0.9.8u 0.9.8v 0.9.8w 0.9.8x
(0) 1.0.0h 1.0.0i 1.0.0j (~)1.0.1a (~)1.0.1b 1.0.1c
{bindist gmp kerberos rfc3779 sse2 static-libs test vanilla zlib}
Installed versions: 0.9.8x(0.9.8)(20:30:48 2012-05-12)(sse2 zlib -bindist -gmp -kerberos -test) 1.0.1c(20:32:47 2012-05-12)(sse2 zlib -bindist -gmp -kerberos -rfc3779 -static-libs -test -vanilla)
Homepage: http://www.openssl.org/
Description: full-strength general purpose cryptography library (including SSL v2/v3 and TLS v1)
root@skare$ ll /usr/lib/libssl*
lrwxrwxrwx 1 root root 13 19 jan 13.02 /usr/lib/libssl3.so -> libssl3.so.12*
-rwxr-xr-x 1 root root 273K 19 jan 13.02 /usr/lib/libssl3.so.12*
lrwxrwxrwx 1 root root 15 12 maj 2012 /usr/lib/libssl.so -> libssl.so.1.0.0*
-rwxr-xr-x 1 root root 340K 12 maj 2012 /usr/lib/libssl.so.0.9.8*
-r-xr-xr-x 1 root root 418K 12 maj 2012 /usr/lib/libssl.so.1.0.0*
and
% ldd /opt/dropbox/dropbox
/opt/dropbox/dropbox:
linux-vdso.so.1 (0x00007fff407fe000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fab31d9e000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007fab31b9a000)
libutil.so.1 => /lib64/libutil.so.1 (0x00007fab31997000)
libm.so.6 => /lib64/libm.so.6 (0x00007fab3169c000)
libssl.so.0.9.8 => /usr/lib64/libssl.so.0.9.8 (0x00007fab31446000)
libcrypto.so.0.9.8 => /usr/lib64/libcrypto.so.0.9.8 (0x00007fab310b2000)
libc.so.6 => /lib64/libc.so.6 (0x00007fab30d06000)
/lib64/ld-linux-x86-64.so.2 (0x00007fab31fbb000)
libz.so.1 => /lib64/libz.so.1 (0x00007fab30af0000)
then, this could be portage bug? I need your comment, portage team.
It looks like a portage bug. Please attach output of the following command:
grep openssl /var/log/emerge.log
As a workaround, this will probably make the problem go away: emerge --oneshot openssl:0.9.8 root@skare$ grep openssl /var/log/emerge.log 1350513491: >>> emerge (1 of 419) dev-libs/openssl-1.0.1c to / 1350513491: === (1 of 419) Cleaning (dev-libs/openssl-1.0.1c::/usr/portage/dev-libs/openssl/openssl-1.0.1c.ebuild) 1350513491: === (1 of 419) Compiling/Merging (dev-libs/openssl-1.0.1c::/usr/portage/dev-libs/openssl/openssl-1.0.1c.ebuild) 1350541774: >>> emerge (1 of 184) dev-python/pyopenssl-0.13 to / 1350541774: === (1 of 184) Cleaning (dev-python/pyopenssl-0.13::/usr/portage/dev-python/pyopenssl/pyopenssl-0.13.ebuild) 1350541774: === (1 of 184) Compiling/Merging (dev-python/pyopenssl-0.13::/usr/portage/dev-python/pyopenssl/pyopenssl-0.13.ebuild) 1355384387: *** emerge --jobs=9 --keep-going --verbose --load-average=19.0 --oneshot --deep app-admin/eclean-kernel:0 app-benchmarks/bootchart2:0 app-portage/gentoolkit:0 dev-java/java-config:2 dev-java/javatoolkit:0 dev-libs/boost:0 dev-python/argparse:0 dev-python/astng:0 dev-python/autopep8:0 dev-python/beaker:0 dev-python/beautifulsoup:4 dev-python/bsddb3:0 dev-python/cython:0 dev-python/dbus-python:0 dev-python/docutils:0 dev-python/feedparser:0 dev-python/ipy:0 dev-python/logilab-common:0 dev-python/lxml:0 dev-python/mako:0 dev-python/markupsafe:0 dev-python/numpy:0 dev-python/pep8:0 dev-python/pip:0 dev-python/pycairo:0 dev-python/pycrypto:0 dev-python/pygments:0 dev-python/pygobject:3 dev-python/pylint:0 dev-python/pymountboot:0 dev-python/pyopenssl:0 dev-python/PyQt4:0 dev-python/pyxdg:0 dev-python/setuptools:0 dev-python/sip:0/9 dev-python/unittest2:0 dev-python/winpdb:0 dev-util/gdbus-codegen:0 net-irc/xchat:2 net-misc/dropbox:0 net-zope/zope-fixers:0 net-zope/zope-interface:0 sys-apps/file:0 sys-devel/gdb:0 sys-libs/libcap-ng:0 1360004512: >>> emerge (7 of 15) dev-python/pyopenssl-0.13-r1 to / 1360004512: === (7 of 15) Cleaning (dev-python/pyopenssl-0.13-r1::/usr/portage/dev-python/pyopenssl/pyopenssl-0.13-r1.ebuild) 1360004512: === (7 of 15) Compiling/Merging (dev-python/pyopenssl-0.13-r1::/usr/portage/dev-python/pyopenssl/pyopenssl-0.13-r1.ebuild) 1360004521: === (7 of 15) Merging (dev-python/pyopenssl-0.13-r1::/usr/portage/dev-python/pyopenssl/pyopenssl-0.13-r1.ebuild) 1360004523: >>> AUTOCLEAN: dev-python/pyopenssl:0 1360004523: === Unmerging... (dev-python/pyopenssl-0.13) 1360004526: >>> unmerge success: dev-python/pyopenssl-0.13 1360004528: === (7 of 15) Post-Build Cleaning (dev-python/pyopenssl-0.13-r1::/usr/portage/dev-python/pyopenssl/pyopenssl-0.13-r1.ebuild) 1360004528: ::: completed emerge (7 of 15) dev-python/pyopenssl-0.13-r1 to / 1360268414: >>> emerge (4 of 90) dev-libs/openssl-0.9.8y to / 1360268414: === (4 of 90) Cleaning (dev-libs/openssl-0.9.8y::/usr/portage/dev-libs/openssl/openssl-0.9.8y.ebuild) 1360268414: === (4 of 90) Compiling/Merging (dev-libs/openssl-0.9.8y::/usr/portage/dev-libs/openssl/openssl-0.9.8y.ebuild) 1360268414: >>> emerge (5 of 90) dev-libs/openssl-1.0.1d to / 1360268414: === (5 of 90) Cleaning (dev-libs/openssl-1.0.1d::/usr/portage/dev-libs/openssl/openssl-1.0.1d.ebuild) 1360268414: === (5 of 90) Compiling/Merging (dev-libs/openssl-1.0.1d::/usr/portage/dev-libs/openssl/openssl-1.0.1d.ebuild) 1360268513: === (4 of 90) Merging (dev-libs/openssl-0.9.8y::/usr/portage/dev-libs/openssl/openssl-0.9.8y.ebuild) 1360268515: >>> AUTOCLEAN: dev-libs/openssl:0.9.8 1360268515: === Unmerging... (dev-libs/openssl-0.9.8x) 1360268518: >>> unmerge success: dev-libs/openssl-0.9.8x 1360268520: === (4 of 90) Post-Build Cleaning (dev-libs/openssl-0.9.8y::/usr/portage/dev-libs/openssl/openssl-0.9.8y.ebuild) 1360268520: ::: completed emerge (4 of 90) dev-libs/openssl-0.9.8y to / 1360268520: === (5 of 90) Merging (dev-libs/openssl-1.0.1d::/usr/portage/dev-libs/openssl/openssl-1.0.1d.ebuild) 1360268524: >>> AUTOCLEAN: dev-libs/openssl:0 1360268524: === Unmerging... (dev-libs/openssl-1.0.1c) 1360268527: >>> unmerge success: dev-libs/openssl-1.0.1c 1360268533: === (5 of 90) Post-Build Cleaning (dev-libs/openssl-1.0.1d::/usr/portage/dev-libs/openssl/openssl-1.0.1d.ebuild) 1360268533: ::: completed emerge (5 of 90) dev-libs/openssl-1.0.1d to / It seems I have a huge emerge.log ;) Comment #0 shows the libraries preserved for openssl-1.0.0a-r3, but this version does not show in emerge.log. Did you trim your emerge.log at some point in the past, so it no longer contains the merge of openssl-1.0.0a-r3? Has emerge been showing that these libraries are preserved for a very long time? Does /var/db/pkg/dev-libs/openssl-1.0.0a-r3 still exist? Does `emerge --oneshot openssl:0.9.8` make the problem go away? 1) Yes, I've probably deleted my emerge.log a couple of times in the past. Seems like the first entry is from 20th of June 2012, and this system has been up and running for at least 3 years. Probably even more. Might be 9 years :) I've migrated it a couple of times (to new disks, new hardware, etc), but not sure Is there a way to check that btw? 2) Yes, the issue has been present for quite some time, at least half a year. Might be a year even, I've just figured it would go away by itself at some point, so I didn't bother reporting it. It's such a small annoyance anyway, just figured I'd finally report it since it hadn't gone away. 3) I'll get back to you on the last point.. Yes, the issue seems to have been resolved. I did however seem to see that it was fixed just before I ran 'emerge -1 openssl-openssl:0.9.8', but I'm not sure. Sounds a bit too good to be true :) I suspect that the problem may have been fixed a long time ago. I guess we can just close it for now, since nobody has reported anything like this happening recently. |
