Processing of systemd_227-1_source.changes

systemd_227-1_source.changes uploaded successfully to localhost along with the files: systemd_227-1.dsc systemd_227.orig.tar.gz systemd_227-1.debian.tar.xz Greetings, Your Debian queue daemon (running on host franck.debian.org) ___

Bug#799324: marked as done (systemd: Instance variable %i not available for RuntimeDirectory)

Your message dated Thu, 08 Oct 2015 09:52:06 + with message-id and subject line Bug#799324: fixed in systemd 227-1 has caused the Debian Bug report #799324, regarding systemd: Instance variable %i not available for RuntimeDirectory to be marked as done.

Bug#795494: marked as done (udev: network interfaces incorrectly named if naming rules are not in 70-persistent-net.rules)

Your message dated Thu, 08 Oct 2015 09:52:06 + with message-id and subject line Bug#795494: fixed in systemd 227-1 has caused the Debian Bug report #795494, regarding udev: network interfaces incorrectly named if naming rules are not in

Bug#798391: marked as done (systemd: RuntimeDirectory= creates directory with wrong group)

Your message dated Thu, 08 Oct 2015 09:52:06 + with message-id and subject line Bug#798391: fixed in systemd 227-1 has caused the Debian Bug report #798391, regarding systemd: RuntimeDirectory= creates directory with wrong group to be marked as done. This

Re: systemd-boot (Re: PR: fsateler/coredump)

On Wed, Oct 07, 2015 at 02:31:19PM +0200, Michael Biebl wrote: > Am 07.10.2015 um 14:13 schrieb Julian Andres Klode: > > I thought about this a bit. What we need is basically two things: > > > > > (1) a package installing the bootloader tools and updating the > > bootloader in the ESP > >

Bug#797326: marked as done (systemd: immediately unmounts manually mounted filesystem (listed in fstab with noauto))

Your message dated Thu, 08 Oct 2015 09:52:06 + with message-id and subject line Bug#797326: fixed in systemd 227-1 has caused the Debian Bug report #797326, regarding systemd: immediately unmounts manually mounted filesystem (listed in fstab with noauto)

Re: systemd-boot (Re: PR: fsateler/coredump)

On 7 October 2015 at 09:31, Michael Biebl wrote: > Afaics, that's about 200K. So yeah, I could live with having those > shipped in the systemd package. > > and bootctl is useful on its >> own, even for people not using systemd-boot (it shows the >> boot configuration). > >> You

Re: systemd-boot (Re: PR: fsateler/coredump)

On Thu, Oct 08, 2015 at 10:55:08AM -0300, Felipe Sateler wrote: > On 7 October 2015 at 09:31, Michael Biebl wrote: > > Afaics, that's about 200K. So yeah, I could live with having those > > shipped in the systemd package. > > > > and bootctl is useful on its > >> own, even for

Re: systemd-boot (Re: PR: fsateler/coredump)

Am 08.10.2015 um 17:20 schrieb Julian Andres Klode: > I'm wondering if it makes sense to have some sort of systemd > meta package. I recently wondered very long where machinectl > was when I wanted to try machinectl shell... We added machinectl to the package description, so it should turn up

[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 #800417 (http://bugs.debian.org/800417) # Bug title: systemd: leaks a unix stream

systemd 226-4 MIGRATED to testing

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

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

Bug#801342: systemd: plain dm-crypt volumes not brought up on boot

Package: systemd Version: 215-17+deb8u2 Severity: normal [This was originally meant as a followup to #712439 which has been archived.] Dear maintainers, I upgraded a laptop from wheezy to jessie last weekend using dist-upgrade which installed systemd as the init system. Since the upgrade

Bug#801354: libpam-systemd: breaks lightdm: Failed to create session: Connection timed out

Package: libpam-systemd Version: 227-1 Severity: serious After the upgrade to systemd packages 227-1, I get various timeouts with lightdm: [...] Oct 09 02:57:45 zira systemd[1581]: run-rpc_pipefs.mount: Mount process exited, code=exited status=1 Oct 09 02:57:45 zira systemd[1581]: Failed

Bug#801354: libpam-systemd: breaks lightdm: Failed to create session: Connection timed out

Am 09.10.2015 um 03:13 schrieb Vincent Lefevre: > Package: libpam-systemd > Version: 227-1 > Severity: serious > > After the upgrade to systemd packages 227-1, I get various timeouts > with lightdm: > > [...] > Oct 09 02:57:45 zira systemd[1581]: run-rpc_pipefs.mount: Mount process > exited,

Bug#801354: libpam-systemd: breaks lightdm: Failed to create session: Connection timed out

On 2015-10-09 03:22:17 +0200, Michael Biebl wrote: > Why does a simple umount fail? I don't know. These errors appeared with this upgrade. I never got such errors before (logs begin at Fri 2015-07-03 14:03:14 CEST). > Which version of libmount1/mount is installed? 2.27-3 for both. > Please

Bug#801361: [systemd] attempts to unmount filesystems at end of boot, INCLUDING ROOT

Package: systemd Version: 227-1 Severity: important --- Please enter the report below this line. --- I've downgraded all systemd components to 226-4 in the meantime. The machine in question has /var, /tmp on ZFS (/tmp is mounted "legacy style"). Because these are needed fairly early in the boot