On Tue, Oct 20, 2026 at 05:49:16PM +0100, Colin Watson wrote:
> On Tue, Oct 20, 2026 at 07:35:44PM +0300, Adrian Bunk wrote:
> > Migration status for frescobaldi (4.0.5+ds1-1 to 4.0.7+ds1-1): BLOCKED:
> > Rejected/violates migration policy/introduces a regression
> > Issues preventing migration:
> > ∙ ∙ frescobaldi/loong64 has unsatisfiable dependency
> > ∙ ∙ frescobaldi/ppc64el has unsatisfiable dependency
> > ∙ ∙ frescobaldi/s390x has unsatisfiable dependency
> >
> >
> > Due to:
> > debian/frescobaldi.substvars:python3:Depends=python3-ly (>= 0.9.5),
> > python3-pyqt6, python3-pyqt6.qtwebengine, python3-qpageview, python3:any
>
> Thanks. Looks like this was previously dealt with by removing binaries on
> some architectures (https://bugs.debian.org/1131561) but not actually taking
> any measures to ensure that they wouldn't come back on the next upload.
>
> But it looks like the only bits of Frescobaldi that require QtWebEngine are
> the SVG view and the LilyPond documentation browser, so we can probably
> reduce this to a Recommends.
debian/control already has:
Depends: ..., python3-pyqt6.qtwebengine [amd64 arm64 armhf i386],...
The problem is that this doesn't help when ${python3:Depends} also
creates a dependency.
python3-qpageview seems to have the same problem, but in both
${python3:Depends} and debian/control.
cu
Adrian
