We should forget about small efficiencies — Donald Knuth
5 Jun
When I try to upgrade my system, but I get the error below:
sojia src # emerge -uvDNp worldThese are the packages that I would merge, in order:
Calculating world dependencies …done!
[blocks B ] sys-apps/pam-login (is blocking sys-apps/shadow-4.0.15-r2)
[ebuild U ] sys-apps/shadow-4.0.15-r2 [4.0.14-r1] +nls -nousuid +pam (-selinux) -skey 1,264 kBTotal size of downloads: 1,264 kB
According to this page on http://forums.gentoo.org, the clue is in the shadow ChangeLog:
*shadow-4.0.14-r2 (12 Mar 2006)
12 Mar 2006; Diego Pettenò +files/login.defs,
+files/login.pamd, +shadow-4.0.14-r2.ebuild:
Merge pam-login back into shadow, as 4.x version was already being used;
this means that upgrade from 4.0.14-r1 requires to remove pam-login before.
To solve “emerge -C pam-login && emerge -1 shadow”, this is safe to do.
Update: Thanks Julian. It’s more safe to perform “emerge –buildpkgonly –nodeps shadow && emerge -C pam-login && emerge –usepkgonly shadow“
Popularity: 23% [?]
2 Responses for "[Gentoo] sys-apps/pam-login blocks sys-apps/shadow"
not really very safe to do! If emerge shadow fails you are locked out.
Better to go
emerge –buildpkgonly –nodeps shadow && emerge -C pam-login && emerge –usepkgonly shadow
as suggested in the thread linked above.
Julian, thanks :)
Leave a reply