Summary: | sys-apps/portage-2.1.6.11: emerge -p --depclean exits with 0 even when it fails | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Pacho Ramos <pacho> |
Component: | Core - Interface (emerge) | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Pacho Ramos
![]() *** This bug has been marked as a duplicate of bug 266861 *** I already knew the "perl" problem, but this is simply for exit status when emerge fails, that it "0" when it should be other one Thanks This is fixed in =sys-apps/portage-2.1.6.13. I don't think this is fixed because afaik action_depclean() always returns success. emerge --depclean * Always study the list of packages to be cleaned for any obvious * mistakes. Packages that are part of the world set will always * be kept. They can be manually added to this set with * `emerge --noreplace <atom>`. Packages that are listed in * package.provided (see portage(5)) will be removed by * depclean, even if they are part of the world set. * * As a safety measure, depclean will not remove any packages * unless *all* required dependencies have been resolved. As a * consequence, it is often necessary to run `emerge --update * --newuse --deep @system @world` prior to depclean. Calculating dependencies... done! * Dependencies could not be completely resolved due to * the following required packages not being installed: * * >=virtual/perl-IO-Compress-Bzip2-2.012 pulled in by: * perl-core/Archive-Tar-1.40 * * Have you forgotten to run `emerge --update --newuse --deep @system @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`. fewslaptop mingramm # echo $? 1 On line 14357, unresolved_deps() is called. If this fails, action_depclean() returns 1. (In reply to comment #5) > On line 14357, unresolved_deps() is called. If this fails, action_depclean() > returns 1. Oh, that's right. Thanks. Yes, I confirm the fix as I have see it today and now it behaved properly :-) Thanks |