Summary: | [PATCH] binhost remote metadata cache updates | ||
---|---|---|---|
Product: | Portage Development | Reporter: | André Luiz A. G. Carvalho <alcarvalho> |
Component: | Binary packages support | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | leho |
Priority: | High | Keywords: | InVCS |
Version: | 2.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 136244 | ||
Attachments: | Patch for the version 2.0.51.22-r1, applied to lib/portage/pym/getbinpkg.py |
Description
André Luiz A. G. Carvalho
2005-09-27 14:47:50 UTC
Created attachment 69377 [details]
Patch for the version 2.0.51.22-r1, applied to lib/portage/pym/getbinpkg.py
This is my proposed patch to it.
Thanks, this is in svn r4182. This has been released in 2.1.1_pre5. hi guys sorry for gravedigging, but i could use some help. im currently doing well with a binhost configuration over apache2 and https, but one thing bugs me. here's the scenario: * compile a mypackage on BINHOST with one set of USE flags * emerge -vagk mypackage on CLIENT * realize that the mypackage needs another set of USE flags, perhaps one removed or smth * recompile a mypackage on BINHOST with USE="-this that" or similar * PROBLEM: emerge -vagk mypackage on CLIENT is not able to see the new set of USE flags for mypackage! so far a really clumsy solution has been: * BINHOST: mv /usr/portage/packages/mypackage.tbz2 ~ * emerge -vagk mypackage on CLIENT, it doesnt find the package and suggest ebuild, ctrl+c * BINHOST: mv ~/mypackage.tbz2 /usr/portage/packages/ * emerge -vagk mypackage on CLIENT now sees the correct USE flag set is this normal, is there something i can do to make CLIENT detect the changed USE flag metadata immediately? my googling skills gave me this bug as the best related result i could find.. portage is 2.1.4.4 |