Bug#1031046: Only include in Bookworm with commitment to stable updates
C. Maj
chris at PenguinPBX.com
Fri Dec 13 00:08:37 GMT 2024
On 12/12/24 16:27, Jonas Smedegaard wrote:
> I am confused, and concerned for the maintenance of asterisk.
Agreed 100%.
I write from my previous-slash-night-job email address from where I've
submitted some work here towards getting Asterisk on Debian in the past,
but my day-job is currently Open Source Solutions Advocate at Sangoma,
the primary sponsors and developers of the upstream Asterisk (and
FreePBX) projects.
Please know that many people at Sangoma are very much interested in
supporting the work to get Asterisk 22 in Debian 13. This was a topic of
conversation at the most recent AstriDevCon held virtually last week:
https://github.com/asterisk/documentation/commit/4cec2ba69c8303790243c9f9d315ec86f5fc998a
Regarding security issues, these are regularly handled by multiple core
developers employed by Sangoma, in an orderly, organized manner. The
Debian security team should rest soundly knowing that this is not an
all-volunteer operation putting out pristine Asterisk tarballs upstream.
That said, there does not appear to be any active, open security issues
for the asterisk package in trixie at:
https://tracker.debian.org/pkg/asterisk
Asterisk 22 is an LTS release in 2024, scheduled to go SFO in 2028 and
EOL in 2029, which if Debian 13 is released in 2025 and is EOL in 2028,
this should be an okay fit for Sangoma employees to take responsibility
for the bulk of the security needs ie. all those that are not related to
Debian-team changes. More on Asterisk versions here:
https://docs.asterisk.org/About-the-Project/Asterisk-Versions/
Unfortunately, the current Asterisk on Debian build process is, shall we
say, cumbersome to reproduce independently. Shining some light on a
basic outline of the *current* steps used would be most helpful.
And yes, again, I volunteer to help (and would offer to update my
backported scripts to Debian 12 from earlier in the year, if I thought
that would help)!
Kind regards,
Chris Maj
More information about the Pkg-voip-maintainers
mailing list