Hi Matthia,

On Fri, Jul 17, 2015 at 04:07:26PM +0000, Mattia Rizzolo wrote:
> On Fri, Jul 17, 2015 at 03:52:15PM +0200, Andreas Tille wrote:
> > I tried to reproduce this problem but was unable to reproduce it in a
> > pbuilder environment.  Are any specific build options needed to
> > reproduce this (since in my build log
> >    dh_strip_nondeterminism -O--parallel
> > is not even called:
> > 
> >    ...
> >    dh_link -O--parallel
> >    debian/rules override_dh_compress
> >    ...
> Well, currently it's called by our modified debhelper. The bug to get it
> mainlined is #759895.
> Either you install our patched debhelper or you modify the package to call it.
> dh patch:
> https://anonscm.debian.org/cgit/reproducible/debhelper.git/commit/?id=cb27ff633c19deb7e027045e219771668e598fb0

Ahhh, that's interesting.  My situation is that I just wanted to find
out why some of our team packages are about to be removed.  I do not
expect myself to be very helpful in fixing the problem.  The only thing
I would like to know is why this bug is qualified as serious if there is
no build error when using the available tools but fails only with a
patched tool.  IMHO this does qualify as important as maximum.  Please
do not understand me wrong: Any bug should be fixed but I see no point
in kicking a chain of packages out uf testing only because a package
using a patched debhelper fails to build.

Kind regards



Reproducible-builds mailing list

Reply via email to