|
From: | Phil Holmes |
Subject: | Re: lilypond-2.19.41-1.documentation.tar.bz2 file missing |
Date: | Mon, 16 May 2016 14:34:07 +0100 |
"Federico Bruni" <address@hidden> wrote in message news:address@hidden
Il giorno lun 16 mag 2016 alle 10:57, Thomas Morley <address@hidden> ha scritto:Got my git-repository finally updated.The mentioned patch is in master, but the link on the website is indeed broken.Federico may I ask you to have a look?It's broken because Phil didn't make the 2.19.42 release yet. As soon as he uploads it, it should be ok.Related but different issue: http://lilypond.org/download (without trailing slash) should serve already (before the 2.19.42 release) the HTML page in the preferred language. There might be an issue with the browser cache though, which may add the trailing slash automatically. If you use Firefox, go to the History>Show all history, search lilypond.org, right-click on it and click on "Forget this site".
I tried to make the release but it failed. I've tried to post to .devel with details of the failure, but nothing appeared there. If this makes it through, could someone forward it to .devel, please?
I'm trying to build a Gub release, but failing very quickly. In the logs, I get:
invoking cd /home/gub/NewGub/gub/downloads/lilypond/git && git fetch git://git.sv.gnu.org/lilypond.git release/unstable:refs/heads/git.sv.gnu.org//lilypond.git/release/unstable fatal: The remote end hung up unexpectedly Command barfed: cd /home/gub/NewGub/gub/downloads/lilypond/git && git fetch git://git.sv.gnu.org/lilypond.git release/unstable:refs/heads/git.sv.gnu.org//lilypond.git/release/unstable (extra line breaks added for Gmane posting)If I try the command manually, not surprisingly the cd works, but I again get a failure from git:
git fetch git://git.sv.gnu.org/lilypond.git release/unstable:refs/heads/git.sv.gnu.org//lilypond.git/release/unstable fatal: Invalid refspec 'release/unstable:refs/heads/git.sv.gnu.org//lilypond.git/release/unstable'I'm wondering whether it's to do with the changes at Savannah, but does anyone have a better idea or a fix?
Ta. --Phil Holmes
[Prev in Thread] | Current Thread | [Next in Thread] |