- Package:
- libguestfs0
- Source:
- libguestfs
- Description:
- guest disk image management system - shared library
- Submitter:
- Ian Jackson
- Date:
- 2023-07-05 09:51:03 UTC
- Severity:
- normal
Depends: libacl1 (>= 2.2.51-8), libaugeas0 (>= 1.0.0), libc6 (>= 2.17), libcap2 (>= 1:2.10), libfuse2 (>= 2.8), libhivex0 (>= 1.2.2+git20100712), libmagic1 (>= 5.12), libpcre3, libselinux1 (>= 1.32), libsystemd0, libtsk13 (>= 4.2.0), libvirt0 (>= 0.9.4~rc1), libxml2 (>= 2.8.0), libyajl2 (>= 2.0.4), supermin (>= 5), qemu-system-x86, sgabios, db-util, icoutils, netpbm, osinfo-db, acl, attr, binutils, bsdmainutils, btrfs-progs, btrfs-tools, bzip2, cpio, cryptsetup, curl, diffutils, dosfstools, extlinux, file, gawk, gdisk, genisoimage, grub2-common, iproute2 | iproute, isc-dhcp-client, kmod | module-init-tools, ldmtool, less, lsscsi, lvm2, lzop, mdadm, mtools, ntfs-3g, openssh-client, parted, procps, psmisc, qemu-utils, scrub, sleuthkit, syslinux, systemd | sysvinit, udev, xz-utils, zerofree I can't imagine that libguestfs is completely broken without all of that lot. In fact, it can be loaded into programs which do not use libguestfs facilities without any of them. I suggest that everything which is not a library be removed. Ian.
Yep, stumbled upon this just now too, as trying to get just one simple utility which happens to be packaged in "libguestfs-tools", suddenly wanted to install a DHCP client and systemd on my machine. Folks, seriously? Moreover, stretch was supposed to be usable without systemd, but here we have: dep: systemd system and service manager or sysvinit Package not available How can you have package in stretch (option-)depend on a package not in it? I'm not an expert on your packaging names, but I suppose the new name for that one is sysvinit-core. Too sad to see Debian at this level of quality, I guess there's really no other option than to migrate to Devuan.
Is there a reason libguestfs0 depends on isc-dhcp-client specifically, instead of the virtual dhcp-client? I prefer dhcpcd over isc-dhcp-client, and there are several other dhcp-client implementations as well. If it really does need something specifically from isc-dhcp-client, could it be moved to Recommends instead of Depends (i.e. is it really a universal dependency, or is it just some limited extra functionality)? Thanks, Beolach
* Beolach: I just checked. The applicance init script does support both dhclient and dhcpcd, so we should be able to do alterenate dependencies. Cheers, -Hilko