Processing of asterisk-spandsp-plugins_0.0.20050227-1_i386.changes

[Jose Carlos Garcia Sogo]

--=-mMNUSdrdK/Yuxva4Lxou
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

El vie, 13-05-2005 a las 15:33 -0700, Steve Langasek escribi=C3=B3:
> On Fri, May 13, 2005 at 07:25:48PM +0200, Kilian Krause wrote:
> > Am Freitag, den 13.05.2005, 17:55 +0100 schrieb Paul Cupis:
> > > Archive Administrator wrote:
> > > > asterisk-spandsp-plugins_0.0.20050227-1_i386.changes uploaded succe=
ssfully to localhost
> > > > along with the files:
> > > >   asterisk-spandsp-plugins_0.0.20050227-1.dsc
> > > >   asterisk-spandsp-plugins_0.0.20050227.orig.tar.gz
> > > >   asterisk-spandsp-plugins_0.0.20050227-1.diff.gz
> > > >   asterisk-app-fax_0.0.20050227-1_i386.deb
> > > >   asterisk-app-dtmftotext_0.0.20050227-1_i386.deb
>=20
> > > pkg-voip,
>=20
> > > Because of this upload, my fixed asterisk-spandsp-plugins package wil=
l
> > > likely not get into sarge.
>=20
> > well, there was no version in sarge at the time i was preparing the
> > upload, thus the position of "that old version is more likely to be in
> > sarge than the new one" seemed and seems still quite strange to me. I d=
o
> > read the release team thinks the old one more suitable and thus for my
> > personal point, i'd agree to go through t-p-u if the new SID version is
> > chosen unsuitable.
>=20
> Yes, you will need to re-upload the old code to t-p-u if you want this in
> sarge.  We are not going to let a new, untested (in Debian) codebase into
> sarge this late.

 Ok, I will prepare it this weekend.

--=20
Jose Carlos Garcia Sogo
   jsogo@debian.org

--=-mMNUSdrdK/Yuxva4Lxou
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQBChdLyS+BYJZB4jhERAlmDAJ0ZHE1cnsB2L6GqfxmzQrVBZWmsmACcDqUK
fuO+Uy8+7gCMreTgg2wQ4N0=
=kDu0
-----END PGP SIGNATURE-----

--=-mMNUSdrdK/Yuxva4Lxou--