Catalin Trifu schreef: > Hi, > > emerge -pvDu shows this: > > Calculating world dependencies ...done! [blocks B ] > dev-php/PEAR-Archive_Tar (is blocking dev-php/PEAR-PEAR-1.3.6-r2) > [blocks B ] dev-php/PEAR-Console_Getopt (is blocking > dev-php/PEAR-PEAR-1.3.6-r2) [blocks B ] dev-php/PEAR-XML_RPC (is > blocking dev-php/PEAR-PEAR-1.3.6-r2) [blocks B ] > <dev-php/PEAR-PEAR-1.3.6-r2 (is blocking dev-php/PEAR-PEAR-1.3.6-r2) > > If this is not strage (the last line at least) then I don't know what > is :) Any ideas how to solve it ? > > Catalin >
If you look at the dependencies of PEAR-PEAR-1.3.6-r2, you will see that they are reversed from the dependencies of 1.3.5; (from www.gentoo-portage.com) Runtime Dependencies PEAR-PEAR-1.3.6-r2 ! dev-lang/php - cgi ! dev-lang/php - dev-lang/php ! dev-php/mod_php - ! dev-php/PEAR-PEAR - 1.3.6-r2 ! dev-php/PEAR - Archive_Tar ! dev-php/PEAR - Console_Getopt ! dev-php/PEAR - XML_RPC PEAR-PEAR-1.3.5 dev-lang/php >= dev-php/PEAR-Archive_Tar - 1.1 >= dev-php/PEAR-Console_Getopt - 1.2 >= dev-php/PEAR-XML_RPC - 1.0.4 virtual/php The reason for this can be found in the ChangeLog 09 Jan 2006; Sebastian Bergmann <[EMAIL PROTECTED]> PEAR-PEAR-1.3.6-r2.ebuild: Block packages that this package bundles. So the moduleblocks are blocked because they will be installed by PEAR-PEAR-1.3.6-r2 The last line is not strange at all-- you perhaps missed the "<" line in the blocker. What I see in this output <dev-php/PEAR-PEAR-1.3.6-r2 (is blocking dev-php/PEAR-PEAR-1.3.6-r2) is saying that some version of PEAR-PEAR less than 1.3.6-r2 is blocking the installation of 1.3.6-r2. According (again) to the Changelog: 09 Jan 2006; Luca Longinotti <[EMAIL PROTECTED]> files/pear.conf, PEAR-PEAR-1.3.6-r2.ebuild: Change pear.conf to auto-sobstitute the php binary's path, plus some other cosmetical fixes. Fix pear USE flag requirement, not really needed. Jan 2006; Sebastian Bergmann <[EMAIL PROTECTED]> +files/pear.conf, PEAR-PEAR-1.3.6-r2.ebuild: Install /etc/pear.conf. There are some serious changes in this package that require a clean installation, as if the package was never installed. But you know the drill; remove blocking packages, try your emerge again. Usually this works itself out, because working itself out is Portage's main job. No bugs on b.g.o (yet) to indicate the process is failing in this case. HTH, Holly -- gentoo-user@gentoo.org mailing list