Graham Percival writes: Graham,
> I would like to highlight this bug: > http://code.google.com/p/lilypond/issues/detail?id=1615 Does this patch help? You'll dowload the full repo. What I don't understand, is that when making releases with GUB, the idea is to use a local repo and never use savannah. You could get a commit in that is untested. The idea is to, before making a release, have your ~/vc/lilypond/ master git tree in a final, tested state and use THAT repository, something like make -f lilypond.make LILYPOND_REPO_URL=~/vc/lilypond So this bug could hit anyone, but should never be a problem for the release manager ;-) Jan diff --git a/gub/repository.py b/gub/repository.py index cd6bd5b..01fa57f 100644 --- a/gub/repository.py +++ b/gub/repository.py @@ -573,7 +573,7 @@ cd %(dir_slash_vcs)s && mv *bz2 *deb *gz *zip .. || : # We cannot do a shallow download if we're not tracking # we have to get at least enough history to include the # fixed committish ... :-) - self.shallow = self.is_tracking () + #no shallow# self.shallow = self.is_tracking () assert self.url_host assert self.url_dir def version (self): -- Jan Nieuwenhuizen <jann...@gnu.org> | GNU LilyPond http://lilypond.org Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.nl _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
