Bug 1281954 - B0rken in rawhide
Summary: B0rken in rawhide
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: nant
Version: rawhide
Hardware: All
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Timotheus Pokorra
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: sharpziplib
TreeView+ depends on / blocked
 
Reported: 2015-11-13 21:47 UTC by Raphael Groner
Modified: 2015-11-14 20:55 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-11-14 20:55:50 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Raphael Groner 2015-11-13 21:47:29 UTC
Description of problem:
Error: nothing provides mono(log4net) = 1.2.13.0 needed by nant-1:0.92-4.fc24.x86_64

Version-Release number of selected component (if applicable):
nant-1:0.92-4.fc24.x86_64

How reproducible:
yes

Steps to Reproduce:
1. rpmbuild foo.spec (with BR: nant)
2.
3.

Actual results:
see error above

Expected results:
no error about nant while mock/rpmbuild runs

Additional info:

Comment 1 Timotheus Pokorra 2015-11-14 09:25:30 UTC
I have now triggered a new koji build (nant-0.92-5). 
http://koji.fedoraproject.org/koji/taskinfo?taskID=11831083
That should solve the issue.

It seems log4net was updated to 1.2.14, and somehow the required log4net version is calculated during the build of nant. Perhaps if I define a specific Requires for log4net >= 1.2.13, that might solve the problem for the future when log4net is upgraded?

Comment 2 Timotheus Pokorra 2015-11-14 09:44:16 UTC
I tried what happens if I add 
Requires: mono(log4net) >= 1.2.14 
to the nant spec file. but the resulting rpm shows:
rpm -q --requires  nant
mono(log4net) >= 1.2.14
mono(log4net) = 1.2.14.0

That would not help either. So I leave the spec as it is, and if log4net is updated, I will just rebuild nant.

Comment 3 Raphael Groner 2015-11-14 20:55:50 UTC
Rebuild of sharpziplib worked with success in rawhide. Close this bug as fixed.


Note You need to log in before you can comment on or make changes to this bug.