Description of problem: Pymecavideo don't work. There's an issue is spec. Please update. Version-Release number of selected component (if applicable): 6.1 have to be upated in 6.3 spec file and src rpm joined. How reproducible: Steps to Reproduce: 1. 2. 3. Reproducible: Steps to Reproduce:
Created attachment 7200 [details] good spec file that works with 6.3 version. RPM SOURCE : http://download.tuxfamily.org/oppl/sources/pymecavideo-6.3-1.mga5.src.rpm
CC: (none) => ashashiwa
URL: (none) => http://outilsphysiques.tuxfamily.org/wiki/index.php?title=Pymecavideo#T.C3.A9l.C3.A9chargementsSummary: http://outilsphysiques.tuxfamily.org/wiki/index.php?title=Pymecavideo#T.C3.A9l.C3.A9chargements => Pymecavideo does not work (packaging issue)
Thanks for the report and for your proposed fixed. Assigning to its registered maintainer. For the sake of completeness, could you explain *why* the current package does not work? I see that you added videos to /usr/share/pymecavideo/videos and added a build requirement on docbook-style-xsl and qtiplot as a recommended package, but since you also updated to version 6.3 I can't tell what is bug fixing, and what is related to the version update.
Keywords: (none) => PATCHAssignee: bugsquad => olivier
I tried to update the package with the .tar.gz from github. I took your SPEC, but I have a build problem : make[1]: Entering directory '/pymecavideo/BUILD/pymecavideo-v6.3-e5d4ccd5c023e5ca14ff663b40d438f23f54bed0/data/help' help-fr.xml => help-fr.xhtml warning: failed to load external entity "/usr/share/xml/docbook/stylesheet/nwalsh/xhtml/docbook.xsl" cannot parse /usr/share/xml/docbook/stylesheet/nwalsh/xhtml/docbook.xsl Makefile:19: recipe for target 'help-fr.xhtml' failed make[1]: *** [help-fr.xhtml] Error 4 No package provides /usr/share/xml/docbook/stylesheet/nwalsh/xhtml/docbook.xsl Perhaps we could use the files from the package docbook-style-xsl.
Hi :) Thanks for answer. If you do a double make, it's working. (ugly... but it compiles)
It's probably a bad dependency in the project: the first make is unable to compile, but the second one reuse what has been done for the first. I'll try to see what happens with the double make for the documentation.
Ok, I tried to double-compile it, and it works, but I'm not sure we can accept that for the distribution. However, this leads to strange things such as python files in video directory: Fichier(s) installé(s) (mais non empaquetés)Â : /usr/share/pymecavideo/video/film.py /usr/share/pymecavideo/video/film.pyc /usr/share/pymecavideo/video/film.pyo /usr/share/pymecavideo/video/qualifieFilm.py /usr/share/pymecavideo/video/qualifieFilm.pyc /usr/share/pymecavideo/video/qualifieFilm.pyo
Keywords: (none) => NEEDINFO
About the double make... it's just a suggestion, but may be it's a "latex" things. Need to pass twice ? About the python files in video directory, it was a rest from tests. So I've delete them from git repository.
Hi jb, Thank you for having taken the needed time to report this issue! Did this bug get fixed? If so, please change its status to RESOLVED - FIXED If it didn't, then we regret that we weren't able to fix it in Mageia 5. Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/ It only continued to get important security updates since then, because we are waiting for a big Plasma5 update in Mageia 6, that'll fix many of the Mageia 5 => 6 upgrade issues. If you haven't seen that this bug got fixed, then please check whether this bug still exists in Mageia 6. If it does, then please change the Version (near the top, at the left) to "6". If you know it exists in Cauldron, then change Version to Cauldron. If you see it in both Cauldron and Mageia 6, then please set Version to Cauldron and add MGA6TOO on the Whiteboard. Thanks, Marja
CC: (none) => marja11
@ jb butet: No reply, so closing as OLD since Mageia 5 is no longer maintained. ==> If you didn't reset your password after February 2018, then you'll need to reset it here https://identity.mageia.org/forgot_password to be able to log in and comment in this report. <==
Resolution: (none) => OLDStatus: NEW => RESOLVED