[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1023485: marked as done (Shipped blkid is incompatible with the one in util-linux, break cryptsetup)

Your message dated Sat, 21 Jan 2023 19:30:40 +0300
with message-id <de6cd565-266b-0803-4f1f-7b8792d0b2b1@msgid.tls.msk.ru>
and subject line Re: Shipped blkid is incompatible with the one in util-linux, break cryptsetup
has caused the Debian Bug report #1023485,
regarding Shipped blkid is incompatible with the one in util-linux, break cryptsetup
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1023485: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023485
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: busybox-static
Version: 1:1.35.0-3
Severity: important

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hey!

blkid was added as an applet in busybox. This makes it available in initramfs in
place of the one from util-linux. This prevents cryptsetup to works as the
syntax used is not recognized by busybox.

 10:58 ❱ blkid -l -t UUID=255e21df-9261-47b5-ac37-b4ae4c435a37 -o device
/dev/nvme0n1p3
 10:59 ❱ busybox blkid -l -t UUID=255e21df-9261-47b5-ac37-b4ae4c435a37 -o device
 10:59 ❱ sudo busybox blkid -l -t UUID=255e21df-9261-47b5-ac37-b4ae4c435a37 -o device

cryptsetup-initramfs could parse the output of busybox blkid, but this seems
more fragile. It seems easiest to not ship blkid in busybox (hence the bug
against busybox).

- -- System Information:
Debian Release: bookworm/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental-debug'), (101, 'experimental')
Architecture: amd64 (x86_64)

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

- -- no debconf information

-----BEGIN PGP SIGNATURE-----

iQJGBAEBCAAwFiEErvI0h2bzccaJpzYAlaQv6DU1JfkFAmNmNPMSHGJlcm5hdEBk
ZWJpYW4ub3JnAAoJEJWkL+g1NSX5xT0QAKDHldn2kpQ+q5++vOpu05hYLsz9VkWp
ud2ZH+gNXc85qDHvTN+kKu+h1nMbK8Qk/x6o/orRzvRBAwmJ6XE06tBBulOahoKi
q8dxYorvXQJV3bI7ua1JYsYKTybguE/omN27IguopQdzE1Bac5fkfcKwni5QHEdi
oOda3FNVAdQiZ7mh77nBaD9NtqG4lzMb4rbxwQ5ZGG2BOypVQ7CHnoyPt813PjSI
eh76R5cW9/KgyqbWo4mGVGtZ8DqmVY+BLuVKH0+g+zreieRlbTLhJakwYCUJ4SNS
6ye9M58xtgviBbDUBl4ae7LV9ARSa9RpG6wkLgVw36CrD/QAwAoSsjJwcPRg2xGH
P7O8nyT+tyP3xFmNGAHfJpLO/CPh8B3rNJABSO6F8hGzoh2Ej8zFfmEZ3CfchnmR
SatUtS5yBlvU3wvkdK0VMDpXOdqqJjDkexjm28vriBvyAUi07OBsbqtEILGgJXb6
bOXv6hGWg5F/qA+OgjWdu6YJUbBrZVH7gvePbr5lmwwGItDc0UIrAZxZ5/1FIi5G
G9+NTS+kpFFT0uvD8F6HaqZrPGTSDJM5DSoHxZLkYSYJjZzbrC2Fk9w3AaE7/6u/
05EVetREI89NvCt7GJbvS0jCWIlk3JVMAfbDvoNm6vqqTGJPEMjW81ABkJk6QKpF
3UcOjdL4nGqS
=KLT1
-----END PGP SIGNATURE-----

--- End Message ---
--- Begin Message --- 
Version: 1:1.35.0-4

On Sat, 05 Nov 2022 11:03:35 +0100 Vincent Bernat <bernat@debian.org> wrote:

Package: busybox-static
Version: 1:1.35.0-3
Severity: important

Hey!

blkid was added as an applet in busybox. This makes it available in initramfs in
place of the one from util-linux. This prevents cryptsetup to works as the
syntax used is not recognized by busybox.


This has been fixed in 1:1.35.0-4 but I typoed the Closes: line:

busybox (1:1.35.0-4) unstable; urgency=medium

  * static build: disable blkid applet (CONFIG_BLKID, #1023501)

    Since static build has CONFIG_FEATURE_PREFER_APPLETS=y, enabling
    any utility which is also provided by the system in other ways
    can be risky, since busybox shell will choose its applet version
    instead of running the actual utility, even if that utility file
    exists in $PATH. After enabling blkid, we effectively overwrote
    blkid from libblkid as used in initramfs. The result was non-
    working udev rules for block devices (not creating /dev/disk/by-*/),
    and the system's unbootable.

    Disable it for now at least on static build.
    Closes: 1023501

(note the missing # before the bug number).

Lets close this now.

/mjt

--- End Message ---
Reply to: