On 2/11/25 7:37 PM, Peter Humphrey wrote: >> If you aren't dealing with a broken mirror (bytemark was outright >> dropping some directories via rsync!) then it's just a matter of time. >> The binhost starts up at around 5am each day, runs for a bit, and >> publishes all packages for the day. I usually sync around noon. More >> details at >> >> https://wiki.gentoo.org/wiki/Gentoo_Binary_Host_Quickstart#I_used_to_have_a_ >> binary_package_but_not_anymore.2C_what_happened.3F > > I'm sure that works for you, but I'd have to wait until the afternoon to use > the same approach. ;-(
There is also ongoing work at https://bugs.gentoo.org/924772 to allow portage to detect the version of ::gentoo that was used to produce the binhost and artificially lock `emerge --sync` to that revision. The idea is that then, the packages available to emerge are always corresponding to what the binhost has up-to-date coverage for. Some building blocks for this are already implemented e.g. there is a header in the binhost that identifies the REPO_REVISIONS it supports. No client tooling yet, though you could probably hack together some kind of shell script if you're sufficiently motivated. Really though, I'm fine with emerge --sync and then emerge -puDU @world and just going away and coming back later IFF I notice it is asking to build packages from source that I don't expect to build from source. -- Eli Schwartz
OpenPGP_signature.asc
Description: OpenPGP digital signature
