On Sat, Nov 03, 2012 at 04:29:53PM -0000, Phil Holmes wrote:
> I finished building 2.17.6 about 30 minutes ago. Gub failed again,
> but I know how to fix this manually and have done so, so it's ready
> for upload.
I suggest a moratorium on releases until GUB works. Too many
things can go wrong when manual steps are required.
> I've just pushed a
> commit to gperciva/gub that will likely fix this - although this is
> somewhat "by inspection" so if anyone knows more of the internals of
> gub and can comment, I'd be happy.
This looks questionable to me:
-NATIVE_BUILD_COMMITTISH=$(shell cat
$(LILYPOND_REPO_BRANCH_DIR)/refs/heads/$(LILYPOND_DIRRED_BRANCH))
+NATIVE_BUILD_COMMITTISH=$(shell cat
$(LILYPOND_REPO_DIR)/git/refs/heads/$(LILYPOND_DIRRED_BRANCH))
Isn't _BRANCH_DIR vs. _DIR how we distinguish between master and
release/unstable and stable/2.16 ?
- Graham
_______________________________________________
lilypond-devel mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/lilypond-devel
