Please sync musescore-sftools 20180325-1 (universe) and fluidr3mono-gm-soundfont 2.315-4 (universe) from Debian testing (main)

Bug #1761272 reported by Thorsten Glaser
16
This bug affects 1 person
Affects Status Importance Assigned to Milestone
fluidr3mono-gm-soundfont (Ubuntu)
Fix Released
Undecided
Unassigned
musescore-sftools (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Hi! I’m the Debian maintainer (DD) of the aforementioned two packages, and coordinating MuseScore in Debian and the official MuseScore PPA as upstream contributor.

Please grant an FFe and sync at least musescore-sftools, at best also fluidr3mono-gm-soundfont. Justification below:

You recently (on 2018-03-19) sync’d musescore-sftools 20180222-2 and fluidr3mono-gm-soundfont 2.315-2 together with the latest musescore 2.1.0+dfsg3-3 from Debian. (Thanks for that.)

However, musescore-sftools 20180222 was a first cut of it to get things rolling in Debian due to the DFSG-freeness issues of the soundfont. It contains one tool, whose upstream name was “sfconvert”, but there is already an sfconvert in audiofile-tools in Debian. I renamed it to “musescore-sfconvert” and immediately contacted upstream, and it was agreed to rename to “sf3convert” because they did not like making the name specific to musescore.

That was on about 2018-03-13. I knew an Ubuntu release was approaching, but I figured that it was too late for this to land as new packages, anyway, so I decided against uploading this to Debian immediately (using patches) but wait for upstream to merge the pull requests, and then upload a new version without any Debian-specific patches.

However, upstream was extremeliest busy with the new MuseScore 2.2 release scheduled for end of March and so only merged my PRs on 2018-03-25. I uploaded this to Debian, as well with fluidr3mono-gm-soundfont 2.315-3 that used the new name of the binary package and the included binary.

Please sync the newer musescore-sftools source package; it is functionally identical to the previous one (except the reproducible-builds patch now must be enabled by the -S option), but the binary and manpage have been renamed.

To add a bit of “fun”, upstream also decided to change the name of their “new” soundfont (not yet having passed ftpmaster NEW in Debian) roughly at the same time I was making the upload, so I immediately pushed fluidr3mono-gm-soundfont 2.315-4 with the new name.

The reason we are going to need this is: fluidr3mono-gm-soundfont installs itself as FluidR3Mono_GM.sf3, but it *also* installs a symlink from MuseScore_General.sf3 (instead of MS_General.sf3 as in earlier versions) to that, which is the name of the soundfont expected from MuseScore 2.2 onwards, because it’s upwards compatible (the new soundfont is a fork of fluidr3ono). The Debian packaging for ms_general then diverts that symlink out of the way while installing itself.

The new version of MuseScore depends on fluidr3mono-gm-soundfont (>> 2.315-4~) because of that (with an alternative depends on the new soundfont, not packaged yet).

So, to avoid users having to download 2.315-4 from a PPA additionally, and for upwards compatibility with newer MuseScore versions (from PPA) for bionic for the next couple of years, this is needed. (It also builds reproducibly by using the new -S option, and uses a dpkg-builddeb option to allow for distributions as long back as precise to install the binary .deb file.)

So, please sync the newer version of the soundfont, as well.

There are no Ubuntu changes (I was surprised it had managed to slip into Ubuntu already, in the first place, so someone must already have granted a debian import sync exception).

musescore-sftools (20180325-1) unstable; urgency=high

  * Rename binary to sf3convert as requested by upstream
    (the former package name existed short enough no transition is needed)
  * New upstream snapshot, merges all patches

 -- Thorsten Glaser <email address hidden> Sun, 25 Mar 2018 19:28:35 +0200

and:

fluidr3mono-gm-soundfont (2.315-4) unstable; urgency=high

  * Rename MS_General.sf3 symlink to MuseScore_General.sf3
    since upstream suddenly decided to change it
  * Put the “MIT” licence identifier in ICOP chunk

 -- Thorsten Glaser <email address hidden> Sun, 25 Mar 2018 22:25:07 +0200

fluidr3mono-gm-soundfont (2.315-3) unstable; urgency=high

  * Use compression keeping the .deb installable on trusty
  * Mark as Multi-Arch: foreign, prompted by piuparts
  * Switch to sf3convert (new upstream-requested name)
  * Add option to keep building reproducibly
  * Update Enhances field
  * Use quality settings recommended by S. Christian Collins
  * Compress the .deb with xz -8e saving space on the mirrors

 -- Thorsten Glaser <email address hidden> Sun, 25 Mar 2018 20:44:33 +0200

There is no upstream changelog. I will add a git log from musescore-sftools, though.
I’ve uploaded both to my PPA for bionic (unchanged save for the extra changelog entry for PPA):
- https://launchpad.net/~mirabilos/+archive/ubuntu/mscore/+sourcepub/8894940/+listing-archive-extra
- https://launchpad.net/~mirabilos/+archive/ubuntu/mscore/+sourcepub/8894945/+listing-archive-extra
This should satisfy the “build log” question, and “install log” for musescore-sftools as it’s used to compile the soundfont.

I did install the soundfont in a chroot in which I tested a musescore build, so I can say with an extremely high level of confidence that both are “good”. I also excessively tested both in Debian beforehand.

Revision history for this message
Thorsten Glaser (mirabilos) wrote :
Revision history for this message
Thorsten Glaser (mirabilos) wrote :

Note that musescore-sftools upstream doesn’t even tag releases; these are just the date when I took a git snapshot.

affects: ubuntu → musescore-sftools (Ubuntu)
tags: added: upgrade-software-version
Revision history for this message
Thorsten Glaser (mirabilos) wrote :

I additionally compared the content of the fluidr3mono-gm-soundfont binary package with the one in Debian, and (one built with the same libvorbis version) they were byte-for-byte identical, so I can say with *full* confidence that these two packages will work just fine.

Revision history for this message
Thorsten Glaser (mirabilos) wrote :

ping? What’s the status of the FFe here, so I can apply for sponsorship for the sync request next?

Revision history for this message
Iain Lane (laney) wrote :

sorry Thorsten. Set/Erich, this is on Ubuntu Studio - do you have any objections?

It's fine for me from the release team if it is for you.

Revision history for this message
Thorsten Glaser (mirabilos) wrote :

Hello Set and Erich, ping again?

Revision history for this message
Erich Eickmeyer (eeickmeyer) wrote :

Hi Thorsten & Iain,

I have no objections to this since it doesn't appear to break any workflows. I say go ahead.

Revision history for this message
Thorsten Glaser (mirabilos) wrote :

OK thanks, with the ACK from you and FFe from the release team, I’ve now subscribed ubuntu-sponsors.

Revision history for this message
Jeremy Bícha (jbicha) wrote :

This bug was fixed in the package fluidr3mono-gm-soundfont - 2.315-4
Sponsored for Thorsten Glaser (mirabilos)

---------------
fluidr3mono-gm-soundfont (2.315-4) unstable; urgency=high

  * Rename MS_General.sf3 symlink to MuseScore_General.sf3
    since upstream suddenly decided to change it
  * Put the “MIT” licence identifier in ICOP chunk

 -- Thorsten Glaser <email address hidden> Sun, 25 Mar 2018 22:25:07 +0200

fluidr3mono-gm-soundfont (2.315-3) unstable; urgency=high

  * Use compression keeping the .deb installable on trusty
  * Mark as Multi-Arch: foreign, prompted by piuparts
  * Switch to sf3convert (new upstream-requested name)
  * Add option to keep building reproducibly
  * Update Enhances field
  * Use quality settings recommended by S. Christian Collins
  * Compress the .deb with xz -8e saving space on the mirrors

 -- Thorsten Glaser <email address hidden> Sun, 25 Mar 2018 20:44:33 +0200

Changed in fluidr3mono-gm-soundfont (Ubuntu):
status: New → Fix Released
Changed in musescore-sftools (Ubuntu):
status: New → Fix Released
Revision history for this message
Jeremy Bícha (jbicha) wrote :

This bug was fixed in the package musescore-sftools - 20180325-1
Sponsored for Thorsten Glaser (mirabilos)

---------------
musescore-sftools (20180325-1) unstable; urgency=high

  * Rename binary to sf3convert as requested by upstream
    (the former package name existed short enough no transition is needed)
  * New upstream snapshot, merges all patches

 -- Thorsten Glaser <email address hidden> Sun, 25 Mar 2018 19:28:35 +0200

Revision history for this message
Jeremy Bícha (jbicha) wrote :

Synced. The new binary package will need to be manually approved by an Archive Admin before it will be promoted to bionic.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.