[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Signing server? (Re: Updates testing for F-11)



On Thu, Jun 11, 2009 at 8:39 PM, Christoph
Wickert<christoph wickert googlemail com> wrote:
> Am Donnerstag, den 11.06.2009, 13:37 -0400 schrieb Josh Boyer:
>
>> Unfortunately, rawhide has been taking multiple days to spit out.
>> Combine that with the fact that the two people that do sign/push for
>> updates were both in a FAD this week and you get a bit less response
>> time.
>>
>> I tried to do an updates push earlier this week and it hit some
>> errors.  That needs to be fixed and resumed.  I won't be able to get
>> to this until Sunday at the earliest.  If Jesse or Luke want to fix
>> that up, it might help.
>>
>> josh
>
> Thanks for the answer, Josh, because I just wanted to ask the same
> question.
>
> What is the status of the automatic signing server? I think we really

It exists.  We aren't using it yet because of quite a few factors.

> need it because things need to be predictable for package maintainers.
> Some updates are processed after a day, others not for two weeks.

I'm a bit confused where your date is coming from.  2 weeks seems
wrong lately.  In fact, since I took over the push stuff, it's
normally done daily or as often as the composes allow.  Right now, the
compose for f11-updates alone is 7-8 hours, so doing it daily often
just doesn't work out.  But 2 weeks seems wrong.

Also, signing server won't really help any of the above.

> Especially at release time this is annoying as some of the packages I
> submitted were bugfixes I wanted to be in the Xfce Spin. Another package
> was renamed, if it got pushed in time this would have happend smoothly
> between releases.
>
> So any chance we get a more reliable push mechanism?

If by reliable you mean auto-pushed, maybe.  But that would need
auto-sign and an agreed upon schedule for updates and code.  And right
now, we have a number of things that cause backend failures which
necessitates manually fixing them.

If you'd like to volunteer to code on bodhi and fix some of these, it
would be most welcome.  With the number of people currently working on
it (2-3), it will be a while before we get to that point.

josh


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]