I am uncertain whether the Portage update caused this or whether these "blocked packages" are the result of the recent "emerge rsync". Anyway, I get these warnings when doing a "emerge -pvu world": [blocks B ] app-text/xhtml1 (from pkg dev-util/gtk-doc-1.1) [blocks B ] sys-apps/modutils (from pkg sys-apps/module-init-tools-3.0-r2) [blocks B ] sys-apps/module-init-tools (from pkg sys-apps/modutils-2.4.25) [blocks B ] dev-util/gtk-doc (from pkg app-text/xhtml1-20020801-r1) I understand what these mean, but I don't understand how to fix it. Messing with the modutils in particular sounds dangerous to me. Is there any documented proceduce how to resolve these conficts? Reproducible: Always Steps to Reproduce: 1. 2. 3. Portage 2.0.51-r2 (default-x86-2004.2, gcc-3.3.4, glibc-2.3.4.20040808-r1, 2.6.8-gentoo-r10 i686) ================================================================= System uname: 2.6.8-gentoo-r10 i686 AMD Athlon(tm) Processor Gentoo Base System version 1.4.16 Autoconf: sys-devel/autoconf-2.59-r5 Automake: sys-devel/automake-1.8.5-r1 Binutils: sys-devel/binutils-2.14.90.0.8-r1 Headers: sys-kernel/linux-headers-2.4.21-r1 Libtools: sys-devel/libtool-1.5.2-r5 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-mcpu=athlon -O3 -pipe" CHOST="i686-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-mcpu=athlon -O3 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache distlocks notitles sandbox strict userpriv" GENTOO_MIRRORS="http://gentoo.inode.at/" MAKEOPTS="-j1" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.de.gentoo.org/gentoo-portage" USE="3dnow X Xaw3d altcolors apm avi berkdb bitmap-fonts bonobo caps crypt curl dga divx4linux doc dvd dvdr dvdread emacs encode ethereal extensions f77 foomaticdb gcl gdbm gif gtk gtk2 gtkhtml guile hardened idea imlib ipv6 javascript jpeg leim libg++ libwww lzw-tiff mad mbox mikmod milter mmx moznocompose moznoirc moznomail moznoxft mpeg ncurses opengl oss pam pdflib perl plotutils png python qt quicktime rage128 readline spell ssl tetex threads tiff truetype unicode x86 xml xml2 xv zlib"
The modutils <-> module-init-tools issue can easily be solved by removing one of the packages. If one is using a 2.4 series Kernel, she/he might want to keep modutils and purge module-init-tools. Otherwise if someone is using a 2.6 series Kernel (which you seem to use) he/she might want to keep module-init-tools and remove modutils. modutils/module-init-tools are the utilities used to deal with Linux Kernel modules.
Thanks for the information! I've removed modutils and got those QA warnings in the process: QA Notice: ECLASS 'flag-o-matic' inherited illegally in sys-apps/modutils-2.4.25 QA Notice: ECLASS 'eutils' inherited illegally in sys-apps/modutils-2.4.25 QA Notice: ECLASS 'toolchain-funcs' inherited illegally in sys-apps/modutils-2.4.25
Also see http://forums.gentoo.org/viewtopic.php?t=241017
Forgot to say somthing about the other issue with xhtml1 <-> gtk-doc According to the CVS log of xhtml1-20020801-r1.ebuild [1] there is an issue with these two packages installed altogether. [1] http://www.gentoo.org/cgi-bin/viewcvs.cgi/app-text/xhtml1/xhtml1-20020801-r1.ebuild
Peter: According to the forum entry Jakub pointed to, re-emerging module-init-tools would be a good idea, to make sure it works properly.
Just tried it: removed modutils, remerged init-tools, rebooted. Worked like a charm. Thanks for the help. Any idea what I should do about the xhtml/gtk-doc conflict? I don't really understand how a DTD could block another package, actually. Why would a bunch of text files disturb gtk-doc?
Peter, maybe it would be better to submit a separate bug for that, b/c modutils and module-init-tools conflict has been already solved, see e.g. in Bug 68354.
I'll submit a new PR for the xhtml/gtk-doc thing. Thanks for your help!
not a portage bug
