Summary: | getbinpkgonly does not find available binary file. | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Aniruddha Shankar <k> |
Component: | Unclassified | Assignee: | Portage team <dev-portage> |
Status: | VERIFIED NEEDINFO | ||
Severity: | major | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Aniruddha Shankar
2005-03-22 01:50:57 UTC
after copying the damn binpkg over to the localmachine's /usr/portage/packages/All/, I did emerge -v --usepkgonly mozilla-firefox Calculating dependencies !!! There are no packages available to satisfy: "mozilla-firefox" !!! Either add a suitable binary package or compile from an ebuild. Up for posting the binpkg somewhere so it can be checked over? (wild guess) 13:10 <Kream> the way that I've been solving problems is this: if --getbinpkgonly screws up, make sure all /usr/local/portage, USE flags, /etc/portage/package.keywords are IDENTICAL... then i try to delete the remote metadata files (two of em)... then I try --getbinpkg ... then I resort to manually copying the binaries into /usr/portage/packages/All .... then a --usepkgonly usually works. By then I've been swearing for a long time.. :) This problem was fixed by method 3... spoken to ferringb on #gentoo-portage at Thu May 12 07:47:37 UTC 2005 ... the logs should shed more light on the matter... basically we came to the conclusion that the binpkg flakiness is due to some underlying issues with the binpkg code.. I will be starting a blog to document my experiments with binpkg cheers :) Reopening... If we closed every bug that is planned on being fixed in the next major version, we'd have no open bugs. ;) Closing this again.. There's no useful information here, unfortunately. Closing due to old age |