Re: GUB fail

[Masamichi HOSODA]

> I presume this is owing to the changes to font handling that Masamichi has
> made, and I also presume that I can fix this by updating GUB.  Problem is,
> I'm confused with how to go about the latter.  My current GUB build
> environment is cloned from https://github.com/trueroad/gub and is built from
> the branch origin/pango-1.28.  I can see there are updates to this repo, but
> Github is not currently displaying to me the latest commits.  So: what's the
> easiest way to pick up the needed updates to git?

lilypond document
http://www.lilypond.org/doc/v2.19/Documentation/contributor/other-repositories
says that GUB's repository is
https://github.com/gperciva/gub

It is not my repository
https://github.com/trueroad/gub

My repository's upstream is gperciva/gub/master.
I think that my repository's branch pango-1.28 is obsolete.
It has been merged to upstream.

And, If I understand correctly, the branch master of
https://github.com/gperciva/gub
has already changed configure's font option.
https://github.com/gperciva/gub/pull/14

So, I think that the most easy way is to re-clone from
https://github.com/gperciva/gub

Or, perhaps you might be able to change the origin with the following commands.

$ git remote rm origin
$ git remote add origin address@hidden:gperciva/gub.git
$ git fetch origin
$ git checkout master
$ git merge origin/master