Package: release.debian.org Severity: normal User: [email protected] Usertags: transition
Hey there, the upcoming upload of cryptsetup 2.0.0-1 will bump the libcryptsetup soname from 4 to 12. According to (the very thoughtful) upstream, the API (old functions) is backwards-compatible, so simple rebuilds of the reverse depenencies should be enough. Here's a list of reverse depends: bruteforce-luks cryptmount libpam-mount luksmeta systemd volume-key libblockdev zulucrypt How shall we proceed? The package is ready to be uploaded. Shall we go ahead? Will you (the Release Managers) trigger the binary rebuilds afterwards? Or can/shall we do this ourselves? Cheers jonas Ben file: title = "cryptsetup"; is_affected = .depends ~ "libcryptsetup4" | .depends ~ "libcryptsetup12"; is_good = .depends ~ "libcryptsetup12"; is_bad = .depends ~ "libcryptsetup4"; -- System Information: Debian Release: 9.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
