Bug#571671: dpkg-checkbuilddeps: Unmet build dependencies: build-essential

2010-02-26 Thread Kurt Roeckx
Package: dpkg-dev Version: 1.15.5.6 Severity: serious Hi, It seems that for some reason dpkg-checkbuilddeps now adds the package "build-essential" to the Build-Depends, getting me: $ dpkg-checkbuilddeps dpkg-checkbuilddeps: Unmet build dependencies: build-essential The package build-essential is

Bug#567089: patch proposal to prevent delayed allocation and the zero-length file problem

2010-02-26 Thread Jean-Baptiste Lallement
Hi, On 02/17/2010 09:09 PM, Guillem Jover wrote: The patch (attached) is completely untested, it builds though :), and there's still few things to polish, but I think it handles most of the problematic cases now (except for syncing dirs on removal), it is also I tested the fsync patch. There is

Bug#571485: "subprocess installed post-removal script returned error exit status 128" received from dpkg --purge . Script exits cleanly with return status of zero.

2010-02-26 Thread Stephen Powell
On Fri, 26 Feb 2010 09:14:44 -0500 (EST), Stephen Powell wrote: > So I redirected standard output to standard error, like so: > >zipl >&1 > > This solves the problem. Oops! That's a typo. The words were correct. The command is incorrect. That should have been zipl >&2 (0 = standard in

Bug#571485: "subprocess installed post-removal script returned error exit status 128" received from dpkg --purge . Script exits cleanly with return status of zero.

2010-02-26 Thread Stephen Powell
On Fri, 26 Feb 2010 10:22:33 -0500 (EST), Raphael Hertzog wrote: > I see code setting and exporting DEB_MAINT_PARAMS in > /var/lib/dpkg/info/linux-image-2.6.32-3-amd64.postrm so it should work. That logic is not present in the -trunk kernels currently present in testing. But relief is in sight.

Bug#571485: marked as done ("subprocess installed post-removal script returned error exit status 128" received from dpkg --purge . Script exits cleanly with return status

2010-02-26 Thread Debian Bug Tracking System
Your message dated Fri, 26 Feb 2010 16:22:33 +0100 with message-id <20100226152233.ga30...@rivendell> and subject line Re: Bug#571485: "subprocess installed post-removal script returned error exit status 128" received from dpkg --purge . Script exits cleanly with return status of zero. has caused

Bug#571485: "subprocess installed post-removal script returned error exit status 128" received from dpkg --purge . Script exits cleanly with return status of zero.

2010-02-26 Thread Stephen Powell
On Fri, 26 Feb 2010 01:50:52 -0500 (EST), Raphael Hertzog wrote: > On Thu, 25 Feb 2010, Stephen Powell wrote: >> run-parts itself, of course, is binary. Do you see a problem here? > > No, what leads you to believe that this is the part that is failing ? > The error is probably later in the script.

Bug#571584: dpkg: start-stop-daemon should take options from the environment (or command line)

2010-02-26 Thread Toni Mueller
Package: dpkg Version: 1.14.28 Severity: wishlist Hi, when trying to figure out why a daemon does not start, it would be helpful to see the messages that are normally supressed in init scripts by virtue of passing '--quiet' to start-stop-daemon. Unfortunately, this choice is hardcoded into every