rsyslog init script breaks after package upgrade

2014-03-19 Thread Ralf Jung
severity 731530 important reassign 731530 dpkg 1.16.12 thanks Hi, this issue is still present in current wheezy, including the backports package. Without taking manual steps, it results in rsyslog filling up the disk as log rotation is completely broken - so I'd argue it should have a severity of

Re: rsyslog init script breaks after package upgrade

2014-03-19 Thread Guillem Jover
Hi! On Wed, 2014-03-19 at 09:26:16 +0100, Ralf Jung wrote: > this issue is still present in current wheezy, including the backports > package. Without taking manual steps, it results in rsyslog filling up > the disk as log rotation is completely broken - so I'd argue it should > have a severity of

Re: rsyslog init script breaks after package upgrade

2014-03-19 Thread Ralf Jung
Hi Guillem, > If --exec is supposedly broken then this would affect any daemon using > it, which I find a bit perplexing, and I'd have expected a ton of bug > reports on dpkg due to broken upgrades. I've rechecked it on current > unstable, and it still works here. That's surprising me, too. It wor

Re: rsyslog init script breaks after package upgrade

2014-03-19 Thread Guillem Jover
On Wed, 2014-03-19 at 19:42:55 +0100, Ralf Jung wrote: > > Going over the original bug report I see this very suspicious line: > > > > ,--- > > chrisb@massmail:~$ sudo ls /proc/427/exe -l > > lrwxrwxrwx 1 root root 0 Dec 6 01:33 /proc/427/exe -> > > (deleted)/usr/sbin/rsyslogd > > `--- > > > >

Re: rsyslog init script breaks after package upgrade

2014-03-19 Thread Ralf Jung
Hi, > This seems also suspiciously similar to Chris' kernel: > > ,--- > Kernel: Linux 2.6.32-042stab081.5 (SMP w/20 CPU cores) > `--- > > In which case I'm inclined to say this is a bogus kernel, which > prepends “ (deleted)” instead of appending it. You should report this > to the server provid

Re: propagating the value of the build-profiles field to Packages and Sources files

2014-03-19 Thread Guillem Jover
On Tue, 2014-03-18 at 00:40:45 +0100, Johannes Schauer wrote: > Quoting Guillem Jover (2014-03-14 20:46:23) > > > Right now the information which binary packages do or do not build for > > > which build profile is restricted to debian/control. Coming back to my > > > original mail: what do you see

Re: Process isolation support for start-stop-daemon

2014-03-19 Thread Guillem Jover
On Mon, 2014-03-17 at 18:13:51 +0100, Andrew Shadura wrote: > On Sun, 16 Mar 2014 05:35:41 +0100 Guillem Jover wrote: > > Then there's several implementation details, here's a short list from > > a quick skimming (ignoring style issues and similar): > > > * The command-line option should always be