1. Forum
  2. Usenet
  3. LINUX.DEBIAN.MAINT.DPKG

  • Re: dpkg FTBFS on ports (hurd, x32) with outdated sqv

    From John Paul Adrian Glaubitz@21:1/5 to Guillem Jover on Mon May 19 10:00:01 2025
    XPost: linux.debian.ports.hurd

    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

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Samuel Thibault@21:1/5 to All on Mon May 19 10:40:01 2025
    XPost: linux.debian.ports.hurd

    Guillem Jover, le lun. 19 mai 2025 10:20:06 +0200, a ecrit:
    On Mon, 2025-05-19 at 10:03:02 +0200, Samuel Thibault wrote:
    John Paul Adrian Glaubitz, le lun. 19 mai 2025 09:58:07 +0200, a ecrit:
    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.

    On hurd-any at least, apt currently depends on sqv, so removing sqv
    would make apt uninstallable.

    Yes, as mentioned on my original mail, going this route might require rebuilding apt.

    But better rebuild apt first? Otherwise in the meanwhile the whole
    distrib becomes uninstallable and nothing will build, we cannot recreate chroots, etc.

    (and I'd have to see how to do that rebuild, since to avoid sqv
    installed for apt not to pick it up, that'd mean removing the apt
    package in the build chroot...)

    Samuel

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)