[gentoo-user] portage bug?
Hi, Would anybody, please, confirm the following behavior before I file a report with B.G.O? % emerge -C dev-perl/yaml % emerge --depclean -p [-snip-] Calculating dependencies... done! * Dependencies could not be completely resolved due to * the following required packages not being installed: * * dev-perl/yaml pulled in by: * perl-core/Module-Build-0.28.08 * * Have you forgotten to run `emerge --update --newuse --deep world` prior * to depclean? It may be necessary to manually uninstall packages that no longer * exist in the portage tree since it may not be possible to satisfy their * dependencies. Also, be aware of the --with-bdeps option that is documented * in `man emerge`. % emerge --update --newuse --deep world Calculating dependencies... done! Auto-cleaning packages... No outdated packages were found on your system. -- Best regards, Daniel
Re: [gentoo-user] portage bug?
Daniel Iliev schrieb am 18.05.2009 00:16: Hi, Would anybody, please, confirm the following behavior before I file a report with B.G.O? % emerge -C dev-perl/yaml % emerge --depclean -p [-snip-] Calculating dependencies... done! * Dependencies could not be completely resolved due to * the following required packages not being installed: * * dev-perl/yaml pulled in by: * perl-core/Module-Build-0.28.08 * * Have you forgotten to run `emerge --update --newuse --deep world` prior * to depclean? It may be necessary to manually uninstall packages that no longer * exist in the portage tree since it may not be possible to satisfy their * dependencies. Also, be aware of the --with-bdeps option that is documented * in `man emerge`. % emerge --update --newuse --deep world Calculating dependencies... done! Auto-cleaning packages... No outdated packages were found on your system. What is the problem with this behavior. You unmerge yaml but it is needed by Module-Build. What do you expect --depclean to do? If you run emerge --update --newuse --deep world yaml would be pulled in again as it is needed by Module-Build. --depclean only removes packages that have now reverse dependencies which is not the case here. -- Daniel Pielmeier signature.asc Description: OpenPGP digital signature
Re: [gentoo-user] portage bug?
From what I see, update newuse deep world is NOT pulling it back in. That's the bug. On May 17, 2009 6:26 PM, Daniel Pielmeier daniel.pielme...@googlemail.com wrote: Daniel Iliev schrieb am 18.05.2009 00:16: Hi,Would anybody, please, confirm the following behavior before I file a report with B What is the problem with this behavior. You unmerge yaml but it is needed by Module-Build. What do you expect --depclean to do? If you run emerge --update --newuse --deep world yaml would be pulled in again as it is needed by Module-Build. --depclean only removes packages that have now reverse dependencies which is not the case here. -- Daniel Pielmeier
Re: [gentoo-user] portage bug?
On Mon, 18 May 2009 01:16:24 +0300 Daniel Iliev daniel.il...@gmail.com wrote: Hi, Would anybody, please, confirm the following behavior before I file a report with B.G.O? % emerge -C dev-perl/yaml [...] % emerge --update --newuse --deep world Calculating dependencies... done! Auto-cleaning packages... No outdated packages were found on your system. Try to add --with-bdeps=y and I think you'll find the expected behavior.
Re: [gentoo-user] portage bug?
Jason Weisberger schrieb am 18.05.2009 00:30: From what I see, update newuse deep world is NOT pulling it back in. That's the bug. Okay i should read more carefully. Tried the --with-bdeps option? -- Daniel Pielmeier signature.asc Description: OpenPGP digital signature
Re: [gentoo-user] portage bug?
On Sun, 17 May 2009 18:30:47 -0400 Jason Weisberger jbdu...@gmail.com wrote: From what I see, update newuse deep world is NOT pulling it back in. That's the bug. Exactly. -- Best regards, Daniel
Re: [gentoo-user] portage bug?
Daniel Iliev wrote: Hi, Would anybody, please, confirm the following behavior before I file a report with B.G.O? % emerge -C dev-perl/yaml % emerge --depclean -p [-snip-] Calculating dependencies... done! * Dependencies could not be completely resolved due to * the following required packages not being installed: * * dev-perl/yaml pulled in by: * perl-core/Module-Build-0.28.08 * * Have you forgotten to run `emerge --update --newuse --deep world` prior * to depclean? It may be necessary to manually uninstall packages that no longer * exist in the portage tree since it may not be possible to satisfy their * dependencies. Also, be aware of the --with-bdeps option that is documented * in `man emerge`. % emerge --update --newuse --deep world Calculating dependencies... done! Auto-cleaning packages... No outdated packages were found on your system. It's not a bug, it's counterintuitive expected behavior. The pointer to the answer is buried in the error message: Also, be aware of the --with-bdeps option that is documented in `man emerge` In summary, dev-perl/yaml is a build dependency of Module-Build, and therefore not strictly required. By default, to be safe, depclean expects it to be there. Since Module-Build is already installed, however, by default emerge won't pull it in, because it shouldn't be necessary. Hence, the behavior you observe. You can file a bug if you wish, but make sure to do a full search, as there are misunderstandings of depclean all over b.g.o. Nick
