Hi Chris, Fair point. My reasoning: libiw30 and libiw30t64 ship the identical file (/usr/lib/x86_64-linux-gnu/libiw.so.30) and can never coexist under any circumstance, so I don't think there's a future libiw30 version this should ever need to tolerate, unlike a typical soname bump where reuse of the old name is conceivable.
Simon has already sponsored and uploaded -23 to unstable with the unversioned form, and it's verified to fix the reported upgrade failure. If you think bounding it to a specific pre-t64 version is still the better convention here, I'm glad to prepare a follow-up, just let me know which version you'd use as the ceiling. Best regards, Ahmed Alaoui On Mon, Aug 10, 2026 at 9:26 AM Chris Hofstaedtler <[email protected]> wrote: > On Sat, Aug 08, 2026 at 07:14:52PM +0100, Ahmed Alaoui wrote: > > dpkg: error processing archive .../libiw30t64_30~pre9-22_amd64.deb > > (--unpack): > > trying to overwrite '/usr/lib/x86_64-linux-gnu/libiw.so.30', which is > > also in package libiw30:amd64 (30~pre9-16+b1) > > > > Fix: use unconditional Conflicts/Replaces, since libiw30t64 and libiw30 > > can never coexist regardless of version: > > > > Conflicts: libiw30 > > Replaces: libiw30 > > This seems overly broad, especially when we know the last version > that was available before the migration. > > Chris > >
