Your message dated Tue, 02 Jan 2018 00:19:47 +0000
with message-id <e1ewaj1-000fqg...@fasolo.debian.org>
and subject line Bug#885061: fixed in systemd 236-2
has caused the Debian Bug report #885061,
regarding systemd-timesyncd.service fails to start if static user is removed,
but group is retained
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.)
--
885061: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885061
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 236-1
Severity: normal
Hi,
Following the instructions in /usr/share/doc/systemd/NEWS.Debian.gz
DynamicUser=yes has been enabled for systemd-journal-upload.service,
systemd-journal-gatewayd.service and systemd-timesyncd.service.
This means we no longer need to statically allocate a systemd-journal-upload,
systemd-journal-gateway and systemd-timesync user and you can now safely
remove those system users.
I removed the static systemd-timesync user and rebooted the system, after
which systemd-timesyncd.service failed to start.
When I removed the static systemd-timesync group as well, and rebooted
again, systemd-timesyncd.service worked fine.
(I don't use systemd-journal-{upload,gatewayd}.service, so I don't know if
this applies to these services as well.)
Best regards,
Martin
-- Package-specific info:
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing'), (200, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.13.0-1-amd64 (SMP w/12 CPU cores)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages systemd depends on:
ii adduser 3.116
ii libacl1 2.2.52-3+b1
ii libapparmor1 2.11.1-4
ii libaudit1 1:2.8.2-1
ii libblkid1 2.30.2-0.1
ii libc6 2.25-3
ii libcap2 1:2.25-1.2
ii libcryptsetup4 2:1.7.5-1
ii libgcrypt20 1.8.1-4
ii libgpg-error0 1.27-5
ii libidn11 1.33-2.1
ii libip4tc0 1.6.1-2+b1
ii libkmod2 24-1
ii liblz4-1 0.0~r131-2+b1
ii liblzma5 5.2.2-1.3
ii libmount1 2.30.2-0.1
ii libpam0g 1.1.8-3.6
ii libseccomp2 2.3.1-2.1
ii libselinux1 2.7-2
ii libsystemd0 236-1
ii mount 2.30.2-0.1
ii procps 2:3.3.12-3
ii util-linux 2.30.2-0.1
Versions of packages systemd recommends:
ii dbus 1.12.2-1
ii libpam-systemd 236-1
Versions of packages systemd suggests:
ii policykit-1 0.105-18
ii systemd-container 236-1
Versions of packages systemd is related to:
pn dracut <none>
ii initramfs-tools 0.130
ii udev 236-1
-- Configuration Files:
/etc/systemd/logind.conf changed [not included]
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: systemd
Source-Version: 236-2
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 885...@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, 02 Jan 2018 00:35:14 +0100
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: 236-2
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: 869354 884506 885061 885201
Changes:
systemd (236-2) unstable; urgency=medium
.
* Downgrade priority of libudev1 to optional.
This makes it compliant with recent versions of debian-policy which
recommends to use priority optional for library packages.
* Clarify NEWS entry about removal of system users.
Mention in the recent NEWS entry that the associated system groups
should be removed as well. (Closes: #885061)
* cryptsetup-generator: Don't mistake NULL input as OOM.
Fixes systemd-cryptsetup-generator failing to run during boot.
(Closes: #885201)
* analyze: Use normal bus connection for "plot" verb.
Fixes "systemd-analyze plot" failing to run as root. (Closes: #884506)
* Stop re-enabling systemd services on every upgrade.
This was done so changes to the [Install] section would be applied on
upgrades. Forcefully re-enabling a service might overwrite local
modifications though and thus far, none of the affected services did
actually change its [Install] section. So remove this code from the
maintainer scripts as it was apparently doing more harm then good.
(Closes: #869354)
Checksums-Sha1:
d7b2f64226a44e3769b33c7430732e11eec6aac1 4835 systemd_236-2.dsc
23adc68a90af14a07ac2ad7a51acfc036b2fc658 134036 systemd_236-2.debian.tar.xz
00b993ae6d2a928e83ededc2ec4c133aeb887ebb 9841 systemd_236-2_source.buildinfo
Checksums-Sha256:
c6a65a58c35b3834c6a2363827068abdb7c953a704c1ee201bd85d62d48f0a90 4835
systemd_236-2.dsc
192aabf8bb46c52ad733397711121a25a23297825859264fa920db7bf2fd91c6 134036
systemd_236-2.debian.tar.xz
9cec9948373dc5de70c5ca52b5406ab75ba8e9ad09a94aa0899c82eaefcbe0d6 9841
systemd_236-2_source.buildinfo
Files:
088110ee812577c16b8fc2691bad3b09 4835 admin optional systemd_236-2.dsc
b14cbb6385bd24c611342394f6f58eb3 134036 admin optional
systemd_236-2.debian.tar.xz
d3b0191bbb993d063818bc77abb90784 9841 admin optional
systemd_236-2_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEECbOsLssWnJBDRcxUauHfDWCPItwFAlpKy3wACgkQauHfDWCP
ItzichAAliMBJm7SJAvFK8PtRU34RxKy/kfp7jHdz8xPO8g4HoSJcdeaArbtA0vC
QA2Cw26W+bZ3+8hZHqkqGk8Y8aTYNRU+WP7rKpVdl89QKn54vccGJWZxsC/2H5PL
0S5FukQsVXA+gRj6KmpE0ElajzGODyXaZS6jFBtEgIaI6L++VxaPBC9/9SXP77JI
tC9ZYVHTNm/HhNJZlDZaZXInwXq+vGzR+nD/1DLFYgT2Cs15/dQi6W55V/OoNtuB
W+ttAMRwEWhonm14k+tvRCDOWKMSimjif0DhDqe21uGgcfaBV5wriEg/+I6g41ha
ScoXtwwhYqcY5ksd9VyqkY7hkn0rrsNvmMI5KP58OYYHYcuelbEZmv08wngidarK
V4wIMsAktRvq11YMh+FUHPUPS1oLRrlqSZc2unRtKiwYSFUHMyIRSyQVxDmXVn/G
My2ij98tdEefvOOrlVXF638oDDIaXVg8EbnibT3WCQZSPxL7Z1hs9hjJeXzoHtpa
AyOpPjmYe3LAJJ5bp2digPrBaSDlakgoKSnwAqphkP2KuHZps6GidMfpKj+NMy3I
62E6G2MbTgro3ZtppN8DjOfsqce610pIoKedpeE7A82YtqZnYDopCzUk1PiKzHlU
AhkxXyqQEy3PS/l1DQYjQUpI0N8wI+VCLlHgfk+sV99k7z6rRr0=
=I/OL
-----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
