mbar wrote:Also helped me. Marking solved.

Just a note to add that the method can be applied on a running system for those with servers and no access to datacenter.

Regards,

the only 2 problematic packages which depends on sys-apps/util-linux are udev and lvm it the OP's case.
imho, there is not other alternative to fix this.

but I offer another way, run the livecd, mount the distro, chroot to it and remove sys-apps/util-linux.
update sys-apps/sysvinit which in turn ...

the only 2 problematic packages which depends on sys-apps/util-linux are udev and lvm it the OP's case.
imho, there is not other alternative to fix this.

but I offer another way, run the livecd, mount the distro, chroot to it and remove sys-apps/util-linux.
update sys-apps/sysvinit which in turn ...

Yes guys,
it will definitely break your system!

So try other workarounds for that.

Regards, Andy.

And what are those workarounds ? Because last sysvinit could not be installed because of last util-linux blocking, and last util-linux could not be installed because of last sysvinit blocking. So ...

what is the current block msg?

This is what happen :

apu sysvinit # emerge -upv world

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild NS ] sys-kernel/gentoo-sources-3.0.4 [3.0.3] USE="-build -deblob -symlink" 127 kB
[ebuild U ] sys-apps/util ...

running a system in ~ is not recommended, use package.keywords instead.

in order for this to work (assuming you either use ~amd64 or have both sys-apps/sysvinit and sys-apps/util-linux in packages.keywords, notice that no * is in use), you must make sure that there are no such entries in package ...

actually is does, go to /etc/portage/package.keywords and look for the util-linux entry, remove the * and thats it.

Even without the entry in package.keywords, I end in the same blocking loop. It is what I said in my previous post : without or with entry in package.keywords, util-linux is blocked ...

actually is does, go to /etc/portage/package.keywords and look for the util-linux entry, remove the * and thats it.

Even without the entry in package.keywords, I end in the same blocking loop. It is what I said in my previous post : without or with entry in package.keywords, util-linux is blocked ...

And what are those workarounds ? Because last sysvinit could not be installed because of last util-linux blocking, and last util-linux could not be installed because of last sysvinit blocking. So if there is some workaround, could you please tell us what they are ?


There are no blocks anymore ...

Yes guys,
it will definitely break your system!

So try other workarounds for that.

Regards, Andy.

And what are those workarounds ? Because last sysvinit could not be installed because of last util-linux blocking, and last util-linux could not be installed because of last sysvinit blocking. So ...