On Wed, Mar 29, 2017 at 06:35:35AM +0200, Michael Biebl wrote:
> Am 29.03.2017 um 06:03 schrieb Nathan Dorfman:
> > Package: systemd
> > Version: 232-19
> > Followup-For: Bug #848044
> >
> > Just tried a fresh install using the stretch rc2 amd64 netinst ISO,
> > and the guided/entire-disk LVM+LUKS
Am 29.03.2017 um 06:03 schrieb Nathan Dorfman:
> Package: systemd
> Version: 232-19
> Followup-For: Bug #848044
>
> Just tried a fresh install using the stretch rc2 amd64 netinst ISO,
> and the guided/entire-disk LVM+LUKS install option.
>
> There's no delay at shutdown, but there are errors abou
Am 10.03.2017 um 06:46 schrieb Michael Biebl
>
> systemd (215-17+deb8u7) stable; urgency=medium
I suppose everyone is busy getting stretch into shape…
Still, if you have some time to review/ack this change, I'd be grateful
so I can proceed with the stable upload (or not).
Regards,
Michael
--
Am 28.03.2017 um 22:52 schrieb Michael Biebl:
> A complete debdiff is attached.
Hm, somehow that got lost. Attaching it now.
Regards,
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
diff --git a/debian/changelog b/debian/chan
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 28 Mar 2017 21:23:30 +0200
Source: systemd
Binary: systemd systemd-sysv systemd-container systemd-journal-remote
systemd-coredump libpam-systemd libnss-myhostname libnss-mymachines
libnss-resolve libnss-systemd l
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Hello release team,
since 232-19, a couple of fixes accumulated which we'd like to see enter
testing/stretch
As this potentially affects the installer, I've CC debian-boot aka KiBi.
A com
systemd_232-22_source.changes uploaded successfully to localhost
along with the files:
systemd_232-22.dsc
systemd_232-22.debian.tar.xz
systemd_232-22_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
Hello Michael,
The KVM domain is "auto-started" by libvirtd, and that appears to result
in systemd-machined starting up.
Stopping systemd-machined, then stopping and re-starting the virtual
machine using virsh causes systemd-machined to restart along with it.
I've tried both disabling and m
