Summary: | revdep-rebuild attitude about package sorting | ||
---|---|---|---|
Product: | Portage Development | Reporter: | crusaderky |
Component: | Enhancement/Feature Requests | Assignee: | Portage Tools Team <tools-portage> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | fuzzyray |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 62644 | ||
Bug Blocks: |
Description
crusaderky
2004-09-05 02:14:22 UTC
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 *** |