On 13/07/2024 14.50, Peter Humphrey wrote:
Where I live, updates to portage itself usually take longer to appear as a
binary package than as source, so I can't 'getbinpkg'. Therefore I've set:
The main issue is that you aren't syncing portage towards the bin
server, which makes things out of sync and those you will be building a
lot of the packages instead of fetching the binary files when they are
built. One way to come around this issue is that when you sync your
portage, wait a day before you check what files to update, this way the
binary packages should have been built, but sure it's a pita.
The proper solution had been that you could sync portage against the
binhost and that only if the binhost do have two portage that is always
in par with the packages that has been built. I have my own experience
of this issue from the time when I had multiple machines at home running
Gentoo and I had a build environment that built packages for me. I had
to setup two copies of portage on the build machine, one was the one it
synced and built against, and then there was the portage version that
was provided to the clients in the LAN (sadly this has a complication
for the clients using git instead of rsync), this was only updated after
a successful build. All the client synced portage against the binhost.
If they didn't, then I had the issue as you describe and I had
discussion about this on the gentoo irc channels, but as back then few
people used binhosts so they didn't understand the issue and those
portage don't support to do what you want to do, to filter out new
ebuilds that don't have a binary package at the binhost, just wait
another 20 years and then maybe.
--
//Aho
