On 7/14/24 8:04 AM, Peter Humphrey wrote: > On Sunday, 14 July 2024 07:05:04 BST Eli Schwartz wrote: > >> As a matter of curiosity, why do you need to do any such thing at all? >> >> If there is no binary package available for portage yet, then portage >> will automatically build it from source instead, which is exactly what >> setting -getbinpkg for it would do. So why bother? > > It doesn't do that here. It tries to fetch the binary and bombs out when it > can't be found. Then I have to edit make.conf to update Gentoo, then put it > back as it was for the rest of the system.
This indicates that the Packages index on the binhost server doesn't correspond to the actual packages which are available; it is broadcasting availability of a new sys-apps/portage binpackage but that binpackage is not actually present. It has nothing to do with sys-apps/portage, since if there is a lack of synchronization here then the specific details of packages does not matter at all. It just happens, by coincidence, to trigger for you with the sys-apps/portage package. This is nominally speaking impossible to happen as it implies the binhost is simply broken altogether, which of course never happens in real life because we are all perfect, right? But actual broken binhosts aside, I'm guessing your real issue is using a DNS round robin load balancer or similar as your binhost url. You're getting delivered the Packages index from one server, but actual *.gpkg.tar requests are being serviced by a different load balancing machine, and the two aren't precisely in sync. There are some similar bugs being tracked: https://bugs.gentoo.org/464906 https://bugs.gentoo.org/831657 https://bugs.gentoo.org/890491 https://bugs.gentoo.org/865845 The default gentoobinhost shipped in stage3 tarballs is distfiles.gentoo.org, try changing it to a specific mirror and see if that helps? -- Eli Schwartz
OpenPGP_signature.asc
Description: OpenPGP digital signature
