Package: luksipc
Version: 0.04-2+b1
Severity: normal

luksipc just needs the binaries (/sbin/cryptsetup) from cryptsetup-bin, it
doesn't need the boot process integration from cryptsetup.  As such it
should depend just on the bin package.

This is useful if one is using it with disk images or the like and don't
want update-initramfs to constantly produce scary warnings about not being
able to find your boot device if it isn't encrypted.

-- System Information:
Debian Release: 9.6
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'testing'), (500, 'oldstable'), (490, 
'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-8-amd64 (SMP w/12 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)

Versions of packages luksipc depends on:
ii  cryptsetup  2:1.7.3-4
ii  dmsetup     2:1.02.137-2
ii  libc6       2.27-8

luksipc recommends no packages.

luksipc suggests no packages.

-- no debconf information

Reply via email to