Hi,

As seen in its last migration test run [log], composer (version 2) from
unstable is tested against its source (version 1) from testing (and
without much surprise, that fails).

log: https://ci.debian.net/data/autopkgtest/testing/amd64/c/composer/9210999/log.gz

I believe the source and binary versions should match in order to take a
test into account.

FWIW, I’ve set a “Breaks: php-composer-semver (<= 3)” in the latest
phpunit upload to hint the autopkgtest that there is no point in trying
to test composer from testing, depending on php-composer-semver (<< 3),
since I know its testsuite is not ready for PHPUnit 9 (as currently
available in unstable). For php-composer-semver, it seems to have worked
as intended (i.e., the testing migration picks php-composer-semver from
unstable), but for composer (not explicitly declared in Breaks, but de
facto uninstallable) it failed. I guess I’ll workaround this issue by
declaring an explicit “Breaks: composer (<= 2)” in my next phpunit
upload.

Regards

David

version -3 (unstable) and the binary is version -2 (testing):

https://ci.debian.net/data/autopkgtest/testing/amd64/p/pydevd/24314799/log.gz

Unsurprisingly, that also fails, as a test-time dependency (gdb) has
been moved to a package dependency in version -3.

I guess I'll have to restore the autopkgtest dependency in version -4
to get this to work, but it's a kludge.

Best wishes,

   Julian

Hi,

It's an explicit autopkgtest design choice to allow for this. I don't
think it's at the right level to work around that in debci.

Paul