http://bugzilla.novell.com/show_bug.cgi?id=568280 http://bugzilla.novell.com/show_bug.cgi?id=568280#c10 --- Comment #10 from Dave Plater <davejplater@gmail.com> 2010-01-15 09:37:22 UTC --- So a package that has the license statement "GPL2 or later" cannot be dependent on a package licensed under GPL3. This is their statement : The licensing of the Free version of the core Ghostscript code has been changed to GPLv3 or later. Previously, the core code was GPLv2 only. Ghostscript can now be used with GPLv3 applications, and can no longer be used with applications that are GPLv2-only. This means that lilypond cannot depend on gs-8.70? I wonder how Fedora solved this problem? Getting back to fixing this bug, I removed the workaround from lilypond.spec and the build now fails, even with ghostscript-library-8.64-27.1 linked from Printing:ghostscript ghostscript. This traces back to a gs "failed (11)" which Jan states is the segfault. Factory standard builds of lilypond are blocked ATM but both x86_64 and i586 fails on 11.2. The gs segfault sometimes doesn't happen, you will see that home:plater:branches:openSUSE:Factory:Contrib lilypond 11.1 i586 succeeded. If I insert the line "export GS_LIB="/home/$USER/.fonts" at the beginning of the %build section, lilypond will succeed 90% of the time. Jan has investigated this problem more than I have and I don't have the knowledge nor the time to debug this problem. The clue to reproducing this problem locally is the GS_LIB= variable. Lilypond builds without problem on my own system but fails both with local chrooted build and local osc build. Chrooted builds don't insert the GS_LIB variable by themselves. This is the worst problem to reproduce because it doesn't happen all the time but it does exist. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.