1. Forum
  2. Usenet
  3. LINUX.DEBIAN.PORTS.HURD

  • Strange dd failure makes latest dpkg FTBFS

    From Guillem Jover@21:1/5 to All on Sun Feb 26 14:10:01 2023
    Hi!

    Just uploaded a dpkg release yesterday, with only translation updates
    and an arch definition, and it failed on the hurd-i386 buildd. The
    relevant part is:

    ,---
    ../../../src/at/deb-format.at:403:
    # Test data.tar.bad member
    dd if=/dev/zero of=data.tar.bad bs=1K count=4 status=none
    ar rc pkg-data-bad.deb debian-binary control.tar.gz data.tar.bad
    ar t pkg-data-bad.deb
    dpkg-deb -c pkg-data-bad.deb

    --- - 2023-02-25 23:04:49.224860000 +0000
    +++ /<<PKGBUILDDIR>>/build-tree/src/at/testsuite.dir/at-groups/3/stderr 2023-02-25 23:04:49.000000000 +0000
    @@ -1,2 +1,3 @@
    +dd: error reading '/dev/zero': Invalid argument
    dpkg-deb: error: archive 'pkg-data-bad.deb' uses unknown compression for member 'data.tar.bad', giving up

    3. deb-format.at:168: FAILED (deb-format.at:403)
    `---

    I tried the same dd command on exodar in a sid schroot, and it seems
    to work there, also just built dpkg there too (my hurd-i386 box got
    damaged due to a system crash and have had no time to recover it) and
    it seems to build fine there:

    ,---
    3. deb-format.at:168: ok
    `---

    So perhaps there's something wrong on ironforge? But I assume that would
    have shown other packages failing.

    Thanks,
    Guillem

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Samuel Thibault@21:1/5 to All on Sun Feb 26 16:00:02 2023
    Guillem Jover, le dim. 26 févr. 2023 14:07:37 +0100, a ecrit:
    +dd: error reading '/dev/zero': Invalid argument
    dpkg-deb: error: archive 'pkg-data-bad.deb' uses unknown compression for member 'data.tar.bad', giving up

    3. deb-format.at:168: FAILED (deb-format.at:403)
    `---

    I tried the same dd command on exodar in a sid schroot, and it seems
    to work there, also just built dpkg there too (my hurd-i386 box got
    damaged due to a system crash and have had no time to recover it) and
    it seems to build fine there:

    ,---
    3. deb-format.at:168: ok
    `---

    So perhaps there's something wrong on ironforge? But I assume that would
    have shown other packages failing.

    Mmm, that's odd, we don't really see other packages failing.

    I tried to reboot but that got the same result. I started the recreation
    of the chroot, let's see.

    Samuel

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Samuel Thibault@21:1/5 to All on Mon Feb 27 08:50:01 2023
    Samuel Thibault, le dim. 26 févr. 2023 15:53:15 +0100, a ecrit:
    I tried to reboot but that got the same result. I started the recreation
    of the chroot, let's see.

    Ok, gdb-ing the zero storeio, the culprit is 56d065041793509a6f60671f6ae3400698bd5639, I'll fix that.

    Samuel

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