On Thu, Jan 15, 2009 at 10:30 PM, Neil Bothwick <[email protected]> wrote: > On Thu, 15 Jan 2009 13:24:33 -0800, Mark Knecht wrote: > >> Anyway, it is OK to remove this block and then proceed with the >> system emerge, correct? >> >> Calculating dependencies... done! >> [ebuild U ] sys-devel/gnuconfig-20080123 [20070724] 0 kB [?=>0] >> [ebuild U ] app-arch/lzma-utils-4.32.7 [4.32.5] USE="-nocxx%" 0 kB >> [?=>0] <SNIP> >> [ebuild N ] sys-apps/man-pages-posix-2003a 0 kB [0] >> [ebuild N ] sys-libs/e2fsprogs-libs-1.41.3-r1 USE="nls" 0 kB [0] >> [ebuild U ] sys-apps/util-linux-2.14.1 [2.13.1] USE="crypt nls >> unicode -loop-aes -old-linux (-selinux) -slang (-uclibc)" 0 kB [0] >> [ebuild U ] sys-fs/e2fsprogs-1.41.3 [1.40.4] USE="nls (-static%)" 0 >> kB [0] [blocks b ] <sys-fs/e2fsprogs-1.41 ("<sys-fs/e2fsprogs-1.41" >> is blocking sys-libs/e2fsprogs-libs-1.41.3-r1) > > You don't need to remove anything, just let portage handle the block for > you. Blocks marked with a b (instead of a B) can be handled by recent > portage releases. > Hi,
are you sure that his works in this case? This blocking bug was some time before the new Portage went stable and back then you had to resolve it by hand. So if you're unlucky you have to resolve it by hand, but there's an explanation in bugzilla. Geralt.
