Learn more about these different git repos.
Other Git URLs
We have applied for the following MinGW packages to be added to CVS:
These three packages have a circular dependency, so we would like rel-eng's help in creating the initial Koji repository. The circular dependency and how we normally break it is described here:
If the two noarch binary packages mingw32-runtime and mingw32-w32api from our temporary repository (http://www.annexia.org/tmp/mingw/fedora-10/i386/RPMS/) can be added then we can build mingw32-gcc from source followed by mingw32-runtime and mingw32-w32api from source, and then the circular dependency is broken.
To minimize the time in which the non-built packages are in koji, lets coordinate the building. We'll untag the imported versions so that they can get garbage collected earlier.
This should happen after the CVS admin step is done so that koji itself is ready to take the packages.
CVS has been granted and I've added and tagged the packages.
Of course I can't build any of them :-)
Could we arrange a time, perhaps tomorrow or later this week, to insert the two binary [http://www.annexia.org/tmp/mingw/fedora-10/i386/RPMS/mingw32-runtime-3.15.1-8.fc10.noarch.rpm mingw32-runtime.noarch] and [http://www.annexia.org/tmp/mingw/fedora-10/i386/RPMS/mingw32-w32api-3.12-6.fc10.noarch.rpm mingw32-w32api.noarch] packages and then do the builds from source of all three (gcc, runtime, w32api)?
It is my understanding, based on the way that Koji repositories inherit from each other, that we only need to insert them in the dist-f10 branch, and that will deal with the dist-f11 case too.
The two packages linked above turned out to have a faulty runtime dep
(they were runtime requiring mingw32-gcc, which of course doesn't exist
yet). These packages fix that problem, and were successfully used to
bootstrap EPEL builds in EL-5:
Looks like we missed this last week. Sorry about that. When this week would you like to do this?
I'm very busy this week. May be better to try from next week (after Tue 9th Dec)?
I'm on holiday tomorrow (Monday 8th Dec) but I wonder if we can arrange a date and time for later this week? Any date starting with Tuesday will be good for me.
For EPEL I coordinated successfully with mmcgrath in #fedora-admin, and the whole process took under an hour. Would have been quicker if it hadn't been for a mistake on my part.
My main concern though is whether we can do this just for the dist-f10 build. Will that inherit into dist-f11 or do we need to do dist-f11 separately? Will there be any problems/delays because of bodhi? Do we need to push packages through bodhi during the process?
Forgive my ignorance, but I don't really know very much about how koji/bodhi/F-10/Rawhide all work and interact with each other.
Yeah, we can do this next week. Meeting up in #fedora-admin would work as well. I'm "f13" on freenode.
Packages built for F10 don't make it to F11 until after they've been pushed as updates, so for speed it might be better to do it for both 10 and 11.
These were imported and made available for build.
Thank you jkeating.
We've now got builds of mingw32-gcc, -runtime and -w32api from source:
I will leave this bug open in case you (jkeating) need to close or
remove anything from the -override targets.
Imported builds have been untagged.
Metadata Update from @rjones:
- Issue assigned to jkeating
to comment on this ticket.