I support this request. Yesterday night I have been wrestling with the Mageia version of Denemo: it simply does not work with the current version of Lilypond.

CC: (none) => ejvwaasdijk

(In reply to Erik Jan Waasdijk from comment #1)
> I support this request. Yesterday night I have been wrestling with the
> Mageia version of Denemo: it simply does not work with the current version
> of Lilypond.

Assigning to all packagers collectively, since there is no registered maintainer for this package.
CC'ing daviddavid, because he pushed denemo-2.2.0 to cauldron and he seems to be the de facto maintainer.

CC: (none) => geiger.david68210, marja11
Assignee: bugsquad => pkg-bugs

denemo 2.2.0 is now on mga6/Core/Updates_testing repo!

Please test it, thanks in advance.

I just downloaded the new version and tried it. On my computer the problem is the same as with the old version: typesetting the music gives an error. "Lilypond could not typeset this score."

Thank you, David, for your speedy reaction. Helas, something is still faulty. Denemo.org's tar.xz file does work (except the sound), poerhaps it is worthwile to look for some incompatible dependency in Mageia's repo's.

Greetings,

Erik.

I am running Denemo 2.0.14 from the standard Mageia 6 repos. When I attempt to export as PDF or PNG it claims to have done it, but the files do not show up. The Typeset Music window simply says that lilypond could not typeset the score.

However, I exported the score to a .ly file and compiled it using lilypond from the command line, e.g.

$ lilypond test.ly

Lilypond typeset the score without error and produces a proper, displayable pdf file. In the Denemo options, I set the full path to lilypond (/bin/lilypond) to make sure that Denemo is calling the same lilypond. So Denemo is calling the same lilypond that I invoked from the command line, but unsuccessfully.

The score created by Denemo specifies lilypond version 2.18.0. My system has lilypond version 2.19.61 installed. I don't know if the version difference is causing the Denemo errors or not, but the version difference does not pose a problem to lilypond when typesetting the score manually.

The takeaway is that lilypond is, indeed, able to typeset the Denemo score, but not when invoked by Denemo. It is not an incompatibility between lilypond and the Denemo score. The problem lies somewhere else.

CC: (none) => briankimerer

I spent this afternoon trying out Denemo searching for hints. I found that in the preferences editor the programs "inkscape" and "eog" are presupposed. So I installed them. After this I started Denemo via Konsole and noticed an error telling me that "evince/4/backends" (something like this) did not exist. So I looked for evince and saw that the required file is in the rpm. After installing evince too the typesetting via Lilypond succeeds. It may be that the depencies need correction.

I am not yet able to import a .ly file. But since I do not understand music notation nor the conditions necessary to import such a file, I do not know if this is a problem or not.

After the installation of evince, eog and inkscape it is necessary to delete the file .denemo-2.2.0 in the home directory and start again from zero.

I have confirmed on my computer that installing inkscape, evince, and eog fixes the issue. I also had to delete the folder .denemo-2.0.14 and start over.

I am running the Denemo version in the standard repositories, 2.0.14, so an upgrade to Denemo is not necessary to make this work.

System:    Host: mageia6 Kernel: 4.14.70-desktop-2.mga6 x86_64 (64 bit) Desktop: KDE Plasma 5.12.2
           Distro: Mageia 6 mga6

Have you seen any official listing of dependencies from the author?

So I added on Cauldron inkscape, evince and eog as a recommended packages.

Mageia 6 changed to end-of-life (EOL) status on 2019-09-30. It is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan 
to fix it in a currently maintained version, simply change the 'version' to 
a later Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we 
weren't able to fix it before Mageia 6's end of life. If you are able to 
reproduce it against a later version of Mageia, you are encouraged to click 
on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a more recent
Mageia release includes newer upstream software that fixes bugs or makes them
obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

Best regards,
Aurélien
Bugsquad Team

Resolution: (none) => OLD
Status: NEW => RESOLVED
CC: (none) => ouaurelien

Probably FIXED in mga7 according to comments 7 and 9, but good i you users please verify.

Target Milestone: --- => Mageia 7
Resolution: OLD => FIXED