On Mon, Aug 05, 2019 at 05:47:03PM +0200, Michael Crusoe wrote:
> python3-mypy 0.670-2 in testing has a dependency on python3-typed-ast (<<
> 1.4.0)
>
> But autopkgtests is combining python3-typed-ast 1.4.0-1 with python3-mypy
> 0.670-2 and predictably that fails :-(
That's not what it's happening. I'm reading this log:
https://ci.debian.net/data/autopkgtest/testing/amd64/m/mypy/2664835/log.gz
It *tries* to keep python3-mypy at version 0.670-2, and install
python3-typed-ast 1.4.0-1, but apt refuses that, so instead it removes
the "autopkgtest-satdep" package, which causes the first iteration to
fail. At that point you can read:
autopkgtest: WARNING: package mypy is not installed though it should be
autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from unstable
And indeed it installs:
Get:4 http://deb.debian.org/debian unstable/main amd64 python3-typed-ast amd64 1.4.0-1 [140 kB]
Get:10 http://deb.debian.org/debian unstable/main amd64 python3-mypy all 0.720-2 [835 kB]
Which are perfectly fine.
And then, the tests fails.
So I think you have some actual problem somewhere.
Ah, thank you for that explanation. Very curious. Seems to do with failing to find some modules..
> I can add a "breaks" between python3-typed-ast 1.4.0 and python3-mypy less
> than 0.720; but that seems technically unnecessary..
So, if you did that, britney would have realized it couldn't do that
test, and instead scheduled an autopkgtests triggering both mypy and
python-typed-ast, it wouldn't have tried to do that first iteration that
failed, as I showed above, but I think it would have led to the same
issue anyway.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-