Bug#854699: Shutdown fails with an encrypted filesystem on virtio device

2017-02-10 Thread Yuri D'Elia
On Fri, Feb 10 2017, Michael Biebl wrote: > Looks similar to > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848044 and a lot like > https://github.com/systemd/systemd/issues/1620 Uhm, it does. Aside from the fact that it's not at all harmless as mentioned, since the root fs is not unmounted.

Processing of systemd_232-17_amd64.changes

2017-02-10 Thread Debian FTP Masters
systemd_232-17_amd64.changes uploaded successfully to localhost along with the files: systemd_232-17.dsc systemd_232-17.debian.tar.xz libnss-myhostname-dbgsym_232-17_amd64.deb libnss-myhostname_232-17_amd64.deb libnss-mymachines-dbgsym_232-17_amd64.deb libnss-mymachines_232-17_amd64.deb

systemd_232-17_amd64.changes ACCEPTED into unstable

2017-02-10 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 10 Feb 2017 11:52:46 +0100 Source: systemd Binary: systemd systemd-sysv systemd-container systemd-journal-remote systemd-coredump libpam-systemd libnss-myhostname libnss-mymachines libnss-resolve libnss-systemd l

Bug#854392: marked as done (Run "make check" as root via autopkgtest)

2017-02-10 Thread Debian Bug Tracking System
Your message dated Fri, 10 Feb 2017 12:04:28 + with message-id and subject line Bug#854392: fixed in systemd 232-17 has caused the Debian Bug report #854392, regarding Run "make check" as root via autopkgtest to be marked as done. This means that you claim that the problem has been dealt with

Bug#854396: marked as done (test_exec_privatenetwork is not run due to missing ip)

2017-02-10 Thread Debian Bug Tracking System
Your message dated Fri, 10 Feb 2017 12:04:28 + with message-id and subject line Bug#854396: fixed in systemd 232-17 has caused the Debian Bug report #854396, regarding test_exec_privatenetwork is not run due to missing ip to be marked as done. This means that you claim that the problem has be

Bug#854394: marked as done (test_exec_capabilityboundingset is not run due to missing capsh)

2017-02-10 Thread Debian Bug Tracking System
Your message dated Fri, 10 Feb 2017 12:04:28 + with message-id and subject line Bug#854394: fixed in systemd 232-17 has caused the Debian Bug report #854394, regarding test_exec_capabilityboundingset is not run due to missing capsh to be marked as done. This means that you claim that the prob

Bug#854805: systemd: dbus interraction problems leading to timeouts

2017-02-10 Thread Vincent Danjean
Le 10/02/2017 à 16:47, Vincent Danjean a écrit : > Looking at the logs ("journalctl -b"), the first errors I see are: Here is the start of "journalctl -b" (got as: socat EXEC:"journalctl --no-pager -b",pty GOPEN:boot.log so "less -R boot.log" show colors) Regards, Vincent -- Vincent D

Bug#854814: Fails to start systemd-resolved

2017-02-10 Thread Yuri D'Elia
Package: systemd Version: 232-17 Severity: normal With the update to 232-17, systemd-resolved fails to start with the following error: Feb 10 17:46:31 test systemd[1]: Starting Network Name Resolution... -- Subject: Unit systemd-resolved.service has begun start-up -- Defined-By: systemd -- Supp

dh-systemd seems not to support multiple service units

2017-02-10 Thread Dererk
Dear pkg-systemd Maintainers, I've been trying to deliver a package that has a mix of enabled/disable and started/not started service units. The situation I encounter seems to be reflected at the manpage, when calling dh_systemd_enable, quoting: "Note that this command is not idempotent. dh_prep

Bug#854814: Fails to start systemd-resolved

2017-02-10 Thread Goran LAZAREVIC
Same bug here, temporary workaroud is to edit : /usr/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf and quote as following : [Service] ExecStartPost=+/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || echo "nameserver 127.0.0.53" | /sbin/resolvconf -a systemd-resolved' #ReadWrit

Bug#854814: Fails to start systemd-resolved

2017-02-10 Thread Michael Biebl
Am 10.02.2017 um 17:49 schrieb Yuri D'Elia: > Package: systemd > Version: 232-17 > Severity: normal > > With the update to 232-17, systemd-resolved fails to start with the > following error: > > -- The error number returned by this process is 2. > Feb 10 17:46:31 test systemd[1]: systemd-resolved

Processed: Re: Bug#854814: Fails to start systemd-resolved

2017-02-10 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #854814 [systemd] Fails to start systemd-resolved Severity set to 'important' from 'normal' -- 854814: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854814 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#854814: Fails to start systemd-resolved

2017-02-10 Thread Michael Biebl
Control: severity -1 important Am 10.02.2017 um 17:49 schrieb Yuri D'Elia: > > With the update to 232-17, systemd-resolved fails to start with the > following error: > > -- The error number returned by this process is 2. > Feb 10 17:46:31 test systemd[1]: systemd-resolved.service: Main process

Bug#854699: Shutdown fails with an encrypted filesystem on virtio device

2017-02-10 Thread Michael Biebl
Am 10.02.2017 um 12:14 schrieb Yuri D'Elia: > On Fri, Feb 10 2017, Michael Biebl wrote: >> Looks similar to >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848044 and a lot like >> https://github.com/systemd/systemd/issues/1620 > > Uhm, it does. Aside from the fact that it's not at all harmle

Re: Re: Bug#804908: service is not started under systemd

2017-02-10 Thread Nobuhiro Iwamatsu
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Control: tags 804908 + pending Hi, Thanks for your report. >Am 12.11.2015 um 20:19 schrieb Michael Biebl: >> That is a symlink though, which is only created if the user explicitly >> runs "systemctl enable --user obex.service", which in my case wi