Description of problem: 1- Frescobaldi 3.0 don't start because some libraries of python3-qt5 are missing. I have installed all the python3-qt5 package to make Frescobaldi work, but it is probably possible to install only 5 or 6 libraries of this package. Version-Release number of selected component (if applicable): frescobaldi 3.0 2- Mageia6 is shipping with Lilypond 2.19 and install it in /usr/bin/. Frescobaldi throws a strange error message when compiling because it doesn't expect to find Lilypond in this directory. In the "Edit->preferences" menu of Frescobaldi, tab "Lilypond", the user have to change the Lilypond command "lilypond" by the whole path "/usr/bin/lilypond". I don't know if it is possible to specify this path during the installation of the Frecolbaldi package.
Assignee: bugsquad => rverschelde
Summary: some python3-qt5 paquages are missing for Frescobaldi 3.0.0 + Lilypond install directory => some python3-qt5 requires are missing for Frescobaldi 3.0.0 + Lilypond install directory
(In reply to Gilles Thibault from comment #0) > 1- I believe those are needed: python3-qt5 python3-qt5-svg python3-qt5-webkit > 2- > Mageia6 is shipping with Lilypond 2.19 and install it in /usr/bin/. > Frescobaldi throws a strange error message when compiling because it doesn't > expect to find Lilypond in this directory. > In the "Edit->preferences" menu of Frescobaldi, tab "Lilypond", the user > have to change the Lilypond command "lilypond" by the whole path > "/usr/bin/lilypond". > I don't know if it is possible to specify this path during the installation > of the Frecolbaldi package. This has already been reported upstream but there's no fix yet, so we may need to patch this ourselves: https://github.com/wbsoft/frescobaldi/issues/1041
CC: (none) => doktor5000
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
Status: NEW => RESOLVEDCC: (none) => ouaurelienResolution: (none) => OLD