----- Original Message -----
From: "David Kastrup" <[email protected]>
To: "Phil Holmes" <[email protected]>
Cc: "Federico Bruni" <[email protected]>; <[email protected]>
Sent: Tuesday, May 17, 2016 12:26 PM
Subject: Re: Gub/Savannah problem
"Phil Holmes" <[email protected]> writes:
----- Original Message -----
From: "David Kastrup" <[email protected]>
To: "Federico Bruni" <[email protected]>
Cc: "Phil Holmes" <[email protected]>; <[email protected]>
Sent: Tuesday, May 17, 2016 12:18 PM
Subject: Re: Gub/Savannah problem
Federico Bruni <[email protected]> writes:
Il giorno mar 17 mag 2016 alle 11:44, Phil Holmes
<[email protected]> ha scritto:
That looks like gibberish to me. I think the script or repository or
some environment variable may be misconfigured, pasting together
several
git origin specs.
-- David Kastrup
I've just looked at the logfiles for the previously successful
build, and the command appears identical:
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
From git://git.sv.gnu.org/lilypond
* [new branch] release/unstable ->
git.sv.gnu.org//lilypond.git/release/unstable
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
From git://git.sv.gnu.org/lilypond
* [new branch] release/unstable ->
git.sv.gnu.org//lilypond.git/release/unstable
(I've also attached the output as a text file, to avoid
line-breaking issues).
I've tried that command (copied from the attached file) and gives an
error:
$ 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'
the double slash // is triggering it
So where is it from? Some environment variable?
--
David Kastrup
And why was it not triggered 16 days ago, but was 2 days ago?
Because some environment variable is now set with a trailing slash?
--
David Kastrup
No - the double slash was there in my successful build of 2.19.41 - as I
said, I checked and posted that bit of the log file.
--
Phil Holmes
_______________________________________________
lilypond-devel mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/lilypond-devel
