Re: [asterisk-users] Serious bug in 1.6.2.19 - what is the time frame to fix such bugs?

2011-08-05 Thread Kevin P. Fleming

On 08/03/2011 09:33 PM, Bruce B wrote:

Can you please elaborate on how to apply the patch?
Also, is the repository updated with the new code?


No, of course not. RPMs and DEBs are not patched, they are produced when 
new releases are made. If you haven't seen a new release made that 
includes the patch in question, then RPMs and DEBs don't have it either.


--
Kevin P. Fleming
Digium, Inc. | Director of Software Technologies
Jabber: kflem...@digium.com | SIP: kpflem...@digium.com | Skype: kpfleming
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us out at www.digium.com  www.asterisk.org

--
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
  http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
  http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [asterisk-users] Serious bug in 1.6.2.19 - what is the time frame to fix such bugs?

2011-08-03 Thread Bruce B
Can you please elaborate on how to apply the patch?
Also, is the repository updated with the new code?

Regards,



On Tue, Aug 2, 2011 at 7:34 PM, Richard Mudgett rmudg...@digium.com wrote:

  Can you please point me to the patch that you just made?
 
 The patch is committed to v1.6.2 SVN branch.
 Patch for v1.6.2 only.

 r330490 | jrose | 2011-08-01 16:08:10 -0500 (Mon, 01 Aug 2011) | 12 lines

 Asterisk 18103 - Fix reload crash caused by destroying default parking lot

 Default parking lot was being destroyed in reload and was not being rebuilt
 properly.
 This patch keeps features.c reload from destroying the default parking lot
 in 1.6.2.
 Bug was caused by a hasty backport which didn't test reload enough times to
 catch the
 problem.

 (closes issue ASTERISK-18103)
 Reported by: 808blogger

 Review: https://reviewboard.asterisk.org/r/1337/

 Also -r330505 to fix a ref leak with the above patch.

 Richard

 --
 _
 -- Bandwidth and Colocation Provided by http://www.api-digital.com --
 New to Asterisk? Join us for a live introductory webinar every Thurs:
   http://www.asterisk.org/hello

 asterisk-users mailing list
 To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

--
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
   http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Re: [asterisk-users] Serious bug in 1.6.2.19 - what is the time frame to fix such bugs?

2011-08-02 Thread Bruce B
I am happy it's being taken care of.

Would the patch fix systems that used the Repo to install Asterisk 1.6.2.19?
That is where we all have problems. Or maybe a new version of Asterisk which
yum update would do the job?

On Mon, Aug 1, 2011 at 11:27 PM, Jonathan Rose jr...@digium.com wrote:

 We worked on this bug today and are expecting to release packages with the
 fix soon, possibly tomorrow (Aug 2).  The issue arose from a change in
 features reload which was back-ported to 1.6.2 and was committed without
 enough testing to observe the intermittent crash behavior.

 Thanks for your patience,
 Jonathan R. Rose

 - Original Message -
 From: Vahan Yerkanian va...@arminco.com
 To: Asterisk Users Mailing List - Non-Commercial Discussion 
 asterisk-users@lists.digium.com
 Sent: Sunday, July 31, 2011 3:03:07 AM
 Subject: Re: [asterisk-users] Serious bug in 1.6.2.19 - what is the time
 frame to fix such bugs?

 On 7/30/11 7:39 AM, Bruce B wrote:
  I think this should be a quick fix since it's rendering the latest
  stable version useless and making the impression that it was released
  just to break things and force people onto 1.8x. Just a thought...no
  blame game. But really something like this should be tackled quickly. No
  point to break things so badly on the last stable version.
 
  Regards,
 

 Confirming this issue on 10+ 1.6.2.19 Asterisk servers. This problem
 makes it difficult to do edits on sip.conf on production systems, as
 there is ~25% chance that you'll crash the server and cut the
 established calls. The problem does not exist in 1.6.2.18...

 I think this problem should be fixed or the 1.6.2.19 should be removed
 from the digium repo.

 Regards,
 Vahan

 --
 _
 -- Bandwidth and Colocation Provided by http://www.api-digital.com --
 New to Asterisk? Join us for a live introductory webinar every Thurs:
   http://www.asterisk.org/hello

 asterisk-users mailing list
 To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

 --
 _
 -- Bandwidth and Colocation Provided by http://www.api-digital.com --
 New to Asterisk? Join us for a live introductory webinar every Thurs:
   http://www.asterisk.org/hello

 asterisk-users mailing list
 To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

--
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
   http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Re: [asterisk-users] Serious bug in 1.6.2.19 - what is the time frame to fix such bugs?

2011-08-02 Thread Bruce B
Hi Jonathan,

Any clue with 1.6.2.19.*1 *might be released?

Regards,

On Mon, Aug 1, 2011 at 11:27 PM, Jonathan Rose jr...@digium.com wrote:

 We worked on this bug today and are expecting to release packages with the
 fix soon, possibly tomorrow (Aug 2).  The issue arose from a change in
 features reload which was back-ported to 1.6.2 and was committed without
 enough testing to observe the intermittent crash behavior.

 Thanks for your patience,
 Jonathan R. Rose

 - Original Message -
 From: Vahan Yerkanian va...@arminco.com
 To: Asterisk Users Mailing List - Non-Commercial Discussion 
 asterisk-users@lists.digium.com
 Sent: Sunday, July 31, 2011 3:03:07 AM
 Subject: Re: [asterisk-users] Serious bug in 1.6.2.19 - what is the time
 frame to fix such bugs?

 On 7/30/11 7:39 AM, Bruce B wrote:
  I think this should be a quick fix since it's rendering the latest
  stable version useless and making the impression that it was released
  just to break things and force people onto 1.8x. Just a thought...no
  blame game. But really something like this should be tackled quickly. No
  point to break things so badly on the last stable version.
 
  Regards,
 

 Confirming this issue on 10+ 1.6.2.19 Asterisk servers. This problem
 makes it difficult to do edits on sip.conf on production systems, as
 there is ~25% chance that you'll crash the server and cut the
 established calls. The problem does not exist in 1.6.2.18...

 I think this problem should be fixed or the 1.6.2.19 should be removed
 from the digium repo.

 Regards,
 Vahan

 --
 _
 -- Bandwidth and Colocation Provided by http://www.api-digital.com --
 New to Asterisk? Join us for a live introductory webinar every Thurs:
   http://www.asterisk.org/hello

 asterisk-users mailing list
 To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

 --
 _
 -- Bandwidth and Colocation Provided by http://www.api-digital.com --
 New to Asterisk? Join us for a live introductory webinar every Thurs:
   http://www.asterisk.org/hello

 asterisk-users mailing list
 To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

--
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
   http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Re: [asterisk-users] Serious bug in 1.6.2.19 - what is the time frame to fix such bugs?

2011-08-02 Thread Bruce B
Can you please point me to the patch that you just made?

Thanks

On Mon, Aug 1, 2011 at 11:27 PM, Jonathan Rose jr...@digium.com wrote:

 We worked on this bug today and are expecting to release packages with the
 fix soon, possibly tomorrow (Aug 2).  The issue arose from a change in
 features reload which was back-ported to 1.6.2 and was committed without
 enough testing to observe the intermittent crash behavior.

 Thanks for your patience,
 Jonathan R. Rose

 - Original Message -
 From: Vahan Yerkanian va...@arminco.com
 To: Asterisk Users Mailing List - Non-Commercial Discussion 
 asterisk-users@lists.digium.com
 Sent: Sunday, July 31, 2011 3:03:07 AM
 Subject: Re: [asterisk-users] Serious bug in 1.6.2.19 - what is the time
 frame to fix such bugs?

 On 7/30/11 7:39 AM, Bruce B wrote:
  I think this should be a quick fix since it's rendering the latest
  stable version useless and making the impression that it was released
  just to break things and force people onto 1.8x. Just a thought...no
  blame game. But really something like this should be tackled quickly. No
  point to break things so badly on the last stable version.
 
  Regards,
 

 Confirming this issue on 10+ 1.6.2.19 Asterisk servers. This problem
 makes it difficult to do edits on sip.conf on production systems, as
 there is ~25% chance that you'll crash the server and cut the
 established calls. The problem does not exist in 1.6.2.18...

 I think this problem should be fixed or the 1.6.2.19 should be removed
 from the digium repo.

 Regards,
 Vahan

 --
 _
 -- Bandwidth and Colocation Provided by http://www.api-digital.com --
 New to Asterisk? Join us for a live introductory webinar every Thurs:
   http://www.asterisk.org/hello

 asterisk-users mailing list
 To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

 --
 _
 -- Bandwidth and Colocation Provided by http://www.api-digital.com --
 New to Asterisk? Join us for a live introductory webinar every Thurs:
   http://www.asterisk.org/hello

 asterisk-users mailing list
 To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

--
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
   http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Re: [asterisk-users] Serious bug in 1.6.2.19 - what is the time frame to fix such bugs?

2011-08-02 Thread Richard Mudgett
 Can you please point me to the patch that you just made?
 
The patch is committed to v1.6.2 SVN branch.
Patch for v1.6.2 only.

r330490 | jrose | 2011-08-01 16:08:10 -0500 (Mon, 01 Aug 2011) | 12 lines

Asterisk 18103 - Fix reload crash caused by destroying default parking lot

Default parking lot was being destroyed in reload and was not being rebuilt 
properly.
This patch keeps features.c reload from destroying the default parking lot in 
1.6.2.
Bug was caused by a hasty backport which didn't test reload enough times to 
catch the
problem.

(closes issue ASTERISK-18103)
Reported by: 808blogger

Review: https://reviewboard.asterisk.org/r/1337/

Also -r330505 to fix a ref leak with the above patch.

Richard

--
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
   http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [asterisk-users] Serious bug in 1.6.2.19 - what is the time frame to fix such bugs?

2011-08-01 Thread Bruce B
Thanks for feedback. Yeah, tell me about it. Your description is very
accurate of the situation. I can't believe it's in the repo without any
tests done; even the simplest reload. I don't mean to be a whiner but
honestly the repo is a joke with such an obvious flaw for so long
now

On Sun, Jul 31, 2011 at 4:03 AM, Vahan Yerkanian va...@arminco.com wrote:

 On 7/30/11 7:39 AM, Bruce B wrote:

 I think this should be a quick fix since it's rendering the latest
 stable version useless and making the impression that it was released
 just to break things and force people onto 1.8x. Just a thought...no
 blame game. But really something like this should be tackled quickly. No
 point to break things so badly on the last stable version.

 Regards,


 Confirming this issue on 10+ 1.6.2.19 Asterisk servers. This problem makes
 it difficult to do edits on sip.conf on production systems, as there is ~25%
 chance that you'll crash the server and cut the established calls. The
 problem does not exist in 1.6.2.18...

 I think this problem should be fixed or the 1.6.2.19 should be removed from
 the digium repo.

 Regards,
 Vahan


 --
 __**__**_
 -- Bandwidth and Colocation Provided by http://www.api-digital.com --
 New to Asterisk? Join us for a live introductory webinar every Thurs:
  http://www.asterisk.org/hello

 asterisk-users mailing list
 To UNSUBSCRIBE or update options visit:
  
 http://lists.digium.com/**mailman/listinfo/asterisk-**usershttp://lists.digium.com/mailman/listinfo/asterisk-users

--
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
   http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Re: [asterisk-users] Serious bug in 1.6.2.19 - what is the time frame to fix such bugs?

2011-08-01 Thread Jonathan Rose
We worked on this bug today and are expecting to release packages with the fix 
soon, possibly tomorrow (Aug 2).  The issue arose from a change in features 
reload which was back-ported to 1.6.2 and was committed without enough testing 
to observe the intermittent crash behavior.

Thanks for your patience,
Jonathan R. Rose

- Original Message -
From: Vahan Yerkanian va...@arminco.com
To: Asterisk Users Mailing List - Non-Commercial Discussion 
asterisk-users@lists.digium.com
Sent: Sunday, July 31, 2011 3:03:07 AM
Subject: Re: [asterisk-users] Serious bug in 1.6.2.19 - what is the time frame 
to fix such bugs?

On 7/30/11 7:39 AM, Bruce B wrote:
 I think this should be a quick fix since it's rendering the latest
 stable version useless and making the impression that it was released
 just to break things and force people onto 1.8x. Just a thought...no
 blame game. But really something like this should be tackled quickly. No
 point to break things so badly on the last stable version.

 Regards,


Confirming this issue on 10+ 1.6.2.19 Asterisk servers. This problem 
makes it difficult to do edits on sip.conf on production systems, as 
there is ~25% chance that you'll crash the server and cut the 
established calls. The problem does not exist in 1.6.2.18...

I think this problem should be fixed or the 1.6.2.19 should be removed 
from the digium repo.

Regards,
Vahan

--
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
   http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

--
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
   http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [asterisk-users] Serious bug in 1.6.2.19 - what is the time frame to fix such bugs?

2011-07-31 Thread Vahan Yerkanian

On 7/30/11 7:39 AM, Bruce B wrote:

I think this should be a quick fix since it's rendering the latest
stable version useless and making the impression that it was released
just to break things and force people onto 1.8x. Just a thought...no
blame game. But really something like this should be tackled quickly. No
point to break things so badly on the last stable version.

Regards,



Confirming this issue on 10+ 1.6.2.19 Asterisk servers. This problem 
makes it difficult to do edits on sip.conf on production systems, as 
there is ~25% chance that you'll crash the server and cut the 
established calls. The problem does not exist in 1.6.2.18...


I think this problem should be fixed or the 1.6.2.19 should be removed 
from the digium repo.


Regards,
Vahan

--
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
  http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
  http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [asterisk-users] Serious bug in 1.6.2.19 - what is the time frame to fix such bugs?

2011-07-29 Thread Paul Belanger

On 11-07-29 06:12 PM, Bruce B wrote:

Hi everyone,

Asterisk 1.6.2.19 has a bug per:
https://issues.asterisk.org/jira/browse/ASTERISK-18103

What is the general time to fix this? I think a similar thing is also noted
in 1.8x install. Is it not going to be taken care of because it's 1.6x ?

1.6.2.19 was to be the last release of the 1.6.2 branch, so I'm not sure 
if another build is expected. However the issue does reference 
1.6.2.19.1 so it is possible.


However, you can see what changed between 1.6.2.18 and 1.6.2.19 in an 
attempted to narrow down the bug.


--
Paul Belanger
Digium, Inc. | Software Developer
twitter: pabelanger | IRC: pabelanger (Freenode)
Check us out at: http://digium.com  http://asterisk.org

--
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
  http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
  http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [asterisk-users] Serious bug in 1.6.2.19 - what is the time frame to fix such bugs?

2011-07-29 Thread Kevin P. Fleming

On 07/29/2011 06:20 PM, Paul Belanger wrote:

On 11-07-29 06:12 PM, Bruce B wrote:

Hi everyone,

Asterisk 1.6.2.19 has a bug per:
https://issues.asterisk.org/jira/browse/ASTERISK-18103

What is the general time to fix this? I think a similar thing is also
noted
in 1.8x install. Is it not going to be taken care of because it's 1.6x ?


1.6.2.19 was to be the last release of the 1.6.2 branch, so I'm not sure
if another build is expected. However the issue does reference
1.6.2.19.1 so it is possible.

However, you can see what changed between 1.6.2.18 and 1.6.2.19 in an
attempted to narrow down the bug.


If it was a regression from 1.6.2.18 to 1.6.2.19, then it will be fixed.

--
Kevin P. Fleming
Digium, Inc. | Director of Software Technologies
Jabber: kflem...@digium.com | SIP: kpflem...@digium.com | Skype: kpfleming
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us out at www.digium.com  www.asterisk.org

--
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
  http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
  http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [asterisk-users] Serious bug in 1.6.2.19 - what is the time frame to fix such bugs?

2011-07-29 Thread Bruce B
I think this should be a quick fix since it's rendering the latest stable
version useless and making the impression that it was released just to break
things and force people onto 1.8x. Just a thought...no blame game. But
really something like this should be tackled quickly. No point to break
things so badly on the last stable version.

Regards,

On Fri, Jul 29, 2011 at 6:23 PM, Kevin P. Fleming kpflem...@digium.comwrote:

 On 07/29/2011 06:20 PM, Paul Belanger wrote:

 On 11-07-29 06:12 PM, Bruce B wrote:

 Hi everyone,

 Asterisk 1.6.2.19 has a bug per:
 https://issues.asterisk.org/**jira/browse/ASTERISK-18103https://issues.asterisk.org/jira/browse/ASTERISK-18103

 What is the general time to fix this? I think a similar thing is also
 noted
 in 1.8x install. Is it not going to be taken care of because it's 1.6x ?

  1.6.2.19 was to be the last release of the 1.6.2 branch, so I'm not sure
 if another build is expected. However the issue does reference
 1.6.2.19.1 so it is possible.

 However, you can see what changed between 1.6.2.18 and 1.6.2.19 in an
 attempted to narrow down the bug.


 If it was a regression from 1.6.2.18 to 1.6.2.19, then it will be fixed.

 --
 Kevin P. Fleming
 Digium, Inc. | Director of Software Technologies
 Jabber: kflem...@digium.com | SIP: kpflem...@digium.com | Skype: kpfleming
 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
 Check us out at www.digium.com  www.asterisk.org


 --
 __**__**_
 -- Bandwidth and Colocation Provided by http://www.api-digital.com --
 New to Asterisk? Join us for a live introductory webinar every Thurs:
  http://www.asterisk.org/hello

 asterisk-users mailing list
 To UNSUBSCRIBE or update options visit:
  
 http://lists.digium.com/**mailman/listinfo/asterisk-**usershttp://lists.digium.com/mailman/listinfo/asterisk-users

--
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
   http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users