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

Re: cgiirc Hijacking

Hi Florian,

On Wed, Jun 21, 2006 at 07:34:49PM +0200, Florian Weimer <fw@deneb.enyo.de> wrote:

> * Mario Holbe:
> > We did. 0.5.4-6sarge1 was on s.d.o as soon as possible. Since there were
> > no newer version in unstable, the version on s.d.o should have had
> > automatically override even the unstable version. Of course, if you
> > don't source in s.d.o, you don't get security updates :)
> In this case, the security update should have been propagated to
> testing and unstable automatically.  For a few months, dak behaved
> that way.  I don't know what has changed.

For proposed-updates is a new queue-handling in place [1]. This means
that all packages which get uploaded to security.debian.org get into
this new proposed-update queue, before they get accepted into the real
proposed-update queue. For dak packages in the new proposed-update queue
are just as _not being uploaded at all_ before they are accepted by the
stable release team members.

cgiirc was a special case as version in sid and version in sarge were
the same. Packages from security.d.o still get synced to ftpmaster.d.o,
but into the new proposed-queue, which needs interaction by the stable
release managers. 

We are aware of this, and it should be solved (hopefully) by the next
dinstall run.


[1] http://lists.debian.org/debian-devel-announce/2006/06/msg00007.html

Reply to: