On Mon, Mar 11, 2024 at 01:06:49PM +0100, Andreas Tille wrote: > Yes, I've filed this and this was perfectly intended (even if I forgot > that the bug is done meanwhile which I should have checked before asking > here - sorry about this). It was just that all signs that this package > exists are remaining and its just missing in the Packages file. So > removing a package just means droping it from Packages file and all > other things are cleaned up later on?
"rmadison clustalw" shows: clustalw | 2.1+lgpl-6 | oldoldstable | source, amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x clustalw | 2.1+lgpl-7 | oldstable | source, amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x clustalw | 2.1+lgpl-7 | stable | source, amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x clustalw | 2.1+lgpl-7 | testing | source, amd64, arm64, mips64el, ppc64el, s390x clustalw | 2.1+lgpl-7 | unstable | source, amd64, arm64, mips64el, ppc64el, s390x clustalw | 2.1+lgpl-7 | unstable-debug | source clustalw | 2.1+lgpl-7+b1 | unstable | riscv64 So since clustalw/2.1+lgpl-7/i386 is still in oldstable and stable, it has to be kept in the pool; files are only expired from the pool once they're no longer referenced anywhere. (And yes, I think there's a delay between removing references from index files and removing the actual pool files, to avoid mirroring race conditions.) -- Colin Watson (he/him) [cjwat...@debian.org]
