Re: dpkg FTBFS on ports (hurd, x32) with outdated sqv
Hi,
On Mon, 2025-05-19 at 09:49 +0200, Guillem Jover wrote:
> 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).
So, what does it then use at the moment? How does it figure out whether sqv
is available or not. You somehow have to whitelist the architectures with
sqv, no?
> > 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.
Well, this is something Aurelien has to do. I don't have any access to
the Ports FTP servers, so I can't just easily remove packages, unfortunately.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer
`. `' Physicist
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Reply to: