- Package:
- qt6-svg-dev
- Source:
- qt6-svg-dev
- Description:
- Qt 6 SVG - development files
- Submitter:
- Andrey Rakhmatullin
- Date:
- 2026-06-29 18:17:02 UTC
- Severity:
- normal
qt6-svg-dev 6.10.2-8 has dropped Provides: libqt6svg6-dev a month ago. Multiple packages B-D: libqt6svg6-dev, so I think the correct transition would be filing non-RC bugs for all of those, waiting, dropping Provides, bumping the severities, optionally offering to do NMUs. Failing that, the bugs should have been filed after dropping Provides. However I don't see any such bug reports, the affected packages FTBFS in sid, and qt6-svg is unable to migrate for a month. Are there any specific plans to finish this transition? Not marking this RC in hopes that there are plans to fix the dependent packages instead. Thanks.
Hi Andrey, On Mon, 29 Jun 2026 18:26:45 +0500 Andrey Rakhmatullin <wrar@debian.org> wrote: [...] 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.