Sometimes (actually, several times) revdep-rebuild will fail to sort the packages building order and will simply say "sorting failed; emerging in random order". This can prove catastrophical, since if package B depends on A and A is broken, if B is recompiled before A the compilation will fail. Suggested attitude: a)propose a list of packages that caused the "sorting failed" error. Currently, in most cases the user can only guess what happened. b)place such packages at the end of the build list and correctly sort the other packages. This will minimize errors.
If you can give me some real world examples, I can try to duplicate and see what is causing the issue. Without being able to see the problem occur, I'm not sure that I can do anything to make revdep-rebuild smarter.
it happens whenever the user must rebuild a package whose exact version is no longer in portage. Needless to say, this is quite normal.
Using the --package-names option should be able to handle this situation. The exception will be when a package has been completely removed from the tree.
(In reply to comment #2) > it happens whenever the user must rebuild a package whose exact version is no longer in portage. Needless to say, this is quite normal. Dupe. *** This bug has been marked as a duplicate of 22161 ***
