Unpacking (Step 1) failed #467

NDiGH · 2022-02-19T21:24:06Z

NDiGH
Feb 19, 2022

Hallo,

wenn man für eine 7520/7530 eine Firmware bauen möchte scheitert es an "Step 1: Unpack":

STEP 1: UNPACK
source firmware file: dl/fw/FRITZ.Box_7530-07.29.image
checking signature: valid
unpacking firmware image
abort()ing pseudo client by server request. See https://wiki.yoctoproject.org/wiki/Pseudo_Abort for more details on this.
Check logfile: /home/Downloads/freetz-ng_2022-02-18_IPQ/.fakeroot-cache/pseudo.log
./fwmod: Zeile 694:  4923 Abgebrochen             (Speicherabzug geschrieben) "$TAR_GNU" -xif "$FIRMWARE" -C "$FIRMWARE_DIR"
unpacking filesystem image
    Filesystem on build/original/firmware/var/tmp/filesystem.image is xz compressed (4:0)
    Parallel unsquashfs: Using 6 processors
    9645 inodes (10620 blocks) to write
    created 8963 files
    created 539 directories
    created 681 symlinks
    created 1 devices
    created 0 fifos
unpacking var.tar
abort()ing pseudo client by server request. See https://wiki.yoctoproject.org/wiki/Pseudo_Abort for more details on this.
Check logfile: /home/Downloads/freetz-ng_2022-02-18_IPQ/.fakeroot-cache/pseudo.log
./fwmod: Zeile 694:  5060 Abgebrochen             (Speicherabzug geschrieben) "$TAR_GNU" -xipf "$VARTAR" -C "$VARTAR_DIR"
FINISHED

Hier die pseudo.log:

debug_logfile: fd 2
pid 4884 [parent 4883], doing new pid setup and server start
Setup complete, sending SIGUSR1 to pid 4883.
path mismatch [2 links]: ino 16884141 db '/home/Downloads/freetz-ng_2022-02-18_IPQ/build/original/firmware/var/tmp' req '/proc/self/fd/5'.
path mismatch [2 links]: ino 16893771 db '/home/Downloads/freetz-ng_2022-02-18_IPQ/build/original/kernel/var.tar/var/dev' req '/proc/self/fd/5'.
db cleanup for server shutdown, 22:10:43.010
memory-to-file backup complete, 22:10:43.016.
db cleanup finished, 22:10:43.016

Das Build-System ist ein Arch-Linux:

[user@device ~]$ uname -a
Linux device 5.15.24-1-lts #1 SMP Wed, 16 Feb 2022 16:04:21 +0000 x86_64 GNU/Linux

Edit:
Mit selbst gebauten "host-tools" anstatt den precompiled x86_64 host-tools gibt es diesen Fehler nicht. ~~Da das früher (Nov. 2021) nicht notwendig war, vermute ich, dass das Problem seit 8e70e25, 16eb7cb, 80977e5 oder fd0213e besteht.~~