Bug#800424: libdevel-cover-perl: FTBFS on i386 (Linux + Hurd, not kFreeBSD)

Axel Beckert abe at debian.org
Tue Dec 29 00:33:21 UTC 2015


Hi Emilio,

Emilio Pozuelo Monfort wrote:
> Control: severity -1 important
> 
> Downgrading, as the package has been built on every release architecture.

I know that for the last BinNMU the package built fine on all
architectures except on GNU Hurd.

But I'm not sure if lowering the severity for this issue is really a
good idea. This issue may happen with any built (approximately every
10th to 20th build) and it's pure chance that we got one set of
BinNMUs where this did not happen.

And as far as I can see this issue is not in the test suite but in the
library itself as it seems to produce different results by pure chance
where they should be deterministic. I.e. the test suite found a real
bug from my point of view.

If it wouldn't have wait for perl itself to migrate, I'd set the
severity to serious again to prevent its migration to testing (1.21 is
not in testing yet).

If you can't BinNMU 1.20 from testing for the perl 5.22 migration to
testing, I'd suggest to make an upload of 1.20 again to unstable as
something like 1.21+really1.20-1 or so to avoid having 1.21 in
testing. With the next upstream version everything should be fine
again, so I'd like to avoid adding an epoch just because of this
issue. (Acutally I hoped that there would be a new upstream version
rather soon after this issue became known, but that hasn't happened
yet.)

		Regards, Axel
-- 
 ,''`.  |  Axel Beckert <abe at debian.org>, http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-    |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE



More information about the pkg-perl-maintainers mailing list