From: Ricardo Wurmus <rekado@elephly.net>
To: Mason Hock <masonhock@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: lilypond 2.19.80
Date: Fri, 22 Dec 2017 00:12:13 +0100 [thread overview]
Message-ID: <87y3lvwu9e.fsf@elephly.net> (raw)
In-Reply-To: <4cbdf5e9-e214-cc5e-7447-54e0c294c5a8@gmail.com>
Hi Mason,
> The current version of lilypond in Guix is 2.19.63, and it looks like
> its source is downloads.linuxaudio.org
>
> https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/music.scm?id=v0.14.0-407-gc521c8f1a#n810
>
> but the latest version at downloads.linuxaudio.org is 2.19.80
>
> http://download.linuxaudio.org/lilypond/source/v2.19/
>
> When will Guix be updated to reflect this?
When someone sends a patch or gets around to it. Would you like to
update it and send a patch? It probably won’t be more than two lines
that need to be changed.
--
Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
https://elephly.net
next prev parent reply other threads:[~2017-12-22 2:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-21 18:57 lilypond 2.19.80 Mason Hock
2017-12-21 23:12 ` Ricardo Wurmus [this message]
[not found] ` <1b2ede70-fc48-b789-533a-9ccd8907b025@gmail.com>
2017-12-22 6:39 ` Ricardo Wurmus
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=87y3lvwu9e.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=help-guix@gnu.org \
--cc=masonhock@gmail.com \
/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.
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).