On 09.10.25 14:17, Jonas Smedegaard wrote:
Given that asterisk is not in testing, and the (semi-)official Debian backports for trixie requires that, I assume that success was against something non-(semi-)official a.k.a. "custom".
This is a circular argument. Asterisk is not in Testing – because a volunteer spent their effort to upload it to someplace external to Debian – because it could not go into Backports (from which a tester like, say, Linuxhotel could install it) – because it's not in Testing.
… and this despite the fact that the volunteer in question reported zero changes to build Asterisk for Stable, which presumably would also apply to Testing.
Could we please simply acknowledge that we now have volunteers who would happily work on Asterisk in Stable(-backports) if/when there is some need and/or possibility to actually do so, and … heretic thought here … agree close this bug? Or maybe reduce its severity?
We can always re-open it and kick Asterisk back out of Testing if this turns out to be premature; however, I don't think that'll happen.
-- -- regards -- -- Matthias Urlichs
