Adam Williamson

The CI failure seems to be just because github no longer offers Python 2.x.

The `HOME=/tmp/whatever` is needed because without that buildah has a fit about `~/.config` not being owned by the current user, btw.

Ugh. I guess https://github.com/containers/buildah/issues/3259 is a complicating factor here?

Here's a kinda silly 'fix' for this, I guess... ``` diff --git a/cmd/buildah/main.go b/cmd/buildah/main.go index 524d87b32..df42a82f5 100644 --- a/cmd/buildah/main.go +++ b/cmd/buildah/main.go @@ -40,6 +40,7 @@ type globalFlags struct { MemoryProfile...

I guess we wouldn't want to let arbitrary mirrors just configure this themselves, as a bad mirror owner could maliciously include an IP in its block and force that IP...

My memory was that dnf always tries the first server in the list first for downloads beyond the initial repodata, but will do some kinda randomized round-robin thing for downloading...

So in a quick test (sorry, I went on PTO...) this seems to work. I constructed a metalink file thus, with no timestamp, file size or verification block: ``` http://fedora.mirror.iweb.com/linux/development/41/Everything/x86_64/os/repodata/repomd.xml...

So I tried this locally (I'm also a Fedora packager helping with the Python 3.13 rebuild), and one thing I note is that among all the messages from the failures...

I'll probably do a follow-up to extend the integration tests to cover more of the listing.py logic in the 'real world' as well, it seems like a wise precaution since...

Oooh, shiny, I didn't know that existed. You've gotta think some of those have to be stale. Still, if we want to reduce the impact, we have the option of...