Hi Earlybird, I highly appreciate your suggestion to spent some time on that!
In regard to library bundling in general it is not a thing people like as it tends to let the security and maintenance overhead explode. There is another way in case a library is only used by one single source. This seems to be the case here. $ grep Package debian/control | cut -d " " -f 2 > binaries $ for i in $(cat binaries); do reverse-depends -l -b $i; done asterisk $ for i in $(cat binaries); do reverse-depends -l $i; done | sort | uniq | grep -v -f binaries asterisk-modules So bumping the library would not affect anybody but asterisk and since the need would be for asterisk that would be kind of ok. @Rbasak would you have some better words on the possible next steps here? @Gutsche - I expect you talk about bug 1458323 right? If not I'd recommend you report a new one so that tracking and reproducing it is documented. Especially if Earlybird really find some time to refresh Asterisk (universe) in the LTS that might resolve all that it would be great to have a how-to-trigger and some logs available in that extra bug. Also there please could you check if it is resolved in Yakkety which has a far more modern asterisk? -- 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
