Red Hat Bugzilla – Bug 1247825
mono-nunit should not be packaged; nunit is newer
Last modified: 2015-08-10 06:09:39 EDT
Description of problem:
the mono 22.214.171.124 src rpm get built into a whole lot
of things, two of which are mono-nunit and mono-nunit-devel , which seems to be
nunit 2.4.8 . nunit 2.6.x is available as a separate package.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. install mono-nunit and try rpmbuild --rebuild monodevelop-5.9.4-2.fc23.src.rpm
See discussion leading up to:
basically the private copy of nunit shipped with mono is a bit old and should not be packaged; more up-to-date version of nunit is available separately and monodevelop depends on that; packaging the private and old version of nunit and have it installed, confuses the build process.
Building monodevelop works if you uninstall mono-nunit first and install nunit instead.
I agree this should be cleaned up.
I wonder what the right steps are:
* change mono package to not build mono-nunit and mono-nunit-devel
* change nunit/nunit-devel package to obsolete mono-nunit/mono-nunit-devel
the following packages should be updated to require nunit/nunit-devel:
repoquery --repoid=rawhide-source --archlist=src --whatrequires mono-nunit-devel
repoquery --repoid=rawhide-source --archlist=src --whatrequires mono-nunit
nunit-2.6.4-9.fc23 has been submitted as an update for Fedora 23.
mono-4.0.2-6.fc23 has been submitted as an update for Fedora 23.
* should fix your issue,
* was pushed to the Fedora 23 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing mono-4.0.2-6.fc23'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
nunit-2.6.4-9.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.
mono-4.0.2-6.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.