Bug#972241: FTBFS on amd64 and i386 (error: guestfs_launch failed)
* Richard W.M. Jones: > guestfsd: error while loading shared libraries: libtirpc.so.3: cannot > open shared object file: No such file or directory > > Did something change with how libtirpc gets packaged on Debian > or upstream? Yes, libtirpc package got renamed because that's what Debian does when a libaray SONAME changes. I hope that with the patch I just sent to the libgeustfs mailing list, this can all be ignored in the future. Cheers, -Hilko
Bug#972241: FTBFS on amd64 and i386 (error: guestfs_launch failed)
guestfsd: error while loading shared libraries: libtirpc.so.3: cannot open shared object file: No such file or directory Did something change with how libtirpc gets packaged on Debian or upstream? Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-p2v converts physical machines to virtual machines. Boot with a live CD or over the network (PXE) and turn machines into KVM guests. http://libguestfs.org/virt-v2v
Bug#972241: FTBFS on amd64 and i386 (error: guestfs_launch failed)
control: tag -1 confirmed control: tag -1 pending * Stéphane Glondu: > Package: src:libguestfs > Version: 1:1.42.0-9 > Severity: serious > Tags: ftbfs > > Dear Maintainer, > > Your package FTBFS on amd64 and i386: > > https://buildd.debian.org/status/package.php?p=libguestfs=sid > > The rebuild was triggered by the update of OCaml from 4.08.1 to > 4.11.1, but the error looks independent (I might be wrong). Yes, This is unrelated to the OCaml update. I had noticed the build failure. I'm working to fix the issue properly and prepare a patch for upstream. Cheers, -Hilko
Bug#972241: FTBFS on amd64 and i386 (error: guestfs_launch failed)
Package: src:libguestfs Version: 1:1.42.0-9 Severity: serious Tags: ftbfs Dear Maintainer, Your package FTBFS on amd64 and i386: https://buildd.debian.org/status/package.php?p=libguestfs=sid The rebuild was triggered by the update of OCaml from 4.08.1 to 4.11.1, but the error looks independent (I might be wrong). The build log ends with: > libguestfs: error: appliance closed the connection unexpectedly, see earlier > error messages > libguestfs: child_cleanup: 0x562f7794ec00: child process died > libguestfs: sending SIGTERM to process 3723 > libguestfs: qemu maxrss 405328K > libguestfs: error: guestfs_launch failed, see earlier error messages > libguestfs: closing guestfs handle 0x562f7794ec00 (state 0) > libguestfs: command: run: rm > libguestfs: command: run: \ -rf > /<>/debian/build-4/tmp/libguestfsv1zKZI > libguestfs: command: run: rm > libguestfs: command: run: \ -rf /tmp/libguestfsZpOSRI > make[2]: *** [Makefile:3087: quickcheck] Error 1 > make[2]: Leaving directory '/<>/debian/build-4' > make[1]: *** [debian/rules:126: override_dh_auto_test] Error 2 > make[1]: Leaving directory '/<>' > make: *** [debian/rules:170: build-arch] Error 2 > dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit > status 2 Cheers, -- Stéphane -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.8.0-2-amd64 (SMP w/4 CPU threads) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled