[no subject]

[Sheng Li Hung]

I am Mr.Sheng Li Hung I have a very profitable business proposition for you___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#890008: marked as done (init(8): Some corrections to the manual)

[Debian Bug Tracking System]

Your message dated Sat, 10 Feb 2018 03:11:54 +0100
with message-id <06d81777-180d-df59-b4de-310478079...@debian.org>
and subject line Re: Bug#890008: init(8): Some corrections to the manual
has caused the Debian Bug report #890008,
regarding init(8): Some corrections to the manual
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.)


-- 
890008: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890008
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: init
Version: 1.51
Severity: minor
Tags: patch

Dear Maintainer,

Test nr. 1: Remove space at end of lines.

122:it is signaled by \fBtelinit\fP to change the system's runlevel.  
177:tell \fBinit\fP to re-execute itself (preserving the state). No 
re-examining of 

#

Test nr. 2: Fix warning from man/groff

:330 (macro BR): only 1 argument, but more are expected

#

Test nr. 5: Change - to \(en if it is
a numeric range

83:Runlevels 7-9 are also valid, though not really documented. This is
226:.B 1-5

#

Test nr. 8: Protect . if not end of sentence

59:\fB0\(en6\fP and \fBS\fP (a.k.a. \fBs\fP).  The runlevel is
246:line a bit, so that it takes some more space on the stack. \fBInit\fP

#

Test nr. 25: Change a HYPHEN-MINUS (code 0x55, 2D) to a dash (minus) if it
matches " -[:alpha:]" or \(aq-[:alpha:] (for options)

184:is 5 seconds, but this can be changed with the \fB-t\fP option.
186:\fBtelinit -e\fP tells \fBinit\fP to change the environment
188:The argument of \fB-e\fP is either of the form \fIVAR\fP=\fIVAL\fP
245:The argument to \fB-z\fP is ignored. You can use this to expand the command

#

  Additionally:

  Sentences in the first created patch, that showed a wrong amount of
space between them, were separated ("man-pages(7)"), and a new patch
created.

  Patch:

--- init.8  2017-09-08 19:18:37.0 +
+++ init.8.new  2018-02-09 01:44:20.0 +
@@ -56,7 +56,7 @@ A \fIrunlevel\fP is a software configura
 only a selected group of processes to exist.  The processes spawned by
 \fBinit\fP for each of these runlevels are defined in the
 \fB/etc/inittab\fP file.  \fBInit\fP can be in one of eight runlevels:
-\fB0\(en6\fP and \fBS\fP (a.k.a. \fBs\fP).  The runlevel is
+\fB0\(en6\fP and \fBS\fP (a.k.a.\& \fBs\fP).  The runlevel is
 changed by having a privileged user run \fBtelinit\fP, which sends
 appropriate signals to \fBinit\fP, telling it which runlevel to change
 to.
@@ -80,8 +80,8 @@ the administrator performs maintenance a
 For more information,
 see the manpages for \fBshutdown\fP(8) and \fBinittab\fP(5).
 .PP
-Runlevels 7-9 are also valid, though not really documented. This is
-because "traditional" Unix variants don't use them.
+Runlevels 7\(en9 are also valid, though not really documented.
+This is because "traditional" Unix variants don't use them.
 .PP
 Runlevels \fIS\fP and \fIs\fP are the same.
 Internally they are aliases for the same runlevel.
@@ -119,7 +119,7 @@ provided that these files exist.
 .SH CHANGING RUNLEVELS
 After it has spawned all of the processes specified, \fBinit\fP waits
 for one of its descendant processes to die, a powerfail signal, or until
-it is signaled by \fBtelinit\fP to change the system's runlevel.  
+it is signaled by \fBtelinit\fP to change the system's runlevel.
 When one of the above three conditions occurs, it re-examines
 the \fB/etc/inittab\fP file.  New entries can be added to this file at
 any time.  However, \fBinit\fP still waits for one of the above three
@@ -174,18 +174,18 @@ tell \fBinit\fP to re-examine the \fB/et
 .IP "\fBS\fP or \fBs\fP"
 tell \fBinit\fP to switch to single user mode.
 .IP "\fBU\fP or \fBu\fP"
-tell \fBinit\fP to re-execute itself (preserving the state). No re-examining 
of 
-\fB/etc/inittab\fP file happens. Run level should be one of
-\fBSs0123456\fP
-otherwise request would be silently ignored.
+tell \fBinit\fP to re-execute itself (preserving the state).
+No re-examining of \fB/etc/inittab\fP file happens.
+Run level should be one of \fBSs0123456\fP otherwise request would be
+silently ignored.
 .PP
 \fBtelinit\fP can tell \fBinit\fP how long it should wait
 between sending processes the SIGTERM and SIGKILL signals.  The default
-is 5 seconds, but this can be changed with the \fB-t\fP option.
+is 5 seconds, but this can be changed with the \fB\-t\fP option.
 .PP
-\fBtelinit -e\fP tells \fBinit\fP to change the environment
+\fBtelinit \-e\fP tells \fBinit\fP to change the environment
 for processes it spawns.
-The argument of \fB-e\fP is either of the form \fIVAR\fP=\fIVAL\fP
+The argument of \fB\-e\fP is either of the 

Bug#890008: init(8): Some corrections to the manual

[Bjarni Ingi Gislason]

Package: init
Version: 1.51
Severity: minor
Tags: patch

Dear Maintainer,

Test nr. 1: Remove space at end of lines.

122:it is signaled by \fBtelinit\fP to change the system's runlevel.  
177:tell \fBinit\fP to re-execute itself (preserving the state). No 
re-examining of 

#

Test nr. 2: Fix warning from man/groff

:330 (macro BR): only 1 argument, but more are expected

#

Test nr. 5: Change - to \(en if it is
a numeric range

83:Runlevels 7-9 are also valid, though not really documented. This is
226:.B 1-5

#

Test nr. 8: Protect . if not end of sentence

59:\fB0\(en6\fP and \fBS\fP (a.k.a. \fBs\fP).  The runlevel is
246:line a bit, so that it takes some more space on the stack. \fBInit\fP

#

Test nr. 25: Change a HYPHEN-MINUS (code 0x55, 2D) to a dash (minus) if it
matches " -[:alpha:]" or \(aq-[:alpha:] (for options)

184:is 5 seconds, but this can be changed with the \fB-t\fP option.
186:\fBtelinit -e\fP tells \fBinit\fP to change the environment
188:The argument of \fB-e\fP is either of the form \fIVAR\fP=\fIVAL\fP
245:The argument to \fB-z\fP is ignored. You can use this to expand the command

#

  Additionally:

  Sentences in the first created patch, that showed a wrong amount of
space between them, were separated ("man-pages(7)"), and a new patch
created.

  Patch:

--- init.8  2017-09-08 19:18:37.0 +
+++ init.8.new  2018-02-09 01:44:20.0 +
@@ -56,7 +56,7 @@ A \fIrunlevel\fP is a software configura
 only a selected group of processes to exist.  The processes spawned by
 \fBinit\fP for each of these runlevels are defined in the
 \fB/etc/inittab\fP file.  \fBInit\fP can be in one of eight runlevels:
-\fB0\(en6\fP and \fBS\fP (a.k.a. \fBs\fP).  The runlevel is
+\fB0\(en6\fP and \fBS\fP (a.k.a.\& \fBs\fP).  The runlevel is
 changed by having a privileged user run \fBtelinit\fP, which sends
 appropriate signals to \fBinit\fP, telling it which runlevel to change
 to.
@@ -80,8 +80,8 @@ the administrator performs maintenance a
 For more information,
 see the manpages for \fBshutdown\fP(8) and \fBinittab\fP(5).
 .PP
-Runlevels 7-9 are also valid, though not really documented. This is
-because "traditional" Unix variants don't use them.
+Runlevels 7\(en9 are also valid, though not really documented.
+This is because "traditional" Unix variants don't use them.
 .PP
 Runlevels \fIS\fP and \fIs\fP are the same.
 Internally they are aliases for the same runlevel.
@@ -119,7 +119,7 @@ provided that these files exist.
 .SH CHANGING RUNLEVELS
 After it has spawned all of the processes specified, \fBinit\fP waits
 for one of its descendant processes to die, a powerfail signal, or until
-it is signaled by \fBtelinit\fP to change the system's runlevel.  
+it is signaled by \fBtelinit\fP to change the system's runlevel.
 When one of the above three conditions occurs, it re-examines
 the \fB/etc/inittab\fP file.  New entries can be added to this file at
 any time.  However, \fBinit\fP still waits for one of the above three
@@ -174,18 +174,18 @@ tell \fBinit\fP to re-examine the \fB/et
 .IP "\fBS\fP or \fBs\fP"
 tell \fBinit\fP to switch to single user mode.
 .IP "\fBU\fP or \fBu\fP"
-tell \fBinit\fP to re-execute itself (preserving the state). No re-examining 
of 
-\fB/etc/inittab\fP file happens. Run level should be one of
-\fBSs0123456\fP
-otherwise request would be silently ignored.
+tell \fBinit\fP to re-execute itself (preserving the state).
+No re-examining of \fB/etc/inittab\fP file happens.
+Run level should be one of \fBSs0123456\fP otherwise request would be
+silently ignored.
 .PP
 \fBtelinit\fP can tell \fBinit\fP how long it should wait
 between sending processes the SIGTERM and SIGKILL signals.  The default
-is 5 seconds, but this can be changed with the \fB-t\fP option.
+is 5 seconds, but this can be changed with the \fB\-t\fP option.
 .PP
-\fBtelinit -e\fP tells \fBinit\fP to change the environment
+\fBtelinit \-e\fP tells \fBinit\fP to change the environment
 for processes it spawns.
-The argument of \fB-e\fP is either of the form \fIVAR\fP=\fIVAL\fP
+The argument of \fB\-e\fP is either of the form \fIVAR\fP=\fIVAL\fP
 which sets variable \fIVAR\fP to value \fIVAL\fP,
 or of the form \fIVAR\fP
 (without an equality sign)
@@ -215,15 +215,16 @@ The system console. This is really inher
 if it is not set \fBinit\fP will set it to \fB/dev/console\fP by default.
 .SH BOOTFLAGS
 It is possible to pass a number of flags to \fBinit\fP from the
-boot monitor (eg. LILO). \fBInit\fP accepts the following flags:
+boot monitor (e.g.\& LILO).
+\fBInit\fP accepts the following flags:
 .TP 0.5i
 .B -s, S, single
-Single user mode boot. In this mode \fI/etc/inittab\fP is
-examined and the bootup rc scripts are usually run before
-the single user mode shell is started.
+Single user mode boot.
+In this mode \fI/etc/inittab\fP is examined and the bootup rc scripts
+are usually run before the single user mode shell is started.
 .PP
 .TP 0.5i
-.B 1-5
+.B 1\(en5
 Runlevel to 

Bug#889144: marked as done (stricter PIDfile handling breaks several daemons)

[Debian Bug Tracking System]

Your message dated Fri, 09 Feb 2018 22:52:12 +
with message-id 
and subject line Bug#889144: fixed in systemd 237-2
has caused the Debian Bug report #889144,
regarding stricter PIDfile handling breaks several daemons
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.)


-- 
889144: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889144
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 237-1
Severity: important
Tags: upstream

Hi!

The upstream commit db256aab13d8a89d583ecd2bacf0aca87c66effc "core: be 
stricter when handling PID files and MAINPID sd_notify() messages"
breaks several daemons in Debian.

Known issues exist for

  - munin-node https://bugs.debian.org/889073
  - ulogd2
  - dnsmasq https://lists.debian.org/debian-user/2018/01/msg01331.html

and possibly others.

Symptom is a timeout during service start, constant service restarts (if
configured) and log messages like:

Feb  2 14:22:49 HOST systemd[1]: ulogd2.service: Permission denied while 
opening PID file or unsafe symlink chain: /run/ulog/ulogd.pid
Feb  2 14:23:54 HOST systemd[1]: munin-node.service: Permission denied while 
opening PID file or unsafe symlink chain: /run/munin/munin-node.pid

Problem lies, as far as I understand the change, in the permissions of
the directory in which the PIDfile is created by the daemon. In all
cases it does not belong root:root but the respective service user:

HOST:/run# ls -ld ulog munin
drwxr-xr-x 2 munin root 100 Feb  2 14:50 munin
drwxr-xr-x 2 ulog  ulog  40 Feb  2 14:24 ulog

My quick'n'dirty workaround for munin was to change the PIDfile path to
just "/run" in both the systemd unit and the configuration file and for
ulogd2 I converted the unit from Type=forking to Type=simple, omitting
the PIDfile completely.

But this can only be a workaround in my opinion, because the upstream
change changes an assumption on how and where PIDfiles can work without
any prior notice. This needs to be changed to a non-fatal warning and
not an error, IMHO.

Grüße,
Sven.

-- Package-specific info:

-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 
'unstable'), (500, 'testing'), (200, 'experimental'), (1, 'experimental-debug')
Architecture: i386 (x86_64)
Foreign Architectures: amd64

Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), 
LANGUAGE=de_DE.utf8 (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.12-2
ii  libaudit11:2.8.2-1
ii  libblkid12.30.2-0.3
ii  libc62.26-6
ii  libcap2  1:2.25-1.2
ii  libcryptsetup12  2:2.0.0-1
ii  libgcrypt20  1.8.1-4
ii  libgpg-error01.27-5
ii  libidn11 1.33-2.1
ii  libip4tc01.6.1-2+b1
ii  libkmod2 25-1
ii  liblz4-1 0.0~r131-2+b1
ii  liblzma5 5.2.2-1.3
ii  libmount12.30.2-0.3
ii  libpam0g 1.1.8-3.6
ii  libseccomp2  2.3.1-2.1
ii  libselinux1  2.7-2
ii  libsystemd0  237-1
ii  mount2.30.2-0.3
ii  procps   2:3.3.12-3
ii  util-linux   2.30.2-0.3

Versions of packages systemd recommends:
ii  dbus1.12.2-1
ii  libpam-systemd  237-1

Versions of packages systemd suggests:
ii  policykit-10.105-18
pn  systemd-container  

Versions of packages systemd is related to:
pn  dracut   
ii  initramfs-tools  0.130
ii  udev 237-1

-- Configuration Files:
/etc/systemd/journald.conf changed [not included]
/etc/systemd/logind.conf changed [not included]
/etc/systemd/system.conf changed [not included]

-- debconf-show failed
--- End Message ---
--- Begin Message ---
Source: systemd
Source-Version: 237-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 889...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael Biebl  (supplier of updated systemd package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please 

Bug#889665: marked as done (udev: Please stop shipping debian/extra/rules/70-debian-uaccess.rules)

[Debian Bug Tracking System]

Your message dated Fri, 09 Feb 2018 22:52:12 +
with message-id 
and subject line Bug#889665: fixed in systemd 237-2
has caused the Debian Bug report #889665,
regarding udev: Please stop shipping debian/extra/rules/70-debian-uaccess.rules
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.)


-- 
889665: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889665
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: udev
Version: 236-3
Severity: normal
Tags: sid buster
Control: block -1 by 889136

Hi,

libu2f-udev ships (since #846359 was closed) udev rules granting access to U2F
devices, as maintained in the libu2f-host upstream.

A few udev rules present in 70-debian-uaccess.rules are missing upstream;
#889136 tracks this, and once it is resolved we should stop shipping 
U2F-specific
rules directly in udev.


Best,

  nicoo

-- Package-specific info:

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (900, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages udev depends on:
ii  adduser  3.116
ii  libacl1  2.2.52-3+b1
ii  libblkid12.30.2-0.3
ii  libc62.26-4
ii  libkmod2 25-1
ii  libselinux1  2.7-2
ii  libudev1 236-3
ii  lsb-base 9.20170808
ii  procps   2:3.3.12-3
ii  util-linux   2.30.2-0.3

udev recommends no packages.

udev suggests no packages.

Versions of packages udev is related to:
ii  systemd  236-3

-- debconf information excluded


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: systemd
Source-Version: 237-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 889...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael Biebl  (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: Fri, 09 Feb 2018 23:35:31 +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: 237-2
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers 

Changed-By: Michael Biebl 
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: 889144 889665
Changes:
 systemd (237-2) unstable; urgency=medium
 .
   * Drop debian/extra/rules/70-debian-uaccess.rules.
 Up-to-date udev rules for U2F devices are shipped in libu2f-udev nowadays.
 (Closes: #889665)
   * 

systemd_237-2_source.changes ACCEPTED into unstable

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 09 Feb 2018 23:35:31 +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: 237-2
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers 

Changed-By: Michael Biebl 
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: 889144 889665
Changes:
 systemd (237-2) unstable; urgency=medium
 .
   * Drop debian/extra/rules/70-debian-uaccess.rules.
 Up-to-date udev rules for U2F devices are shipped in libu2f-udev nowadays.
 (Closes: #889665)
   * service: relax PID file symlink chain checks a bit.
 Let's read the PID file after all if there's a potentially unsafe symlink
 chain in place. But if we do, then refuse taking the PID if its outside of
 the cgroup. (Closes: #889144)
Checksums-Sha1:
 42a25a70aca4c68f37a91964699b0c359d51374f 4847 systemd_237-2.dsc
 02bb23e925619c53888b9f8cc3ecc13156188218 134104 systemd_237-2.debian.tar.xz
 38d09fcd0a0d9a3f7098b7e65fe90b31601574ab 9973 systemd_237-2_source.buildinfo
Checksums-Sha256:
 ac589748103ad5e704cde8d6b69ce9a4b45370418b1486b4137c8bd20f1c0a13 4847 
systemd_237-2.dsc
 ed743c30614252caafb5572582858aab7014a2452429448c06543ea6b1431441 134104 
systemd_237-2.debian.tar.xz
 1668fc3b33b4f235a71b2c4eed6e1b0786dba006e6f6e6b24644c0ca2455152a 9973 
systemd_237-2_source.buildinfo
Files:
 dfeb1cdc2dd35abd871663227329c798 4847 admin optional systemd_237-2.dsc
 90279fd7bb8d221a61071c04956ecc51 134104 admin optional 
systemd_237-2.debian.tar.xz
 309c7ebe56c26d0cd6632b6a0fdd1c93 9973 admin optional 
systemd_237-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEECbOsLssWnJBDRcxUauHfDWCPItwFAlp+ImwACgkQauHfDWCP
Itz+OQ/9EgLy2/GsNV61+4CebTHkoyDVldQfJ3L2ziA58GqVmZfFJWIutnzjDlyv
9KIXl9VF+qe852nEosjtwRoEyjXA4QKP5IJmG5y5yepwX74Qx9vHLAkk/kfKWo4e
65Dkx50MF4IgTL+T32UsAbNicojmPGjMSiDK4Sc5u73i3TMbXFJNcJ/bM/UeSERi
oUhvKPlpxN9LZVySYqpHvb2X2ukeb+HTRf48BBUsgGASKNyLNYEu917OHsDY6YB4
vGNZ3geel+kWL3H38Fsxklq/KjrlvAL02Sh2VY0UahrJFAHrbKedthOmqn2kLUdo
EOV2iOQGk+q28iFprFCK3jtbaR3vWtq0Bd3D8aWSq3vavP8Ok2gWyMVNjb4A58xv
+dZSbyn/iEU4pXu6HyaWoEIfbys9/cv9/RFdV8DHyHwUfPlO7vg9QBPyuNJWrzm7
htwkWtbqCpioSz/qncq3iyjl4qQ5iZ3k27tJ9w53JVM9NscrIBHceq2zrsrk/HBY
CjDmKpc2h4T6ttgS5AjgDE91rS02sLEQTU6dVQ0p48CrSvdR0FV39ISGfGEIkVB1
o8gr+FHruPdnzXJP7jRTOrQs7ez6F13S0gimfY5PUzMdN7uqrW25oeWOlro8bQdu
AS9+LAF8GUZWiKEhiwCbgQ+7TeMdfpOvZmtvZIXKzxzntoriWKs=
=Wf4M
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Accepted systemd 237-2 (source) into unstable

[Michael Biebl]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 09 Feb 2018 23:35:31 +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: 237-2
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers 

Changed-By: Michael Biebl 
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: 889144 889665
Changes:
 systemd (237-2) unstable; urgency=medium
 .
   * Drop debian/extra/rules/70-debian-uaccess.rules.
 Up-to-date udev rules for U2F devices are shipped in libu2f-udev nowadays.
 (Closes: #889665)
   * service: relax PID file symlink chain checks a bit.
 Let's read the PID file after all if there's a potentially unsafe symlink
 chain in place. But if we do, then refuse taking the PID if its outside of
 the cgroup. (Closes: #889144)
Checksums-Sha1:
 42a25a70aca4c68f37a91964699b0c359d51374f 4847 systemd_237-2.dsc
 02bb23e925619c53888b9f8cc3ecc13156188218 134104 systemd_237-2.debian.tar.xz
 38d09fcd0a0d9a3f7098b7e65fe90b31601574ab 9973 systemd_237-2_source.buildinfo
Checksums-Sha256:
 ac589748103ad5e704cde8d6b69ce9a4b45370418b1486b4137c8bd20f1c0a13 4847 
systemd_237-2.dsc
 ed743c30614252caafb5572582858aab7014a2452429448c06543ea6b1431441 134104 
systemd_237-2.debian.tar.xz
 1668fc3b33b4f235a71b2c4eed6e1b0786dba006e6f6e6b24644c0ca2455152a 9973 
systemd_237-2_source.buildinfo
Files:
 dfeb1cdc2dd35abd871663227329c798 4847 admin optional systemd_237-2.dsc
 90279fd7bb8d221a61071c04956ecc51 134104 admin optional 
systemd_237-2.debian.tar.xz
 309c7ebe56c26d0cd6632b6a0fdd1c93 9973 admin optional 
systemd_237-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEECbOsLssWnJBDRcxUauHfDWCPItwFAlp+ImwACgkQauHfDWCP
Itz+OQ/9EgLy2/GsNV61+4CebTHkoyDVldQfJ3L2ziA58GqVmZfFJWIutnzjDlyv
9KIXl9VF+qe852nEosjtwRoEyjXA4QKP5IJmG5y5yepwX74Qx9vHLAkk/kfKWo4e
65Dkx50MF4IgTL+T32UsAbNicojmPGjMSiDK4Sc5u73i3TMbXFJNcJ/bM/UeSERi
oUhvKPlpxN9LZVySYqpHvb2X2ukeb+HTRf48BBUsgGASKNyLNYEu917OHsDY6YB4
vGNZ3geel+kWL3H38Fsxklq/KjrlvAL02Sh2VY0UahrJFAHrbKedthOmqn2kLUdo
EOV2iOQGk+q28iFprFCK3jtbaR3vWtq0Bd3D8aWSq3vavP8Ok2gWyMVNjb4A58xv
+dZSbyn/iEU4pXu6HyaWoEIfbys9/cv9/RFdV8DHyHwUfPlO7vg9QBPyuNJWrzm7
htwkWtbqCpioSz/qncq3iyjl4qQ5iZ3k27tJ9w53JVM9NscrIBHceq2zrsrk/HBY
CjDmKpc2h4T6ttgS5AjgDE91rS02sLEQTU6dVQ0p48CrSvdR0FV39ISGfGEIkVB1
o8gr+FHruPdnzXJP7jRTOrQs7ez6F13S0gimfY5PUzMdN7uqrW25oeWOlro8bQdu
AS9+LAF8GUZWiKEhiwCbgQ+7TeMdfpOvZmtvZIXKzxzntoriWKs=
=Wf4M
-END PGP SIGNATURE-


___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Processing of systemd_237-2_source.changes

[Debian FTP Masters]

systemd_237-2_source.changes uploaded successfully to localhost
along with the files:
  systemd_237-2.dsc
  systemd_237-2.debian.tar.xz
  systemd_237-2_source.buildinfo

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Processed: Bug #889665 in systemd marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #889665 [udev] udev: Please stop shipping 
debian/extra/rules/70-debian-uaccess.rules
Added tag(s) pending.

-- 
889665: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889665
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Processed: fixed 878811 in 236-1, tagging 878811, closing 878811

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> fixed 878811 236-1
Bug #878811 [systemd] dummy interface in bridge sticks in "configuring", 
leading to degraded system
Marked as fixed in versions systemd/236-1.
> tags 878811 - moreinfo
Bug #878811 [systemd] dummy interface in bridge sticks in "configuring", 
leading to degraded system
Removed tag(s) moreinfo.
> close 878811
Bug #878811 [systemd] dummy interface in bridge sticks in "configuring", 
leading to degraded system
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
878811: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878811
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Processed: Bug #889144 in systemd marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #889144 [systemd] stricter PIDfile handling breaks several daemons
Added tag(s) pending.

-- 
889144: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889144
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers