Updates and delays in signing packages

[Josh Boyer]

On Sat, Jul 18, 2009 at 02:49:36AM +0530, Rahul Sundaram wrote:
>Hi,
>
>I have a concern with the recent delays in signing packages and how best
>to handle that. I maintain Gnote in Fedora. This is very actively
>maintained and has frequent releases, even weekly. It is also a rather
>young project (original release in Apr 1) and I do get bug reports on
>crashes and other issues that are better fixed quickly. I prefer not to
>push things directly to stable repository. With the recommended time of
>7 days in updates-testing and the delay in signing the package for that
>and signing it for updates repo, the package gets obsoleted by Bodhi
>with the next release update.  What would be the best way to handle this?

I am not exaggerating when I say that updates are getting pushed out as fast
as I can possibly make them.  And signing is NOT, by any means, the hold up
or the slow part.  It takes me roughly an hour to get all the pending updates
signed for a push (both testing and stable).  It takes a push between 2 and
3 days to actually complete right now.

We've had some significant delays due to a variety of factors over the past
couple of weeks.  I think we now have most of the big ones fixed, with the
master mirrors allowing more rsync access, and the updates composes now being
able to hardlink again (reduces mash time).  There is another issue involving
deltarpms that I've filed a bug on, and we should get some speed-up if we can
get that figured out too.

That being said, the updates push will still take quite some time to generate
deltas.  I'm hoping we can get it down to being able to do a complete push
to within a 24 hour period for now, but that remains to be seen.  Also keep
in mind that as F11 grows older, the mash time for it will increase.

I can understand your concern with a very active package like that.  At the
moment, we can't do anything we aren't already trying to do to get official
updates out faster.  Have patience.

josh