Hi there
On 07/02/2026 12:42, Alexander V. Makartsev wrote:
On 2/7/26 14:57, Rob van der Putten wrote:
Hi there
I currently run Asterisk 16 on a Debian 12 / Bookworm box, which is
like installing Asterisk on Debian 11 / Bullseye and then upgrading to
12.
As far as I can tell, this won't work on 13 / Trixie.
From the libgnutls30t64 control;
Breaks: libgnutls30 (<< 3.8.9-3+deb13u1)
Replaces: libgnutls30
Provides: libgnutls30 (= 3.8.9-3+deb13u1)
This leaves me with two options:
- Download Asterisk from the Asterisk site and then compile.
- Backport Asterisk 22 from Debian Unstable / Sid to Debian 13
As a little test I build a backport to 12. This does produce packages,
but I did not test these.
So what does one recommend?
It looks like Asterisk didn't make it to Debian Stable release:
$ rmadison asterisk
asterisk | 1:16.28.0~dfsg-0+deb11u3 | oldoldstable | source
asterisk | 1:16.28.0~dfsg-0+deb11u3 | oldoldstable-debug | source
asterisk | 1:16.28.0~dfsg-0+deb11u4 | oldoldstable | source, amd64, arm64, armhf, i386> asterisk | 1:16.28.0~dfsg-0+deb11u4 | oldoldstable-debug
| source
asterisk | 1:22.8.0+dfsg+~cs6.15.60671435-1 | unstable | source,
amd64, arm64, armhf, i386, loong64, ppc64el, riscv64, s390x
asterisk | 1:22.8.0+dfsg+~cs6.15.60671435-1 | unstable-debug | source
So I think your best bet is to build a backport from source package in
unstable.
I don't know why there is no package in testing yet.
This is due to lack of maintainers. Debian has been asking for new
volunteers for years.
But I'd still go that route myself and tried to build simple backport
inside chroot-ed environment of Debian Stable.
Could be quite an adventure, especially if it also require to build a
chain of different dependencies for it first.
AFIAK, if the Build-Depends do not require a package that is newer than
what is available in Stable this is not an issue. It even builds in
oldstable.
Regards,
Rob
