Updates:
Labels: -Patch-needs_work Patch-abandoned
Comment #11 on issue 1496 by colinpkc...@gmail.com: Update Pango to 1.28.3
http://code.google.com/p/lilypond/issues/detail?id=1496
No change, apart from priority change, since MArch.
___
bug-
Updates:
Labels: -Priority-High Priority-Medium
Comment #10 on issue 1496 by percival.music.ca: Update Pango to 1.28.3
http://code.google.com/p/lilypond/issues/detail?id=1496
(No comment was entered for this change.)
___
bug-lilypond mailing
Comment #9 on issue 1496 by pnorcks: Update Pango to 1.28.3
http://code.google.com/p/lilypond/issues/detail?id=1496
A little update here:
I just tested Pango 1.25.5 with LilyPond, which is the version appropriate
for use in GUB (GNOME platform 2.27.91), but I don't think this is a good
choi
Updates:
Labels: -Patch-new Patch-needs_work
Comment #8 on issue 1496 by percival.music.ca: Update Pango to 1.28.3
http://code.google.com/p/lilypond/issues/detail?id=1496
To avoid confusing our new Patch-review guy: this patch is waiting for
attention from Patrick and/or Jan.
__
Comment #7 on issue 1496 by percival.music.ca: Update Pango to 1.28.3
http://code.google.com/p/lilypond/issues/detail?id=1496
ok. I'll let you and Jan sort this out. Whenever you want me to test GUB
master, I'm happy to do that. Otherwise, I'll focus on the lilypond patch
backlog. I'm no
Comment #6 on issue 1496 by pnorcks: Update Pango to 1.28.3
http://code.google.com/p/lilypond/issues/detail?id=1496
The "build fix" patch is completely unrelated to the Pango bump patch, so
they indeed should be tested separately. To prioritize, I would rank the
Pango issue above my build f
Comment #4 on issue 1496 by percival.music.ca: Update Pango to 1.28.3
http://code.google.com/p/lilypond/issues/detail?id=1496
ok, I can now confirm that mingw::pango can build; I'm now continuing a
general lilypond build. For the record, my GUB git head is:
e234bcda96452a3ec38cf83e96907f1a
Comment #3 on issue 1496 by percival.music.ca: Update Pango to 1.28.3
http://code.google.com/p/lilypond/issues/detail?id=1496
ok, g_int64_hash was introduced in glib-2.22. I'll try that other patch I
saw from you.
In general, I think it would be good to get the dependency-bumping patches
Updates:
Labels: Patch-new
Comment #5 on issue 1496 by percival.music.ca: Update Pango to 1.28.3
http://code.google.com/p/lilypond/issues/detail?id=1496
... and now darwin-x86::glib fails. I believe the answer is here:
http://www.openldap.org/faq/data/cache/1191.html
but I need to go
Comment #2 on issue 1496 by percival.music.ca: Update Pango to 1.28.3
http://code.google.com/p/lilypond/issues/detail?id=1496
Does this mean anything to you off the top of your head?
/main/src/gub/target/mingw/src/pango-1.28.3/modules/basic/basic-win32.c: In
function 'itemize_shape_and_place'
Comment #1 on issue 1496 by pnorcks: Update Pango to 1.28.3
http://code.google.com/p/lilypond/issues/detail?id=1496
tools::pango checks out okay, but I haven't built any of the installers yet.
To clarify, this patch bumps Pango from 1.26.0 to 1.28.3. This has the
following effects (that I've
Status: Accepted
Owner: pnorcks
Labels: Type-Build Priority-High
New issue 1496 by pnorcks: Update Pango to 1.28.3
http://code.google.com/p/lilypond/issues/detail?id=1496
GUB is currently using Pango 1.26.0, but over time I've noticed some major
regressions with shaping of Khmer script, and no
12 matches
Mail list logo
