This is needed to build mixxx for it.
This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle. Changing version to '23'. (As we did not run this process for some time, it could affect also pre-Fedora 23 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23
Package Change Request ====================== Package Name: xmms New Branches: epel7 Owners: spot InitialCC:
Git done (by process-git-requests).
xmms-1.2.11-25.20071117cvs.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-46aa6b49cd
xmms-1.2.11-25.20071117cvs.el7 has been pushed to the Fedora EPEL 7 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with $ su -c 'yum --enablerepo=epel-testing update xmms' You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-46aa6b49cd
I have take a look at the build log. What I don't understand, why it was build with "--disable-esd"? Esound exist in the EPEL repo.
Because esound is buggy, archaic, and effectively unmaintained.
Ok, the we only have the rpmlint errors: rpmlint *.rpm |grep -v incorrect-fsf-address xmms.x86_64: E: explicit-lib-dependency libcanberra-gtk2 <--- why? xmms.x86_64: W: spelling-error %description -l en_US playlists -> play lists, play-lists, stylists <-- only cosmetic xmms.x86_64: W: self-obsoletion xmms-esd < 1:18.20071117cvs obsoletes xmms-esd = 1:1.2.11-25.20071117cvs.el7 <--- why? and here why rpath? xmms.x86_64: E: binary-or-shlib-defines-rpath /usr/libexec/xmms ['/usr/lib64'] xmms.x86_64: E: binary-or-shlib-defines-rpath /usr/libexec/wmxmms ['/usr/lib64']
xmms-1.2.11-25.20071117cvs.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, please make note of it in this bug report.