Summary: | portage-2.1.12.2: emerge -K pulls wrong ebuild | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Dyweni <j6yNRdsH5Fc3> |
Component: | Core | Assignee: | Portage team <dev-portage> |
Status: | UNCONFIRMED --- | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Dyweni
2013-08-19 21:49:02 UTC
You can use this command to check the repository of the binary package: portageq metadata / binary dev-python/pygobject-2.28.6-r53 repository You will probably find that it reports that the repository is 'gentoo'. (In reply to LeeL from comment #0) > Actual Results: > The 'emerge -Kpv' shows it will pull from the "gentoo" repository, not the > "x-portage" repository. If you have a binary package from the "gentoo" repository (as suggested in comment #1), then wouldn't you expect it to pull that in? |