Image you need to build a real long dependency chaing of lets say 25 updates. Imagine you are still on the stable release, so you have no way of testing if the packages really build on rawhide, nether with mock, nor with a scratchbuild. So a chainbuild is to risky for long dependency chain like these, especially now that tags are immutable. If one package fails, the whole chain is broken.
And now imagine, you are in a hurry because the freeze is about to happen in two days. What can a packager do in this situation? The only workaround I see is to refresh http://koji.fedoraproject.org/static-repos/dist-rawhide-current/ or/and http://download.fedora.redhat.com/pub/fedora/linux/development more often.
Background of this situation is Xfce 4.4.3, which was released late yesterday evening. It's a bugfix only update that should not introduce new problems. We would like it to appear in F10, because we don't want users to do a complete Xfce update directly after installation.
I have started a discussion on devel-list, but so far I haven't got any replies. See: https://www.redhat.com/archives/fedora-devel-list/2008-October/msg02399.html
look at http://fedoraproject.org/wiki/PackageMaintainers/UsingKoji#Chained_builds you can chain build development. i would question why you are upgrading releases this late in the release cycle. kojira manages the repos that you can build against. Its not something that we can tell to run at set periods. kojira sees new builds and starts the repo generation process. the repo used internally is not necessarily the same as the current static-repo the static repo is updated to the current koji repo at the top of the hour.
This is not something thats fixable in code.
Replying to [comment:1 ausil]:
look at http://fedoraproject.org/wiki/PackageMaintainers/UsingKoji#Chained_builds you can chain build development.
I know about chained builds but I think I already explained why chained builds are not suitable for such a long dependency chain. Can I also do chained scratch-builds?
i would question why you are upgrading releases this late in the release cycle.
I think I have already explained that in my previous comment too.
Replying to [comment:2 cwickert]:
Replying to [comment:1 ausil]: look at http://fedoraproject.org/wiki/PackageMaintainers/UsingKoji#Chained_builds you can chain build development. I know about chained builds but I think I already explained why chained builds are not suitable for such a long dependency chain. Can I also do chained scratch-builds?
you cant do chain scratch builds because the results of scratch builds are never in a repo. your use case is exactly why chainbuilds exist. sorry you feel that its not suitable. I disagree completely with you.
i would question why you are upgrading releases this late in the release cycle. I think I have already explained that in my previous comment too.
Sorry but i don't buy it any change is risky. regardless the correct answer is to do chain builds here.
if you really have issue with how often koji runs createrepo then file a ticket against koji at https://fedorahosted.org/koji/
Login to comment on this ticket.