autopkgtest failure with perl/5.38.2-3.2

Bug #2059172 reported by Zixing Liu
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
perl (Ubuntu)
New
Undecided
Unassigned

Bug Description

autopkgtest failed with (https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/arm64/p/perl/20240326_162839_855b1@/log.gz):

3968s control.t: warning: can't parse dependency ${t64:Provides}
3968s
3968s # Failed test 'Breaks for libfilter-perl in libperl5.38t64 implies Provides'
3968s # at debian/t/control.t line 267.
3968s
3968s # Failed test 'Breaks for libfilter-perl in libperl5.38t64 implies Replaces'
3968s # at debian/t/control.t line 269.
3968s Use of uninitialized value $replaced_version in substitution (s///) at debian/t/control.t line 273.
3969s
3969s # Failed test 'Replaces version for libfilter-perl in libperl5.38t64 matches Breaks'
3969s # at debian/t/control.t line 274.
3969s # got: undef
3969s # expected: '1.64'
3969s
3969s # Failed test 'Provides version for libfilter-perl in libperl5.38t64 matches Breaks'
3969s # at debian/t/control.t line 280.
3969s # got: ''
3969s # expected: '1.64'
3969s # s/libfilter-perl,/libfilter-perl (= 1.64),/
3969s # Looks like you failed 4 tests of 626.
3969s debian/t/control.t ..
3969s Dubious, test returned 4 (wstat 1024, 0x400)
3969s Failed 4/626 subtests
3969s (less 214 skipped subtests: 408 okay)

Vladimir Petko (vpa1977)
tags: added: update-excuse
Revision history for this message
Gianfranco Costamagna (costamagnagianfranco) wrote :

Hello, I found this

# list special cases where a Breaks entry doesn't need to imply
# Replaces+Provides
my %triplet_check_skip = (
        "perl-base" => [ "libfile-spec-perl" ],
        "libperl5.38" => [ "libfilter-perl" ],
);

Maybe we can do something like
# list special cases where a Breaks entry doesn't need to imply
# Replaces+Provides
my %triplet_check_skip = (
        "perl-base" => [ "libfile-spec-perl" ],
        "libperl5.38" => [ "libfilter-perl" ],
        "libperl5.38t64" => [ "libfilter-perl" ],
);

or similar?

Revision history for this message
Łukasz Zemczak (sil2100) wrote :

On one side I'd like us to take a look at the perl failures for case-by-case situations, as it's only one test failing from the whole suite. On the other hand, we have no time right now for that. So let's hint it for now.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.