[buildd-tools-devel] Bug#842634: Bug#851877: fails every time
Adam Borowski
kilobyte at angband.pl
Mon May 15 00:13:32 UTC 2017
Control: severity -1 important
On Mon, May 15, 2017 at 01:52:09AM +0200, Guillaume Delacour wrote:
> Le 15/05/2017 à 00:50, Adam Borowski a écrit :
> > So it's a fully _reproducible_ bug, with a well-defined immediate cause
> > (even if we haven't identified the indirect cause yet) -- unlike the
> > original report by Santiago Villa. Thus, it looks we have two different
> > bugs that just happen to trigger the same failure mode.
> >
> > And thus, even if we fix the schroot issue, Santiago's bug likely won't be
> > fixed.
> >
> >> Now, the next question is: where does this /etc/hosts come from? The file
> >> is present in the above form directly after unpacking the schroot tarball,
> >> before even entering the schroot.
>
> As this bug is not related to sslh package itself, i've removed the
> pending tag, i let Michael revert
> https://anonscm.debian.org/cgit/collab-maint/sslh.git/commit/?id=243bb3faa682afa8168664eaf5a4f72cfc21ee27
> and closing this bug to disable the autoremoval in testing.
Well, closing is inappropriate, as we have at least _two_ bugs that result
in sslh hanging during the testsuite -- this one being deterministic means
it clearly is not the cause of random FTBFSes as in the original report.
Let's restore the severity then, as the not-yet-known bug happens only some
of the time.
Meow!
--
Don't be racist. White, amber or black, all beers should be judged based
solely on their merits. Heck, even if occasionally a cider applies for a
beer's job, why not?
On the other hand, corpo lager is not a race.
More information about the Buildd-tools-devel
mailing list