Bug#824707: systemd: I get fsck's every other boot: due to systemd-timesyncd not updating hwclock?

2016-05-23 Thread Manuel Bilderbeek
Hi, After a few days, reporting here what's going on now... 1. I haven't seen an fsck of my HDD's ever since I added that e2fsck.conf file 2. When booting, I do get a message that superblock timestamps of my SSD (/dev/sdf1) are too far in the future and I get a very quick fsck of the SDD. It

Bug#805477: closed by Martin Pitt (Bug#805477: fixed in systemd 230-1)

2016-05-23 Thread Michael Biebl
Am 23.05.2016 um 19:09 schrieb Julian Brost: > On 23.05.2016 12:33, Debian Bug Tracking System wrote: >> This is an automatic notification regarding your Bug report >> which was filed against the systemd package: >> >> #805477: systemd: Leak of scope units slowing down "systemctl >> list-unit-file

Bug#805477: closed by Martin Pitt (Bug#805477: fixed in systemd 230-1)

2016-05-23 Thread Julian Brost
On 23.05.2016 12:33, Debian Bug Tracking System wrote: > This is an automatic notification regarding your Bug report > which was filed against the systemd package: > > #805477: systemd: Leak of scope units slowing down "systemctl > list-unit-files" and delaying logins > > It has been closed by M

Bug#825075: deb-systemd-invoke: incomplete handling of policy-rc.d status codes

2016-05-23 Thread Edward Allcutt
Package: init-system-helpers Version: 1.33 Severity: normal Dear Maintainer, In particular, where policy-rc.d returns 0 deb-systemd-invoke prints a spurious warning. The original spec for policy-rc.d mentioned only 0 as the return code for "action allowed" and 104 was added later. invoke-rc.d tr

Bug#816612: marked as done (systemd: Assertion failure, systemd stopped responding)

2016-05-23 Thread Debian Bug Tracking System
Your message dated Mon, 23 May 2016 10:30:48 + with message-id and subject line Bug#816612: fixed in systemd 230-1 has caused the Debian Bug report #816612, regarding systemd: Assertion failure, systemd stopped responding to be marked as done. This means that you claim that the problem has be

systemd_230-1_amd64.changes ACCEPTED into unstable

2016-05-23 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 23 May 2016 09:42:51 +0200 Source: systemd Binary: systemd systemd-sysv systemd-container systemd-journal-remote systemd-coredump libpam-systemd libnss-myhostname libnss-mymachines libnss-resolve libsystemd0 libs

Processing of systemd_230-1_amd64.changes

2016-05-23 Thread Debian FTP Masters
systemd_230-1_amd64.changes uploaded successfully to localhost along with the files: systemd_230-1.dsc systemd_230.orig.tar.gz systemd_230-1.debian.tar.xz libnss-myhostname-dbgsym_230-1_amd64.deb libnss-myhostname_230-1_amd64.deb libnss-mymachines-dbgsym_230-1_amd64.deb libnss-mymachi

Processed: found 825059 in 215-17, fixed 825059 in 229-1

2016-05-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 825059 215-17 Bug #825059 [systemd] CVE-2015-8842 Marked as found in versions systemd/215-17. > # add some version information > fixed 825059 229-1 Bug #825059 [systemd] CVE-2015-8842 Marked as fixed in versions systemd/229-1. > thanks Stopp

Bug#825059: CVE-2015-8842

2016-05-23 Thread Moritz Muehlenhoff
Package: systemd Version: 215-17+deb8u4 Severity: important Tags: security patch As discussed on IRC it would be great if CVE-2015-8842 could be fixed in a jessie point release. Please see here for further links: https://security-tracker.debian.org/tracker/CVE-2015-8842 Cheers, Moritz __