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
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.
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
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
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
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
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,
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
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
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 ?
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
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
12 matches
Mail list logo
