| Summary: | Unmerge is acting weirdly in 1.9.10 (and 1.9.9) | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Karl Trygve Kalleberg (RETIRED) <karltk> |
| Component: | Unclassified | Assignee: | Daniel Robbins (RETIRED) <drobbins> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | karltk |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
OK, both these bugs are now fixed and will appear in 1.9.11 |
[#130 /usr/portage] emerge unmerge /var/db/pkg/media-libs/libpng-1.0.12/libpng-1.0.12.ebuild Traceback (most recent call last): File "/usr/sbin/emerge", line 1179, in ? if 1==unmerge(myaction, myfiles): File "/usr/sbin/emerge", line 700, in unmerge absx=abspath[x] NameError: global name 'abspath' is not defined [#131 /usr/portage] emerge unmerge libpng-1.0.12 !!! Couldn't find match for libpng-1.0.12 >>> unmerge: No packages selected for removal. [#132 /usr/portage] emerge unmerge libpng libpng selected: 1.0.12 1.2.1-r1 protected: none omitted: none >>> Packages in red are slated for removal. >>> Packages in green will not be removed. >>> Waiting 5 seconds before starting unmerge. >>> (Control-C to abort)... >>> Unmerging in: 5 !!! Portage interrupted by SIGINT; exiting. zsh: killed emerge unmerge libpng [#133 /usr/portage] While the docs say gives the example: sys-devel/binutils-2.11.90.0.7 matches binutils-2.11.90.0.7 In practice, the only allowed syntax to unmerge libpng-1.0.12 is emerge unmerge =libpng-1.0.12 So either the syntax parser should be fixed, or the docs should be corrected. Also, the abspath crash is ugly, but not in any way critical.