Hi! On Mon, 2025-05-19 at 09:28:04 +0200, John Paul Adrian Glaubitz wrote: > On Mon, 2025-05-19 at 08:31 +0200, Guillem Jover wrote: > > The just uploaded dpkg, got support for sqv, which is now installed by > > default on minimal chroots due to apt pulling it in on some > > architectures (instead of gpgv). But this support relies on new interfaces > > added in sqv 1.3.0. > > Shouldn't dpkg then get a versioned build-dependency for sqv >= 1.3.0.
sqv is not available on all ports, so that would make it fail on all those ports then. I think a versioned build-conflicts would have been better (but I didn't think there would be outdated versions), but that would then make it uninstallable on the affected ports anyway. Using an arch-restricted build-dependency would be another alternative but I don't feel like tracking where sqv is available over time on dpkg's build dependencies (this seems wrong to me), and would also not fix the issue at hand (on the affected ports dpkg would either be uninstallable, or if not listed, still fail due to the binary being present but not new enough). > FWIW, on x32, rustc needs to be rebootstrapped but last time I tried this > several months ago, it didn't work. I will try that again later this month. If getting a new sqv version built is going to be too hard or time consuming for now, then perhaps removing the sqv binary packages from the port (like it's the state for several other ports) is the quickest fix to be able to build dpkg, as I mentioned in my original mail. Thanks, Guillem
