1. Forum
  2. Usenet
  3. LINUX.DEBIAN.BUGS.RC

  • Bug#1094115: check-postgres: FTBFS: make[1]: *** [debian/rules:19: over

    From Russ Allbery@21:1/5 to Lucas Nussbaum on Sun Feb 9 19:30:01 2025
    Lucas Nussbaum <lucas@debian.org> writes:
    On 04/02/25 at 16:17 +0100, Christoph Berg wrote:
    Re: Lucas Nussbaum
    # Failed test 'Action 'autovac_freeze' self-identifies correctly'
    # at t/02_autovac_freeze.t line 40.
    # 'uid=65534 topuid=10 euid=104 path='/tmp' at /usr/lib/x86_64-linux-gnu/perl-base/File/Temp.pm line 686.

    This doesn't seem like a problem with check-postgres. Is /tmp botched
    in that build chroot?

    I don't think so. There's another bug with /tmp strangeness (#1094100),
    also raised by File::Temp.

    /tmp is shown above as being owned by the nobody user (65534) rather than
    root. Have you by any chance changed something about how UID mappings in
    the file system might work in your builds? For example, if the build
    chroot is on a remote NFS server with root-squash enabled, one might see
    this. I'm not sure if using user namespaces may do something similar.

    --
    Russ Allbery (rra@debian.org) <https://www.eyrie.org/~eagle/>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Lucas Nussbaum@21:1/5 to Russ Allbery on Sun Feb 9 20:30:01 2025
    On 09/02/25 at 10:17 -0800, Russ Allbery wrote:
    Lucas Nussbaum <lucas@debian.org> writes:
    On 04/02/25 at 16:17 +0100, Christoph Berg wrote:
    Re: Lucas Nussbaum
    # Failed test 'Action 'autovac_freeze' self-identifies correctly'
    # at t/02_autovac_freeze.t line 40.
    # 'uid=65534 topuid=10 euid=104 path='/tmp' at /usr/lib/x86_64-linux-gnu/perl-base/File/Temp.pm line 686.

    This doesn't seem like a problem with check-postgres. Is /tmp botched
    in that build chroot?

    I don't think so. There's another bug with /tmp strangeness (#1094100), also raised by File::Temp.

    /tmp is shown above as being owned by the nobody user (65534) rather than root. Have you by any chance changed something about how UID mappings in
    the file system might work in your builds? For example, if the build
    chroot is on a remote NFS server with root-squash enabled, one might see this. I'm not sure if using user namespaces may do something similar.

    I switched to using the unshare sbuild backend (instead of schroot). But
    if I understand the current state of things correctly, this is also the
    case on buildds.

    Lucas

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