Re: Requesting input for pjproject/asterisk packaging

2018-11-20 Thread Ian Jackson
Marc Haber writes ("Re: Requesting input for pjproject/asterisk packaging"): > b. The multi tarball feature of dpkg-source would be helpful for a > number of other packages, it's about time that someone seriously uses > it. I have been using it for Xen in stretch-secu

Re: Requesting input for pjproject/asterisk packaging

2018-11-19 Thread Marc Haber
On Mon, 19 Nov 2018 23:40:44 +0100, Bernhard Schmidt wrote: >1.) Drop src:asterisk and src:pjproject from Buster. Worst option, cutting our users of from Asterisk totally. >2.) Keep the current pjproject and Asterisk version and don't follow the >upgrade. This will probably be harder as it sound

Re: Requesting input for pjproject/asterisk packaging

2018-11-19 Thread Marc Haber
On Tue, 20 Nov 2018 09:33:18 +0800, Paul Wise wrote: >On Tue, Nov 20, 2018 at 6:46 AM Bernhard Schmidt wrote: > >> 1.) Drop src:asterisk and src:pjproject from Buster. > >IMO this seems like the most appropriate option until both projects >are high enough quality. That would, IMO, be another step

Re: Requesting input for pjproject/asterisk packaging

2018-11-19 Thread Paul Wise
On Tue, Nov 20, 2018 at 6:46 AM Bernhard Schmidt wrote: > 1.) Drop src:asterisk and src:pjproject from Buster. IMO this seems like the most appropriate option until both projects are high enough quality. -- bye, pabs https://wiki.debian.org/PaulWise

Re: Requesting input for pjproject/asterisk packaging

2018-11-19 Thread W. Martin Borgert
On 2018-11-19 23:40, Bernhard Schmidt wrote: > Asterisk maintainers have first offerered, then recommended working > around this issue by shipping a private copy I suggest to go that way. I really do not like embedded code copies, but this situation is a perfect excuse for allowing one. Debian fro