Control: severity -1 serious
On Mon, 29 Jun 2026 23:15:41 +0500 Andrey Rakhmatullin <[email protected]> wrote:
On Mon, Jun 29, 2026 at 07:46:44PM +0200, Patrick Franz wrote:
>> Are there any specific plans to finish this transition?
>
>My plan was to file bugs against the affected packages but I wanted to
>give them some time to fix it on their own.
I see.
Please consider that in Debian the way "to give them some time to fix it
on their own" is the one I described: to file non-RC bugs before
the change or, if for some reason that wasn't done, at least to file RC
ones after it. Currently the way it is going to be fixed is, instead of
maintainers learning from the BTS that their packages need to be fixed, is
one of these:
* the maintainer tries to make a new upload, finds that their package
FTBFS
* somebody tries to rebuild the package, finds that it FTBFS, files an RC
bug - this is going to happen for at least some of them due to ongoing
transitions, this is how I learned about this issue
* a routine mass QA rebuild finds that the package FTBFS, the rebuilder
files an RC bug
This is inconvenient for everyone involved and can take indeterminate
amount of time. And, it seems, even fixed package won't migrate until all
of them get fixed and qt6-svg is unblocked.
Please do as Andrey suggest. That is:
- restore the provides so that the rdeps can build. This is affecting
transitions (e.g. the ongoing python 3.14 one), so I'm setting the severity to RC).
- file bugs against the rdeps at severity important, asking to update to the new
dependencies.
- eventually (e.g. in a couple of months) update the bugs to serious and drop
the provides. bonus points if you help reduce the number of remaining bugs by
doing team uploads or NMUs.
Cheers,
Emilio
