#3426 Tag request nant-0.85-32.1.fc12 for dist-f12-updates-candidate
Closed: Fixed None Opened 14 years ago by pfj.

{{{
NAnt is currently broken in f12 due to log4net being signed with a different .snk file than before. This is just a rebuild to fix the problem and other


It's tagged, it may take around 20 minutes until it appears in the buildroots. Please report back when the tagging is no longer needed.

I've built fixed mono-sharpcvslib-0.35-14.fc12 (#3440), and now nant-0.85-32.1.fc12 (bootstrap version needed to build circular deps like mono-sharpcvslib) can be untagged from dist-f12-override.

I resubmitted pfj's non-bootstrap version of nant build, which successfully completed against fixed mono-sharpcvslib.
Please now tag the new nant-0.85-33.fc12 for dist-f12-override.

Both nant-0.85-33.fc12 and mono-sharpcvslib-0.35-14.fc12 should stay tagged for dist-f12-override until they hit stable F-12 updates.

nant-0.85-33.fc12 is now tagged and nant-0.85-32.1.fc12 untagged

nant-0.85-33.fc12 is now in dist-f12-updates and can be untagged from dist-f12-override. Thanks!

untagged nant-0.85-33.fc12

Metadata Update from @pfj:
- Issue assigned to till

7 years ago

Login to comment on this ticket.

Metadata