On 17/04/12 18:34, Nikos Chantziaras wrote:
On 17/04/12 18:10, Alan McKinnon wrote:
On Tue, 17 Apr 2012 18:01:43 +0300
Nikos Chantziaras<rea...@gmail.com> wrote:
emerge --depclean seems to have bugged out for me:
* Dependencies could not be completely resolved due to
* the following required packages not being installed:
*
* =dev-libs/openssl-0.9.8* pulled in by:
* app-emulation/vmware-workstation-8.0.2.591240
*
* dev-libs/openssl:0.9.8 pulled in by:
* www-client/google-chrome-19.0.1084.24_beta131971
It says to do a "emerge --update --newuse --deep --with-bdeps=y
@world". Which is what I just did to begin with (and running it again
doesn't result in anything getting emerged.)
It also says:
* Also, note that it may be necessary to manually uninstall
* packages that no longer exist in the portage tree, since it may
* not be possible to satisfy their dependencies.
However, dev-libs/openssl is installed and seems to be in the tree:
$ eix -e dev-libs/openssl
[I] dev-libs/openssl
Available versions:
(0.9.8) 0.9.8r (~)0.9.8s 0.9.8s-r1 0.9.8t 0.9.8u
(0) 1.0.0d 1.0.0e (~)1.0.0e-r1 (~)1.0.0f 1.0.0f-r1
1.0.0g 1.0.0h **1.0.1
{{bindist gmp kerberos rfc3779 sse2 static-libs test vanilla
zlib}} Installed versions: 0.9.8u(0.9.8)(22:32:12 12/03/12)(sse2
zlib -bindist -gmp -kerberos -test) 1.0.0h(22:33:20 12/03/12)(sse2
zlib -bindist -gmp -kerberos -rfc3779 -static-libs -test)
I think you should file a bug against www-client/google-chrome
It wants the exact version dev-libs/openssl:0.9.8 but the oldest in
portage is dev-libs/openssl:0.9.8r
Chances are the dev simply left off the version suffix by accident
That can't be it. There's a wildcard at the end:
=dev-libs/openssl-0.9.8*
which should match 0.9.8u.
No wait, that's vmware. The chrome ebuild pulls a slot:
dev-libs/openssl:0.9.8
This also matches correctly. The 0.9.8 slot matches all those versions.
So no problem with that either.
