Bug#855094: initramfs-tools-core: Error on upgrade if cryptsetup is installed, but a current busybox isn't

Package: initramfs-tools-core Version: 0.127 Severity: serious Justification: Policy 3.5 I tried a partial upgrade of initramfs-tools, but it failed, complaining that busybox was too old, see console messages below. The version of busybox installed at that time was 1:1.22.0-9+deb8u1. I solved this

Bug#854516: kstars should depend on libqt5sql5-sqlite

Package: kstars Version: 4:16.08.3-1 Severity: serious Justification: Policy 3.5 If libqt5sql5-sqlite is not installed, starting kstars produces a popup window with this message: The file citydb.sqlite could not be found. KStars cannot run properly without this file. KStars searches for this

Bug#854008: kstars-data-extra-tycho2: deepstars.dat installed in wrong directory

Package: kstars-data-extra-tycho2 Version: 1.1r1-9 Severity: grave Justification: renders package unusable The current testing version of kstars, version 4:16.08.3-1, expects deepstars.dat to reside in /usr/share/kstars along with its other data files. However, the current testing version of kstar

Bug#768889: efibootmgr: "dpkg-buildpackage -b" installs efibootmgr in /usr/sbin

Package: efibootmgr Version: 0.11.0-1 Severity: serious Justification: Policy 4.9 Dear Maintainer, I used "dpkg-buildpackage -b" to build efibootmgr and it has created efibootmgr in /usr/sbin (in addition to building the .deb package). Here's a snippet from the build log, note the "Installed Fil

Bug#768880: efibootmgr: unusable if reading any boot variable fails

I've just tested with efibootmgr 0.5.4-3 (the current stable version) and it can list the boot entries. strace shows that it receives an EIO error, but it doesn't cause the program to abort. -- Jan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscri

Bug#768880: efibootmgr: unusable if reading any boot variable fails

Package: efibootmgr Version: 0.11.0-1 Severity: critical Justification: breaks the whole system Dear Maintainer, On my system, reading Boot0005 fails with EIO: openat(AT_FDCWD, "/sys/firmware/efi/vars/", O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = 3 brk(0) = 0x

Bug#764386: libefivar0: Segmentation fault in vars_get_variable() (vars.c:165)

On Wed, Oct 29, 2014 at 12:11:18PM -0500, D. Jared Dominguez wrote: > Can you confirm whether this is still an issue for you? New versions > of libefivar0 are in testing and unstable. Please test against them. The segmentation fault still occurs with libefivar0 version 0.15-1 and efibootmgr versio

Bug#764386: libefivar0: Segmentation fault in vars_get_variable() (vars.c:165)

Package: libefivar0 Version: 0.12-1 Severity: critical Justification: breaks the whole system Upgrading libefivar0 from version 0.10-5 to 0.12-1 causes a segmentation fault when running efibootmgr without arguments (I tried it with both efibootmgr 0.7.0-2 and 0.9.0-1). I'm not quite sure if sever

Bug#300113: Bug#297137 / Bug#300113: bash 2.05-0beta1 not recent enough

The version of bash that failed for me in Bug#297137 was 2.05a-11. The version in the Depends field in hotplug-0.0.20040329-20 is 2.05-0beta1 which is OLDER than 2.05a-11. The comment in Bug#300113 speaks of version 2.05b-beta1 which doesn't exist. The changelog entry for version 2.05b-1 suggests

Bug#297137: hotplug: /etc/init.d/hotplug stopped working because 'unset' fails

Package: hotplug Version: 0.0.20040329-17 Severity: grave Tags: patch Justification: renders package unusable "/etc/init.d/hotplug start" aborts almost immediately, it doesn't even print the "Starting hotplug subsystem" message. I didn't notice this until I tried to use an USB device and found t