Description of problem: the package configure in version 1.0.6 user a different way how python version is setup This is not reflected in the spec file. When the packaged is rebuilt on a machine with python 2 installed it chose python2 but install packages under python3 libraries. The result is that spatch cannot load its python libraries because it runs with python2 while libraries where installed under python3 Version-Release number of selected component (if applicable): 1.0.6 5 How reproducible: rpmbuild -ba coccinelle.spec Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
It does seem to be different from how we're doing it (and from the documentation). However I can't work out how you're supposed to set the python version. Setting PYVER has no visible effect.
Question posted upstream: https://systeme.lip6.fr/pipermail/cocci/2017-January/003966.html
I've tried something like that but it didn't helped %{__sed} -i \ -e 's,LIBDIR=.*,LIBDIR=%{_libdir},' \ -e 's,MANDIR=.*,MANDIR=%{_mandir},' \ -e 's,SHAREDIR=.*,SHAREDIR=%{_libdir}/%{name},' \ -e 's,DYNLINKDIR=.*,DYNLINKDIR=%{_libdir}/ocaml,' \ -e 's,PYTHON_VERSION=.*,PYTHON_VERSION=3,' \ -e 's,PYTHON_VERSION_MAJOR=.*,PYTHON_VERSION_MAJOR=3,' \ Makefile.config
So looks like the python libraries for this version should be installed under private directory and not to the python system libraries. So the spec has to be fixed accordingly.
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle. Changing version to '26'.
*** Bug 1544204 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. 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 Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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 Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Still an issue in F27
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.