In the context of archlinux/infrastructure#531 we are currently thinking about whether packages appearing on the Archive with some delay could cause issues for the repro infrastructure 🤔
As far as we understand it right now the packages are exclusively synced from the archive:
|
ARCHIVEURL="${ARCH_ARCHIVE_CACHE:-https://archive.archlinux.org/packages}" |
|
readonly archive_url="${ARCH_ARCHIVE_CACHE:-https://archive.archlinux.org/packages}" |
In the new setup that could cause some issues if the rebuilder picks up the package faster than it is synced to the archive. So we wanted to ask about input to this, would it be good just to add a fallback to the T0 or geo mirrors? Or some kind of retry mechanism..? 🤔
In the context of archlinux/infrastructure#531 we are currently thinking about whether packages appearing on the Archive with some delay could cause issues for the repro infrastructure 🤔
As far as we understand it right now the packages are exclusively synced from the archive:
archlinux-repro/repro.in
Line 24 in 6e8cee9
archlinux-repro/buildinfo
Line 72 in 6e8cee9
In the new setup that could cause some issues if the rebuilder picks up the package faster than it is synced to the archive. So we wanted to ask about input to this, would it be good just to add a fallback to the T0 or geo mirrors? Or some kind of retry mechanism..? 🤔