From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>
Cc: GNU Debbugs <control@debbugs.gnu.org>,
Nicolas Goaziou <mail@nicolasgoaziou.fr>,
71668@debbugs.gnu.org
Subject: [bug#71668] [PATCH] gnu: musescore: Update to 4.3.2.
Date: Mon, 08 Jul 2024 14:51:12 -0400 [thread overview]
Message-ID: <87h6czzpi7.fsf@gmail.com> (raw)
In-Reply-To: <4391c70e5e1ae23fae78779449162fbe0a3811ca.camel@gmail.com> (Liliana Marie Prikler's message of "Fri, 05 Jul 2024 10:04:07 +0200")
unarchive 71668
reopen 71668
thanks
Hi Liliana!
Liliana Marie Prikler <liliana.prikler@gmail.com> writes:
> Hi Maxim,
>
> Am Sonntag, dem 23.06.2024 um 21:54 -0400 schrieb Maxim Cournoyer:
>> Hi,
>>
>> Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
>>
>> > * gnu/packages/music.scm (musescore): Update to 4.3.2.
>> >
>> > Change-Id: I78b5508645430a6f96d9fc03caa1015a4905a6f2
>> > ---
>> > gnu/packages/music.scm | 4 ++--
>> > 1 file changed, 2 insertions(+), 2 deletions(-)
>> >
>> > diff --git a/gnu/packages/music.scm b/gnu/packages/music.scm
>> > index c12bb843fe..e5669c5d87 100644
>> > --- a/gnu/packages/music.scm
>> > +++ b/gnu/packages/music.scm
>> > @@ -5393,7 +5393,7 @@ (define-public sfizz
>> > (define-public musescore
>> > (package
>> > (name "musescore")
>> > - (version "4.2.1")
>> > + (version "4.3.2")
>> > (source
>> > (origin
>> > (method git-fetch)
>> > @@ -5402,7 +5402,7 @@ (define-public musescore
>> > (commit (string-append "v" version))))
>> > (file-name (git-file-name name version))
>> > (sha256
>> > - (base32
>> > "0rc5ma1k0cjllfl86apbyj61sh0691lsmqnvqicyn0zi53z8w9v0"))
>> > + (base32
>> > "1hx0l6d7avyfbh88hwn01h9q51mgd9zix91q2kgg1ax73pqxhfs2"))
>> > (modules '((guix build utils)))
>> > (snippet
>> > '(begin
> Did you really push this? I don't see it on master.
Looks like I haven't. Sorry for the noise.
> Anyhow, I noticed that MuseScore swapped its build flags. At the very
> least, you'll have to write
> "-DMUE_DOWNLOAD_SOUNDFONT=OFF"
> "-DMUE_BUILD_DIAGNOSTICS=OFF"
> instead of the ones we're currently using.
>
> I also started investigating the FSDG issues[1] and at the very least
> it seems some unbundling is needed for the thirdparty stuff.
OK. I've reopened the issue so we can track these comments as part of a
v2.
--
Thanks,
Maxim
prev parent reply other threads:[~2024-07-08 18:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-20 6:53 [bug#71668] [PATCH] gnu: musescore: Update to 4.3.2 Nicolas Goaziou via Guix-patches via
2024-06-24 1:54 ` bug#71668: " Maxim Cournoyer
2024-07-05 8:04 ` [bug#71668] " Liliana Marie Prikler
2024-07-08 18:51 ` Maxim Cournoyer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h6czzpi7.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=71668@debbugs.gnu.org \
--cc=control@debbugs.gnu.org \
--cc=liliana.prikler@gmail.com \
--cc=mail@nicolasgoaziou.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).