Arch Linux User Repository

All,

Remember, please vote for this pkg if you find it useful!

I have updated this AUR pkg so it can be installed in parallel with musescore4.

Note that this has NOT been extensively tested for regressions. Right now it's a Works-For-Me.

If you run into any problems please post a comment so I receive a notice, or contact me directly. HTH :)

P.S.: Since MuseScore has moved on from ver. 3, there will almost certainly be no upstream maintenance releases for this. I'll try to look around to see if anyone forks ver. 3.6.2 in order to maintain it. Please contact me if you know of a good and active fork. In the very long run, the only way to keep this working may be to create an AppImage and/or Flatpak and/or Snap image of this pkg. Do let me know if you are interested in this. TIA :)

Clemmitt

P.S.: If you find this pkg useful, please vote for it so it rises up in popularity rankings to become visible on the AUR pkgs page! And if you run into any problems make sure to add a comment so I am notified. Very likely I will not be able to patch any non-trivial problems that originate in the upstream source, but I will look to see if I can find a fix. I use MuseScore3 several times each month to prepare music for public services. Thank you all :)

All,

I created this pkg because my MuseScore workflow is disrupted now that the GUI has been redesigned in ver. 4. Some functions I use frequently are more difficult or "obscure." Also note that at this time not all MuseScore3 features have been implemented in MuseScore4:

https://musescore.org/en/node/334701

I didn't attempt to make this pkg installable in parallel with musescore-4.x. The names of a few files that conflict with the musescore-4.x pkg (like icons) are hardcoded in the source, so those would need to be patched. In addition, I'm not familiar with how to deal with mimetypes/PNG files nor metainfo/org.musescore.MuseScore.appdata.xml. These would need to be addressed to remove all pkg version conflicts.

Anyone who is interested in installing ver. 3 in parallel with ver. 4 please post a comment here or contact me. TIA :)

Clemmitt Sigler

All,

In the last couple of days I am noticing a text input hesitation/freeze problem with the "Save As..." dialog (among others). And a lot of GLib-GIO-CRITICAL warnings are thrown:

(mscore3:44602): GLib-GIO-CRITICAL **: 12:33:12.901: GFileInfo created without standard::is-hidden
(mscore3:44602): GLib-GIO-CRITICAL **: 12:33:12.901: file ../glib/gio/gfileinfo.c: line 1587 (g_file_info_get_is_hidden): should not be reached
(mscore3:44602): GLib-GIO-CRITICAL **: 12:33:12.901: GFileInfo created without standard::is-backup
(mscore3:44602): GLib-GIO-CRITICAL **: 12:33:12.901: file ../glib/gio/gfileinfo.c: line 1609 (g_file_info_get_is_backup): should not be reached

Perhaps there is an issue with the recent glib2 update?... Dunno. Please post here if you know more or have a fix. Thx :)

Clemmitt

@kiasoc5,

PKGBUILD updated, but on my box this doesn't eliminate the dependency breakage. It does, however, build for me in a clean chroot....

I believe it's necessary to do the remove musescore3/upgrade system/reinstall musescore3 dance to solve the dependency conflict. I think this cropped up because portmidi changed upstream back to the original source. This caused a huge difference in version numbers so an epoch number had to be specified(?).

Sorry I can't solve this with my PKGBUILD :\ Thx again :)

Clemmitt

@kiasoc5,

Thank you for the heads-up! I didn't pay any attention to the three .so files listed as dependencies when I cribbed this PKGBUILD from the last one provided for ver. 3. In fact, I'm not sure why they are listed rather than their pkgs:

portmidi; portaudio; libvorbis

I am surprised by "breaks dependency 'libportmidi.so=1-64' required by musescore3", because the libportmidi.so dependency doesn't specify a version. Working on a solution :) Again, thx

Clemmitt

Cannot upgrade my system:

resolving dependencies...
looking for conflicting packages...
error: failed to prepare transaction (could not satisfy dependencies)
:: installing portmidi (1:2.0.4-1) breaks dependency 'libportmidi.so=1-64' required by musescore3

All,

I didn't realize (until I looked) that official AppImage releases are available for download from the MuseScore github site. If you wish to download ver. 3.6.2 to "archive" for future use, please go to:

https://github.com/musescore/MuseScore/releases/tag/v3.6.2

At the bottom of the page under "Assets" you can find an AppImage. (NB: I haven't tried it.)

Apparently, the major design and functionality revisions from ver. 3 to 4 came with some amount of controversy. There was talk of a short-term continuation to a ver. 3.7 which was rejected by the project leaders. There have also been proposals to fork the ver. 3.6.2 code. Some forum threads FYI:

https://musescore.org/en/node/342126

https://musescore.org/en/node/325306

On this forum thread search to the bottom of the first page for a post by Jim Ivy:

https://musescore.org/en/node/334200

Clearly, MuseScore 3 is abandoned with final ver. 3.6.2 and there will be no further development or support.

Concerning out-of-tree development/support, there are over 2,100 forks of the MuseScore github project. Heaven only knows if any of them are good and working continuations of 3.6.2 to provide maintenance, minimal development, etc.

Again, anyone who knows of a good fork of MuseScore 3 please post a comment here. Unless there is one, the official AppImage of 3.6.2 may be the best workable long term solution. (My expectation is that future changes to Qt will break the MuseScore 3.6.2 code base, and I'm NOT a Qt expert....)

I think all of this is real a shame because -- at least to me -- the GUI of ver. 4 is just plain confusing.... It makes the routine functions I use to transcribe and edit MIDI files (for public services which I support) much more difficult, and obscure, than ver. 3. I'm afraid MuseScore is the only freely available tool which can meet my needs so I may be stuck on 3.6.2 forever... ever... (ever...) ((ever...)) ;)

Clemmitt

All,

Remember, please vote for this pkg if you find it useful!

I have updated this AUR pkg so it can be installed in parallel with musescore4.

Note that this has NOT been extensively tested for regressions. Right now it's a Works-For-Me.

If you run into any problems please post a comment so I receive a notice, or contact me directly. HTH :)

P.S.: Since MuseScore has moved on from ver. 3, there will almost certainly be no upstream maintenance releases for this. I'll try to look around to see if anyone forks ver. 3.6.2 in order to maintain it. Please contact me if you know of a good and active fork. In the very long run, the only way to keep this working may be to create an AppImage and/or Flatpak and/or Snap image of this pkg. Do let me know if you are interested in this. TIA :)

Clemmitt

All,

While I'm at it... if you wish to build an AUR pkg in a clean chroot, the easiest way is to use extra-x86_64-build from the devtools pkg. Sample steps:

$ mkdir ~/my_AUR_dir/tmp
$ cp ~/some_dir/PKGBUILD ~/my_AUR_dir/tmp/
$ mkdir ~/my_AUR_dir/AUR_deps
$ cp ~/some_other_dir/pkg-name-1.2-3-x86_64.pkg.tar.zst ~/my_AUR_dir/AUR_deps/
$ cd ~/my_AUR_dir/tmp/
$ extra-x86_64-build -c -r ~/my_AUR_dir/tmp/ -- -I ~/my_AUR_dir/AUR_deps/pkg-name-1.2-3-x86_64.pkg.tar.zst

A forum thread I started (and closed) can be found at:

https://bbs.archlinux.org/viewtopic.php?id=281573

HTH! :)

Clemmitt

@kiasoc5,

When building AUR pkgs, make sure to install the base-devel group first. See:

https://wiki.archlinux.org/title/Arch_User_Repository#Getting_started

The debugedit pkg is a part of that group. If you have any other problems, please be sure to post a comment, and thanks for checking this pkg out :)

Clemmitt

Please add debugedit to makedeps, when building in a chroot the build complains that the debugedit executable is not present.

Thanks for this package. I will build the package in my git folder and use it directly from there (I will not install it).