Summary: | sys-apps/portage - emerge: -k may trigger keyword check on installed packages | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Sebastian Luther (few) <SebastianLuther> |
Component: | Core | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | Keywords: | InVCS |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 210077, 288499 |
Description
Sebastian Luther (few)
2009-10-02 10:08:18 UTC
The inconsistency is fixed in r14472, while preserving the behavior required for bug 252167. There's another change in r14474, so KEYWORDS from ebuild in tree are used when checking for keyword mask on installed packages. This is fixed in 2.2_rc43. I think I hit the same bug with portage 2.1.6.13, is it possible ? I have a similar setup (binhost + client with --usepkgonly) and when a package which was built with ~arch goes stable, I must rebuild the package to allow the merge on the client. For example, right now I have gnome-light-2.26 built and merged on the binhost, but not merged on the client. When it will go stable (very soon), I think that I'll have to rebuild most of the packages to allow the merge. Each time it happens, the ebuild embedded in the binary package is keyworded ~arch. (In reply to comment #4) > I think I hit the same bug with portage 2.1.6.13, is it possible ? Yes, it's the same bug. This is fixed in 2.1.7. |