Package: dpkg-dev
Version: 1.17.1
Severity: wishlist
Hi,
I't be nice if dpkg-buildpackage would report build information (e.g.
things like the name of the generated changes file) to build-tools
invoking it.
Doing this via a status fd would be nice[1] since we could then
implement more nice
package: src:dpkg
severity: important
version: 1.17.5
dpkg seems to often fail on kfreebsd-amd64 on unstable (I had not
experienced this with wheezy). The error message is
E: Sub-process /usr/bin/dpkg returned an error code (1)
This is easily recoverable by running the command a second time,
Hi,
Michael Gilbert wrote:
dpkg seems to often fail on kfreebsd-amd64 on unstable (I had not
experienced this with wheezy).
I can confirm that for kfreebsd-i386.
The error message is
E: Sub-process /usr/bin/dpkg returned an error code (1)
Yeah, and noting else. It's not clear, why there
On 22/12/2013 21:53, Axel Beckert wrote:
E: Sub-process /usr/bin/dpkg returned an error code (1)
Yeah, and noting else. It's not clear, why there was an error.
This is easily recoverable by running the command a second time, which
usually succeeds.
Yeah, but it often needs multiple
Hi!
On Sun, 2013-12-22 at 10:18:32 +0100, Guido Günther wrote:
I't be nice if dpkg-buildpackage would report build information (e.g.
things like the name of the generated changes file) to build-tools
invoking it.
Doing this via a status fd would be nice[1] since we could then
implement
Hi!
On Sun, 2013-12-22 at 21:53:19 +0100, Axel Beckert wrote:
Michael Gilbert wrote:
dpkg seems to often fail on kfreebsd-amd64 on unstable (I had not
experienced this with wheezy).
I can confirm that for kfreebsd-i386.
Ok, this is something new, I had not seen it before, but I can see
On Mon, 23 Dec 2013, Guillem Jover wrote:
Doing this via a status fd would be nice[1] since we could then
implement more nice things like progress information (we'd then be able
to detect easily which dpkg-buildpackage's steps failed) without parsing
the full build output.
[1] The
On Mon, 23 Dec 2013, Guillem Jover wrote:
The problem is that something messes with dpkg's standard output and
error, and it fails when doing the fflush() and ferror() check on it
in m_output() I think. But this seems to be coming from something
lower than dpkg or apt, perhaps a change in
8 matches
Mail list logo
