Summary: | emerge -k/--usepkg visibility support (package.mask, etc...) for binary packages | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Martin Hierling <martin.hierling> |
Component: | Core - Interface (emerge) | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | kenyon, robbat2 |
Priority: | High | Keywords: | InVCS |
Version: | 2.1 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 155723, 200044 |
Description
Martin Hierling
2006-10-02 01:50:26 UTC
It seems to mask correctly for me. Are you sure that you don't have mysql in /etc/portage/package.unmask also? Try this please: grep -r mysql /etc/portage Oh, I know why. It's because you don't have a matching mysql-4.1.20.ebuild in the tree, so emerge is assuming that it's not masked. I'll see what I can do... sorry for needing so long: # grep -r mysql /etc/portage /etc/portage/package.mask:>=dev-db/mysql-4.0.99 but you have figured it out. So any fixes upcoming in portage? regards Martin The masking check that we use for binary packages is a hack that uses the portage tree's visibility check. We'll have to implement a new visibility check that works correctly for binary and installed packages. Hopefully it will get fixed soon, but there are lots of competing bugs that need attention. *** Bug 159368 has been marked as a duplicate of this bug. *** *** Bug 171280 has been marked as a duplicate of this bug. *** This is fixed in 2.1.4_rc11. |