Your message dated Tue, 10 Oct 2017 16:48:46 +0000
with message-id <e1e1xi3-0008e7...@fasolo.debian.org>
and subject line Bug#852534: fixed in systemd 235-1
has caused the Debian Bug report #852534,
regarding systemd: cryptsetup-generator does not support LUKS on network devices
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 ow...@bugs.debian.org
immediately.)
--
852534: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852534
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: open-iscsi
Version: 2.0.874-1~bpo8+1
Severity: normal
Dear Maintainer,
I have a NAS that exports an iSCSI target. I have created a LUKS volume
on a partition on this target, used that volume as a PV, and created an
LVM VG/LV on top of it. On boot, systemd waits for 90s for the iSCSI
device and its subsidiary devices to appear before bringing up the
network. This is similar to bug #775778.
I am not sure that this is a bug in open-iscsi, but I'm filing it here
on the basis of the strong similarity with #775778. (I'm running jessie
with updates from jessie-backports, so I have the patches from that bug
already.)
This is how I setup my volume:
# The iSCSI part works fine.
iscsiadm … --login
# Device shows up as /dev/sdb; I create a /dev/sdb1 partition using
# fdisk, of type 8e.
# Create encrypted LUKS volume on /dev/sdb1, open and map as
# /dev/mapper/sdb1_crypt.
cryptsetup luksFormat /dev/sdb1
cryptsetup luksOpen /dev/sdb1 sdb1_crypt \
--key-file /root/blackbird-ullu
# Set up LVM PV, VG, and LV mapped to /dev/mapper/blackbird-ullu,
# with an ext4 filesystem on top.
pvcreate /dev/mapper/sdb1_crypt
vgcreate blackbird /dev/mapper/sdb1_crypt
lvcreate -n ullu -l 100%VG blackbird
mkfs.ext4 /dev/mapper/blackbird-ullu
mount /dev/mapper/blackbird-ullu /media/nas
I have an entry in /etc/crypttab like this:
sdb1_crypt UUID=ae6b9263-d63c-4515-b7ce-51e5cc4caa9f /root/blackbird-ullu
luks
And an entry in /etc/fstab like this (I've tried various variants here,
see below):
/dev/mapper/blackbird-ullu /media/nas ext4 defaults,nofail,_netdev 0 6
There are three devices involved:
- /dev/disk/by-uuid/<x>: is the iSCSI target (/dev/sdb)
- /dev/mapper/sdb1_crypt: result of cryptsetup luksOpen /dev/sdb1
- /dev/mapper/blackbird-ullu: LV built on top of sdb1_crypt
Now I suffer from the 90s wait on startup (before network-online), where
systemd waits for the dev-mapper-blackbird\x2dullu.device to become
available, along with dev-disk-by\x2duuid-<xxx>.device and
dev-mapper-sdb1_crypt.device.
After the timeout, the boot proceeds, brings up the network, starts
iscsid, and runs /lib/open-iscsi/activate-storage.sh once /dev/sdb is
available, but the "vgchange -aay" command fails because the PV is not
yet mapped with cryptsetup:
activate-storage.sh[2618]: Volume group "blackbird" not found
activate-storage.sh[2618]: Skipping volume group blackbird
activate-storage.sh[2618]: Warning: could not activate all LVM groups.
This is the first time I have used iSCSI or systemd, so my attempts to
resolve this are pretty amateurish, but here's an overview:
(a) I shortened the 90s timeout for all three devices by creating
drop-in overrides for the corresponding .device units under
/etc/systemd/system:
dev-disk-by\x2duuid-ae6b9263\x2dd63c\x2d4515\x2db7ce\x2d51e5cc4caa9f.device.d/nowait.conf
dev-mapper-sdb1_crypt.device.d/nowait.conf
dev-mapper-blackbird\x2dullu.device.d/nowait.conf
[Unit]
JobTimeoutSec=1
(I later removed the third file and instead added the
x-systemd.device-timeout=1s mount flag in /etc/fstab for the
/dev/mapper/blackbird-ullu volume, but this is functionally equivalent
to the above.)
After this, the boot proceeded with only a 1s wait, with messages like this:
systemd[1]: dev-mapper-sdb1_crypt.device: Job
dev-mapper-sdb1_crypt.device/start timed out.
systemd[1]: Timed out waiting for device dev-mapper-sdb1_crypt.device.
systemd[1]: Dependency failed for Cryptography Setup for sdb1_crypt.
systemd[1]: Dependency failed for Encrypted Volumes.
systemd[1]: cryptsetup.target: Job cryptsetup.target/start failed with
result 'dependency'.
systemd[1]: systemd-cryptsetup@sdb1_crypt.service: Job
systemd-cryptsetup@sdb1_crypt.service/start failed with result 'dependency'.
systemd[1]: dev-mapper-sdb1_crypt.device: Job
dev-mapper-sdb1_crypt.device/start failed with result 'timeout'.
systemd[1]:
dev-disk-by\x2duuid-ae6b9263\x2dd63c\x2d4515\x2db7ce\x2d51e5cc4caa9f.device:
Job dev-disk-by\x2duuid-ae6b9263\x2dd63c\x2d4515\x2db7ce\x2d51e5cc4caa
systemd[1]: Timed out waiting for device
dev-disk-by\x2duuid-ae6b9263\x2dd63c\x2d4515\x2db7ce\x2d51e5cc4caa9f.device.
systemd[1]:
dev-disk-by\x2duuid-ae6b9263\x2dd63c\x2d4515\x2db7ce\x2d51e5cc4caa9f.device:
Job dev-disk-by\x2duuid-ae6b9263\x2dd63c\x2d4515\x2db7ce\x2d51e5cc4caa
systemd[1]: dev-mapper-blackbird\x2dullu.device: Job
dev-mapper-blackbird\x2dullu.device/start timed out.
systemd[1]: Timed out waiting for device
dev-mapper-blackbird\x2dullu.device.
systemd[1]: Dependency failed for /media/nas.
systemd[1]: media-nas.mount: Job media-nas.mount/start failed with result
'dependency'.
systemd[1]: Dependency failed for File System Check on
/dev/mapper/blackbird-ullu.
systemd[1]: systemd-fsck@dev-mapper-blackbird\x2dullu.service: Job
systemd-fsck@dev-mapper-blackbird\x2dullu.service/start failed with result
'dependency'.
systemd[1]: dev-mapper-blackbird\x2dullu.device: Job
dev-mapper-blackbird\x2dullu.device/start failed with result 'timeout'.
(b) To address the "vgchange -aay" problem, I enabled global/use_lvmetad
in lvm.conf. Now activate-storage.sh still fails to activate the volume
group, but lvmetad activates it once the PV is mapped. I've edited the
following log excerpt to remove unrelated interleaved output:
systemd[1]: Starting iSCSI initiator daemon (iscsid)...
iscsid[2544]: iSCSI logger with pid=2548 started!
systemd[1]: Started iSCSI initiator daemon (iscsid).
systemd[1]: Starting Login to default iSCSI targets...
kernel: scsi host4: iSCSI Initiator over TCP/IP
kernel: scsi 4:0:0:0: Direct-Access SYNOLOGY iSCSI Storage 3.1 PQ:
0 ANSI: 5
kernel: sd 4:0:0:0: Attached scsi generic sg1 type 0
kernel: sd 4:0:0:0: [sdb] 3897335808 512-byte logical blocks: (2.00 TB/1.81
TiB)
kernel: sd 4:0:0:0: [sdb] Write Protect is off
kernel: sd 4:0:0:0: [sdb] Mode Sense: 3b 00 00 00
kernel: sd 4:0:0:0: [sdb] Write cache: disabled, read cache: enabled,
doesn't support DPO or FUA
iscsiadm[2558]: Logging in to [iface: default, target:
iqn.2017-01.in.lweshal:blackbird.Target-1.6f8f6dc754, portal:
192.168.11.2,3260] (multiple)
iscsiadm[2558]: Login to [iface: default, target:
iqn.2017-01.in.lweshal:blackbird.Target-1.6f8f6dc754, portal:
192.168.11.2,3260] successful.
kernel: sdb: sdb1
kernel: sd 4:0:0:0: [sdb] Attached SCSI disk
…
systemd[1]: Reached target Bluetooth.
systemd[1]: Starting Cryptography Setup for sdb1_crypt...
systemd-cryptsetup[2729]: Set cipher aes, mode xts-plain64, key size 256
bits for device /dev/disk/by-uuid/ae6b9263-d63c-4515-b7ce-51e5cc4caa9f.
systemd[1]: Reached target Multi-User System.
systemd[1]: Reached target Graphical Interface.
iscsid[2548]: iSCSI daemon with pid=2549 started!
iscsid[2548]: Connection1:0 to [target:
iqn.2017-01.in.lweshal:blackbird.Target-1.6f8f6dc754, portal:
192.168.11.2,3260] through [iface: default] is operational now
activate-storage.sh[2618]: Volume group "blackbird" not found
activate-storage.sh[2618]: Skipping volume group blackbird
activate-storage.sh[2618]: Warning: could not activate all LVM groups.
systemd[1]: Started Login to default iSCSI targets.
systemd[1]: dev-mapper-sdb1_crypt.device: Job
dev-mapper-sdb1_crypt.device/start timed out.
systemd[1]: Timed out waiting for device dev-mapper-sdb1_crypt.device.
systemd[1]: Dependency failed for Cryptography Setup for sdb1_crypt.
systemd[1]: systemd-cryptsetup@sdb1_crypt.service: Job
systemd-cryptsetup@sdb1_crypt.service/start failed with result 'dependency'.
systemd[1]: dev-mapper-sdb1_crypt.device: Job
dev-mapper-sdb1_crypt.device/start failed with result 'timeout'.
systemd[1]: Reached target Remote File Systems (Pre).
systemd[1]: Startup finished in 12.294s (kernel) + 14.191s (userspace) =
26.485s.
systemd[1]: Starting LVM2 PV scan on device 254:4...
lvm[3268]: 1 logical volume(s) in volume group "blackbird" now active
systemd[1]: Started LVM2 PV scan on device 254:4.
systemd[1]: Starting File System Check on /dev/mapper/blackbird-ullu...
systemd-fsck[3282]: /dev/mapper/blackbird-ullu: clean, 11/121798656 files,
7928205/487165952 blocks
systemd[1]: Started File System Check on /dev/mapper/blackbird-ullu.
systemd[1]: Mounting /media/nas...
systemd[1]: Mounted /media/nas.
Note that although systemd-cryptsetup@sdb1_crypt service is considered
to have failed, it actually does its job and maps the encrypted volume:
● systemd-cryptsetup@sdb1_crypt.service - Cryptography Setup for sdb1_crypt
Loaded: loaded (/etc/crypttab; generated; vendor preset: enabled)
Active: active (exited) since Thu 2017-01-05 07:24:32 IST; 1h 6min ago
Docs: man:crypttab(5)
man:systemd-cryptsetup-generator(8)
man:systemd-cryptsetup@.service(8)
Process: 2729 ExecStart=/lib/systemd/systemd-cryptsetup attach sdb1_crypt
/dev/disk/by-uuid/ae6b9263-d63c-4515-b7ce-51e5cc4caa9f /root/blackbird-ullu
luks (code=exited, status=0/SUCCESS)
Main PID: 2729 (code=exited, status=0/SUCCESS)
Jan 05 07:24:31 ullu.lweshal.in systemd[1]: Starting Cryptography Setup for
sdb1_crypt...
Jan 05 07:24:31 ullu.lweshal.in systemd-cryptsetup[2729]: Set cipher aes, mode
xts-plain64, key size 256 bits for device
/dev/disk/by-uuid/ae6b9263-d63c-4515-b7ce-51e5cc4caa9f.
Jan 05 07:24:32 ullu.lweshal.in systemd[1]: Dependency failed for Cryptography
Setup for sdb1_crypt.
Jan 05 07:24:32 ullu.lweshal.in systemd[1]:
systemd-cryptsetup@sdb1_crypt.service: Job
systemd-cryptsetup@sdb1_crypt.service/start failed with result 'dependency'.
So now the volume is correctly mounted and everything works, the only
problem is the spurious wait and the timeout/dependency errors.
(c) I tried to set correct dependencies for the devices in my drop-in
override files. For example,
dev-disk-by\x2duuid-ae6b9263\x2dd63c\x2d4515\x2db7ce\x2d51e5cc4caa9f.device:
[Unit]
Requires=iscsi.service
After=iscsi.service
dev-mapper-sdb1_crypt.device:
[Unit]
Requires=iscsi.service
dev-disk-by\x2duuid-ae6b9263\x2dd63c\x2d4515\x2db7ce\x2d51e5cc4caa9f.device
After=iscsi.service
dev-disk-by\x2duuid-ae6b9263\x2dd63c\x2d4515\x2db7ce\x2d51e5cc4caa9f.device
dev-mapper-blackbird\x2dullu.device:
[Unit]
Requires=iscsi.service dev-mapper-sdb1_crypt.device
After=iscsi.service dev-mapper-sdb1_crypt.device
I later removed this last file and added a x-systemd.requires=foo.device
mount flag in /etc/fstab; I tried many combinations: one .device, both
.devices, requires=/dev/mapper/sdb1_crypt, requires=/dev/disk/by-uuid/…
and so on.
All of these attempts resulted in systemd detecting ordering cycles and
breaking them randomly—some of these situations worked, while others did
not. Just as an example, here's one such loop-breaking:
open-iscsi.service: Found ordering cycle on open-iscsi.service/start
open-iscsi.service: Found dependency on network-online.target/start
open-iscsi.service: Found dependency on networking.service/start
open-iscsi.service: Found dependency on local-fs.target/start
open-iscsi.service: Found dependency on lvm2-activation.service/start
open-iscsi.service: Found dependency on cryptsetup.target/start
open-iscsi.service: Found dependency on
systemd-cryptsetup@sdb1_crypt.service/start
open-iscsi.service: Found dependency on
dev-disk-by\x2duuid-ae6b9263\x2dd63c\x2d4515\x2db7ce\x2d51e5cc4caa9f.device/start
open-iscsi.service: Found dependency on open-iscsi.service/start
open-iscsi.service: Breaking ordering cycle by deleting job
network-online.target/start
network-online.target: Job network-online.target/start deleted to break
ordering cycle starting with open-iscsi.service/start
open-iscsi.service: Found ordering cycle on open-iscsi.service/start
open-iscsi.service: Found dependency on network-online.target/start
open-iscsi.service: Found dependency on networking.service/start
open-iscsi.service: Found dependency on local-fs.target/start
open-iscsi.service: Found dependency on lvm2-activation.service/start
open-iscsi.service: Found dependency on cryptsetup.target/start
open-iscsi.service: Found dependency on
systemd-cryptsetup@sdb1_crypt.service/start
open-iscsi.service: Found dependency on
dev-disk-by\x2duuid-ae6b9263\x2dd63c\x2d4515\x2db7ce\x2d51e5cc4caa9f.device/start
open-iscsi.service: Found dependency on open-iscsi.service/start
open-iscsi.service: Breaking ordering cycle by deleting job
local-fs.target/start
local-fs.target: Job local-fs.target/start deleted to break ordering cycle
starting with open-iscsi.service/start
open-iscsi.service: Found ordering cycle on open-iscsi.service/start
open-iscsi.service: Found dependency on network-online.target/start
open-iscsi.service: Found dependency on networking.service/start
open-iscsi.service: Found dependency on local-fs.target/start
open-iscsi.service: Found dependency on lvm2-activation.service/start
open-iscsi.service: Found dependency on cryptsetup.target/start
open-iscsi.service: Found dependency on
systemd-cryptsetup@sdb1_crypt.service/start
open-iscsi.service: Found dependency on
dev-disk-by\x2duuid-ae6b9263\x2dd63c\x2d4515\x2db7ce\x2d51e5cc4caa9f.device/start
open-iscsi.service: Found dependency on open-iscsi.service/start
open-iscsi.service: Breaking ordering cycle by deleting job
cryptsetup.target/start
cryptsetup.target: Job cryptsetup.target/start deleted to break ordering cycle
starting with open-iscsi.service/start
I tried various other things, including masking lvm2-activation.service
(safe because of lvmetad), overriding cryptsetup.target and explicitly
listing all the other systemd-cryptsetup@… services but the iscsi one,
overriding systemd-cryptsetup@sdb1_crypt.service altogether and removing
all references to cryptsetup.target, and so on. Nothing really worked.
Summary: I reduced the timeout and enabled lvmetad, and the volume was
correctly mounted after boot. I was not able to specify dependencies in
such a way as to remove the spurious timeout/dependency errors.
(I have not included open-iscsi configuration details here. The use of
lvmetad solved the "vgchange -aay" problem, and everything else related
to iscsi works fine. But I'm happy to provide more details if required,
please let me know.)
Thank you for your attention.
-- System Information:
Debian Release: 8.6
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.8.0-0.bpo.2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages open-iscsi depends on:
ii debconf [debconf-2.0] 1.5.56
ii init-system-helpers 1.22
ii libc6 2.19-18+deb8u6
ii libisns0 0.96-5~bpo8+1
ii libmount1 2.25.2-6
ii lsb-base 4.1+Debian13+nmu1
ii udev 230-7~bpo8+2
Versions of packages open-iscsi recommends:
ii busybox 1:1.22.0-9+deb8u1
open-iscsi suggests no packages.
--- End Message ---
--- Begin Message ---
Source: systemd
Source-Version: 235-1
We believe that the bug you reported is fixed in the latest version of
systemd, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 852...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Michael Biebl <bi...@debian.org> (supplier of updated systemd package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Tue, 10 Oct 2017 18:29:28 +0200
Source: systemd
Binary: systemd systemd-sysv systemd-container systemd-journal-remote
systemd-coredump systemd-tests libpam-systemd libnss-myhostname
libnss-mymachines libnss-resolve libnss-systemd libsystemd0 libsystemd-dev udev
libudev1 libudev-dev udev-udeb libudev1-udeb
Architecture: source
Version: 235-1
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers
<pkg-systemd-maintainers@lists.alioth.debian.org>
Changed-By: Michael Biebl <bi...@debian.org>
Description:
libnss-myhostname - nss module providing fallback resolution for the current
hostname
libnss-mymachines - nss module to resolve hostnames for local container
instances
libnss-resolve - nss module to resolve names via systemd-resolved
libnss-systemd - nss module providing dynamic user and group name resolution
libpam-systemd - system and service manager - PAM module
libsystemd-dev - systemd utility library - development files
libsystemd0 - systemd utility library
libudev-dev - libudev development files
libudev1 - libudev shared library
libudev1-udeb - libudev shared library (udeb)
systemd - system and service manager
systemd-container - systemd container/nspawn tools
systemd-coredump - tools for storing and retrieving coredumps
systemd-journal-remote - tools for sending and receiving remote journal logs
systemd-sysv - system and service manager - SysV links
systemd-tests - tests for systemd
udev - /dev/ and hotplug management daemon
udev-udeb - /dev/ and hotplug management daemon (udeb)
Closes: 805553 852534 865081 865450 867902 869995 870638
Changes:
systemd (235-1) unstable; urgency=medium
.
[ Michael Biebl ]
* New upstream version 235
- cryptsetup-generator: use remote-cryptsetup.target when _netdev is
present (Closes: #852534)
- tmpfiles: change btmp mode 0600 → 0660 (Closes: #870638)
- networkd: For IPv6 addresses do not treat IFA_F_DEPRECATED as not ready
(Closes: #869995)
- exec-util,conf-files: skip non-executable files in execute_directories()
(Closes: #867902)
- man: update udevadm -y/--sysname-match documentation (Closes: #865081)
- tmpfiles: silently ignore any path that passes through autofs
(Closes: #805553)
- shared: end string with % if one was found at the end of a expandible
string (Closes: #865450)
* Refresh patches
* Bump Build-Depends on libmount-dev to (>= 2.30)
* Install new modprobe.d config file
* Bump Standards-Version to 4.1.1
.
[ Martin Pitt ]
* Merge logind-kill-off autopkgtest into logind test.
This was horribly inefficient as a separate test (from commit
6bd0dab41e), as that cost two VM resets plus accompanying boots; and
this does not change any state thus does not require this kind of
isolation.
Checksums-Sha1:
068aed4d1f241aba3eb9f7e456e3ac6da5f2184d 4836 systemd_235-1.dsc
bda1bd1cb09bba798c3e125fb902f6c9e75308c4 6586406 systemd_235.orig.tar.gz
6ffc03a17d6d1426d14fd7d7903ae8203cdcabf1 131088 systemd_235-1.debian.tar.xz
69d6ae59b996922dcf32ee94bc09c3ea5540d516 9847 systemd_235-1_source.buildinfo
Checksums-Sha256:
e15a22e0baf47aecb2f7ff82d8f4d30d3f8bb3d266811f3cb17fb2f534edecd1 4836
systemd_235-1.dsc
25811f96f5a027bf2a4c9383495cf5b623e385d84da31e473cf375932b3e9c52 6586406
systemd_235.orig.tar.gz
5c562a1cb4e8e33775c0392e7fd21ad1ef9089360465e4f34879c052f07332c5 131088
systemd_235-1.debian.tar.xz
563e83c75e351c7751cd03f72fd93fd8252a39996461e23a2a5a3ee5ac7d028d 9847
systemd_235-1_source.buildinfo
Files:
476b8be7a9307403ab5690137b0f6fcd 4836 admin optional systemd_235-1.dsc
d53a925f1ca5b2e124de0a8aa65d0db2 6586406 admin optional systemd_235.orig.tar.gz
92120ac97d98db585c167ef7f1596788 131088 admin optional
systemd_235-1.debian.tar.xz
346ecc5d8b2c12de3c5f7d2c2855bfbe 9847 admin optional
systemd_235-1_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEECbOsLssWnJBDRcxUauHfDWCPItwFAlnc9asACgkQauHfDWCP
Itxsmg//aFhS5ut1RxV1DmNwjk0bA9P5KkWA4shECXApO4z51ymzJtvzWT1TvAzK
m+X2qWvtEF62LcG+amyEsSZPqyFcR1w1hkPEgs6lTH47w67TVT0RnJWEfW112aac
Gb/HJrR952F0i6yfQfydl4OoHHqNHUZ101Cb9iQ83eHpKk+uEW4lBeTsTFGWXTRv
gX/hveqByxmmt1+dFDxeQrgzDdHlJRHVEyKzHiOavfo+ewtvHJSk+aKaSeDDV984
tV2ppCyQxPL5qNKdF1Rx4G0mLR3gTehuYAVaWXWQocJGKSaAUyquQObX8q1f46dp
bkGpzFfAIG742klgY7HEIBo4MpYxyE5viIpxl/vKLrDB+S9rEU9B6ITgpt6F+xRB
EgPNj7UPvNYo3gipnQkmvlbF08xzQHQrNQczA92DK3K01gREflcRSqUMTDQVrN1i
qHM8MRMwFpvWEMmv8w+kbqitKR//8wSCqY0Lofzp8u0hPSnsfzL3i13bIK/aq5nn
dIU5HkfTT0wIvRg+HKXqnXfiX5l2rgNO0V2+4C1TygJfp7Fh+EWoH5QT+1wVYG0d
tSvVK1qpOKuKnocDGa4DGS61HVRk2RMxCXg8hvAky1MwiXmKfWq9q+xeEIZVL4PH
jsA1+6sY+GGRitQFAUXxlsLESYNKTQRphyHRZIh/Keqzz7zQuLU=
=Zg9z
-----END PGP SIGNATURE-----
--- End Message ---
_______________________________________________
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
