Can anybody at least confirm this is not correct behavior? Suggest how to
troubleshoot this further? As best as I can tell my profile is
ok, 'hardened/x86' and portage doesn't want to update itself...
I don't understand why my currently installed udev wants the currently
installed baselayout
On Mon, 20 Apr 2009 13:00:40 -0600
darren kirby bulli...@badcomputer.org wrote:
Can anybody at least confirm this is not correct behavior? Suggest how to
troubleshoot this further? As best as I can tell my profile is
ok, 'hardened/x86' and portage doesn't want to update itself...
I'd
quoth the Mike Kazantsev:
...or, you can accept mask and just downgrade udev (adding later,
incompatible versions to package.mask: =sys-fs/udev-...).
I'd suggest issuing this command to see which one will suit your system:
Ok, I found the version of baselayout was masked for 'corruption',
K, no idea what's going on. This is a hardened server, just synced a moment
ago:
-
# emerge -puD system
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild NS ] sys-devel/libtool-1.3.5 [1.5.26] 527 kB [0]
[ebuild UD]
4 matches
Mail list logo
