* Miao Wang <[email protected]> [260316 13:05]:
2026年3月16日 18:29，Miao Wang <[email protected]> 写道：
I'm curious about when old arch:all packages are deleted. I noticed
that old arch:any packages are only deleted when a corresponding
new binary package is uploaded. Is there any different policies
on the deletion of old arch:all packages?
I discovered that when uploading an arch:any binary package, the
previous version arch-all packages built by the same source package
are removed from the Packages file of that architecture. In our case,
the package built for amd64 was uploaded before the starting of the
build for the arch-all package, and the ipxe-qemu package, which is
arch-all, got removed from the index for amd64. Since arch-all
packages are built on amd64, the build dependency for ipxe:all cannot
be satisfied.
As a result, to make the build successful, we should ensure that
the start of building on all happens before the upload of amd64 packages,
otherwise there is possibility that similar event like this happens.
Is there any mechanisms achieving this?
No, you cannot influence the scheduling of these things. If you need
components of your own package, you probably need to split the
relevant parts off into a separate source. Or find another way of
not self-depending, which is often easier and a more stable
solution (except when your package is a self-hosting compiler of
course).
Chris
