Bug#848814: diffoscope: FTBFS: dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.5 returned exit code 13

Source: diffoscope Version: 63 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20161219 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > mak

Bug#848705: dpkg-dev: have dpkg-genbuildinfo add extra information based on DEB_BUILD_OPTIONS=buildinfo=xxx

Package: dpkg-dev Version: 1.18.15 Severity: wishlist Dear Maintainer, One of the purposes of buildinfo files is to aid in debugging, e.g. to be able to see what particular build-environment variation (between two builds) may have caused a failure to reproduce some binary hashes. This goal

Re: [PATCH] Archive .buildinfo files so we are at least collecting them now for future use.

Hi Ansgar, Jörg, On Thu, Dec 15, 2016 at 08:53:02PM +0100, Chris Lamb wrote: > Attached is the following: > > commit 0d670db32f57ae1efa75fdc9eb3fa79efd660b88 > Author: Chris Lamb > Date: Thu Dec 15 20:17:05 2016 +0100 > > Archive .buildinfo files so we are at

Re: [diffoscope] 01/01: Use js-beautify as JavaScript code beautifier for .js files

Hey Emanuel :) On Sun, Dec 18, 2016 at 09:55:08PM +, Emanuel Bronshtein wrote: > e3amn2l-guest pushed a commit to branch master > in repository diffoscope. > > commit 002f05444cc0a238d8e617b31dabef4111b4ecd2 > Author: Emanuel Bronshtein > Date: Sun Dec 18 23:52:51 2016

Re: Bug#774415: From srebuild sbuild-wrapper to debrebuild

On Mon, Dec 19, 2016 at 10:02:58AM +0100, Johannes Schauer wrote: > Other ways to solve this problem include: > - only accept .buildinfo files that include the .dsc filename and checksum > - accept .changes files that reference both the .buildinfo and the .dsc those two seem sensible to me.

Re: Bug#774415: From srebuild sbuild-wrapper to debrebuild

Hi, Quoting HW42 (2016-12-19 07:37:00) > So you (at least josch and ntyi) seem to prefer to have the user facing part > in sbuild/pbuilder and the common functionality in some kind of library. How > should the "library" interface look like for sbuild? pbuilder is written in bash, so a plain-text