Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 458306 - revdep-rebuild exit code can indicate success even if there was a failure
Summary: revdep-rebuild exit code can indicate success even if there was a failure
Status: RESOLVED DUPLICATE of bug 351054
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Tools (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Portage Tools Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-19 15:16 UTC by Robert Forsman
Modified: 2013-02-20 14:27 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Forsman 2013-02-19 15:16:28 UTC 
Several packages have post-installation messages of the form

revdep-rebuild --library something-obsolete.so && rm something-obsolete.so

Unfortunately, revdep-rebuild sometimes exits with a success status even when things go horribly wrong.  In my case I was rebuilding packages depending on libgmp.so, one of which is gcc.  When /usr filled up, the rebuild malfunctioned, revdep-rebuild indicated success, and libgmp was deleted, crippling the system compiler and probably several other applications.

To recover I had to cross-compile gcc on another computer and install the resulting binary package.


Reproducible: Always

Steps to Reproduce:
1. have an almost-full /usr
2. revdep-rebuild something
3. echo $?
Actual Results:  
revdep-rebuild indicated success even though the ebuild died in the middle.

Expected Results:  
revdep-rebuild should have indicated a failure.
Comment 1 Robert Forsman 2013-02-19 16:13:39 UTC 
revdep-rebuild is from gentoolkit-0.3.0.4
Comment 2 Jeroen Roovers (RETIRED) gentoo-dev 2013-02-20 14:27:50 UTC 
(In reply to comment #1)
> revdep-rebuild is from gentoolkit-0.3.0.4

You may want to upgrade to 0.3.0.7.

*** This bug has been marked as a duplicate of bug 351054 ***