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

Kilian Krause kk@verfaction.de
Fri, 13 May 2005 19:25:48 +0200


--=-RH3RKqx85nx+8dY5ECak
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

Hi Paul,

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 successfu=
lly 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 will
> likely not get into sarge.

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 do
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.

Yet i do remember this spandsp-0.0.2pre17 was requested from pkg-voip
for a whatever feature i don't recall right now. Some user claimed that
it would have a benefit that'd not be included in pre10 (would need to
look up more details). Unfortunatelly the ChangeLog in the upstream
source was identical for 0.0.2pre10 and pre17, thus i couldn't tell from
there when writing debian/changelog, but the diff revelead it's quite a
large edit between the two.=20

This being said, i'd welcome a position from d-r@l.d.o about if we shall
prepare a t-p-u upload with the fix Paul asked for in the first place or
have the SID version ready. (done for all but arm, m68k, mips)

> Is there any interest from this group in trying to get this into sarge?

Sure.

> As long as the group agree to try to let it in I can try to get help
> from the RMs, but if the maintainer (this group/list) will not support
> its inclusion, it will not be allowed in.

ACKd, but anyway reporting a NMU before "just doing it" would have been
preferred as we all do read email daily even if we don't upload due to a
lack of time.

--=20
Best regards,
 Kilian

--=-RH3RKqx85nx+8dY5ECak
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: Dies ist ein digital signierter Nachrichtenteil

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

iD8DBQBChOMcvdkzt4X+wX8RAsq6AJ4/FwNLwmv4Dfpfu+ZDk4w+AMe+QwCffEwx
AVkX02nz2lzRvqhKJ3WRh60=
=A8Kj
-----END PGP SIGNATURE-----

--=-RH3RKqx85nx+8dY5ECak--