Your message dated Mon, 9 May 2022 22:15:33 +0200 with message-id <d441398c-6b82-cec9-76a5-4666c045d2d8@debian.org> and subject line Re: Bug#1010754: unblock: spyder/5.3.0+dfsg1-7 and unblock: spyder-unittest/0.5.0-3 has caused the Debian Bug report #1010754, regarding unblock: spyder/5.3.0+dfsg1-7 and unblock: spyder-unittest/0.5.0-3 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 1010754: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010754 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: unblock: spyder/5.3.0+dfsg1-7 and unblock: spyder-unittest/0.5.0-3
- From: Julian Gilbey <jdg@debian.org>
- Date: Mon, 09 May 2022 10:10:52 +0100
- Message-id: <[🔎] 165208745217.3484843.13833703503605490768.reportbug@erdos.d-and-j.net>
Package: release.debian.org Severity: normal User: release.debian.org@packages.debian.org Usertags: unblock Please unblock package spyder and spyder-unittest (If this isn't the correct Usertags to use, please forgive me - I couldn't figure out a better one.) [ Reason ] The binary packages of spyder (spyder, python3-spyder and spyder-common) are all "Architecture: all". However, the 5.x versions of spyder (the previous one in stable was 4.x) now depend on python3-pyqt5.qtwebengine, which is only available on six architectures. For this reason, spyder's autopkgtest has seen a regression on ppc64el and s390x as the package is no longer installable on those architectures. spyder-unittest depends on spyder, and so has exactly the same issue. And when spyder-notebook and spyder-terminal are ready, they will face the same as well, in spite of being Architecture: all. I don't know how to handle this situation - can the package be allowed to migrate to testing and only appear in the Packages file for those architectures on which python3-pyqt5.qtwebengine is available? If not, what should I do? [ Impact ] Spyder is a popular package and it would be very sad if it were not in Debian in the future. [ Tests ] A large unit test suite. [ Checklist ] The checklist points do not seem to be relevant at this stage in the release cycle unblock spyder/5.3.0+dfsg1-7 unblock spyder-unittest/0.5.0-3
--- End Message ---
--- Begin Message ---
- To: Julian Gilbey <jdg@debian.org>, 1010754-done@bugs.debian.org
- Subject: Re: Bug#1010754: unblock: spyder/5.3.0+dfsg1-7 and unblock: spyder-unittest/0.5.0-3
- From: Paul Gevers <elbrus@debian.org>
- Date: Mon, 9 May 2022 22:15:33 +0200
- Message-id: <d441398c-6b82-cec9-76a5-4666c045d2d8@debian.org>
- In-reply-to: <[🔎] 165208745217.3484843.13833703503605490768.reportbug@erdos.d-and-j.net>
- References: <[🔎] 165208745217.3484843.13833703503605490768.reportbug@erdos.d-and-j.net>
Hi Julian, On 09-05-2022 11:10, Julian Gilbey wrote:Please unblock package spyder and spyder-unittest (If this isn't the correct Usertags to use, please forgive me - I couldn't figure out a better one.)We don't have a usertag for this situation yet, so unblock is totally fine.The binary packages of spyder (spyder, python3-spyder and spyder-common) are all "Architecture: all". However, the 5.x versions of spyder (the previous one in stable was 4.x) now depend on python3-pyqt5.qtwebengine, which is only available on six architectures. For this reason, spyder's autopkgtest has seen a regression on ppc64el and s390x as the package is no longer installable on those architectures.Ackspyder-unittest depends on spyder, and so has exactly the same issue. And when spyder-notebook and spyder-terminal are ready, they will face the same as well, in spite of being Architecture: all.Please let us know when that happens.I don't know how to handle this situation - can the package be allowed to migrate to testing and only appear in the Packages file for those architectures on which python3-pyqt5.qtwebengine is available? If not, what should I do?Send the e-mail that you did. You're hitting a bug in britney (our migration software) that it doesn't check properly if source packages that build only arch:all binaries have all their dependencies met when it schedules the autopkgtests. We will enable the package to migrate.Spyder is a popular package and it would be very sad if it were not in Debian in the future.O, definitely. I was surprised it got uninstalled on my own system.unblock spyder/5.3.0+dfsg1-7 unblock spyder-unittest/0.5.0-3Those don't work ;), but I add the right hint: force-skiptest. PaulAttachment: OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---