Re: Bug#912521: perl: 5.28 FTBFS on kfreebsd: test failures

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: Bug#912521: perl: 5.28 FTBFS on kfreebsd: test failures

James Clarke-2
> On 31 Oct 2018, at 22:38, Niko Tyni <[hidden email]> wrote:
>
> Source: perl
> Version: 5.28.0-3
> Severity: important
> X-Debbugs-Cc: [hidden email]
> Tags: ftbfs
>
> This package failed to build on kfreebsd-amd64.
>
>  https://buildd.debian.org/status/fetch.php?pkg=perl&arch=kfreebsd-amd64&ver=5.28.0-3&stamp=1541024336&raw=0
>
>  Failed 3 tests out of 2544, 99.88% okay.
> ../dist/Time-HiRes/t/utime.t
> ../lib/File/Copy.t
> run/switches.t
>
> Copying the debian-bsd list. Could you please investigate?
>
> The timing with the Perl 5.28 transition starting today is unfortunate;
> I didn't notice that the kfreebsd experimental buildds finally got
> around to trying perl a couple of days ago so I wasn't aware of these
> failures.
>
> You (as in debian-bsd@) might want to consider uploading 5.28.0-3
> binaries built with DEB_BUILD_OPTIONS=nocheck or something for now to
> get the transition binNMUs. But you probably know better than me how
> all that stuff works.

Hi Niko,
I did this two weeks ago, but it turns out one of the failures (run/switches.t)
is important, as it reveals that `perl -pi -e ... /tmp/foo` is broken, which in
turn causes r-base-core's postinst to fail. I've tracked this down and sent a
patch upstream[1]; could you please apply this to the packaging?

Thanks,
James

[1] https://rt.perl.org/Ticket/Display.html?id=133668

Reply | Threaded
Open this post in threaded view
|

Re: Bug#912521: perl: 5.28 FTBFS on kfreebsd: test failures

Niko Tyni-3
On Mon, Nov 19, 2018 at 03:50:46PM +0000, James Clarke wrote:

> I did this two weeks ago, but it turns out one of the failures (run/switches.t)
> is important, as it reveals that `perl -pi -e ... /tmp/foo` is broken, which in
> turn causes r-base-core's postinst to fail. I've tracked this down and sent a
> patch upstream[1]; could you please apply this to the packaging?

Thanks! Applied in 5.28.0-4 (just uploaded.)
--
Niko