On Sun, Jan 15, 2023 at 07:37:01PM +0100, Paul Gevers wrote:
> With a recent upload of metakernel the autopkgtest of metakernel fails in
> testing when that autopkgtest is run with the binary packages of metakernel
> from unstable on s390x. It passes when run with only packages from testing.
> In tabular form:
> 
>                        pass            fail
> metakernel             from testing    0.29.4-1
> versioned deps [0]     from testing    from unstable
> all others             from testing    from testing
> 
> Currently this regression is blocking the migration to testing [1]. Can you
> please investigate the situation and fix it?
> 
> More information about this bug and the reason for filing it can be found on
> https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
> 
> Paul

Hello Paul,

Thanks for the report. I ran the following to try and reproduce this using
unstable:

ssh zelenka.debian.org
schroot -b -c sid -n $LOGNAME-metakernel
dd-schroot-cmd -c $LOGNAME-metakernel apt-get update
dd-schroot-cmd -c $LOGNAME-metakernel apt-get dist-upgrade
dd-schroot-cmd -c $LOGNAME-metakernel apt-get build-dep metakernel
dd-schroot-cmd -c $LOGNAME-metakernel apt-get install python3-metakernel 
python-metakernel-doc autopkgtest autodep8 pybuild-plugin-autopkgtest
schroot -r -c $LOGNAME-metakernel
/usr/bin/autopkgtest --shell-fail metakernel -- null
exit
schroot -e -c $LOGNAME-metakernel

However, all the tests passed for both python 3.10 & 3.11.

> [0] You can see what packages were added from the second line of the log
> file quoted below. The migration software adds source package from unstable
> to the list if they are needed to install packages from metakernel/0.29.4-1.
> I.e. due to versioned dependencies or breaks/conflicts.
> [1] https://qa.debian.org/excuses.php?package=metakernel
> 
> https://ci.debian.net/data/autopkgtest/testing/s390x/m/metakernel/30188929/log.gz

I tried to look for this list of packages on the second line of the log.gz URL,
but second line I see is:

autopkgtest [16:36:08]: version 5.27

In any case, to the best of my knowledge, there aren't any direct versioned
deps from metakernel.

Moreover, I don't know how to inject metakernel/0.29.4-1 into a bookworm
schroot on zelenka, so I'm a bit stuck here :(

Any ideas on how to proceed?

--Joe

Reply via email to