Package: kpartx Version: 0.8.5-2 Severity: minor Dear Maintainer,
While testing a script, I stumbled over a case where kpartx -av (expectedly) failed to setup loop devices for a standard text file. The script failed later because the exit code of the command was 0 (echo $? directly after execution of kpartx -av <text file>), which I expected to signal success. So, it would be great if kpartx one day would return exit codes > 0 on failures in line with other utilities, as this avoids inventing heuristics to parse the output to achieve failure/success detection. -- System Information: Debian Release: 11.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-7-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_USER, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages kpartx depends on: ii dmsetup 2:1.02.175-2.1 ii libc6 2.31-12 ii libdevmapper1.02.1 2:1.02.175-2.1 ii udev 247.3-5 kpartx recommends no packages. kpartx suggests no packages. -- no debconf information
