In F-12 nant is broken after log4net update. Probably needs a bootstrap-rebuild-debootstrap-rebuild cycle to get it working again. From Koji builder: + nant -D:use-strong-name=true compile-release ** (/usr/lib64/NAnt/bin/NAnt.exe:25048): WARNING **: The following assembly referenced from /usr/lib64/NAnt/bin/NAnt.exe could not be loaded: Assembly: log4net (assemblyref_index=1) Version: 1.2.10.0 Public Key: 2a6b8347ed52b694 The assembly was not found in the Global Assembly Cache, a path listed in the MONO_PATH environment variable, or in the location of the executing assembly (/usr/lib64/NAnt/bin/). ** (/usr/lib64/NAnt/bin/NAnt.exe:25048): WARNING **: Could not load file or assembly 'log4net, Version=1.2.10.0, Culture=neutral, PublicKeyToken=2a6b8347ed52b694' or one of its dependencies. Unhandled Exception: System.TypeLoadException: Could not load type 'NAnt.Console.ConsoleStub' from assembly 'NAnt, Version=0.85.2478.0, Culture=neutral, PublicKeyToken=null'. error: Bad exit status from /var/tmp/rpm-tmp.aSZjnt (%build)
Ping? nant is still broken in F-12, which means that packages that use nant cannot be rebuilt should the need arise. I also sent a mail about the problem to fedora-mono mailing list: http://lists.fedoraproject.org/pipermail/mono/2010-February/000234.html As I said in the mail, I would be happy to help with getting this fixed.
Sorry for the delay on this. The problem is that this package has a circular dependancy problem which normally needs someone higher up the food chain to sort. I'll ask spot if he can do the rebuild/bootstrap etc.
Thanks for looking into this. I believe you can do the bootstrapping yourself. As far as I can tell it should be something like this: 1) set "%global bootstrap 1" in nant.spec 2) rebuild nant, which should just work since it now builds nant against bundled binaries 3) request F-12 buildroot override for nant (make tag-request) 4) set "%global bootstrap 0" in nant.spec 5) rebuild nant, which should now work since we have a working nant tagged into buildroot override 6) push update through Bodhi All done!
Paul, do you think I could get comaintainer access to nant so I could help you get this fixed? I have already requested access in pkgdb, so if you think it's fine, you can just approve me in there. Thanks.
*** Bug 567751 has been marked as a duplicate of this bug. ***
A simple bootstrap of nant is not sufficient: build with bootstrap 1 https://koji.fedoraproject.org/koji/buildinfo?buildID=157658 tagged into buildroot: $#: koji latest-pkg dist-f12-build nant Build Tag Built by ---------------------------------------- -------------------- ---------------- nant-0.85-32.1.fc12 dist-f12-override pfj build with bootstrap 0 https://koji.fedoraproject.org/koji/buildinfo?buildID=157728
I rebuilt mono-sharpcvslib to fix this build error and re-submitted nant's build which now succeeded. More info in my mail to fedora-mono list: http://lists.fedoraproject.org/pipermail/mono/2010-February/000236.html What needs to be done is submit mono-sharpcvslib-0.35-14.fc12 and nant-0.85-33.fc12 in Bodhi as one update group. I can't do it myself as I don't have commit access to nant.
(In reply to comment #7) > What needs to be done is submit mono-sharpcvslib-0.35-14.fc12 and > nant-0.85-33.fc12 in Bodhi as one update group. I can't do it myself as I don't > have commit access to nant. I'll take care of this.
mono-sharpcvslib-0.35-14.fc12,nant-0.85-33.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/mono-sharpcvslib-0.35-14.fc12,nant-0.85-33.fc12
mono-sharpcvslib-0.35-14.fc12, nant-0.85-33.fc12 has been pushed to the Fedora 12 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=updates-testing update mono-sharpcvslib nant'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F12/FEDORA-2010-2897
mono-sharpcvslib-0.35-14.fc12, nant-0.85-33.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.