Package: nvme-cli Version: 2.2.1-2 Severity: important Hi,
in addition to the wrong placement of udev rules files (already reported in #1026054), nvme-cli also seems to place the systemd service & target files into the wrong directory. Affected files are: * nvmefc-boot-connections.service * nvmf-autoconnect.service * nvmf-connect@.service * nvmf-connect.target It places them into ´/lib/systemd/´ instead of the correct directory for system-wide systemd files: ´/lib/systemd/system/'. Thanks for maintaining nvme-cli in Debian Peter -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'stable-security'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.0.0-6-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_CRAP Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages nvme-cli depends on: ii libc6 2.36-7 ii libjson-c5 0.16-2 ii libnvme1 1.2-2 ii uuid-runtime 2.38.1-4 ii zlib1g 1:1.2.13.dfsg-1 Versions of packages nvme-cli recommends: ii pci.ids 0.0~2022.12.19-1 nvme-cli suggests no packages. -- no debconf information
