Summary: | app-portage/gentoolkit- 0.3.0_rc10-1 app-revdep-rebuild doesn't find broken packages | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Attila Stehr <as.gentoo> |
Component: | Tools | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | SebastianLuther |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | Other | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | example revdep-rebuild VS revdep-rebuild --library <lib_name> |
Description
Attila Stehr
2010-07-07 17:59:57 UTC
Created attachment 237927 [details]
example revdep-rebuild VS revdep-rebuild --library <lib_name>
Please re-read the part of then revdep-rebuild man page about the --library option. If everything is ok and the result of running revdep-rebuild (whis is 'nothing to do') is right, why is portage telling me the following after emerging evolution-data-server? Old versions of installed libraries _were_detected_ on your system. * In order to avoid breaking packages that depend on these old libs, * the libraries are not being removed. You need to run revdep-rebuild * in order to remove these old dependencies. If you do not have this * helper program, simply emerge the 'gentoolkit' package. * * # revdep-rebuild --library libedataserver-1.2.so.11 Shouldn't (just) 'revdep-rebuild' discover that packages using libedataserver (which was updated) need to be rebuilt? (In reply to comment #3) > Shouldn't (just) 'revdep-rebuild' discover that packages using libedataserver > (which was updated) need to be rebuilt? > No, because revdep-rebuild only detects cases where a binary/library is broken because a library it links against is missing. What emerge tells you is that libedataserver-1.2.so.11 has not been removed (even if the new version doesn't install it) to keep its consumers working. That's why revdep-rebuild wouldn't detect the consumers as broken. Ok, I apologise! 'man revdep-rebuild' does exactly state what you wrote. Now, is there a tool which checks if packages need to / should be rebuild due to updated libraries/dependencies? For now I use grep on the portage log files to find out which 'revdep-rebuild --library <...>' needs to be executed but I guess not everyone sets PORT_LOGDIR so finding out what has to be done would be difficult then, wouldn't it? I - and maybe other users too - would really be thankful if something 'automatic' would exist. emerge prints the warnings right after it finished. People are expected to read them or to use some logging facility and read the logs. |