Re: Handling autopkgtests for arch-all packages uninstallable on some archs

Hi, On 01-01-2025 22:52, Julian Gilbey wrote: Is this the best way to let you know about such cases in future? This, a bug report against the release.debian.org pseudo package or a note on IRC (#d-release). A bug report is the best way to not get lost, but you probably will not wait so long

Re: Handling autopkgtests for arch-all packages uninstallable on some archs

On Wed, Jan 01, 2025 at 09:38:46PM +0100, Paul Gevers wrote: > Hi, > > On 01-01-2025 21:22, Julian Gilbey wrote: > > I could mark the autopkgtests as only > > running on those four archs. Is that the best thing to do, or is > > there some way to indicate to ci.debian.net that the package is not >

Re: Handling autopkgtests for arch-all packages uninstallable on some archs

Hi, On 01-01-2025 21:22, Julian Gilbey wrote: I could mark the autopkgtests as only running on those four archs. Is that the best thing to do, or is there some way to indicate to ci.debian.net that the package is not installable on some archs and so it should not try to test the package on them

Handling autopkgtests for arch-all packages uninstallable on some archs

Hi! I'm a little bemused about how to handle the spyder suite of packages. spyder (via the python3-spyder binary and Build-Depends) depends on python3-pyqt5.qtwebengine, which is (according to rmadison) only present on amd64, armhf, i386, mips64el. ci.debian.net now only attempts to run the spyd