On Thu, Nov 27, 2008 at 12:29:06AM +0100, Till Maas wrote: > On Wed November 26 2008, Patrice Dumas wrote: > > > I guess that it is that part that I would like to be skipped, such that > > there is no need of any checking, and the update goes straigth to > > testing or stable, without being even in pending state. > > I hope I understood everything correctly: The pending state indicates that > either the composing process currently runs or that it needs to be started. > Does this help you? Indeed. So right after pending, the update pushed to stable should be in stable. While if passing through testing it is once in pending while testing is composing, then the maintainer can push it to stable, then it is waiting for the next compose, and is then in a (hidden) pending state before reaching stable. So in the end the time of entering in a repo from a state to another is about 2 days, one day waiting for the previous compose and another for the compose the package is in itself. For my package it should then have lasted about 4 days, but it was streched to 8 for the reasons Jesse explained. Still 2 days is quite a long time to wait, but I can't see a way to shorten that time, except with a shortened compose time. I guess there is no other way than taking koji builds for pepople in a hurry. -- Pat -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
