Summary: | emerge --noreplace does not add package to world file | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Jeremy Rann <xerog1> |
Component: | Core - Interface (emerge) | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | minor | CC: | sep, simpledark |
Priority: | High | Keywords: | REGRESSION |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 181949 | ||
Attachments: | fix 2.1.2.x so --noreplace properly adds atoms to the world file |
Description
Jeremy Rann
2007-08-14 23:37:37 UTC
It's supposed to work. Can you try it with portage-2.1.3.5? There have been lots of changes in that code since 2.1.2.x and hopefully the bug has already been fixed. I upgraded to Portage 2.1.3.6, and it worked just fine. Then, just to be sure, I downgraded Portage back to the "stable" version (not ~x86), removed fluxbox from the world file manually, and tried it again - I was able to repeat the same behavior. So, indeed, this appears to be fixed by 2.1.3.6. Thanks! Great, thanks for testing that. *** Bug 190341 has been marked as a duplicate of this bug. *** Since the solution is to upgrade to an "unstable" version of portage, is it wise to consider the stabilization of the "fixed" version (2.1.3.6)? Thanks Created attachment 129273 [details, diff]
fix 2.1.2.x so --noreplace properly adds atoms to the world file
I think 2.1.3.7 is good for stabilization but I'm planning to wait about 2 more weeks before I request it. If some emergency comes up before then that requires a 2.1.2.13 release then this patch will be included.
*** Bug 191184 has been marked as a duplicate of this bug. *** |