When calling emerge -G, it creates/updates a local cache metadata at /var/cache/edb/remote_metadata.pickle. The problem is: if any package was removed from server, it simply ignores this and keeps it in cache. If we try to install that package, emerge thinks it exists and tries to install, but fails at the time of download, of course with 404 error. The patch that I made corrects this in a straight forward way by removing from the local cache, any package removed from server. The patch is for version 2.0.51.22-r1 of portage.
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