[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Lilypond-auto] Issue 2585 in lilypond: current po breaks GUB
From: |
lilypond |
Subject: |
Re: [Lilypond-auto] Issue 2585 in lilypond: current po breaks GUB |
Date: |
Mon, 04 Jun 2012 13:34:11 +0000 |
Comment #3 on issue 2585 by address@hidden: current po breaks GUB
http://code.google.com/p/lilypond/issues/detail?id=2585
Correction: it's a mismatch between the GUB version of msgfmt and the
6-day-old change to po/cs.po. There are two options: 1) update msgfmt in
GUB, 2) change po/cs.po (and probably other .po files).
1) Updating gettext in GUB might be a one-hour job. Edit
gub/specs/gettext.py, build, upload to your test server, ask lilypond-user
for 2-3 people to test the main binaries (mingw, darwin-x86, linux-x86,
linux-64), then when they all say it's good send a patch to me.
Or it might be a 30-hour job. Update gettext, have a compile error because
the later gettext requires more libraries. Find or update those libraries
in GUB. New gettext compiles, but then other software which uses gettext
doesn't compile because gettext is too new. Update that other software.
Finish build. Upload binaries. New software works on linux, but breaks in
mingw. Scour the internet for other instances of the error messages. Try
fix, rebuild, upload, etc.
For the record, I will provide the same amount of help that I do for Colin
-- I'll read your reports, I'll make suggests as they pop into my head, I
may test stuff occasionally on my own machine, but I am not offering to do
any "real work" on this.
2) the new po/cs.po comes from two places: text edited by the translator,
and some other build process (which I believe comes from "make po-replace"
but don't quote me on that).
- if it's text edited by the translator, I can almost guarantee that it can
be fixed in 30 minutes or less.
- if it's a changed build process (within lilypond), then it's probably
6d84a36fd1dde3fe2035ff17a78672c72f3ab0fc or some similar commit within the
past month. I'm confident that it can be fixed in 60 minutes or less.
If you're in a mood to play with GUB, then I don't want to discourage you
(since there's a lot of old software in GUB that would be helpful to
update), but I want to make sure you know what you're getting into.
- [Lilypond-auto] Issue 2585 in lilypond: current po breaks GUB, lilypond, 2012/06/03
- Re: [Lilypond-auto] Issue 2585 in lilypond: current po breaks GUB, lilypond, 2012/06/04
- Re: [Lilypond-auto] Issue 2585 in lilypond: current po breaks GUB, lilypond, 2012/06/04
- Re: [Lilypond-auto] Issue 2585 in lilypond: current po breaks GUB,
lilypond <=
- Re: [Lilypond-auto] Issue 2585 in lilypond: current po breaks GUB, lilypond, 2012/06/04
- Re: [Lilypond-auto] Issue 2585 in lilypond: current po breaks GUB, lilypond, 2012/06/04
- Re: [Lilypond-auto] Issue 2585 in lilypond: current po breaks GUB, lilypond, 2012/06/04
- Re: [Lilypond-auto] Issue 2585 in lilypond: current po breaks GUB, lilypond, 2012/06/04
- Re: [Lilypond-auto] Issue 2585 in lilypond: current po breaks GUB, lilypond, 2012/06/04
- Re: [Lilypond-auto] Issue 2585 in lilypond: current po breaks GUB, lilypond, 2012/06/07
- Re: [Lilypond-auto] Issue 2585 in lilypond: current po breaks GUB, lilypond, 2012/06/11
- Re: [Lilypond-auto] Issue 2585 in lilypond: current po breaks GUB, lilypond, 2012/06/11
- Re: [Lilypond-auto] Issue 2585 in lilypond: current po breaks GUB, lilypond, 2012/06/12