On Tue, Feb 13, 2018 at 01:18:02PM +0100, Thorsten Glaser wrote: > Now, in between the time FOO-common is ACCEPTed and FOO has been > rebuilt for that architecture, landed on the mirrors, etc., APT > wants to upgrade FOO-common and remove the old version of FOO. Note that the archive has some protection against this – it does fail if you have multiple architectures in your sources through, but yes, this quasi-blocks the removal of arch:all packages from the arch:any Packages files and using Packages-all… … because the archive could/can include both arch:all versions and apt would "just" need to figure out that the two versions come from the very same source, so it could ignore the "newer" version (or pick the "older") if needed. apt e.g. does something similar for M-A:same packages from different architectures in different versions to avoid pointless "remove the world to upgrade libc6:fastarch" solutions. It's on the list of things to do at least since I implemented Packages-all support at all… not too long ago but not exactly recent either… "later" after being done with the current batch I guess (if nobody else beats me). Best regards David Kalnischkies
Attachment:
signature.asc
Description: PGP signature