Allow asterisk to build on bookworm without bookwork-backports (systemd-dev dependency)
Martin Rampersad
martin.rampersad at emkal.ca
Wed Dec 11 15:28:13 GMT 2024
Hi Matthias,
Thank you for your offer of assistance. However after hearing Jonas' reply and reviewing the commit history on salsa, I now realize that my attempt (and maybe yours) to build unstable Asterisk for Bookworm carries at least one subtle footgun:
#1024822 - fail2ban: misses asterisk logs using suffix .log since asterisk 19 - Debian Bug report logs
Bookworm's fail2ban doesn't have the fix for this, so what I thought was just a need to rebuild Asterisk might become a need to rebuild some unknown number of related packages, track my own bugs, and maintain my own patches.
More importantly, my effort and yours do not help Asterisk return to Debian testing or stable, perhaps it is less effort (and more appropriate for this mailing-list) to just do what is needed in that regard, and as a nice side effect everyone can use it.
I am not opinionated about Asterisk packaging. I actually find gbp clone salsa/asterisk and gbp buildpackage to be a reasonable method. The pristine-tar branch seems to be defined by the debian/watch file, so I suspect it updates nearly automatically.
I really would like to help, and just need a pointer on how to do it.
Martin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-voip-maintainers/attachments/20241211/d10d35a9/attachment.htm>
More information about the Pkg-voip-maintainers
mailing list