Jesse Keating wrote:
That's going to be pretty difficult to do with the way our push and sync
scripts work.
At most an update that is going from testing to stable should disappear
for only a few hours, that would be between the updates-testing push of
the day an the subsequent branched
On Tue, Mar 02, 2010 at 12:26:35 +0100,
Kevin Kofler kevin.kof...@chello.at wrote:
We could have the branched compose compose from dist-f13 + dist-f13-updates
and move everything which was part of its compose from dist-f13-updates to
dist-f13 on completion. That way dist-f13-updates would
On Tue, 2010-03-02 at 06:59 -0600, Bruno Wolff III wrote:
probably could save some churn if the packages were signed with the
same key. (I am not sure if that is true yet; though my understanding is
that there will eventually be one key used to sign any official builds
coming out of koji.)
Currently I am following F13 and I have been noticing a lot of packages
disappearing from updates-testing before showing up in the branched release
(but similar things happen with normal updates, just less often).
When things disappear from updates-testing it isn't immediately obvious
if this is
On Mon, 2010-03-01 at 12:42 -0600, Bruno Wolff III wrote:
Currently I am following F13 and I have been noticing a lot of packages
disappearing from updates-testing before showing up in the branched release
(but similar things happen with normal updates, just less often).
When things
