Processed: Re: Bug#884784: systemd-network segfaults

Processing commands for cont...@bugs.debian.org: > forwarded 884784 https://github.com/systemd/systemd/issues/7760 Bug #884784 [systemd] systemd-network segfaults Set Bug forwarded-to-address to 'https://github.com/systemd/systemd/issues/7760'. > tags 884784 + upstream Bug #884784 [systemd]

Re: problems with pkg systemd

Am 18.01.2018 um 15:59 schrieb Matthieu Castay: > Hi > > I installed a new debian buster and  the systemd-timesync did not start. > I had to create user & group manualy to make systemd-timesync able to start > > user : > systemd-timesync:x:121:126:systemd Time >

Bug#887456: init-system-helpers: deb-systemd-helper does not honor the same package-relevant unit paths as systemd

On Wed, Jan 17, 2018 at 9:44 PM, Michael Biebl wrote: > Am 17.01.2018 um 11:35 schrieb Guillem Jover: >> --- a/script/deb-systemd-helper >> +++ b/script/deb-systemd-helper >> @@ -122,6 +122,8 @@ sub find_unit { >> $service_path = "/etc/systemd/system/$scriptname"; >>

problems with pkg systemd

Hi I installed a new debian buster and the systemd-timesync did not start. I had to create user & group manualy to make systemd-timesync able to start user : systemd-timesync:x:121:126:systemd Time Synchronization,,,:/run/systemd:/usr/sbin/nologin group : systemd-timesync:x:126: Thanks

Bug#887396: systemd-timesyncd.service: Start request repeated too quickly.

Am 18.01.2018 um 05:26 schrieb Andre Verwijs: > additional information: > >   > > /etc/passwd should have this line by default : > > systemd-timesync:x:100:102:NTP Time sync:/sbin/nologin > >   > > to set user/group and to start systemd-timesyncd.service at boot. Adding this user statically

Bug#887556: non deterministic behavior of network-online.target

On 01/17/18 23:00, Michael Biebl wrote: > Am 17.01.2018 um 22:11 schrieb Michael Biebl: > >> It's not systemd that pulls in network-online.target. You should contact >> the ifupdown maintainers why apparently network-online.target does not >> work for you. > > btw, in your syslog.fail, it seems

Bug#887456: init-system-helpers: deb-systemd-helper does not honor the same package-relevant unit paths as systemd

Am 17.01.2018 um 11:35 schrieb Guillem Jover: > --- a/script/deb-systemd-helper > +++ b/script/deb-systemd-helper > @@ -122,6 +122,8 @@ sub find_unit { > $service_path = "/etc/systemd/system/$scriptname"; > } elsif (-f "/lib/systemd/system/$scriptname") { > $service_path =

Bug#887556: non deterministic behavior of network-online.target

Am 17.01.2018 um 22:11 schrieb Michael Biebl: > It's not systemd that pulls in network-online.target. You should contact > the ifupdown maintainers why apparently network-online.target does not > work for you. btw, in your syslog.fail, it seems like network-online.target is not started at all.

Bug#887556: non deterministic behavior of network-online.target

Am 17.01.2018 um 21:39 schrieb Vladislav Kurz: > Package: systemd > Version: 232-25+deb9u1 > Severity: normal > > Hello, > > This is a followup to archived bug #870361 > > I have been installing new servers with similar setup as last time, and > ran into the same problem. I think I have

Processed: Re: systemd should depend on e2fsprogs explicitly

Processing control commands: > severity -1 minor Bug #887250 [systemd] systemd should depend on e2fsprogs explicitly Severity set to 'minor' from 'normal' -- 887250: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887250 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#887250: systemd should depend on e2fsprogs explicitly

Control: severity -1 minor I think thus far, nobody has done the analysis part for systemd. On Sun, Jan 14, 2018 at 08:11:47PM +0100, Helmut Grohne wrote: > /bin/journalctl contains chattr. According to file it is a ELF 64-bit LSB > shared object, x86-64, version 1 (SYSV) >

Bug#887250: systemd should depend on e2fsprogs explicitly

Am 14.01.2018 um 20:11 schrieb Helmut Grohne: > * Add e2fsprogs to Depends. > * Add e2fsprogs to Recommends. A recommends will probably not work for systemd to ensure that e2fsprogs is by default installed alongside systemd. It's the same problem as discussed in #887343 where Recommends are not

Bug#887501: systemctl status should not use --pager

Hi Guido, for all my replies, keep in mind, that I don't have any idea what serverspec is or does... Am 17.01.2018 um 15:25 schrieb Guido Günther: > On Wed, Jan 17, 2018 at 02:59:07PM +0100, Michael Biebl wrote: >> Am 17.01.2018 um 14:15 schrieb Guido Günther: >> Hm, I'm not quite convinced we

Processed: mkosi e2fsprogs dep fixed in git

Processing commands for cont...@bugs.debian.org: > tags 887213 + pending Bug #887213 [mkosi] mkosi should depend on e2fsprogs explicitly Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 887213:

Bug#887501: systemctl status should not use --pager

Hi Michael, On Wed, Jan 17, 2018 at 02:59:07PM +0100, Michael Biebl wrote: > Am 17.01.2018 um 14:15 schrieb Guido Günther: > > Package: init-system-helpers > > Version: 1.51 > > Severity: normal > > Tags: patch > > > > Hi, > > systemctl status should be invoked with --no-pager, otherwise it might

Bug#887501: systemctl status should not use --pager

Am 17.01.2018 um 14:15 schrieb Guido Günther: > Package: init-system-helpers > Version: 1.51 > Severity: normal > Tags: patch > > Hi, > systemctl status should be invoked with --no-pager, otherwise it might > hang on non-interactive command. This was observed running serverspec's > >describe

Bug#887501: systemctl status should not use --pager

Package: init-system-helpers Version: 1.51 Severity: normal Tags: patch Hi, systemctl status should be invoked with --no-pager, otherwise it might hang on non-interactive command. This was observed running serverspec's describe service('systemd-timesyncd') do it { should be_running }

Bug#887456: init-system-helpers: deb-systemd-helper does not honor the same package-relevant unit paths as systemd

On Wed, 2018-01-17 at 03:20:03 +0100, Michael Biebl wrote: > Am 16.01.2018 um 20:02 schrieb Guillem Jover: > > Source: init-system-helpers > > Source-Version: 1.51 > > Severity: normal > > Tags: patch > > The current list of paths honored by deb-systemd-helper does not match > > the one in

systemd 236-3 MIGRATED to testing

FYI: The status of the systemd source package in Debian's testing distribution has changed. Previous version: 236-2 Current version: 236-3 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive

Bug#883877: rsyslog: fails to configure, dpkg --configure exits with error

2018-01-17 4:24 GMT+02:00 Michael Biebl : > On Tue, 19 Dec 2017 06:55:34 +0100 Michael Biebl wrote: >> Am 19.12.2017 um 02:18 schrieb Martin-Éric Racine: >> > 2017-12-19 2:02 GMT+02:00 Michael Biebl : >> >> Am 18.12.2017 um 20:07 schrieb

Bug#883877: rsyslog: fails to configure, dpkg --configure exits with error

On Tue, 19 Dec 2017 06:55:34 +0100 Michael Biebl wrote: > Am 19.12.2017 um 02:18 schrieb Martin-Éric Racine: > > 2017-12-19 2:02 GMT+02:00 Michael Biebl : > >> Am 18.12.2017 um 20:07 schrieb Martin-Éric Racine: > >>> 2017-12-18 2:08 GMT+02:00 Michael Biebl

Bug#886908: systemd enabled services unable to access shares

Am 11.01.2018 um 07:54 schrieb Hannu Laitinen: > Package: systemd > Version: 236-2 Can you please upgrade to 236-3, reboot and then test again and report back with your findings. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?

Bug#887456: init-system-helpers: deb-systemd-helper does not honor the same package-relevant unit paths as systemd

Hi Guillem Am 16.01.2018 um 20:02 schrieb Guillem Jover: > Source: init-system-helpers > Source-Version: 1.51 > Severity: normal > Tags: patch > > Hi! > > The current list of paths honored by deb-systemd-helper does not match > the one in systemd [L]. That's fine for several of them because

Bug#887396: marked as done (systemd-timesyncd.service: Start request repeated too quickly.)

Your message dated Tue, 16 Jan 2018 12:08:32 +0100 with message-id and subject line Re: Bug#887396: systemd-timesyncd.service: Start request repeated too quickly. has caused the Debian Bug report #887396, regarding systemd-timesyncd.service: Start

Bug#887396: systemd-timesyncd.service: Start request repeated too quickly.

Am 16.01.2018 um 10:55 schrieb André Verwijs: > > libnss-systemd  installed. > > "getent passwd systemd-timesync" says: > > systemd-timesync:*:62583:62583:Dynamic User:/:/sbin/nologin Does this problem persist after a reboot? What is the output of systemctl status systemd-timesyncd.service

Bug#887396: systemd-timesyncd.service: Start request repeated too quickly.

libnss-systemd installed. "getent passwd systemd-timesync" says: systemd-timesync:*:62583:62583:Dynamic User:/:/sbin/nologin .. Op 15-01-18 om 23:13 schreef Michael Biebl: Am 15.01.2018 um 21:57 schrieb Andre Verwijs: Package: systemd Version: 236-2 Severity: important Tags: upstream

Bug#887419: marked as done (systemd: should depend on udev)

Your message dated Tue, 16 Jan 2018 10:11:43 +0100 with message-id <713d1121-6570-1a56-9aa1-fd7ada391...@debian.org> and subject line Re: systemd: should depend on udev has caused the Debian Bug report #887419, regarding systemd: should depend on udev to be marked as done. This means that you

Bug#887419: systemd: should depend on udev

Package: systemd Version: 232-25+deb9u1 Severity: normal On a vm at linode.com /home wouldn't be mounted (mount would hang forever with x-systemd.automount and abort leading to sulogin without it) and swap wouldn't be enabled when udev wasn't installed. udev was in "rc" state, so maybe a "dpkg

Bug#887343: systemd-timesyncd does not start with DynamicUser=yes

Michael Biebl [2018-01-16 7:41 +0100]: > Even with this fix though, we should imho make sure to have > libnss-systemd installed by default. > See the problem with Recommends and the initial bootstrap I mentioned > earlier. > What are we going to do about this? Hmm, in Debian I don't think we

Bug#887343: systemd-timesyncd does not start with DynamicUser=yes

Am 15.01.2018 um 23:58 schrieb Felipe Sateler: > Control: tags -1 patch fixed-upstream > > On Mon, Jan 15, 2018 at 10:42 AM, Felipe Sateler wrote: >> It appears timesyncd wants to do this to support being run as root and then >> dropping privileges. However, this will fail

Processed: Re: Bug#887343: systemd-timesyncd does not start with DynamicUser=yes

Processing control commands: > tags -1 patch fixed-upstream Bug #887343 [systemd] systemd-timesyncd does not start with DynamicUser=yes Added tag(s) patch and fixed-upstream. -- 887343: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887343 Debian Bug Tracking System Contact

Bug#887343: systemd-timesyncd does not start with DynamicUser=yes

Control: tags -1 patch fixed-upstream On Mon, Jan 15, 2018 at 10:42 AM, Felipe Sateler wrote: > Control: forwarded -1 https://github.com/systemd/systemd/issues/7883 > > On Mon, Jan 15, 2018 at 8:57 AM, Martin Pitt wrote: >> >> Guido Günther [2018-01-15

Bug#887396: systemd-timesyncd.service: Start request repeated too quickly.

Am 15.01.2018 um 21:57 schrieb Andre Verwijs: > Package: systemd > Version: 236-2 > Severity: important > Tags: upstream > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where appropriate *** > >* What led up to the situation? >* What exactly did you do

Hello Dear

I am Miss Zenab Warlord Ibrahim Coulibaly 24 years old female from the Republic of Ivory Coast, am the Daughter of Late Chief Sgt.Warlord Ibrahim Coulibaly who died on 28 April 2011 following a fight with the Republican Forces. My father of blessed memory deposited the sum of US$ 27.5 Million

Bug#887343: systemd-timesyncd does not start with DynamicUser=yes

Control: forwarded -1 https://github.com/systemd/systemd/issues/7883 On Mon, Jan 15, 2018 at 8:57 AM, Martin Pitt wrote: > Guido Günther [2018-01-15 12:14 +0100]: > > > > This seems to be caused by the fact that libnss-systemd is not a hard > > > > dependency of systemd. I'm

Processed: Re: Bug#887343: systemd-timesyncd does not start with DynamicUser=yes

Processing control commands: > forwarded -1 https://github.com/systemd/systemd/issues/7883 Bug #887343 [systemd] systemd-timesyncd does not start with DynamicUser=yes Set Bug forwarded-to-address to 'https://github.com/systemd/systemd/issues/7883'. -- 887343:

Bug#887343: systemd-timesyncd does not start with DynamicUser=yes

Am 15.01.2018 um 12:57 schrieb Martin Pitt: > If timesyncd in particular somehow wants to resolve the systemd-timesyncd > system user in its own code, then that either should be fixed, or systemd > needs > to raise libnss-systemd to a Depends: for that particular bug/reason. grepping through the

Bug#887343: systemd-timesyncd does not start with DynamicUser=yes

Am 15.01.2018 um 12:57 schrieb Martin Pitt: > Note that *in general*, DynamicUser=yes does not *require* libnss-systemd. > Services start without it, the only effect is that showing the process with > tools like "ps" will not be able to resolve a dynamic user ID to a name - it > will just be shown

Bug#887343: systemd-timesyncd does not start with DynamicUser=yes (requires libnss-systemd)

Am 15.01.2018 um 12:55 schrieb Guido Günther: > Turning it into a dependency would probably be best. It might be > sufficient to have it as a dependency of systemd-sysv, not systemd > itself. Yes, the Recommends: libnss-systemd in systemd-sysv would be bumped to Depends: libnss-systemd. While

Bug#887293: marked as done (casync should depend on e2fsprogs explicitly)

Your message dated Mon, 15 Jan 2018 09:07:20 -0300 with message-id

Bug#887343: systemd-timesyncd does not start with DynamicUser=yes

Guido Günther [2018-01-15 12:14 +0100]: > > > This seems to be caused by the fact that libnss-systemd is not a hard > > > dependency of systemd. I'm not sure what the best solution is? Having a > > > service that is enabled by fails to start looks weird though. Maybe > > > providing a static user

Bug#887343: systemd-timesyncd does not start with DynamicUser=yes (requires libnss-systemd)

Hi Guido Am 15.01.2018 um 12:14 schrieb Guido Günther: > Hi, > On Mon, Jan 15, 2018 at 11:24:33AM +0100, Michael Biebl wrote: >> Am 15.01.2018 um 10:18 schrieb Guido Günther: >> It requires libnss-systemd, yes. Do you not have it installed? >> It's a recommends, so should be installed by default

Bug#887343: systemd-timesyncd does not start with DynamicUser=yes

Hi, On Mon, Jan 15, 2018 at 11:24:33AM +0100, Michael Biebl wrote: > Am 15.01.2018 um 10:18 schrieb Guido Günther: > > Package: systemd > > Version: 236-3 > > Severity: normal > > File: systemd-timesyncd.service > > > > Hi, > > on a newly installed (without installing recommends) system¹ > >

Bug#887343: systemd-timesyncd does not start with DynamicUser=yes

Package: systemd Version: 236-3 Severity: normal File: systemd-timesyncd.service Hi, on a newly installed (without installing recommends) system¹ systemd-timesyncd fails to start like $ systemctl status systemd-timesyncd ● systemd-timesyncd.service - Network Time Synchronization Loaded:

Bug#887250: systemd should depend on e2fsprogs explicitly

Hi Helmut Am 14.01.2018 um 20:11 schrieb Helmut Grohne: > Package: systemd > Version: 236-3 > User: helm...@debian.org > Usertags: nonessentiale2fsprogs > > Dear maintainer, > > We want to make removing e2fsprogs from installations possible. For standard > installations this is not useful, but

Bug#887250: systemd should depend on e2fsprogs explicitly

Am 14.01.2018 um 21:07 schrieb Michael Biebl: > Hi Helmut > > Am 14.01.2018 um 20:11 schrieb Helmut Grohne: >> /bin/journalctl contains chattr. According to file it is a ELF 64-bit LSB >> shared object, x86-64, version 1 (SYSV) >> /bin/systemd-tmpfiles contains chattr. According to file it is a

Bug#887293: casync should depend on e2fsprogs explicitly

Package: casync Version: 2-1 User: helm...@debian.org Usertags: nonessentiale2fsprogs Dear maintainer, We want to make removing e2fsprogs from installations possible. For standard installations this is not useful, but embedded applications and chroots benefit from such an option. For getting

Bug#887250: systemd should depend on e2fsprogs explicitly

Package: systemd Version: 236-3 User: helm...@debian.org Usertags: nonessentiale2fsprogs Dear maintainer, We want to make removing e2fsprogs from installations possible. For standard installations this is not useful, but embedded applications and chroots benefit from such an option. For getting

Bug#887213: mkosi should depend on e2fsprogs explicitly

Package: mkosi Version: 3+17-1 User: helm...@debian.org Usertags: nonessentiale2fsprogs Dear maintainer, We want to make removing e2fsprogs from installations possible. For standard installations this is not useful, but embedded applications and chroots benefit from such an option. For getting

Processed: Bug #882629: systemd: debian/copyright refers to the CC0 license by URL

Processing control commands: > tag -1 patch Bug #882629 [systemd] systemd: debian/copyright refers to the CC0 license by URL Added tag(s) patch. -- 882629: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882629 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#882629: Bug #882629: systemd: debian/copyright refers to the CC0 license by URL

Control: tag -1 patch Dear maintainers, Here is a commit solving this bug, please consider merging it. Best, nicoo commit 7133a44cc745a1dbeecba49cf5c287ed375b2ffd Author: Nicolas Braud-Santoni Date: Sun Jan 14 19:10:08 2018 +0100 debian/copyright: Refer to

Bug#886731: linux-image-4.9.0-4-amd64: DKMS sends system in suspend since linux-image-4.9.0-3-amd64

On Fri, 2018-01-12 at 01:12 +, Ben Hutchings wrote: > On Thu, 2018-01-11 at 12:25 +0100, Marc-Robin Wendt wrote: > > Hello Ben and Michael, > > > > thanks for taking time. Of course its DPMS. Sorry for the typo. > > > > Reproducing the bug turns out, it first appears in linux-image- > >

Bug#886908: VS: Bug#886908: systemd enabled services unable to access shares

Sorry for delay.. Am 11.01.2018 um 14:15 schrieb Hannu Laitinen: > Hello > > It doesn't matter if I use server with keyboard/monitor (which I > mainly > use) or SSH both have same issue. When you mean keyboard/monitor, I assume you meant that you login locally on a tty? - yes locally. > A

systemd_236-3~bpo9+1_source.changes ACCEPTED into stretch-backports

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 12 Jan 2018 10:39:46 +0100 Source: systemd Binary: systemd systemd-sysv systemd-container systemd-journal-remote systemd-coredump systemd-tests libpam-systemd libnss-myhostname libnss-mymachines libnss-resolve

Processing of systemd_236-3~bpo9+1_source.changes

systemd_236-3~bpo9+1_source.changes uploaded successfully to localhost along with the files: systemd_236-3~bpo9+1.dsc systemd_236-3~bpo9+1.debian.tar.xz systemd_236-3~bpo9+1_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

systemd-cron 1.5.12-2 MIGRATED to testing

FYI: The status of the systemd-cron source package in Debian's testing distribution has changed. Previous version: 1.5.12-1 Current version: 1.5.12-2 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will

Bug#886731: linux-image-4.9.0-4-amd64: DKMS sends system in suspend since linux-image-4.9.0-3-amd64

On Thu, 2018-01-11 at 12:25 +0100, Marc-Robin Wendt wrote: > Hello Ben and Michael, > > thanks for taking time. Of course its DPMS. Sorry for the typo. > > Reproducing the bug turns out, it first appears in linux-image-4.9.0-4- > amd64 and now linux-image-4.9.0-5-amd64. > > When I boot the

Bug#886811: marked as done (Can't do system-wide mounts/unmounts in a ssh sessions)

Your message dated Thu, 11 Jan 2018 16:19:14 + with message-id and subject line Bug#885325: fixed in systemd 236-3 has caused the Debian Bug report #885325, regarding Can't do system-wide mounts/unmounts in a ssh sessions to be marked as done. This means

systemd_236-3_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 11 Jan 2018 16:46:04 +0100 Source: systemd Binary: systemd systemd-sysv systemd-container systemd-journal-remote systemd-coredump systemd-tests libpam-systemd libnss-myhostname libnss-mymachines libnss-resolve

Processing of systemd_236-3_source.changes

systemd_236-3_source.changes uploaded successfully to localhost along with the files: systemd_236-3.dsc systemd_236-3.debian.tar.xz systemd_236-3_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) ___

Bug#886908: systemd enabled services unable to access shares

[please always CC the bug report] Am 11.01.2018 um 14:15 schrieb Hannu Laitinen: > Hello > > It doesn't matter if I use server with keyboard/monitor (which I mainly > use) or SSH both have same issue. When you mean keyboard/monitor, I assume you meant that you login locally on a tty? > A

Bug#886908: systemd enabled services unable to access shares

Am 11.01.2018 um 07:54 schrieb Hannu Laitinen: > Package: systemd > Version: 236-2 > Severity: important > > - My system starts with openvpn, plexmediaserver etc. After the system has > booted up I mount smb shares from vpn tunnel and files are accessable via > normal commandline and can

Bug#886731: linux-image-4.9.0-4-amd64: DKMS sends system in suspend since linux-image-4.9.0-3-amd64

Hello Ben and Michael, thanks for taking time. Of course its DPMS. Sorry for the typo. Reproducing the bug turns out, it first appears in linux-image-4.9.0-4- amd64 and now linux-image-4.9.0-5-amd64. When I boot the system from grub with old kernel linux-image-4.9.0-3- amd64 or

Bug#886908: systemd enabled services unable to access shares

Package: systemd Version: 236-2 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? - After system has booted up and systemd services have started, the applications are unable to access

Bug#886731: linux-image-4.9.0-4-amd64: DKMS sends system in suspend since linux-image-4.9.0-3-amd64

Control: tags -1 + moreinfo On Wed, 10 Jan 2018 18:12:46 + Ben Hutchings wrote: > Control: reassign -1 systemd > > On Tue, 2018-01-09 at 11:50 +0100, Marc-Robin Wendt wrote: > > Package: src:linux > > Version: 4.9.65-3+deb9u1 > > Severity: normal > > > > Dear

Processed: Re: Bug#886731: linux-image-4.9.0-4-amd64: DKMS sends system in suspend since linux-image-4.9.0-3-amd64

Processing control commands: > tags -1 + moreinfo Bug #886731 [systemd] linux-image-4.9.0-4-amd64: DKMS sends system in suspend since linux-image-4.9.0-3-amd64 Added tag(s) moreinfo. -- 886731: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886731 Debian Bug Tracking System Contact

Processed: Re: Bug#886731: linux-image-4.9.0-4-amd64: DKMS sends system in suspend since linux-image-4.9.0-3-amd64

Processing control commands: > reassign -1 systemd Bug #886731 [src:linux] linux-image-4.9.0-4-amd64: DKMS sends system in suspend since linux-image-4.9.0-3-amd64 Bug reassigned from package 'src:linux' to 'systemd'. No longer marked as found in versions linux/4.9.65-3+deb9u1. Ignoring request

Bug#886812: service: start/stop tries to use invalid systemd units when using socket templates

On Wed, 2018-01-10 at 12:23 +0100, Michael Biebl wrote: > Am 10.01.2018 um 09:57 schrieb Cyrill Troxler: > > Package: init-system-helpers > > Version: 1.48 > > > > I stumbled upon a issue with the start/stop triggers when using > > systemd > > socket templates on Debian stretch. I started

Processed: Re: Bug#886811: Can't do system-wide mounts/unmounts in a ssh sessions

Processing control commands: > reassign -1 systemd 236-1 Bug #886811 [openssh-server] Can't do system-wide mounts/unmounts in a ssh sessions Bug reassigned from package 'openssh-server' to 'systemd'. No longer marked as found in versions openssh/1:7.6p1-2. Ignoring request to alter fixed

Bug#886812: service: start/stop tries to use invalid systemd units when using socket templates

Am 10.01.2018 um 09:57 schrieb Cyrill Troxler: > Package: init-system-helpers > Version: 1.48 > > I stumbled upon a issue with the start/stop triggers when using systemd > socket templates on Debian stretch. I started getting unrelated error > messages when entering `service some_service start`

Bug#884994: systemd: shutdown does not send its warning messages when time is more than ten minutes

Hello, Fwiw, this behaviour makes sense to me. If you start a scheduled login 2 days in advance, sending a shutdown message every minute would not be helpful. Restricting that to the last ten minutes seems reasonable. How did sysvinit behave in that regard? As far as I remember, sysvinit

Bug#886812: service: start/stop tries to use invalid systemd units when using socket templates

Package: init-system-helpers Version: 1.48 I stumbled upon a issue with the start/stop triggers when using systemd socket templates on Debian stretch. I started getting unrelated error messages when entering `service some_service start` on a system which has a systemd socket template defined.

Bug#884994: systemd: shutdown does not send its warning messages when time is more than ten minutes

Am 08.01.2018 um 13:20 schrieb Christoph Pleger: > Hello, > >> >> This functionality has been reworked completely based on systemd-logind. >> >> Can you please test with a more recent version, like 232 from stable. > > at least, the problem does not occur in this form on a stretch machine, >

Bug#886654: marked as done (systemd : >12 user processes are left running even after checking out of an X Session)

Your message dated Wed, 10 Jan 2018 00:49:57 +0100 with message-id <4f86fb80-c3db-e5cc-3370-316161f9c...@debian.org> and subject line Re: Bug#886654: systemd : >12 user processes are left running even after checking out of an X Session has caused the Debian Bug report #886654, regarding systemd :

Processed: [bts-link] source package systemd

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package systemd > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user bts-link-upstr...@lists.alioth.debian.org Setting user to

[bts-link] source package systemd

# # bts-link upstream status pull for source package systemd # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org # remote status report for #885325 (http://bugs.debian.org/885325) # Bug title: systemd: Daemon start with

Bug#886654: systemd : >12 user processes are left running even after checking out of an X Session

Package: systemd Version: 232-25+deb9u1 Severity: normal -- Package-specific info: -- System Information: Debian Release: 9.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-4-amd64

Bug#884994: systemd: shutdown does not send its warning messages when time is more than ten minutes

Hello, This functionality has been reworked completely based on systemd-logind. Can you please test with a more recent version, like 232 from stable. at least, the problem does not occur in this form on a stretch machine, though I find it a disadvantage that no warning message is shown

systemd-cron_1.5.12-2_amd64.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 07 Jan 2018 13:05:44 +0100 Source: systemd-cron Binary: systemd-cron Architecture: source amd64 Version: 1.5.12-2 Distribution: unstable Urgency: medium Maintainer: Debian Systemd Maintainers

Processing of systemd-cron_1.5.12-2_amd64.changes

systemd-cron_1.5.12-2_amd64.changes uploaded successfully to localhost along with the files: systemd-cron_1.5.12-2.dsc systemd-cron_1.5.12-2.debian.tar.xz systemd-cron-dbgsym_1.5.12-2_amd64.deb systemd-cron_1.5.12-2_amd64.buildinfo systemd-cron_1.5.12-2_amd64.deb Greetings,

systemd 236-2 MIGRATED to testing

FYI: The status of the systemd source package in Debian's testing distribution has changed. Previous version: 236-1 Current version: 236-2 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive

systemd_236-2~bpo9+1_source.changes ACCEPTED into stretch-backports

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 06 Jan 2018 16:16:17 +0100 Source: systemd Binary: systemd systemd-sysv systemd-container systemd-journal-remote systemd-coredump systemd-tests libpam-systemd libnss-myhostname libnss-mymachines libnss-resolve

Processing of systemd_236-2~bpo9+1_source.changes

systemd_236-2~bpo9+1_source.changes uploaded successfully to localhost along with the files: systemd_236-2~bpo9+1.dsc systemd_236-2~bpo9+1.debian.tar.xz systemd_236-2~bpo9+1_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

Bug#886342: systemd-networkd: Unknown section 'Tap'. Ignoring.

On Thursday, 4 January 2018 19:54:41 CET Michael Biebl wrote: > Am 04.01.2018 um 19:30 schrieb Wolfgang Walter: > > Package: systemd > > Version: 236-2 > > > > Problem: since upgrading to 236-1 I get the following error: > > > > systemd-networkd:[810]: /etc/systemd/network/tunnel.netdev: :5:

Bug#886342: systemd-networkd: Unknown section 'Tap'. Ignoring.

Hello Michael, thanks for your answer. On Thursday, 4 January 2018 19:54:41 CET Michael Biebl wrote: > Am 04.01.2018 um 19:30 schrieb Wolfgang Walter: > > Package: systemd > > Version: 236-2 > > > > Problem: since upgrading to 236-1 I get the following error: > > > > systemd-networkd:[810]:

Bug#886342: systemd-networkd: Unknown section 'Tap'. Ignoring.

Am 04.01.2018 um 19:30 schrieb Wolfgang Walter: > Package: systemd > Version: 236-2 > > Problem: since upgrading to 236-1 I get the following error: > > systemd-networkd:[810]: /etc/systemd/network/tunnel.netdev: :5: Unknown > section 'Tap'. Ignoring. > Please share the complete file. Have

Bug#886342: systemd-networkd: Unknown section 'Tap'. Ignoring.

Package: systemd Version: 236-2 Problem: since upgrading to 236-1 I get the following error: systemd-networkd:[810]: /etc/systemd/network/tunnel.netdev: :5: Unknown section 'Tap'. Ignoring. The same problem exists with other kinds as VLAN MACVTAP I did not change these .netdev files, and I

[bts-link] source package systemd

# # bts-link upstream status pull for source package systemd # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org # remote status report for #885325 (http://bugs.debian.org/885325) # Bug title: systemd: Daemon start with

Bug#886131: cryptsetup freezes shutdown procedure

On Tue, 02 Jan 2018 16:27:18 +0100 Raphael wrote: > Package: cryptsetup > Version: 2:1.7.5-1 > Severity: normal > > Hi, > > Like https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792552 , my > shutdown process never ends due to 'stopping remaining crypto disks'. > Though,

Processed: Re: Bug#886156: systemd: crashes the system on reloading

Processing control commands: > reassign -1 linux-image-4.14.0-2-amd6 Bug #886156 [systemd] systemd: crashes the system on reloading Bug reassigned from package 'systemd' to 'linux-image-4.14.0-2-amd6'. Warning: Unknown package 'linux-image-4.14.0-2-amd6' Warning: Unknown package

Bug#886156: systemd: crashes the system on reloading

Control: reassign -1 linux-image-4.14.0-2-amd6 Am 02.01.2018 um 19:09 schrieb Kjö Hansi Glaz: > Package: systemd > Version: 236-2 > Severity: normal > > Dear Maintainer, > > When I upgrade the system with apt, the system often becomes > unresponsive after reloading systemd. Please find below

Bug#886156: systemd: crashes the system on reloading

Package: systemd Version: 236-2 Severity: normal Dear Maintainer, When I upgrade the system with apt, the system often becomes unresponsive after reloading systemd. Please find below the journal output when this happens: déc. 31 02:11:37 debian systemd[1]: Reloading. déc. 31 02:11:37 debian

Processed: reassign 886131 to udev, forcibly merging 791944 886131, affects 791944

Processing commands for cont...@bugs.debian.org: > reassign 886131 udev Bug #886131 [cryptsetup] cryptsetup freezes shutdown procedure Bug reassigned from package 'cryptsetup' to 'udev'. No longer marked as found in versions cryptsetup/2:1.7.5-1. Ignoring request to alter fixed versions of bug

Bug#851400: closed by Michael Biebl <bi...@debian.org> (Re: systemd: Going into suspend yust after waking up)

Hi, sorry, didn't see the last replay :-( It is not related to the lid switch - it happened also if the laptop was open all the time. The problem was also when stretch got stable, but didn't try it again in the last three months or so. I'll retest it in a few days. Best regards, Michael

Bug#885201: marked as done (systemd-cryptsetup-generator: incorrectly reports “Out of memory”)

Your message dated Tue, 02 Jan 2018 00:19:47 + with message-id and subject line Bug#885201: fixed in systemd 236-2 has caused the Debian Bug report #885201, regarding systemd-cryptsetup-generator: incorrectly reports “Out of memory” to be marked as done.

Bug#885061: marked as done (systemd-timesyncd.service fails to start if static user is removed, but group is retained)

Your message dated Tue, 02 Jan 2018 00:19:47 + with message-id 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

systemd_236-2_source.changes ACCEPTED into unstable

Accepted: -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

Processing of systemd_236-2_source.changes

systemd_236-2_source.changes uploaded successfully to localhost along with the files: systemd_236-2.dsc systemd_236-2.debian.tar.xz systemd_236-2_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) ___

Bug#878811: dummy interface in bridge sticks in "configuring", leading to degraded system

Control: tags -1 + moreinfo On Mon, 16 Oct 2017 21:57:15 +0200 Marc Haber wrote: > Package: systemd > Version: 235-2.0~zgSID+1 > Severity: normal > Tags: upstream patch > Forwarded: https://github.com/systemd/systemd/issues/6961 > > This is upstream issue 6961,

Processed: Re: dummy interface in bridge sticks in "configuring", leading to degraded system

Processing control commands: > tags -1 + moreinfo Bug #878811 [systemd] dummy interface in bridge sticks in "configuring", leading to degraded system Added tag(s) moreinfo. -- 878811: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878811 Debian Bug Tracking System Contact

<    1   2   3   4   5   6   7   8   9   10   >