Comment 4 for bug 1596405
Revision history for this message
| gutschke (markus+launchpad) wrote Re: Obsolete 13.1 LTS branch release in Xenial | #4 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
As is, Asterisk is completely broken in Xenial. A fresh install crashes within seconds of service start up. While I can't guarantee that tracking upstream would fix this particular problem, it stands a much higher chance of getting the attention of the Asterisk developers. Shipping an outdated and unmaintained version isn't doing anybody any favors.
On the other hand, I do understand that developer resources are limited. So, maybe, completely pulling the broken copy of Asterisk from Xenial is the only viable option at this point?
As a work-around for Ubuntu users, I found that moving Asterisk into an LXD container works pretty well. Obviously, I can't run Xenial in that container, as it would trigger the same problem. But Debian Jessie has a working copy of Asterisk at this time and that easily installs in a container.