Regarding NEW and ftp-master approval

Fabian Fagerholm fabbe at paniq.net
Mon Oct 23 18:37:25 UTC 2006


On Mon, 2006-10-23 at 19:02 +0200, Andreas Metzler wrote:
> On 2006-10-23 Fabian Fagerholm <fabbe at paniq.net> wrote:
> > Another question is convincing the FTP-masters to allow cyrus-sasl-2.1
> > into sid and then etch.
>
> That is not necessary. If it is accepted in experimental, a following
> upload to sid without *more* newly introduced packages does not
> require NEW processing and ftp-master acceptance. - ftp-master would
> need to actively block it.

Steve Langasek tells me that cyrus-sasl2 (the old package) is frozen. So
even though going through NEW for an experimental upload allows us to
upload directly to sid without going through NEW, I don't think we
should do that without agreeing with the FTP-masters first.

Of course, you only said that technically, we just need to go through
NEW once whenever we introduce new binary packages, which is completely
true. :)

> Must haves:
> * seamless upgrade. - Doesn't the upgrade to db4.4 require some
>   handholding in the maintainerscripts? - Or does upstream's code
>   itself automatically db-upgrade its data sorces?

AFAIK, there is no auto-upgrade of data sources. So we have to take a
look at converting. I think Cyrus IMAPd does something similar, so we
could perhaps reuse some code from there.

-- 
Fabian Fagerholm <fabbe at paniq.net>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.alioth.debian.org/pipermail/pkg-cyrus-sasl2-debian-devel/attachments/20061023/ff6e2f92/attachment.pgp


More information about the Pkg-cyrus-sasl2-debian-devel mailing list