Forwarding to the bug tracker.
Jeremy
---------- Forwarded message ----------
From: Chris Lamb <la...@debian.org>
Date: Wed, Oct 5, 2016 at 2:29 PM
Subject: Re: Bug#839848: network-manager-openvpn: FTBFS:
ERROR:test-import-export.c:823:test_proxy_http_export: assertion
failed (error == NULL): failed to write file: Failed to create file
To: Jeremy Bicha <jbi...@ubuntu.com>
Jeremy Bicha wrote:
> On Wed, Oct 5, 2016 at 1:57 PM, Chris Lamb <la...@debian.org> wrote:
> > network-manager-openvpn fails to build from source in unstable/amd64:
>
> Replying off-bug.
(I'd prefer if we talked on the BTS even if on — technically — the wrong
bug for a particular issue. Any reason why replying off-bug…?)
> If the reproducible builds project is filing FTBFS bugs (which you do
> a lot of and tag as being related to the reproducible project), then I
> think its scope is pretty broad
I'm filing them personally (and reproducing them locally before filing.)
I am only tagging them as reproducible related to a) raise the profile
of that project and b) I use the fact that they fail on the Reproducible
testing framework as a cue to build it locally... ie. Reproducible is
not primarily a QA effort, alas.
> my suggestion to test whether output varies with parallel building
> disabled is too far removed from your goals.
Test *output* ? Do you mean pass/fail result? Mmm there are lots of tests
one might do; I wish there was a more general framework for testing these
things rather than piggy-backing on something that doesn't /quite/ fit.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
