[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Issue 1726 in lilypond: python versions might not be updating
From: |
lilypond |
Subject: |
Issue 1726 in lilypond: python versions might not be updating |
Date: |
Thu, 30 Jun 2011 17:44:28 +0000 |
Status: Accepted
Owner: ----
Labels: Type-Build Priority-Medium
New issue 1726 by percival.music.ca: python versions might not be updating
http://code.google.com/p/lilypond/issues/detail?id=1726
We have one report that since 2.15.2, files in
out/python/
and/or
out/scripts/
do not get an updated version number. The final version then looks for
/2.15.2/ in the install dir, instead of looking for 2.15.3 or 2.15.4.
I have not checked that this is true. Interested parties should:
- set their VERSION to something silly like 2.15.1
- delete their build/ dir
- build from scratch
- change VERSION to 2.15.4
- **KEEP** the build/ dir
- do "make"
- look for version numbers in the .py files. If you still see a 2.15.1,
then this is a real problem.
If it's a real problem, the culprit might be the indentation change, or it
might be whatever build system stuff has happened in the last month.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Issue 1726 in lilypond: python versions might not be updating,
lilypond <=