On Tue, Nov 15, 2022 at 09:43:48PM +0100, Paul Gevers wrote: > Source: python-cfg-diag, remrun > Control: found -1 python-cfg-diag/0.4.0-1 > Control: found -1 remrun/0.2.2-1 > Severity: serious > Tags: sid bookworm > User: [email protected] > Usertags: breaks needs-update > > Dear maintainer(s), > > With a recent upload of python-cfg-diag the autopkgtest of remrun fails in > testing when that autopkgtest is run with the binary packages of > python-cfg-diag from unstable. It passes when run with only packages from > testing. In tabular form: > > pass fail > python-cfg-diag from testing 0.4.0-1 > remrun from testing 0.2.2-1 > all others from testing from testing > > I copied some of the output at the bottom of this report. > > Currently this regression is blocking the migration of python-cfg-diag to > testing [1]. Due to the nature of this issue, I filed this bug report > against both packages. Can you please investigate the situation and reassign > the bug to the right package?
Hi, Thanks for filing this bug report, and thanks for working on all the infrastructure related to debci, autopkgtest, and ci.debian.org; it has made working on Debian easier and more pleasant! I am indeed aware that version 0.4.x of python-cfg-diag will break remrun-0.2.2; that's the reason I uploaded remrun-0.2.3 on the very next day - it includes a bumped dependency on python-cfg-diag >= 0.4 in both debian/control and debian/tests/control. I just realized that maybe I should have given a hint about that breakage in the python-cfg-diag package itself; would it be a good idea to upload a new Debian revision with `Breaks: remrun < 0.2.3`? G'luck, Peter -- Peter Pentchev [email protected] [email protected] [email protected] PGP key: http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E EFB0 2527 DF13
signature.asc
Description: PGP signature
