Bug#1031046: Only include in Bookworm with commitment to stable updates

[Matthias Urlichs]

On 13.12.24 01:08, C. Maj wrote:
> 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. 

It'd be *very* helpful if you could spend some work to make all these 
steps unnecessary in the first place.

The outline (and what I'd do if I had less than zero free time *sigh* to 
improve the situation) is, as far as I could determine:

* The Asterisk build includes four vendorized git archives: pjsip, mp3, 
and Asterisk codec+format support for amr and opus. These are unpacked 
to toplevel "X…" directories.

pjproject is on version 2.14.1 and merely gets "unbroken" by removing 
the build of "bdimad_dev.o". Could the pjproject stack be packaged as 
"real" Debian packages instead, as AFAICT Asterisk seems not to require 
a patched pjproject any more? Does Asterisk work OK with pjsip release 2.15?

The AMR and Opus codecs get patched into main/codec_builtin.c et al. 
Given that everybody and their dog does this, could upstream Asterisk 
please incorporate github.com:traud/asterisk-opus.git and …-amr.git?

Likewise, the mp3 part is a trimmed-down version of libmpg123, which by 
now is in Debian anyway. Please investigate what's required to simply 
use that instead.

* the whole kaboodle is then packaged into a bunch of tar files.

* Next, during build, variouos patches are applied. Then the Xpjproject 
directory is repacked to third-party/pjproject/pjproject-VERSION.tar.gz 
(with an "adjusted" checksum file) so that the Asterisk build process 
finds it.

* If this process does any work to remove non-DFSG-free material, I 
didn't notice. Admittedly I didn't go out of my way to look for that 
part either.

* I already wrote about my opinion WRT pristine-tar, debian/patches, and 
all that. To summarize, I strongly advocate to base your workflow on 
your normal Asterisk git releases, to use a git-centered workflow 
instead of quilt, and to not reproduce Debian's current Asterisk 
archive. It's not necessary.

To that effect, it'd help if you'd push *signed* git tags whenever you 
release Asterisk.

-- 
-- mit freundlichen Grüßen
-- 
-- Matthias Urlichs

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-voip-maintainers/attachments/20241213/3cd7f0be/attachment-0001.sig>