I see. Actually, it probably won't fit SRU policy due to the paragraph:

> Note that some noise introduced by autoreconf is okay, but making
structural changes to the build system (such as introducing new library
dependencies) is generally not.

in the linked document.

13.1-cert7 and 13.9.1 depend on a newer version of pjproject which is
currently not available in the 16.04 repositories, meaning that at least
those two packages need to be backported (there is a huge mess with
audio/video related issues. How is Ubuntu's stance on bundled libraries?
13.9.1 supports building against a bundled copy of pjproject which
removes the need to backport any other dependency. In fact, that is how
I'm currently building 13.9.1 on Xenial.

The library is bundled to ensure that a version that has been tested for
regressions by Digium is used for linking (Asterisk links to it
statically).

Is this allowed? I won't be able to do the packaging on company time
because we have the above setup working quite well but am interested in
following up on this project on my own time (i.e. not very hurriedly).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1596405

Title:
  Obsolete 13.1 LTS branch release in Xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/asterisk/+bug/1596405/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to