Summary: | --getbinpkgonly asks for out-of-tree package | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Aniruddha Shankar <k> |
Component: | Unclassified | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | chrisa, esigra, rockoo |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 155723 | ||
Attachments: | root awaaz # emerge -uvDdG world output |
Description
Aniruddha Shankar
2005-04-04 03:42:17 UTC
Created attachment 55265 [details]
root awaaz # emerge -uvDdG world output
here's the output of emerge --update --verbose --debug --deep --getbinpkgonly
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. ;) *** Bug 118652 has been marked as a duplicate of this bug. *** I've been using getbinpkgonly on at least 2 different set of boxes in the last 2 years and my observations are that if portage trees (and use flags) are in sync, no problem of this sort occurs. Given the first comment here, it's not clear to me if the build box and the binary box are in sync wrt to portage tree state. This should be fixed since the binhost protocal is completely different since portage-2.1.6. However, you must point PORTAGE_BINHOST directly at $PKGIDIR, and not the All/ subdirectory. It's documented in `man make.conf`. 5 years.... jeez. |