Re: Issue 2338 in lilypond: OS X LilyPad not working
Comment #46 on issue 2338 by colingh...@gmail.com: OS X LilyPad not working http://code.google.com/p/lilypond/issues/detail?id=2338 Klaus Foehl reported by private email that 2.15.32 fails to load on MacOS X 10.4.11 x86. See my followup posting here: http://lists.gnu.org/archive/html/bug-lilypond/2012-03/msg00395.html So the status of lilypond-2.15.32 on MacOS X right now is as follows: |-+-++--| | MacOS X | x86/ppc | User | Issue 2338 | | version | || on 2.15.32 | |-+-++--| | 10.4.11 | ppc | Ole Schmidt| verified | | | | James Worlton | verified | |-+-++--| | 10.4.11 | x86 | Klaus Foehl| fails| |-+-++--| | 10.5.8 | ppc | Stan Sanderson | verified | |-+-++--| | 10.5.8 | x86 | Stan Sanderson | verified | |-+-++--| | 10.6.8 | x86 | Ole Schmidt| verified | |-+-++--| | 10.7.3 | x86 | Eric Schissel | verified | | | | Hans Aikema| verified | |-+-++--| | 10.7.x | x86 | Phillipe | verified | |-+-++--| I'm leaving this as verified for now. Even though James Worlton reported 2271 was fixed on 2.15.30 the symptoms are identical to what Klaus Foehl reports agains 2.15.32 Looks like we should re-open issue 2271 and try to get agreement between James and Klaus about the behaviour of 2.15.30 and 2.15.32 on MacOS X 10.4.11 ppc. Comments, please. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2338 in lilypond: OS X LilyPad not working
Updates: Status: Verified Comment #44 on issue 2338 by colingh...@gmail.com: OS X LilyPad not working http://code.google.com/p/lilypond/issues/detail?id=2338 Various Mac OS X users, credited below, have verified this issue on 2.15.32. The only Mac OS X configuration not covered is 10.4.11 on x86 So I'm marking this as verified. A big thanks from the bug squad to all the users who gave their time to help with this effort. MacOS X x86/ppc User Issue 2338 version on 2.15.32 -+-++ 10.4.11 ppc Ole Schmidt verified James Worltonverified -+-++ 10.4.11 x86 not verified -+-++ 10.5.8 ppc Stan Sanderson verified -+-++ 10.5.8 x86 Stan Sanderson verified -+-++ 10.6.8 x86 Ole Schmidt verified -+-++ 10.7.3 x86 Eric Schisselverified Hans Aikema verified -+-++ 10.7.x x86 Phillipe verified ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2338 in lilypond: OS X LilyPad not working
Comment #40 on issue 2338 by colingh...@gmail.com: OS X LilyPad not working
http://code.google.com/p/lilypond/issues/detail?id=2338
Klaus Foegel reported on lilypond-user:
http://article.gmane.org/gmane.comp.gnu.lilypond.general/70477
http://article.gmane.org/gmane.comp.gnu.lilypond.general/70478
I'm a bit concerned that even with the plist fixed Klaus still has a
problem getting Lilypad to run.
I'm going to get some 10.4 users to run the new Lilypad app and confirm
that they have no issue launching it.
Klaus' post below:
Hello,
MacOS X x86: LilyPond 2.15.31-1 unpacked and installed on
Mac OS X Version 10.4.11 MacMini Intel Core Duo.
Adding the missing /string to a line including spaces in Info.plist,
after reboot proper Lilypond icon shows up. As per issue 2338.
Double-clicking on icon gives Error, no description in the Error Window,
Console log see below.
Regards
Klaus
P.S.
1) Similar post this morning did not come through, hence re-posting.
2) lilypond inside ...resources..bin... does work.
3) unavailable for testing next 2.7 weeks
Mac OS X Version 10.4.11 (Build 8S2167)
2012-03-04 21:37:44 +
2012-03-04 21:37:44.707 SystemUIServer[78] lang is:en
Mar 4 21:37:45 klaus-foehls-computer mDNSResponder: Adding
browse domain local.
Traceback (most recent call last):
File /Users/kf/Desktop/testlily/LilyPond.app/Contents/Resou
rces/__boot__.py, line 31, in module
_run('LilyPond.py')
File /Users/kf/Desktop/testlily/LilyPond.app/Contents/Resou
rces/__boot__.py, line 28, in _run
execfile(path, globals(), globals())
File /Users/kf/Desktop/testlily/LilyPond.app/Contents/Resou
rces/LilyPond.py, line 3, in module
from PyObjCTools import AppHelper
File PyObjCTools/AppHelper.pyc, line 14, in module
File AppKit/__init__.pyc, line 9, in module
File Foundation/__init__.pyc, line 10, in module
File CoreFoundation/__init__.pyc, line 21, in module
File CoreFoundation/_CoreFoundation.pyc, line 18, in module
File CoreFoundation/_CoreFoundation.pyc, line 11, in __load
ImportError: dlopen(/Users/kf/Desktop/testlily/LilyPond.app/Cont
ents/Resources/lib/python2.6/lib-dynload/CoreFoundation/_CoreFou
ndation.so, 2): Symbol not found: _CFFileDescriptorCreate
Referenced from: /Users/kf/Desktop/testlily/LilyPond.app/Conte
nts/Resources/lib/python2.6/lib-dynload/CoreFoundation/_CoreFoundation.so
Expected in: /System/Library/Frameworks/CoreFoundation.framewo
rk/CoreFoundation
2012-03-04 21:38:00.639 LilyPond[131] LilyPond Error
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2338 in lilypond: OS X LilyPad not working
Comment #42 on issue 2338 by colingh...@gmail.com: OS X LilyPad not working http://code.google.com/p/lilypond/issues/detail?id=2338 Stan Sanderson reports that 2.15.32 launches on MacOS X 10.5.8 x86 http://lists.gnu.org/archive/html/lilypond-user/2012-03/msg00120.html ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2338 in lilypond: OS X LilyPad not working
Updates: Status: Fixed Labels: fixed_2_15_32 Comment #34 on issue 2338 by gra...@percival-music.ca: OS X LilyPad not working http://code.google.com/p/lilypond/issues/detail?id=2338 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2338 in lilypond: OS X LilyPad not working
Comment #35 on issue 2338 by voo...@gmail.com: OS X LilyPad not working http://code.google.com/p/lilypond/issues/detail?id=2338 It's still broken - info.plist is missing a /string tag at the end of line 57. After manually adding the missing tag, things seem to be OK. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2338 in lilypond: OS X LilyPad not working
Updates: Status: Accepted Comment #36 on issue 2338 by d...@gnu.org: OS X LilyPad not working http://code.google.com/p/lilypond/issues/detail?id=2338 On the bright side, the speed of the feedback was such that the thought of working on the problem until it gets fixed is becoming more realistic for those who want to tackle it. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2338 in lilypond: OS X LilyPad not working
Updates: Status: Fixed Comment #37 on issue 2338 by gra...@percival-music.ca: OS X LilyPad not working http://code.google.com/p/lilypond/issues/detail?id=2338 Given that we do not have a 2.15.32 release yet, I think it is premature to claim that the binary does not work. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2338 in lilypond: OS X LilyPad not working
Comment #38 on issue 2338 by d...@gnu.org: OS X LilyPad not working http://code.google.com/p/lilypond/issues/detail?id=2338 Ouch. Indeed. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2338 in lilypond: OS X LilyPad not working
Updates: Labels: Patch-new Comment #22 on issue 2338 by mts...@gmail.com: OS X LilyPad not working http://code.google.com/p/lilypond/issues/detail?id=2338#c22 Integrates new version of LilyPad http://codereview.appspot.com/5713050 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2338 in lilypond: OS X LilyPad not working
Comment #23 on issue 2338 by mts...@gmail.com: OS X LilyPad not working http://code.google.com/p/lilypond/issues/detail?id=2338 I built a version for OS X this morning that works using Christian's new LilyPad. I tested it on my mac and it works like a charm. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2338 in lilypond: OS X LilyPad not working
Comment #24 on issue 2338 by gra...@percival-music.ca: OS X LilyPad not working http://code.google.com/p/lilypond/issues/detail?id=2338 How was that tarball created? I refuse to accept any patch which uses a tarball created with unknown methods. That would be begging for problems down the road. I want a patch or pull request for https://github.com/gperciva/lilypad which updates the code, or at least updates the macosx/README to say what manual steps must be taken to alter the build created with the code. See comments 3 and 4 in this issue. Once I have that, I'll upload the tarball to lilypond.org and we can proceed as usual. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2338 in lilypond: OS X LilyPad not working
Comment #25 on issue 2338 by mts...@gmail.com: OS X LilyPad not working http://code.google.com/p/lilypond/issues/detail?id=2338 This is out of my zone of competencies. Christian - can you make a patch w/ respect to the lilypad on git hub that will generate the tarball you posted in comment #3? ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2338 in lilypond: OS X LilyPad not working
Comment #26 on issue 2338 by colingh...@gmail.com: OS X LilyPad not working http://code.google.com/p/lilypond/issues/detail?id=2338 As I understand it, what is required is: git clone lilypad create a new local branch unpack Christian's lilypad tarball alongside the git one merge Christian's edits into the local git branch use a git patch command upload patch in the usual way for review. Mike, Christian, is the above correct? If so I'm happy to give it a shot. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2338 in lilypond: OS X LilyPad not working
Comment #27 on issue 2338 by mts...@gmail.com: OS X LilyPad not working http://code.google.com/p/lilypond/issues/detail?id=2338 I don't think it works this way - Christian's tarball is an out-of-the-box ready-to-work LilyPad, whereas Graham's git branch is (if I'm not mistaken) the code that actually builds LilyPad. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2338 in lilypond: OS X LilyPad not working
Comment #28 on issue 2338 by colingh...@gmail.com: OS X LilyPad not working http://code.google.com/p/lilypond/issues/detail?id=2338 Right. I'll contact Christian and ask him to tar up his dev directory then. Otherwise, is my outline of the work involved to get to a patch correct? ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2338 in lilypond: OS X LilyPad not working
On Mar 1, 2012, at 3:12 PM, lilyp...@googlecode.com wrote: Comment #28 on issue 2338 by colingh...@gmail.com: OS X LilyPad not working http://code.google.com/p/lilypond/issues/detail?id=2338 Right. I'll contact Christian and ask him to tar up his dev directory then. Otherwise, is my outline of the work involved to get to a patch correct? Yup - the idea is that we want grahms fork of LilyPad to produce a reliable LilyPad from scratch. I think it's worth it to do this to get 2.16 out. Afterwards, we should do some brainstorming about better ways to package manage. For example, brew has a lilypond OS X port of the stable version and jEdit can be used. If these become the Mac OS X instructions on the webpage, people will actually get a better UI than if they download what we bundle. It then becomes necessary that developer resources be spent on maintaining these packages, but it seems like this is a better (and more decentralized) use of our time than maintaining a GUI text editor. Cheers, MS ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2338 in lilypond: OS X LilyPad not working
Comment #29 on issue 2338 by chh...@gmail.com: OS X LilyPad not working http://code.google.com/p/lilypond/issues/detail?id=2338 Yes, I admit, I have cheated when creating the 0.6.2 package by manually fixing the Info.plist file. To get this all cleared up, I have built a new version of osx lilypad (0.6.3) [1] from a clean checkout of https://github.com/chhitz/lilypad (see my Pull-Request) according to the checked-in README. Further I have verified that this lilypad build can be processed by GUB to produce a working LilyPond.app for darwin-x86. [1] http://klarinett.li/lilypond/osx-lilypad-universal-0.6.3.tar.gz ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2338 in lilypond: OS X LilyPad not working
Comment #30 on issue 2338 by colingh...@gmail.com: OS X LilyPad not working http://code.google.com/p/lilypond/issues/detail?id=2338 Pull request here: https://github.com/gperciva/lilypad/pulls ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2338 in lilypond: OS X LilyPad not working
Updates: Status: Accepted Labels: -fixed_2_15_31 Comment #32 on issue 2338 by gra...@percival-music.ca: OS X LilyPad not working http://code.google.com/p/lilypond/issues/detail?id=2338 oops, I should wait until GUB is updated. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2338 in lilypond: OS X LilyPad not working
Comment #33 on issue 2338 by mts...@gmail.com: OS X LilyPad not working http://code.google.com/p/lilypond/issues/detail?id=2338 Go for it - I haven't forked your GUB yet and am still using the one for which I don't have commit access. I'll make the move w/in the next week. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2338 in lilypond: OS X LilyPad not working
Updates: Labels: -Type-Build -Patch-needs_work Type-Critical Patch-review Comment #20 on issue 2338 by gra...@percival-music.ca: OS X LilyPad not working http://code.google.com/p/lilypond/issues/detail?id=2338 I disagree; the question at hand is whether we should remove OSX from the list of supported platforms. If we do not do this, then this remains a Critical issue. As it happens, I wanted this patch to miss one countdown, but I think it should go on the next one. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2338 in lilypond: OS X LilyPad not working
Comment #21 on issue 2338 by d...@gnu.org: OS X LilyPad not working http://code.google.com/p/lilypond/issues/detail?id=2338 I don't think it makes any sense to put individual varying problems with MacOSX in our Changes file. It might make sense mentioning them on the download page. But I think that we should rather put there a link to the issue tracker, OpSys-OSX entries with status New, Accepted, Started, Fixed. On the assumption that Verified issues are not relevant if you installed the latest version. That way we don't need any manual updates of MacOSX info. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2338 in lilypond: OS X LilyPad not working
Comment #18 on issue 2338 by nfgodd...@gmail.com: OS X LilyPad not working http://code.google.com/p/lilypond/issues/detail?id=2338 Hi, I'm seeing the same issue on OSX Lion (10.7.3) using Lilypond 2.15.30 as stated above, adding /string to the end of the line: stringBuild from Fri Feb 17 13:02:09 2012 in Lilypond.app/Content/Info.plist fixes it and the icon for the app is restored and the program seems to run fine. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2338 in lilypond: OS X LilyPad not working
Updates: Owner: d...@gnu.org Labels: -Type-Critical -Patch-review Type-Build Patch-needs_work Comment #19 on issue 2338 by colinpkc...@gmail.com: OS X LilyPad not working http://code.google.com/p/lilypond/issues/detail?id=2338 Given the simple enough fix: requiring OSX users to manually edit the Info.plist, should the patch not document this as well? Also, because of the simple workaround, I think it cannot be considered Critical, so I'm marking it as Type-build because of comment #3. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2338 in lilypond: OS X LilyPad not working
Comment #9 on issue 2338 by d...@gnu.org: OS X LilyPad not working http://code.google.com/p/lilypond/issues/detail?id=2338 So we are again at square one, right? We have some information that some OSX applications do not work on some (or all) OSX versions, and nobody knows how to move forward on this one, we have nobody who can or will take responsibility for OSX, and it is the only critical issue holding up the next stable release. Feedback from actual OSX users takes, if we are lucky, a week to arrive after blind (and quite costly) best-faith efforts from non-users of the platform, even for trivial changes. I really don't see how we can declare the degree to which OSX is supported anything other than Good luck!. It is somewhat comforting that the command line application LilyPond itself is usually not affected. Would we have a better chance for being at least able to deliver LilyPond (and most Python utilities) if we skipped on the third-party applications/editors/desktop-icons and just recommended downloading and installing them separately? ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2338 in lilypond: OS X LilyPad not working
Comment #10 on issue 2338 by stans...@gmail.com: OS X LilyPad not working http://code.google.com/p/lilypond/issues/detail?id=2338 Please look at my post on the User list regarding info.plist omission in the x86 2.15.30-1 version. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2338 in lilypond: OS X LilyPad not working
Comment #11 on issue 2338 by gra...@percival-music.ca: OS X LilyPad not working http://code.google.com/p/lilypond/issues/detail?id=2338 David -- I know exactly what needs to be done. I'm not doing it because I don't want to be doing it. I've already spent more than 5 hours this past weekend and today dealing with admin issues, so as far as I'm concerned my soul is pure. The biggest stumbling blocks are: 1) nobody wants to take responsibility for OSX. Simply having somebody keeping track of the issue and delegating tasks would be a big step forward. 2) too few people can build* GUB. See recent emails by Carl and me on -devel. * BTW, by this I mean too few people can even complete 'make boostrap', i.e. nothing osx-specific at all, in GUB. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2338 in lilypond: OS X LilyPad not working
Comment #12 on issue 2338 by d...@gnu.org: OS X LilyPad not working http://code.google.com/p/lilypond/issues/detail?id=2338 Stan, you omitted a pointer to the posting. I spent about half an hour digging it up. It reported the problem triggering this report 8 days ago. You can see in this issue that Christian Hitz provided a new tarball 5 days ago. There has been a request to make his sources available in a manner where this is not just a blind game of being in luck with picking a suitable version of LilyPad and transferring it to GUB with lots of manual work. There has been no reply apparently so far. This is a total resource hog poking around blindly in the dark, making a mockery of all release planning. This issue is, at the moment, lying dormant. There is no owner, nothing going forward on it, and its state of Critical, correctly assigned for a regression and/or failing components in a supported platform, is delaying a stable release of LilyPond indefinitely. As long as we have nobody declaring to take a reasonable amount of responsibility for keeping OSX workable, there is no point in maintaining the supported platform status. Because it does not mean that we support OSX, but rather that we stop supporting anything else as well. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2338 in lilypond: OS X LilyPad not working
Comment #13 on issue 2338 by d...@gnu.org: OS X LilyPad not working http://code.google.com/p/lilypond/issues/detail?id=2338 Regarding comment #11: David -- I know exactly what needs to be done. I'm not doing it because I don't want to be doing it. Believe it or not: I have no beef with that. I have no interest in providing CP/M support for LilyPond either though I probably would be the best qualified person among those reading these lists. I have no sympathy for the you should be doing it because you are better at it than me stance. It is not just that it is a lot of work to do for somebody else, it is also that it is _totally_ _inefficient_ work since those whom it would concern are not even stepping up for _timely_ and _reliable_ feedback. This farce has been going on for _months_. We have to adapt our decisions and planning to our resources. And I have not seen anything to suggest that our resources permit declaring OSX a supported platform, one where a failure in components will be considered release-critical. You have made the last OSX release cycle because David is such a nice guy, as bad a reason as any I can imagine. And lo-and-behold, it was in vain since it appears you integrated a tarball that was basically unchecked in an important component. And caused another extended delay with no end in sight. Even if you were willing to do this song-and-dance routine again and again, I would feel _totally_ silly asking for it. And I am not such a nice guy that I would take over such a futile task and stop working on things that actually lead to results. I don't see any way around stopping to guarantee LilyPad (and likely other components) to work as delivered under MacOSX. We can point to the respective web sites, and to our source code. And then it is up to the OSX users how they deal with that. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2338 in lilypond: OS X LilyPad not working
Updates: Labels: Patch-new Comment #14 on issue 2338 by d...@gnu.org: OS X LilyPad not working http://code.google.com/p/lilypond/issues/detail?id=2338#c14 changes.tely: declare MacOSX unsupported This addresses issue 2338. http://codereview.appspot.com/5694092 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2338 in lilypond: OS X LilyPad not working
Updates: Labels: Patch-review Comment #15 on issue 2338 by d...@gnu.org: OS X LilyPad not working http://code.google.com/p/lilypond/issues/detail?id=2338#c15 Patchy the autobot says: LGTM. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2338 in lilypond: OS X LilyPad not working
Comment #16 on issue 2338 by colingh...@gmail.com: OS X LilyPad not working http://code.google.com/p/lilypond/issues/detail?id=2338 Here is a link to Stan's posting: http://lists.gnu.org/archive/html/lilypond-user/2012-02/msg00854.html And here is the text: On Feb 18, 2012, at 2:50 PM, Stan Sanderson address@hidden wrote: On Mac OS X x86, LilyPond 2.15.30-1 would not run after expansion. A problem was reported with the Info.plist file. Upon examining the file (via: View Package Contents) I found a missing /string. All runs well after adding it to the info.plist file. I found the missing command by comparing the bad file to one from a previous (working) version, 2.15.22. Stan I note the discussion in the bug list today. The issue initially reported is easily corrected. As far as I know, there was no response to my message and I assumed the discussion was closed. I am an occasional user of LilyPond who is willing, to the best of my time and ability constraints, help test Mac PPC and x86, OS X v10.5.8 versions of LilyPond. The current latest development version (2.15.30-1) works for me on both platforms. Stan ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2338 in lilypond: OS X LilyPad not working
Comment #17 on issue 2338 by colingh...@gmail.com: OS X LilyPad not working http://code.google.com/p/lilypond/issues/detail?id=2338 Dave Kastrup posted a report from Klaus Foehl: http://lists.gnu.org/archive/html/bug-lilypond/2012-02/msg01058.html Phil Holmes identified (and I agree) that this looks to be another report of this issue. So Klaus Foehl, Philippe Massart and Stan Sanderson have all reported the same bug. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2338 in lilypond: OS X LilyPad not working
Comment #5 on issue 2338 by d...@gnu.org: OS X LilyPad not working http://code.google.com/p/lilypond/issues/detail?id=2338 I am pointing out that OSX has now been responsible for about a month of stable release delay. The people spending most of the time for fixing the problem have no way of testing it. Any useful feedback even for total blunders takes weeks to arrive, and arrives more by accident rather than release-related coordinated testing, testing that does not require more skills than actually using the respective platform. And that right before a major release. I think we owe the OSX users the following information in the release announcement for 2.16: a) since we don't have any actual users of MacOSX available for systematic testing and feedback, support for MacOSX is only provisional. If any component of it works, you are in luck. b) without anybody willing to engage in regular, timely and systematic testing, we have no option but considering MacOSX an unsupported platform. While we will package MacOSX versions for the near future, there is no way for us to know whether any part of them will actually work, and on what OSX versions. For that reason, it does not make sense to have our release schedule set back in case somebody actually happens to report a problem short before a release. Without anybody willing to do systematic testing and thus provide the most basic criterion for calling a system supported, any problem occuring only in relation with OSX will not be considered release-critical. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2338 in lilypond: OS X LilyPad not working
Issue 2338: OS X LilyPad not working http://code.google.com/p/lilypond/issues/detail?id=2338 This issue is now blocking issue 2271. See http://code.google.com/p/lilypond/issues/detail?id=2271 -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2338 in lilypond: OS X LilyPad not working
Comment #7 on issue 2338 by carl.d.s...@gmail.com: OS X LilyPad not working http://code.google.com/p/lilypond/issues/detail?id=2338 I would agree with this description if it applied to OSX 10.4. We have users regularly using OSX 10.5 through 10.7. Thanks, Carl ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2338 in lilypond: OS X LilyPad not working
Comment #4 on issue 2338 by gra...@percival-music.ca: OS X LilyPad not working http://code.google.com/p/lilypond/issues/detail?id=2338 Could I get a pull request for the fix you made to your fork of lilypad? I'm guessing this wasn't the only commit which produced that tarball. https://github.com/chhitz/lilypad/commit/481284468bd1155b52376453d0f6679f86cefb40 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2338 in lilypond: OS X LilyPad not working
Comment #3 on issue 2338 by chh...@gmail.com: OS X LilyPad not working http://code.google.com/p/lilypond/issues/detail?id=2338 it happened with 2.15.30. I broke it - again ;) The search string used in GUB to replace the build information in the bundle is greedier than expected. It also consumed a /string making the Info.plist invalid. A fixed bundle tar ball is available here: http://klarinett.li/lilypond/osx-lilypad-universal-0.6.2.tar.gz ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 2338 in lilypond: OS X LilyPad not working
Status: Accepted Owner: Labels: Type-Defect OpSys-OSX New issue 2338 by ralphbug...@gmail.com: OS X LilyPad not working http://code.google.com/p/lilypond/issues/detail?id=2338 Philippe Massart writes : LilyPad Editor is not working on Mac OS X (x86 version). Running it shows an error : py2app stuc executable has encountered a fatal error, and will now terminate. The Info.plist file must have a PyRuntimeLocations array containing string values for preferred Python runtime locations. These strings should be otool -L style mach ids; @executable_stub and ~ prefixes will be translated accordingly. Another thing to note : the application bundle is a standard icon, not the usual lilypond one. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2338 in lilypond: OS X LilyPad not working
Updates: Labels: -Type-Defect Type-Critical Comment #1 on issue 2338 by gra...@percival-music.ca: OS X LilyPad not working http://code.google.com/p/lilypond/issues/detail?id=2338 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2338 in lilypond: OS X LilyPad not working
Comment #2 on issue 2338 by carl.d.s...@gmail.com: OS X LilyPad not working http://code.google.com/p/lilypond/issues/detail?id=2338 We need to know two things: what version of LilyPond were you running, and what version of OS/X. We can't troubleshoot without that. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
