When I run revdep-rebuild -p, I get:
Code: Select all
Assigning files to ebuilds... done.
(/root/.revdep-rebuild.4_ebuilds)
Evaluating package order... done.
(/root/.revdep-rebuild.5_order)
All prepared. Starting rebuild...
emerge --oneshot -p =app-misc/cbtracker-1.0b
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild R ] app-misc/cbtracker-1.0b
Now you can remove -p (or --pretend) from arguments and re-run revdep-rebuild.
Code: Select all
# revdep-rebuild
Configuring search environment for revdep-rebuild
Checking reverse dependencies...
Packages containing binaries and libraries broken by a package update
will be emerged.
Collecting system binaries and libraries... using existing /root/.revdep-rebuild.1_files.
Collecting complete LD_LIBRARY_PATH... using existing /root/.revdep-rebuild.2_ldpath.
Checking dynamic linking consistency... using existing /root/.revdep-rebuild.3_rebuild.
Assigning files to ebuilds... using existing /root/.revdep-rebuild.4_ebuilds.
Evaluating package order... using existing /root/.revdep-rebuild.5_order.
All prepared. Starting rebuild...
emerge --oneshot =app-misc/cbtracker-1.0b
blah
blah
blah
>>> Original instance of package unmerged safely.
>>> app-misc/cbtracker-1.0b merged.
>>> No packages selected for removal by clean
>>> Auto-cleaning packages...
>>> No outdated packages were found on your system.
* GNU info directory index is up-to-date.
Build finished correctly. Removing temporary files...
You can re-run revdep-rebuild to verify that all libraries and binaries
are fixed. If some inconsistency remains, it can be orphaned file, deep
dependency, binary package or specially evaluated library.
Code: Select all
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild R ] app-misc/cbtracker-1.0b
Now you can remove -p (or --pretend) from arguments and re-run revdep-rebuild.
Thanks!
