* Emilio Pozuelo Monfort:
>
> Did you run it against testing packages, except for libcdio from unstable?

If I install libdevice-cdio-perl from testing, it will automatically
install libcdio from testing, as well, because of the dependency on the
old SONAME.

$ apt depends libdevice-cdio-perl
<...>
  Depends: libiso9660-11 (>= 2.0.0)

This transition is to update to libiso9660-12.

I think it is impossible to do what you're suggesting. And I agree with
Gregor Herrmann that it doesn't make sense. Shouldn't we test the new
package? This is, by the way, what I said I'm doing locally:

  $ dpkg --no-pager --list libdevice-cdio-perl libcdio-dev libcdio19t64 
libiso9660-dev libiso9660-11 libiso9660-12
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name                Version      Architecture Description
  
+++-===================-============-============-============================================================
  ii  libcdio-dev:i386    2.2.0-1      i386         library to read and control 
CD-ROM (development files)
  ii  libcdio19t64:i386   2.2.0-1      i386         library to read and control 
CD-ROM
  ii  libdevice-cdio-perl 2.0.0-2      i386         CD Input and control library
  ii  libiso9660-12:i386  2.2.0-1      i386         library to work with 
ISO9660 filesystems
  ii  libiso9660-dev:i386 2.2.0-1      i386         library to work with 
ISO9660 filesystems (development files)

  $ autopkgtest -B . -- null
  <...>
  t/07.iso2.t .....
  1..5
  # Test ISO9660::IFS routines
  ok 1 - Open CD image ../data/isofs-m1.cue
  ok 2 - CD 9660 file stats: find_lsn(26)
  ok 3 - CD 9660 file stats: stat('COPYING)'
  ok 4 - Read directory: readdir('/')
  ok 5 - File contents comparison
  ok
  <...>
  autopkgtest [23:36:44]: @@@@@@@@@@@@@@@@@@@@ summary
  autodep8-perl-build-deps PASS
  autodep8-perl        PASS (superficial)
  autodep8-perl-recommends PASS (superficial)

> I'm not sure what the failing test is actually doing, as I can't find
> a debian/tests/control file

It doesn't have this file because it uses Perl's default thing (via
pkg-perl-autopkgtest). You can tell by this line in debian/control:

  Testsuite: autopkgtest-pkg-perl

The way it works it that it automatically runs all the tests under the
't/' directory.

> but it's installing build-deps from testing, which means that it's
> using/mixing the old libcdio.

Shouldn't the CI be testing the new package?

> So perhaps the test is broken, 
> although I'm not sure why it segfaults on those arches and not others, and 
> that 
> may be a real bug.

I agree that it could be a real bug, but do you think this could be a
bug in the CI itself? It is testing the old packages... Have they
always failed?

Reply via email to