Bug#1012626: sicherboot requires dependency on systemd-boot{,-efi}

2022-06-10 Thread Dustin L. Howett
Package: sicherboot
Version: 0.1.5
Severity: normal
X-Debbugs-Cc: dus...@howett.net

As of systemd-251.2-3, systemd-boot and systemd-boot-efi have been split
out of the systemd package. This causes sicherboot to fail to install
new kernels; confer bug #1012625 for the systemd report. Recommend a
dependency on systemd-boot and systemd-boot-efi.

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.18.1 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages sicherboot depends on:
ii  binutils  2.38-4
ii  efitools  1.9.2-2
ii  systemd   251.2-4
ii  uuid-runtime  2.38-4

sicherboot recommends no packages.

sicherboot suggests no packages.

-- no debconf information



Bug#1012625: systemd-boot: update to split -boot and -boot-efi out of systemd can harm working system

2022-06-10 Thread Dustin L. Howett
Package: systemd-boot
Version: 251.2-4
Severity: normal
X-Debbugs-Cc: dus...@howett.net

The upgrade to systemd-251.2-4 removed systemd-boot and the EFI stub
glue from /usr/lib/systemd/boot. This can result in an eventual failure
to boot[1], especially when combined with a package such as `sicherboot`
that manages the installation of secure boot signed kernels.

On upgrade:

---

sicherboot: Installing 5.18.1 to ESP
objcopy: '/usr/lib/systemd/boot/efi/linuxia32.efi.stub': No such file
objcopy: --change-section-vma .initrd=0x0300 never used
objcopy: --change-section-vma .linux=0x0004 never used
objcopy: --change-section-vma .cmdline=0x0003 never used
objcopy: --change-section-vma .osrel=0x0002 never used
run-parts: /etc/initramfs/post-update.d//zz-sicherboot exited with return code 1
dpkg: error processing package initramfs-tools (--configure):
 installed initramfs-tools package post-installation script subprocess returned 
error exit status 1

---

I realize that some of the burden here is on sicherboot to express a
dependency on systemd-boot and systemd-boot-efi; however, this change to
the systemd package has the potential to break non-sicherboot user flows
as well.

[1] or to upgrade to new supported versions of the bootloader
transparently, potentially exposing users to security issues.

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.18.1 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages systemd-boot depends on:
ii  libc6  2.33-7
ii  libsystemd-shared  251.2-4
ii  systemd-boot-efi   251.2-4

Versions of packages systemd-boot recommends:
ii  efibootmgr  17-1

systemd-boot suggests no packages.

-- no debconf information



Bug#899342: bluez 5.49-2 preinst is improperly authored and fails during preinstall

2018-05-22 Thread Dustin L. Howett
Package: bluez
Version: 5.49-2
Severity: important

The installation of this package fails with the following error:

Preparing to unpack .../01-bluez_5.49-2_amd64.deb ...
/var/lib/dpkg/tmp.ci/preinst: 28: /var/lib/dpkg/tmp.ci/preinst: Syntax error: 
"fi" unexpected (expecting "done")
dpkg: error processing archive 
/tmp/apt-dpkg-install-WpvNhe/01-bluez_5.49-2_amd64.deb (--unpack):
 new bluez package pre-installation script subprocess returned error exit 
status 2

preinst has a number of unclosed loops dpanning lines 16-26:

for conffile in \
/etc/bluetooth/rfcomm.conf \
/etc/bluetooth/serial.conf \
/etc/bluetooth/audio.conf; do \
dpkg-maintscript-helper rm_conffile \
${conffile} 5.21-2 bluez -- "$@"
!>>> missing done here 

for conffile in \
/etc/bluetooth/proximity.conf; do \
dpkg-maintscript-helper rm_conffile \
${conffile} 5.47-1 bluez -- "$@"
!>>> missing done here 

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.16.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages bluez depends on:
ii  dbus  1.12.8-2
ii  kmod  25-1
ii  libasound21.1.6-1
ii  libc6 2.27-3
ii  libdbus-1-3   1.12.8-2
ii  libdw10.170-0.4
ii  libglib2.0-0  2.56.1-2
ii  libreadline7  7.0-5
ii  libudev1  238-4
ii  lsb-base  9.20170808
ii  udev  238-4

bluez recommends no packages.

Versions of packages bluez suggests:
pn  pulseaudio-module-bluetooth  

-- no debconf information



Bug#841385: golang-go does not participate in alternatives, gccgo-6 stomps /usr/bin/go

2016-10-19 Thread Dustin L. Howett
Package: golang-go
Version: 2:1.7~1
Severity: important

Installing gccgo-6=6.2.0-6 after golang-go=2:1.7~1 triggers an
update-alternatives that replaces /usr/bin/go with a symbolic link to
/etc/alternatives/go.

It looks like the fix for #840190 did not coordinate with an update to
golang-go that integrates with the alternatives system.

-- System Information:
Debian Release: stretch/sid
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'unstable'), (500, 'testing'), 
(500, 'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages golang-go depends on:
ii  golang-1.7-go  1.7.3-1
ii  golang-src 2:1.7~1

golang-go recommends no packages.

golang-go suggests no packages.

-- no debconf information