Frescobaldi package broken in Jammy
Hi, I would like to call for attention on these bugs: https://bugs.launchpad.net/ubuntu/+source/frescobaldi/+bug/1993213 https://bugs.launchpad.net/ubuntu/+source/frescobaldi/+bug/1983579 https://bugs.launchpad.net/ubuntu/+source/frescobaldi/+bug/1991322 In a nutshell, the Frescobaldi package (LilyPond music sheet editor) is completely unusable on Ubuntu Jammy. The fix is to upgrade it to Frescobaldi 3.2. I hope it's OK I raise this here. I do this because this issue has a bad impact on our community, and has received no visible attention from Ubuntu maintainers since it was first reported 2 months and a half ago. Best regards, Jean -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Frescobaldi package broken in Jammy
Hi Jean, Thanks for your interest Quoting Jean Abou Samra (2022-10-23 13:59:01) > https://bugs.launchpad.net/ubuntu/+source/frescobaldi/+bug/1993213 > https://bugs.launchpad.net/ubuntu/+source/frescobaldi/+bug/1983579 > https://bugs.launchpad.net/ubuntu/+source/frescobaldi/+bug/1991322 > > In a nutshell, the Frescobaldi package (LilyPond music sheet editor) > is completely unusable on Ubuntu Jammy. The fix is to upgrade it to > Frescobaldi 3.2. We usually don't upload new upstream releases to stable series¹, but rather cherry-pick specific fixes. This is implied by the SRU rules in the "New upstream microreleases" section. https://wiki.ubuntu.com/StableReleaseUpdates This is particularly relevant in this case since the 3.2 version seems to have picked up a whole new dependency which isn't even in the archive. The best way to ensure we fix this in Jammy is to point us towards the specific commit(s) that address the problem at hand, or, even better, prepare a debdiff with those patches to get the package sponsored. Cheers, Simon ¹: Whole new upstream versions can still be backported when going through the Backports process, see https://wiki.ubuntu.com/UbuntuBackports -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Frescobaldi package broken in Jammy
Hi Simon, Thanks for replying! Le 24/10/2022 à 15:02, Simon Chopin a écrit : We usually don't upload new upstream releases to stable series¹, but rather cherry-pick specific fixes. This is implied by the SRU rules in the "New upstream microreleases" section. https://wiki.ubuntu.com/StableReleaseUpdates This is particularly relevant in this case since the 3.2 version seems to have picked up a whole new dependency which isn't even in the archive. Well, it's kind of not really a new dependency, it's basically a bunch of code that was moved from the core code base into a separate repository, but I understand what you mean. The best way to ensure we fix this in Jammy is to point us towards the specific commit(s) that address the problem at hand, or, even better, prepare a debdiff with those patches to get the package sponsored. I don't know my way around the Debian/Ubuntu packaging tools, but here is the list of commits that look relevant to me: https://github.com/frescobaldi/frescobaldi/commit/1177e03157e7a38d25943458c8930317d98c9e0a https://github.com/frescobaldi/frescobaldi/commit/5a3605b93f2ee4d2f287ce39183713056d88a29c https://github.com/frescobaldi/frescobaldi/commit/87f87249f1ef0ab0e54490dfed47db0718f4f072 https://github.com/frescobaldi/frescobaldi/commit/849f299ee97f0b2cd0bc81c9a01153f349c1d340 https://github.com/frescobaldi/frescobaldi/commit/c0d68b4e1a6c8f6ed4e4f5d0147dc0d83f5c889c https://github.com/frescobaldi/frescobaldi/commit/73cd53e7e089537aa853eea7d43f212145bd5ef5 Of course, you'd want to test that the app starts before integrating the cherry-picks. Best, Jean -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Frescobaldi package broken in Jammy
Le 24/10/2022 à 15:24, Jean Abou Samra a écrit : Of course, you'd want to test that the app starts before integrating the cherry-picks. P.S. If there is a way to test a fixed .deb, I can try out the basic features (compilation, syntax update, etc.) if that would help (but I am not an Ubuntu user myself so I'll have to install a VM, thus I will need a little time…). -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Frescobaldi package broken in Jammy
On Sun, Oct 23, 2022 at 01:59:01PM +0200, Jean Abou Samra wrote: > I would like to call for attention on these bugs: > https://bugs.launchpad.net/ubuntu/+source/frescobaldi/+bug/1993213 > https://bugs.launchpad.net/ubuntu/+source/frescobaldi/+bug/1983579 > https://bugs.launchpad.net/ubuntu/+source/frescobaldi/+bug/1991322 > In a nutshell, the Frescobaldi package (LilyPond music sheet editor) > is completely unusable on Ubuntu Jammy. The fix is to upgrade it to > Frescobaldi 3.2. > I hope it's OK I raise this here. I do this because this issue has a > bad impact on our community, and has received no visible attention > from Ubuntu maintainers since it was first reported 2 months and > a half ago. In a serendipitous coincidence, my son has just started piano lessons and so I find myself using lilypond for the first time in years. I wasn't trying to use frescobaldi - a text editor is enough for me - but it means I am in a position to confirm the bugs in question. On Mon, Oct 24, 2022 at 06:02:37AM -0700, Simon Chopin wrote: > We usually don't upload new upstream releases to stable series¹, but > rather cherry-pick specific fixes. This is implied by the SRU rules in > the "New upstream microreleases" section. > https://wiki.ubuntu.com/StableReleaseUpdates > This is particularly relevant in this case since the 3.2 version seems > to have picked up a whole new dependency which isn't even in the > archive. > The best way to ensure we fix this in Jammy is to point us towards the > specific commit(s) that address the problem at hand, or, even better, > prepare a debdiff with those patches to get the package sponsored. > ¹: Whole new upstream versions can still be backported when going > through the Backports process, see https://wiki.ubuntu.com/UbuntuBackports I am prepared to argue in this case that a full-upstream update in SRU would be appropriate on the grounds that the package is completely unusable and therefore the regression potential is nil, and has a better chance of correctness than cherry-picking individual commits and hoping we've caught all the type errors. This doesn't obviously fix the problem of the missing dependency. I will check with the rest of the SRU team how they would want this handled. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: PGP signature -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Frescobaldi package broken in Jammy
Le 25/10/2022 à 07:50, Steve Langasek a écrit : This doesn't obviously fix the problem of the missing dependency. I will check with the rest of the SRU team how they would want this handled. Any update on this? Thanks, Jean OpenPGP_signature Description: OpenPGP digital signature -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Frescobaldi package broken in Jammy
On Sun, Nov 06, 2022 at 01:03:02PM +0100, Jean Abou Samra wrote: > Le 25/10/2022 à 07:50, Steve Langasek a écrit : > > This doesn't obviously fix the problem of the missing dependency. I will > > check with the rest of the SRU team how they would want this handled. > Any update on this? The packages have been uploaded now and are awaiting review by an(other) SRU Team member. https://launchpad.net/ubuntu/jammy/+queue?queue_state=0&queue_text=python-qpageview https://launchpad.net/ubuntu/jammy/+queue?queue_state=1&queue_text=frescobaldi Cheers, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: PGP signature -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Frescobaldi package broken in Jammy
Le 18/11/2022 à 21:25, Steve Langasek a écrit : On Sun, Nov 06, 2022 at 01:03:02PM +0100, Jean Abou Samra wrote: Le 25/10/2022 à 07:50, Steve Langasek a écrit : This doesn't obviously fix the problem of the missing dependency. I will check with the rest of the SRU team how they would want this handled. Any update on this? The packages have been uploaded now and are awaiting review by an(other) SRU Team member. https://launchpad.net/ubuntu/jammy/+queue?queue_state=0&queue_text=python-qpageview https://launchpad.net/ubuntu/jammy/+queue?queue_state=1&queue_text=frescobaldi Cheers, Thank you for doing this. Please let me know when the review step is completed. OpenPGP_signature Description: OpenPGP digital signature -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Frescobaldi package broken in Jammy
On Tue, Nov 22, 2022 at 06:56:21PM +0100, Jean Abou Samra wrote: > Le 18/11/2022 à 21:25, Steve Langasek a écrit : > > On Sun, Nov 06, 2022 at 01:03:02PM +0100, Jean Abou Samra wrote: > > > Le 25/10/2022 à 07:50, Steve Langasek a écrit : > > > > This doesn't obviously fix the problem of the missing dependency. I > > > > will > > > > check with the rest of the SRU team how they would want this handled. > > > Any update on this? > > The packages have been uploaded now and are awaiting review by an(other) SRU > > Team member. > > > > https://launchpad.net/ubuntu/jammy/+queue?queue_state=0&queue_text=python-qpageview > > > > https://launchpad.net/ubuntu/jammy/+queue?queue_state=1&queue_text=frescobaldi > Thank you for doing this. Please let me know when the review step is > completed. If you are subscribed to the launchpad bugs, you'll be able to track the progress there. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: PGP signature -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Frescobaldi package broken in Jammy
Le 22/11/2022 à 22:40, Steve Langasek a écrit : Thank you for doing this. Please let me know when the review step is completed. If you are subscribed to the launchpad bugs, you'll be able to track the progress there. We're at the testing stage now, but I need help figuring out how to perform that test. See https://bugs.launchpad.net/ubuntu/+source/frescobaldi/+bug/1993213/comments/4 Thanks, Jean OpenPGP_signature Description: OpenPGP digital signature -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
