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

[Paul Cupis]

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,

No - the whole point of my upload to get a version into sarge. :(

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

Joey Hess has emailed saying that 0.0.20050203-2.1 (my NMU) would be
accepted as it was a minor change to fix an RC bug.

As we are in sarge freeze, no new upstreams are being accepted unless
there are overwhelming reasons for them.

> 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)

Please see Joeys email <20050513151223.GA32296@kitenet.net>.

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

Well I made a 0-day NMU during a BSP to fix an RC-bug which was keeping
the package out of sarge (which is frozen). The bug had been in the BTS
for ~2.5 weeks with no response from the maintainer.

It should have been obvious that the minor change was to get the package
past the RMs during freeze, not just a random NMU - perhaps I should
have been more explicit.

I joined the pkg-voip list just after uploading so I could see that the
package got into sarge - I do hope to stay here and contribute
"normally" post-freeze.

Regards,

Paul Cupis
-- 
paul@cupis.co.uk