On 1/20/25 12:18 PM, Dmitry Shachnev wrote:
On Sat, Jan 18, 2025 at 03:01:00PM +0100, Sebastiaan Couwenberg wrote:
None of the python3-pyqt5.qtwebkit rdeps are key packages, so I suggest you
upload a revision of pyqt5 without qtwebkit support and make the bugreports
for the rdeps like this one RC to have chance of shipping trixie without
qtwebkit.
As bugs for python3-pyqt5.qtwebkit reverse dependencies were filed quite
recently, I think we should give the maintainers some time to react and
prepare updates. I propose the following timeline:
- One week from now, on 2025-01-27, bump the severities to RC and post a
notice that python3-pyqt5.qtwebkit will be removed soon.
Make the severity important then or already.
- Two weeks from now, on 2025-02-03, actually upload a version of pyqt5 that
does not build python3-pyqt5.qtwebkit binary anymore. (I will probably
also remove some other binaries without rdeps in that upload.)
Now that python3-pyqt5.qtwebkit is no longer built, make the severity serious
for the rdep bugreports.
This is similar to transition where a package FTBFS with the new version in
experimental which are filed as important, and become serious when that version
is uploaded to unstable.
- After pyqt5 is uploaded, we can bump severity of #1069574 to RC, so
eventually Qt WebKit and its remaining reverse dependencies are marked for
auto-removal.
You can already set the severity of #1069574 to serious because you don't
intend to have it in trixie.
The autoremoval won't kick in until pyqt5 without qtwebkit support has migrated
to testing.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
