| Summary: | updates for portage advertised even if there is nothing to update | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Alex Riesen <fork0> |
| Component: | Unclassified | Assignee: | Portage team <dev-portage> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
Does it want to downgrade portage if you set ACCEPT_KEYWORDS="x86" ? Yes. It clears the issue up, I think :) $ ACCEPT_KEYWORDS="x86" emerge -p portage These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild UD] sys-apps/portage-2.0.49-r3 [2.0.49-r4] Nick, maybe we should change the check as normally there is no reason to downgrade portage (and the message is misleading). Marking this as invalid for now. |
I got the message after emerge sync: * An update to portage is available. It is _highly_ recommended * that you update portage now, before any other packages are updated. * Please do so and then update ALL of your configuration files. But, when I tried to update it: $ ACCEPT_KEYWORDS="~x86" USE="-java -esd -cups" emerge -p portage These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild R ] sys-apps/portage-2.0.49-r4 Note the "R". No updates, as it seems. Consequent emerge -Up portage produced: >>> --upgradeonly implies --update... adding --update to options. These are the packages that I would merge, in order: Calculating dependencies ...done! That is - nothing. Reproducible: Sometimes Steps to Reproduce: