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 successfully 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 > > pkg-voip, > > 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. 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. -- Steve Langasek postmodern programmer
Attachment:
signature.asc
Description: Digital signature