Re: Issue with latest asterisk's security update in jessie

2019-12-01 Thread José Miguel Gonçalves

Hi Adrian,

On 01/12/19 15:00, Adrian Bunk wrote

thanks for the report and apologies for the breakage, there is now an
+deb8u8 with the broken change reverted.



I confirm that with +deb8u8 everything is now OK.
Thanks for the quick fix.

Best regards,
José Gonçalves



Re: Issue with latest asterisk's security update in jessie

2019-12-01 Thread Adrian Bunk
On Sun, Dec 01, 2019 at 09:14:24AM +0100, Bernhard Schmidt wrote:
> Hi Jose,

Hi Jose,

> Thanks. This update was handled by the Debian LTS team. I will try to find 
> some time later tonight to check it out.

thanks for the report and apologies for the breakage, there is now an 
+deb8u8 with the broken change reverted.

> Best regards,
> Bernhard

cu
Adrian



Re: Issue with latest asterisk's security update in jessie

2019-12-01 Thread Adrian Bunk
On Sun, Dec 01, 2019 at 02:08:13PM +0100, Bernhard Schmidt wrote:
> Am 01.12.19 um 10:37 schrieb Adrian Bunk:
> 
> Hi Adrian,

Hi Bernhard,

> >> Thanks. This update was handled by the Debian LTS team. I will try to find 
> >> some time later tonight to check it out.
> > Thanks for the report.
> > This was my update, and I am currently looking into this.
> 
> Thanks. I see that you uploaded +deb8u8, which works fine for me.

yes, I reverted the change that broke.

Why it was broken was easy to understand, more embarrassing was 
understanding how my testing was botched.

> You you have a git repo to push to
> https://salsa.debian.org/pkg-voip-team/asterisk/tree/jessie ? Otherwise
> I'll just import the dscs.

Please import the dscs.

> Bernhard

Thanks
Adrian



Re: Issue with latest asterisk's security update in jessie

2019-12-01 Thread Bernhard Schmidt
Am 01.12.19 um 10:37 schrieb Adrian Bunk:

Hi Adrian,

>> Thanks. This update was handled by the Debian LTS team. I will try to find 
>> some time later tonight to check it out.
> Thanks for the report.
> This was my update, and I am currently looking into this.

Thanks. I see that you uploaded +deb8u8, which works fine for me.

You you have a git repo to push to
https://salsa.debian.org/pkg-voip-team/asterisk/tree/jessie ? Otherwise
I'll just import the dscs.

Bernhard



Re: Issue with latest asterisk's security update in jessie

2019-12-01 Thread Adrian Bunk
On Sun, Dec 01, 2019 at 09:14:24AM +0100, Bernhard Schmidt wrote:
> Hi Jose,
> 
> Thanks. This update was handled by the Debian LTS team. I will try to find 
> some time later tonight to check it out.

Thanks for the report.

This was my update, and I am currently looking into this.

> Best regards,
> Bernhard

cu
Adrian



Re: Issue with latest asterisk's security update in jessie

2019-12-01 Thread Bernhard Schmidt
Hi Jose,

Thanks. This update was handled by the Debian LTS team. I will try to find some 
time later tonight to check it out.

Best regards,
Bernhard

Am 1. Dezember 2019 02:30:55 MEZ schrieb "José Miguel Gonçalves" 
:
>Hi,
>
>After upgrading asterisk in jessie with the latest security update 
>(1:11.13.1~dfsg-2+deb8u7), I've found that it did not start correctly, 
>because it did not bind to the SIP port (5060).
>Looking at the asterisk logs I found these warnings:
>
>[2019-12-01 01:09:26] WARNING[43208] loader.c: Error loading module 
>'chan_sip.so': /usr/lib/asterisk/modules/chan_sip.so: undefined symbol: 
>ast_format_cap_count
>[2019-12-01 01:09:26] WARNING[43208] loader.c: Error loading module 
>'chan_sip.so': /usr/lib/asterisk/modules/chan_sip.so: undefined symbol: 
>ast_format_cap_count
>[2019-12-01 01:09:26] WARNING[43208] loader.c: Module 'chan_sip.so' 
>could not be loaded.
>
>To keep my system running I needed to revert to the previous asterisk 
>version.
>
>Best regards,
>José Gonçalves
>
>