Hopefully they will make it sooner than later.
I'm talking to the lilypond-list mailing list, and seeing if we can get anybody to work on the update. So far, not much luck. This is now somewhat urgent, as snappy's recent update means older versions of qtwebengine (notably, version -5.15.13_p20240322 that's currently in the tree) won't work with it. See this bug on FreeBSD's bugzilla: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278633 Updating frescobaldi to work with PyQt6 involves work that it's beyond my skills to know how to do, but I hope we can get this looked at. Lilypond is *the* music-notation software for Linux, and frescobaldi is *the* IDE for it.
(In reply to N. Andrew Walsh from comment #1) > This is now somewhat urgent, as snappy's recent update means older versions > of qtwebengine (notably, version -5.15.13_p20240322 that's currently in the > tree) won't work with it. See this bug on FreeBSD's bugzilla: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278633 That seems to have been just a downstream packaging mishap, at least I cannot reproduce it (and someone else would have complained by now).
Yeah, that looks like the usual snappy ABI break shenanigans. We sorted that out on our end already.
ftr seems the qt6 porting was merged last week, so this is just missing a release (or a snapshot if we're ever in a hurry, seems to still be issues though so think it's too early for that). fwiw this is the last "real" consumer of dev-python/pyqtwebengine excluding cleanups as far as I can see.
Hi Ionen, what exactly do you mean about "missing a release"? I've asked the lilypond mailing list if anybody would be able to work on it, but as was the case with my previous comment, I'm not sure there'll be any takers. What would be involved with updating Frescobaldi to use PyQtWebEngine-6 and thus qtwebengine:6? Would it be as simple as changing version numbers in the ebuild? My programming skills are zero, so I'm not going to be much help if it's anything more than that.
That upstream has done the porting, but just hasn't released a new version with that "yet" (latest is still 3.3.0 and that version does not support Qt6). Aka https://github.com/frescobaldi/frescobaldi/pull/1780 was merged. And e.g. https://github.com/frescobaldi/frescobaldi/blob/5d419c831/pyproject.toml#L12 depends on PyQt6 now, not 5) So, until a release we can't update it downstream unless we do snapshots, but I wouldn't recommend doing that so soon after they ported it (unless want to do unkeyworded snapshots in preparation). Haven't tried it but had a peek and as far as the ebuilds go, I don't *think* much will be needed beside: 1. pyqt5 -> pyqt6 + recheck pyqt6's USE deps for validity 2. pyqtwebengine -> pyqt6-webengine 3. drop(?) python-poppler-qt5 for now? Thing is that it doesn't exist yet, see https://github.com/frescobaldi/frescobaldi/commit/c4f5e45869ac4 -- maybe situation will have changed by the time of a release and we'll be able to package it. Either way, it's more of a optfeature and should work even without: >This file loads even if popplerqt6 is absent, although the PDF preview >panel only shows a message about missing the popplerqt6 module. 4. update dev-python/qpageview to use pyqt6, have new frescobaldi depend on that version, and the old have a upper bound until we drop the qt5 version (qpageview is also already ported upstream to use qt6 but still needs a release), its pep517 build system changed to hatchling too so should need s/setuptools/hatchling/ and s/pyqt5/pyqt6/, and same deal for python-poppler-qt5. 5. recheck if other dependencies are still correct (I think so? not looked too closely)
OK, so a good bit more involved than anything I can do. However, as the new frescobaldi appears to be in their master branch now (including an updated qpageview), I really hope this can be updated soon. I don't really have any stake in it (the current frescobaldi-3.3.0 works fine for me), but being able to purge Qt5 from my system would be nice. Thanks for looking into this. I know it's a really niche group of users, but it's really appreciated.
This is now the last package to depend on dev-python/pyqtwebengine. 4.0.0 could be near: https://github.com/frescobaldi/frescobaldi/commit/5048d1e77b397f0c662356d55098c7aa2468e233
On that note, I don't mind handling the bump when it comes given already looked at this a bit -- not that I plan to maintain this myself long term after that except maybe a bump/backport or two for early regression fixes. If v4 drags for too long, I could try a snapshot too. Albeit for now they seem to be working on regressions and missing pieces so I wouldn't hurry too much. wrt python-poppler-qt6, I think upstream may be planning to straight up remove support[1] rather than port it, may not be a concern. [1] https://github.com/frescobaldi/frescobaldi/pull/1832
(In reply to Ionen Wolkens from comment #9) > If v4 drags for too long, I could try a snapshot too. Albeit for now they > seem to be working on regressions and missing pieces so I wouldn't hurry too > much. Looking closer, I do kind of expect it to drag given last release was about 2 years ago and, while commits happen, they are kind infrequent. May or may not do an unkeyworded snapshot for testing/preparation either way if I have time later. I don't use this so it may be hard to tell (haven't installed/started it once yet, only looked at build system), but could keyword it anytime + stable if we feel it's good enough.
According to discussions on the lilypond mailing list, Frescobaldi 4 was scheduled to release on the 20th. It's apparently already in the master branch, so it might be reasonable to put together a -9999 "live" version to build from that version. According to the discussions, it seems like it's in a working state; I'm not sure why the official release has been delayed.
(In reply to Ionen Wolkens from comment #9) > wrt python-poppler-qt6, I think upstream may be planning to straight up > remove support[1] rather than port it, may not be a concern. Had a closer look at that earlier, the alternative that the Qt6 version of dev-python/qpageview uses is pyqt6[pdfium]... which means a dependency on qtwebengine:6[pdfium] At a glance it doesn't seem like it can be optional, or at least qpageview has no code to gracefully handle PyQt6 lacking QtPdf support, and frescobaldi hard-requires qpageview (In reply to N. Andrew Walsh from comment #11) > According to discussions on the lilypond mailing list, Frescobaldi 4 was > scheduled to release on the 20th. It's apparently already in the master > branch, so it might be reasonable to put together a -9999 "live" version to > build from that version. Not really interested in maintaining a live ebuild, interested in snapshots though given we could use in place of a proper release (if it drags for a whill) to let us cleanup the Qt5 version. Still going to wait a bit for that though.
(In reply to Ionen Wolkens from comment #12) > Not really interested in maintaining a live ebuild, interested in snapshots > though given we could use in place of a proper release (if it drags for a > whill) to let us cleanup the Qt5 version. > > Still going to wait a bit for that though. Fair enough. Apparently they were (are?) still sorting out some issues with building the packages for macOS (new policy about self-signed certificates or something similar that's too in-the-weeds for me to get into here), but as far as I can tell that's been resolved (or, at least, I don't see any more open pull requests). There looks to be one open issue (also macOS) about a crash on shutdown, so maybe they're waiting on that before releasing: https://github.com/frescobaldi/frescobaldi/issues/1868 But in any case, I'm optimistic that they'll have a release Soon™, so I'm fine with being patient. Thanks for keeping on this.
Update: see this PR: https://github.com/frescobaldi/frescobaldi/pull/1887 that was the missing piece for the 4.0.0 release, so once it's merged I assume they'll be an official version out that can be built into an ebuild. With GIMP 3 coming out a couple days ago, we are most certainly living in exciting times.
Update: new PR schedules 4.0.0 release for TODAY ZOMG: https://github.com/frescobaldi/frescobaldi/pull/1896 * hyperventilates into a paper bag *
Probably won't be able to look at this today, but will look soon'ish when I have time.
Wonder if it was meant to have a tarball with pre-generated files (it got tagged but the release page is missing atm, it does have one for 3.3.0 that we could've used in the past but just didn't). These got a bit more annoying to handle given need to generate in python_compile for a usable ${EPYTHON} and also wouldn't want to depend on tox just to invoke these msgfmt rules (doesn't use a Makefile anymore).
(In reply to Ionen Wolkens from comment #17) > usable ${EPYTHON} Well, for the EPYTHON bit guess can solve this by switching to single impl (not sure why this is multi).
I have it bumped locally (along qpageview-1.0.0) and it seems to work, but build system misses installing several files (it only installs .py and skips all .png/.svg/.md files that were formerly installed), which leads to missing icons and errors like: FileNotFoundError: [Errno 2] No such file or directory: '/usr/lib/python3.12/site-packages/frescobaldi/userguide/404.md' Also misses .desktop and its icon, but needing to install it manually seems intended, so will do just that. Could install the rest manually too, but given seems release page was removed (I received the release announcement for 4.0.0 but it shows 3.3.0 as the latest), maybe(?) this been noticed and being worked on. Hopefully will get a tarball with pre-generated files too.
I now see a release page for 4.0.0, but it just posted at … 06:25 UTC, roughly. So maybe they did a quick hotfix? https://github.com/frescobaldi/frescobaldi/releases/tag/v4.0.0
(In reply to N. Andrew Walsh from comment #20) > I now see a release page for 4.0.0, but it just posted at … 06:25 UTC, > roughly. So maybe they did a quick hotfix? > > https://github.com/frescobaldi/frescobaldi/releases/tag/v4.0.0 Yeah, was about to mention (just seen it). Unfortunately no tarball with pre-generated files though (but we can live without that). The tag hasn't changed, so issue remains, filed [1] [1] https://github.com/frescobaldi/frescobaldi/issues/1898
(In reply to N. Andrew Walsh from comment #20) > I now see a release page for 4.0.0, but it just posted at … 06:25 UTC, > roughly. So maybe they did a quick hotfix? > > https://github.com/frescobaldi/frescobaldi/releases/tag/v4.0.0 … and this is where I realize, as this release is dedicated to his memory, that Urs Liska, one of the main contributors to Lilypond and someone I worked with from time to time and greatly liked, died back in January :( Guess I'll be raising a glass in his name once this is out. Thanks again for your work on this.
I might push it soon anyway, a python_domodule is easy enough to "fix" the files issue. > The tag hasn't changed Actually it did, so had to re-manifest -- but new commit is unrelated to that issue. Hopefully tag moves won't be a repeated event and it'll be a 4.0.1 for any future quick fixes.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5206c2b51ecf13aed785ae3529ca8c918bae46d6 commit 5206c2b51ecf13aed785ae3529ca8c918bae46d6 Author: Ionen Wolkens <ionen@gentoo.org> AuthorDate: 2025-03-30 01:54:10 +0000 Commit: Ionen Wolkens <ionen@gentoo.org> CommitDate: 2025-03-30 08:19:37 +0000 media-sound/frescobaldi: add 4.0.0 Hardly know this so not really tested beyond checking if it starts and seems normal, please report if find any downstream packaging issues, or major issues that we should backport fixes for before potential stable (after reporting upstream if not already). Please also CC me for downstream bugs for now, haven't added myself as maintainer given may not handle this package long term (just trying to get it in a good state to be easier to handle for other maintainers). If no major issues, hoping to stabilize before the py3.13 target switch in May (3.13 is not on 3.3.0, untested) and soon follow that by 3.3.0 removal to allow pyqtwebengine (Qt5) cleanup. Closes: https://bugs.gentoo.org/905637 Closes: https://bugs.gentoo.org/926681 Closes: https://bugs.gentoo.org/943686 Closes: https://bugs.gentoo.org/952546 Signed-off-by: Ionen Wolkens <ionen@gentoo.org> media-sound/frescobaldi/Manifest | 1 + media-sound/frescobaldi/frescobaldi-4.0.0.ebuild | 68 ++++++++++++++++++++++++ 2 files changed, 69 insertions(+)
