On Thu, 19 May 2016 23:31:29 +0200 Manuel Bilderbeek
wrote:
> Hi,
>
> On 19-05-16 23:04, Michael Biebl wrote:
> >> Looks like I need to have systemd-timesync run *before* systemd-fsck!?
> >
> > If your hwclock drifts that much, maybe
> > /etc/e2fsck.conf:
> > [options]
> > broke
Processing commands for cont...@bugs.debian.org:
> retitle 824491 document how to disable new interface names for usb network
> interfaces
Bug #824491 [udev] udev: impossible to disable predictable network interface
names
Changed Bug title to 'document how to disable new interface names for usb
Control: reopen -1
Control: found -1 1.5.4-2
Hi!
It seems that the fix for #820088 introduced in systemd-cron version
1.5.4-2 is incomplete: At least on my system the setgid bit is only
correctly cleared after I re-install systemd-cron, but not after the
first install (see the log below for more
Processing control commands:
> reopen -1
Bug #820088 {Done: Alexandre Detiste }
[systemd-cron] /usr/bin/crontab still has the setgid bit set
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
N
FYI: The status of the systemd source package
in Debian's testing distribution has changed.
Previous version: 229-5
Current version: 229-6
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day you will receive
lat
Package: ftp.debian.org
Severity: normal
As discussed in [1] I would like to make it possible for minimal
systems (mostly buildd chroots and application containers like Docker)
to not have to install an init system.
For this the "Essential: yes" field is moved from "init" to
"init-system-helpers"
