Hello,
How long should it take to have a newly build package to become usable as a BuildRequires in devel? I was under the impression that it was immediately available?
Looking at the doc in the wiki and at koji website, it seems that there are tags that corresponds with packages in the buildroot, like dist-f8-build http://koji.fedoraproject.org/koji/taginfo?tagID=13 as seen in 'Targets building from this tag'. And tags that correspond with collections like dist-f8. However in the inheritance graph for dist-f8-build it seems that dist-f8 are available in builds (which is quite logical). But is this dependence immediately available?
I think that these issues, especially the inheritance, should be documented at the end of http://fedoraproject.org/wiki/Koji
The practical use case is that I would like to rebuild grads against the latest libnc-dap build that I submitted some hours ago, but latest build I fired was against an old release.
-- Pat
On Wed, 22 Aug 2007 08:34:44 -0500 Rex Dieter rdieter@math.unl.edu wrote:
the 'newRepo' task runs about every ~20 minutes (give or take).
Actually the newRepo task runs when a package is tagged that would be seen by a build collection. The time it takes a newRepo command to complete is somewhere around 20 minutes, depending on the buildsystem load.
Now there are cases where many packages finish building while a current newRepo task is running. We don't start a newRepo task for each of those builds, instead we just know that as soon as the current repo task is complete to start a new one, or something along those lines.
If you're working on the devel branch, you can make use of chain-build (make help) which will allow you to set up a chain of builds that will automatically wait for the previous link in the chain to be available in buildroots before building the next link in the chain.