Skip to content

musescore: update to 4.7.0#57968

Open
chrysos349 wants to merge 6 commits into
void-linux:masterfrom
chrysos349:musescore
Open

musescore: update to 4.7.0#57968
chrysos349 wants to merge 6 commits into
void-linux:masterfrom
chrysos349:musescore

Conversation

@chrysos349
Copy link
Copy Markdown
Contributor

@chrysos349 chrysos349 commented Nov 21, 2025

I made changes so that musescore could find the packages below:

  • migrated flac, libogg, libsndfile to cmake
  • added lame.pc to lame not allowed, thus removed
  • replaced libflac with flac as a dep in libflac-devel, because /usr/lib64/cmake/FLAC/targets.cmake requires binaries.

Testing the changes

  • I tested the changes in this PR: YES

Local build testing

  • I built this PR locally for my native architecture, (x86-64)

Comment thread srcpkgs/lame/files/lame.pc.in Outdated
@chrysos349 chrysos349 changed the title musescore: update to 4.6.3 musescore: update to 4.6.4 Dec 14, 2025
@Rutpiv
Copy link
Copy Markdown
Contributor

Rutpiv commented Dec 26, 2025

While looking into a MuseScore update, I noticed this PR also switches flac, libogg, and libsndfile to CMake. I’m not opposed to the change, but I might be missing some context: what’s the rationale?

According to upstream documentation, all three projects still support both autotools and CMake. In particular, libogg and libsndfile describe autotools as the primary or recommended build system, while FLAC treats both as equivalent.

For reference, I built MuseScore 4.6.4 locally against the current packages, without these build-system changes, and the build completed successfully. The only thing I noticed was CMake warnings about missing package config files for FLAC and libsndfile (SndFile) (e.g. FLACConfig.cmake / SndFileConfig.cmake), and then it fell back to pkg-config and continued.

I also tested the resulting build locally, and everything is working perfectly on my side. Thanks for working on this update.

Given that, is the goal mainly to provide CMake package config files/targets for these libraries and eliminate those warnings, or is there a concrete MuseScore-related failure with the autotools-built variants?

@chrysos349
Copy link
Copy Markdown
Contributor Author

Bundled deps vs system deps

@chrysos349 chrysos349 changed the title musescore: update to 4.6.4 musescore: update to 4.6.5 Dec 29, 2025
@github-actions
Copy link
Copy Markdown

Pull Requests become stale 90 days after last activity and are closed 14 days after that. If this pull request is still relevant bump it or assign it.

@github-actions github-actions Bot added the Stale label Mar 30, 2026
@chrysos349
Copy link
Copy Markdown
Contributor Author

Bump

@github-actions github-actions Bot removed the Stale label Mar 31, 2026
@doprz
Copy link
Copy Markdown

doprz commented Apr 7, 2026

Would it be possible to patch this PR to resolve the issue I outlined in: musescore/MuseScore#32911

or should we wait until this is patched upstream. The main thing is that the issue is with the MuseSampler shared lib which is closed-source.

TLDR; the fix is:

  • sudo ln -s /var/lib/dbus/machine-id /etc/machine-id
  • Delete ~/Muse Sounds/.instruments and re-download any instrument pack via MuseSounds Manager

@classabbyamp
Copy link
Copy Markdown
Member

no, upstream should fix it first

@chrysos349
Copy link
Copy Markdown
Contributor Author

Is there anything blocking this PR from being merged at the moment?

@chrysos349 chrysos349 changed the title musescore: update to 4.6.5 musescore: update to 4.7.0 May 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants