How do the archives work?

[Matt Zimmerman]

On Thu, Feb 24, 2005 at 11:55:10AM -0500, Matt Galvin wrote:

> I know this may be internal info, but I wondered if it would be
> possible to get some insight into how the archives work in terms of
> knowing when we will see updates and such. For example on the
> hoary-changes list we can see that a new version of something was
> accepted but it can be as much as 2-3 days before the package "hits
> the acrhive". I understand things need to be tested and QA'd to some
> extent before releasing it for community testing. But as we saw these
> past few days, some packages did not get into the archive at the
> expected time due to some "apparently" cyclic deps (i think i read
> that somewhere), and many of us hit the issues with gamin, inotify,
> and new kernel yesterday.

http://www.ubuntulinux.org/wiki/BuildDaemons

covers how packages are built and when they enter the archive.  The primary
exceptions are the installer builds (which happen once per day, and are
manually placed in the archive), live image builds (once per day) and CD
builds (once per day).

Apart from those, if an update will take a few days to hit the archive, it's
because it hasn't been uploaded yet. :-)

-- 
 - mdz