Fedora Extras 4 Package Build Report

[Ville Skyttä]

On Wed, 2005-11-02 at 12:57 -0600, Quentin Spencer wrote:

> When these releases are done, doesn't that mean the build system has the 
> released packages available for future builds?

Unless I'm mistaken, they should actually be available even earlier,
right after they've been built.  But see below.

>  After receiving this 
> e-mail I requested a build of another package (octave-forge) that failed 
> because mock installed an old version of ginac.

This is from memory, anyone feel free to correct any inaccuracies:

The scripts currently used to sign/move/sync the packages work so that
the notification mail is sent when the respective packages are signed
and moved out from the needsign area.  After that, the repodata is
rebuilt for the corresponding repository.  During this repodata rebuild
(~5 minutes or so, IIRC, not before, not after) there may be a window
when the newly signed packages aren't actually available in any
repository at all.

Also, note that there is a significant delay between sending these
notification mails and the moment when the packages are actually
available in public repositories.  In addition to the repodata rebuild,
there's at least the repoview rebuild for that particular distro
version, and possibly the whole sign/move/repodata/repoview shebang for
another distro version (or two) before the packages go public.  The
buildsys should be unaffected by this longer "window" though.

Yep, there's some room for improvement...