Processed: Re: Bug#833854: sks: no longer logs to /var/log/sks/

2016-08-29 Thread Debian Bug Tracking System
Processing control commands: > affects 834524 + sks charybdis Bug #834524 [init-system-helpers] init-system-helpers: does not own /etc/rc?.d Added indication that 834524 affects sks and charybdis -- 833854: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833854 834524: http://bugs.debian.org/cg

Processed: Re: Bug#833854: sks: no longer logs to /var/log/sks/

2016-08-29 Thread Debian Bug Tracking System
Processing control commands: > affects 834524 + sks charybdis Bug #834524 [init-system-helpers] init-system-helpers: does not own /etc/rc?.d Ignoring request to set affects of bug 834524 to the same value previously set -- 834524: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834524 Debian Bu

Bug#834524: Bug#833854: sks: no longer logs to /var/log/sks/

2016-08-29 Thread Daniel Kahn Gillmor
Control: affects 834524 + sks charybdis Over on https://bugs.debian.org/833854, On Fri 2016-08-19 17:49:52 -0400, anarcat wrote: > On Tue, Aug 09, 2016 at 09:23:51PM +0200, Christoph Anton Mitterer wrote: >> On Tue, 2016-08-09 at 12:06 -0400, Daniel Kahn Gillmor wrote: >> > it'd also likely fix th

Processed: [bts-link] source package systemd

2016-08-29 Thread Debian Bug Tracking System
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 bts-link-upstr...@lists.alioth.debian.o

[bts-link] source package systemd

2016-08-29 Thread bts-link-upstream
# # 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 #794721 (http://bugs.debian.org/794721) # Bug title: udev_queue_get_udev_is_active API

Bug#832713: systemd: after "systemd (231-1) unstable" update systemd-jurnald.service fails to start

2016-08-29 Thread Felipe Sateler
On 29 August 2016 at 12:10, Pete Batard wrote: > Please find my boot log. Note that I've tried commenting out > 'MemoryDenyWriteExecute=yes' in the various .service config files, but it > didn't help. > > If you need anything else, please let me know. This log is not verbose. Could you boot with

Bug#832713: systemd: after "systemd (231-1) unstable" update systemd-jurnald.service fails to start

2016-08-29 Thread Pete Batard
Please find my boot log. Note that I've tried commenting out 'MemoryDenyWriteExecute=yes' in the various .service config files, but it didn't help. If you need anything else, please let me know. Regards, /Pete [0.00] Booting Linux on physical CPU 0xf00 [0.00] Initializing cgro

Processed: Re: Bug#832713: systemd: after "systemd (231-1) unstable" update systemd-jurnald.service fails to start

2016-08-29 Thread Debian Bug Tracking System
Processing control commands: > tags -1 moreinfo Bug #832713 {Done: Martin Pitt } [systemd] systemd: after "systemd (231-1) unstable" update systemd-jurnald.service fails to start Bug #832893 {Done: Martin Pitt } [systemd] Failed at step SECCOMP spawning systemd-networkd Added tag(s) moreinfo. Ad

Bug#832713: systemd: after "systemd (231-1) unstable" update systemd-jurnald.service fails to start

2016-08-29 Thread Felipe Sateler
Control: tags -1 moreinfo Control: found -1 231-5 On 28 August 2016 at 17:46, Pete Batard wrote: > On 2016.08.28 15:37, Felipe Sateler wrote: >> >> Could you try 231-5 from unstable? > > > Oops, I mean 231-5 broke it. I'm seeing the issue back in 231-5 and not > 231-4 as I mentioned earlier. > >