Summary: | sys-apps/portage-2.1.6.11: newuse and binpkg do not work together | ||
---|---|---|---|
Product: | Portage Development | Reporter: | sf <sf-gentoo> |
Component: | Core - Interface (emerge) | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | Keywords: | InVCS |
Priority: | High | ||
Version: | 2.1 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 210077, 268228 | ||
Attachments: |
emerge --info
fix USE comparison for binary packages |
Description
sf
2009-04-30 11:03:21 UTC
Created attachment 189946 [details]
emerge --info
I've seen this before. It's a quirk in the USE calculation, related to IUSE defaults, that can be solved by rebuilding the package so that it contains the latest IUSE. I'll fix it to so that the IUSE of the binary package do not affect the calculation. Created attachment 189995 [details, diff]
fix USE comparison for binary packages
I think this patch fixes the specific issue that you're reporting. If the patch is saved as /tmp/newuse.patch, then it can be applied as follows:
patch /usr/lib/portage/pym/_emerge/__init__.py /tmp/newuse.patch
This is fixed in 2.1.6.12. |