| Summary: | portage: --upgradeonly adds --update | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Kyle Hankins <kyle.p.hankins> |
| Component: | Core | Assignee: | Portage team <dev-portage> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | CC: | Andreas.Klauer |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
*** Bug 31559 has been marked as a duplicate of this bug. *** It's old and was invalid: adding of --update does not cause the downgrade, missing ebuilds do that. |
Attempting to --upgradeonly automatically adds --update. This forces me to downgrade packages to lower version numbers (to the current stable release). Shouldn't upgradeonly "only" "upgrade"? In order to upgrade and keep my unstable packages, I must --update and then reinstall. the text is as follows: flux@xanadu portage $ sudo emerge -Up world >>> --upgradeonly implies --update... adding --update to options. These are the packages that I would merge, in order: Calculating world dependencies ...done! [ebuild U ] sys-devel/gettext-0.12.1 [0.11.5-r1] [ebuild U ] sys-fs/e2fsprogs-1.34 [1.33] [ebuild U ] app-text/gtkspell-2.0.4 [2.0.2] [ebuild UD] net-im/gaim-0.72-r1 [0.74] /**NOTE DOWNGRADE**/ [ebuild U ] net-p2p/bittorrent-3.3.0 [3.2.1b-r4] [ebuild U ] media-libs/libsdl-1.2.6-r3 [1.2.6-r2] [ebuild U ] dev-util/cvs-1.11.11 [1.11.10]