Learn more about these different git repos.
Other Git URLs
If it isn't necessary anymore, can you please remove the buildroot override for the gtk-sharp2-2.12.1-1.fc9 build in F-9:
https://koji.fedoraproject.org/koji/buildinfo?buildID=63643
currently this means that gecko-sharp2 can't be installed in the buildsys and ends up preventing a rebuild of blam, see:
https://bugzilla.redhat.com/show_bug.cgi?id=471836
for more details. Alternatively gecko-sharp2 could be rebuilt, but that may cause more broken deps and would require more testing of all affected packages. Removing the -override tag would allow a blam update to be pushed quickly.
untagging.
See also ticket #1065
Oops... This is bad...
Actually many pacakges are already rebuilt against newer gtk-sharp2-2.12.1-1.fc9, gnome-sharp-2.16.1-2.fc9 and also some packages rebuilt against these packages are already pushed into F-9 stable (bug 468055). So again these packages have to be tagged as dist-f9-override. Please retag.
OK... (re)tagging gtk-sharp2-2.12.1-1.fc9
So ignore/untag the stuff from ticket #1065 ?
Forget my comment, my brain merged gtk-sharp2 and gecko-sharp2
Okay, thanks for retag. Now this issue is being tracked on https://bugzilla.redhat.com/show_bug.cgi?id=468055.
I will rebuild blam and so on.
Replying to [comment:5 rdieter]:
Umm. I also seem to be confused. So now gtk-sharp2-2.12.1-1.fc9 is not tagged as dist-f9-override (as I can see). Would you retag this?
(re)tagged along with the stuff from #1065 (ipod-sharp-0.8.0-5.fc9 and muine-0.8.8-10.fc9)
could you also tag gecko-sharp2-0.12-7.fc9.1 ? thanks.
gecko-sharp2-0.12-7.fc9.1 tagged.
I think everything is tagged here. I'll do a untag pass after the next updates push to clear out any unnecessary overrides.
As I wrote in #1065, now these are tagged as dist-f9-updates and I guess override tag is no longer needed.
Login to comment on this ticket.