systemd_232-10_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 13 Jan 2017 05:08:55 +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

Processing of systemd_232-10_source.changes

systemd_232-10_source.changes uploaded successfully to localhost along with the files: systemd_232-10.dsc systemd_232-10.debian.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org) ___ Pkg-systemd-maintainers mailin

Bug#851210: segfault during update and directly after initramfs, system unusable

Am 13.01.2017 um 05:01 schrieb Michael Biebl: > I missed to consider upstream commit 605405c6c when applying the patches > to v232. > uau on IRC helped identify the problem, thank you for that! > > Upload is pending. > I also want to mention, that systemd-nspawn came in pretty handy when debug

Bug#851210: segfault during update and directly after initramfs, system unusable

Am 13.01.2017 um 01:53 schrieb Michael Biebl: > Hi Sven, > > thanks for the bug report and sorry for the fuckup :-/ > > It seems this bug is caused by the patches I pulled from > https://github.com/systemd/systemd/pull/4835 Let me add here that this was my mistake when cherry-picking the upstrea

Bug#851210: segfault during update and directly after initramfs, system unusable - more info

OK, got to a working system without downgrading systemd to 232-8. I took a hint from Michael's post and ran: systemctl disable tor.service After that my system could boot in the normal systemd way. However, if I tried to run: systemctl status tor.service Then systemd would crash. So I believ

Bug#851210: segfault during update and directly after initramfs, system unusable

Hi Sven, thanks for the bug report and sorry for the fuckup :-/ It seems this bug is caused by the patches I pulled from https://github.com/systemd/systemd/pull/4835 Unfortunately in my testing such a problem did not show up, so this must my a certain .service unit which systemd trips over. Am 1

Processed: notfound 851210 in 232-8

Processing commands for cont...@bugs.debian.org: > notfound 851210 232-8 Bug #851210 [systemd] segfault during update and directly after initramfs, system unusable Bug #851211 [systemd] systemd 232-9 segfaults at boot No longer marked as found in versions systemd/232-8. No longer marked as found

Bug#851210: segfault during update and directly after initramfs, system unusable - more info

I ran into the same issue as Sven describes. While the system will not reboot using the default option, if I select the '(sysvinit)' option the system boots and is basically functional. I do need to manually set a nameserver in /etc/resolv.conf for network access. I have not been able to downg

Processed: merging 851210 851211

Processing commands for cont...@bugs.debian.org: > merge 851210 851211 Bug #851210 [systemd] segfault during update and directly after initramfs, system unusable Bug #851210 [systemd] segfault during update and directly after initramfs, system unusable Marked as found in versions systemd/232-8.

systemd/udev fails to upgrade from 232-8 to 232-9

Dear systemd maintainers, on my up-to-date unstable system (amd64) the update from version 232-8 to 232-9 fails, I'm not sure if it is actually systemd or udev, but I suspect the latter. Here is what I get: # apt-get upgrade Reading package lists... Done Building dependency tree Reading state i

Processed: Re: Bug#846944: Installing libnss-resolve before libnss-mdns breaks mDNS name resolution

Processing control commands: > clone 846944 -2 Bug #846944 [libnss-resolve] Installing libnss-resolve before libnss-mdns breaks mDNS name resolution Bug 846944 cloned as bug 851180 > reassign -2 libnss-mdns 0.10-7 Bug #851180 [libnss-resolve] Installing libnss-resolve before libnss-mdns breaks m

Bug#846944: Installing libnss-resolve before libnss-mdns breaks mDNS name resolution

Control: clone 846944 -2 Control: reassign -2 libnss-mdns 0.10-7 On Thu, 08 Dec 2016 at 15:20:34 +0100, Michael Biebl wrote: > With multiple packages mangling nsswitch.conf, this feels like it's > becoming very brittle and maybe we need a proper API like pam-auth-update. That would be nice, but l

Bug#850447: systemd backport sections only 4K aligned, won't boot with arm64 64K kernel

Control: reassign -1 release.debian.org Control: retitle -1 nmu: systemd_230-7~bpo8+2 Control: user -1 release.debian@packages.debian.org Control: usertags -1 binnmu Am 09.01.2017 um 18:26 schrieb Steven Capper: > Hi, > FWIW, I found that disabling gold (by tweaking configure.ac >

Processed (with 2 errors): Re: Bug#850447: systemd backport sections only 4K aligned, won't boot with arm64 64K kernel

Processing control commands: > reassign -1 release.debian.org Bug #850447 [systemd] systemd backport sections only 4K aligned, won't boot with arm64 64K kernel Bug reassigned from package 'systemd' to 'release.debian.org'. No longer marked as found in versions systemd/230-7~bpo8+2. Ignoring reque

Processed: tagging 850447

Processing commands for cont...@bugs.debian.org: > tags 850447 - moreinfo Bug #850447 [systemd] systemd backport sections only 4K aligned, won't boot with arm64 64K kernel Removed tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 850447: http://bug

Bug#802018: marked as done (systemd: _SYSTEMCTL_SKIP_REDIRECT=true is leaked to daemon)

Your message dated Thu, 12 Jan 2017 16:20:13 + with message-id and subject line Bug#802018: fixed in systemd 232-9 has caused the Debian Bug report #802018, regarding systemd: _SYSTEMCTL_SKIP_REDIRECT=true is leaked to daemon to be marked as done. This means that you claim that the problem ha

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

Your message dated Thu, 12 Jan 2017 16:20:13 + with message-id and subject line Bug#781730: fixed in systemd 232-9 has caused the Debian Bug report #781730, regarding systemd: Instance variable %i not available for ReadWriteDirectories to be marked as done. This means that you claim that the

systemd_232-9_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 12 Jan 2017 16:59:22 +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

Processing of systemd_232-9_source.changes

systemd_232-9_source.changes uploaded successfully to localhost along with the files: systemd_232-9.dsc systemd_232-9.debian.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org) ___ Pkg-systemd-maintainers mailing l

Bug#851164: udev: NVMe symlinks broken by devices with spaces in model or serial strings

Package: systemd Version: 232-8 Severity: normal Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu zesty ubuntu-patch Dear Maintainer, udev creates symlinks for all NVMe drives at /dev/disk/by-id/nvme-MODEL_SERIAL. The MODEL and SERIAL strings come directly from the NVMe dev

Bug#851143: systemd: doesn't use all the mount options from /etc/fstab when mounting on boot

Am 12.01.2017 um 12:43 schrieb Russell Coker: > Package: systemd > Version: 232-8 > Severity: normal > > When I boot a server that mounts a filesystem via NFS it ignores the context= > mount option to set a SE Linux context of the files. > > What I want is to use the type mail_spool_t for a NFS m

Bug#851143: systemd: doesn't use all the mount options from /etc/fstab when mounting on boot

Package: systemd Version: 232-8 Severity: normal When I boot a server that mounts a filesystem via NFS it ignores the context= mount option to set a SE Linux context of the files. What I want is to use the type mail_spool_t for a NFS mounted mail spool instead of the default nfsd_rw_t (a generic