On Wed, Jul 27, 2016 at 04:58:28PM -0400, Ceridwen wrote:
> > Using "setarch uname26" on non-x86 architectures may cause issues
> > with recent versions of glibc, too:
> All the variations can be disabled at the command line or with a config
> file, so anyone using reprotest can disable `kernel` to
Package: reprotest
Version: 0.2
Severity: normal
Hi,
reprotest 0.2 fails to build properly on jessie, that is, it builds but
the .deb only contains the changelog.gz and copyright. On sid it builds
fine. I suppose some build depends must be adjusted, eg some versioned
depends increased and some ve
Package: reprotest
Severity: wishlist
Hi Ceridwen,
while reading the very interesting thread about variations for reprotest
(=congrats, nice work!), it occurred to me that it would be nice if reprotest
could do both tests simultaneously, either
- on two different hosts -b1node foo -b1port 4222 -
Hi Jakub,
Thanks for the review.
> Shouldn't it be "possible"? After all, our list of dh_* commands might
> be out of date.
Indeed it should; I copy-pasted from elsewhere without checking. Fixed.
> This doesn't work that well if the typoed command is in close distance
> to multiple existing c
Hi Chris!
Thanks for the updated patch.
* Chris Lamb , 2016-07-23, 20:13:
+Certainty: certain
Shouldn't it be "possible"? After all, our list of dh_* commands might
be out of date.
+# Unknown command, so check for likely misspellings
+foreach my $x ($dh_com
Source: hyperscan
Version: 4.2.0-1
Severity: wishlist
Tags: patch
User: reproducible-builds@lists.alioth.debian.org
Usertags: locale
X-Debbugs-Cc: reproducible-builds@lists.alioth.debian.org
Hi,
While working on the "reproducible builds" effort [1], we have noticed
that hyperscan could not be b
