> 2026年3月16日 18:22，Michael Tokarev <[email protected]> 写道：
>
> On 16.03.2026 13:09, Miao Wang wrote:
>
>>> ipxe build-depends on:
>>> - qemu-system-i386:amd64 | qemu-system-i386:amd64
>>> qemu-system-x86 depends on missing:
>>> - ipxe-qemu:amd64 (> 1.21.1+git20220113.fbbdc3926+dfsg-1~)
>>>
>>> This installability chain doesn't seem to work on the buildds with
>>> the current state in unstable.
>
>> I don't know why this should happen. The previous version ipxe-qemu was
>> actually in the archive before my upload. Actually it was available when
>> building on amd64, so building on amd64 was successful. Why it became
>> unavailable when building on all? I don't quite understand the reason
>> and I don't know how to prevent this from happening.
>
> This is a general issue on buildds when a package build-depends on
> itself (either directly or through an inter-dependency). Sometimes
> it works, but once any build failure happens, it wont work anymore until
> dependencies are changed.
>
> This is why I created a special build profile for qemu (it build-depends
> on itself directly), - because if any error happens when building, it
> wont work anymore and needs to be re-uploaded with missing pieces
> included.
>
> In qemu things are a bit easier, since it build-depends on arch-all
> component of itself (qemu-system-data) when building arch-indep
> pieces only. Here with ipxe, things are a bit more complicated.
>
> How ipxe uses qemu-system-x86 during build, exactly?
Actually, for running tests.
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?
Cheers,
Miao Wang
