On 2026-02-21 23:28:18 +0000, Lyndon Brown wrote: > On Sun, 2026-02-22 at 00:10 +0100, Sebastian Ramacher wrote: > > On 2026-02-21 23:04:23 +0000, Lyndon Brown wrote: > > > libvpx11 will just have to be patched then. > > > > It can't. libvpx11 is cruft in unstable. > > I don't understand. Not being a DD I've never uploaded a package to > Debian infrastructure before. Does the infrastructure not provide a way > for older lib packages still in the archive to be updated in situations > like this? You're not seriously telling me that once libvpx11 was > replaced with libvpx12, that's it, it's just not possible for it to be > updated ever again and the only option possible is to wait for every > package using it to move on to the new one (or be dropped)?
Yes, that is what I am saying. libvpx11 is no longer built by any source package. It is kept in the archive because there are other packages that still depend on it and would otherwise be rendered uninstallable. Fixing it would require that somebody re-introduces the package. But in any case, this issue only affects unstable as the affected package are all removed from testing. The best way forward is to provide patches and fix the packages that still depend on the cruft package. Cheers -- Sebastian Ramacher
