Hi, I'm considering building Audacity 2.1.0 to make available in EPEL testing for EPEL5,6,7.
EPEL-7 builds with the current Fedora spec, after conditionalizing out the package appdata improvements that are suitable for Fedora 22 and later.
EPEL-6 build current fails due to missing build requires: DEBUG util.py:388: Error: No Package found for portaudio-devel >= 19-16 DEBUG util.py:388: Error: No Package found for soxr-devel
portaudio is available in EPEL, but is at a lower version. It appears that since 19-16 (2013-05-04), only distro rebuilds have caused build version increments, so I would consider it to be stable, at least within Fedora. I can request the Fedora/EPEL7 maintainer to update for EPEL5,6.
I can request or take soxr into EPEL5/6. I haven't tried building it locally yet.
Referring to EPEL update policy, any recommendations about building for epel-updates-testing, with the view to leaving it there until positive feedback Karma accumulates ?
On 2015-05-07, 13:18 GMT, David Timms wrote:
Hi, I'm considering building Audacity 2.1.0 to make available in EPEL testing for EPEL5,6,7.
EPEL-7 builds with the current Fedora spec, after conditionalizing out the package appdata improvements that are suitable for Fedora 22 and later.
EPEL-6 build current fails due to missing build requires: DEBUG util.py:388: Error: No Package found for portaudio-devel >= 19-16 DEBUG util.py:388: Error: No Package found for soxr-devel
I would go with the update for the EPEL7 only. People using EPEL6 should be left to the stable system. I am sure Audacity in EPEL6 can very well edit zillion of music files (I used it myself) and here the stability of the system and no need to update is IMHO more important for somebody who still uses EPEL6 than getting the latest bells and whistles. And I wouldn't even think about touching EPEL5 ... you get to the RPM dependency hell in its most brutal form and all responsibility for anything broken by touching this monstrosity. Just leave EPEL<7 be.
Best,
Matěj
epel-devel@lists.fedoraproject.org