hmm.. ok just signed up today, only saw last message
On 31/01/2011 17:13, Tony Graziano wrote:
Please read the entire thread...
On Mon, Jan 31, 2011 at 11:16 AM, xavier houghton
mailto:xav...@mtdanywhere.com>> wrote:
so you can't simply do a yum update? was planning to upgrade to
4.4
Please read the entire thread...
On Mon, Jan 31, 2011 at 11:16 AM, xavier houghton wrote:
> so you can't simply do a yum update? was planning to upgrade to 4.4 this
> week to test ldap.
>
I stated from my experiences that is was not "supported" (though it might
work, but others were hitting depe
so you can't simply do a yum update? was planning to upgrade to 4.4 this
week to test ldap.
not used SIPx for a while but that seemd to be how to upgrade according
to the wiki
On 31/01/2011 15:33, Nathaniel Watkins wrote:
> There was definitely a big point made about being able to restore backu
There was definitely a big point made about being able to restore backups from
a post 4.2 environment forward...
Having to re-install every time there is a major version change was/is a huge
hassle - it definitely keeps folks at bay from using some of the newer features
- I know I was hesitant
On Fri, Jan 28, 2011 at 5:52 PM, Tony Graziano
wrote:
> No it actually doesn't always.
>
> That is why it is a snapshot "development" version.
>
> I've had to start over several times myself. That is expected in a
> non-production release cycle.
>
> Let's not muddy the waters here. 4.2.1 to 4.4 (p
On Fri, Jan 28, 2011 at 5:03 PM, Charles Chalekson wrote:
> Attempting to yum update to 4.4.0 from 4.2.1 and am getting a failure due to
> some dependency issues.
>
> Am I doing something wrong?
>
> Thanks,
> Charles
>
>
> --> Running transaction check
> ---> Package erlang.i386 0:R13B04-1.3 set
> Backing up on one major version and restoring to a different version has
> never been a recommended course of action.
>
> That's what a proper update script, which takes into account db schema
> changes, does.
I got that, just wasn't clear on dev vs stable.
___
ssage -
From: sipx-users-boun...@list.sipfoundry.org
To: sipx-users
Sent: Fri Jan 28 18:16:18 2011
Subject: Re: [sipx-users] upgrade from 4.2.1 to 4.4.0
> Let's not muddy the waters here. 4.2.1 to 4.4 (pre pre beta) is certainly
> not going to work as an in place upgrade at this time.
> Let's not muddy the waters here. 4.2.1 to 4.4 (pre pre beta) is certainly
> not going to work as an in place upgrade at this time... so be patient or...
Do you mean that major releases do have backup restore then, just not dev
versions?
That's easy to live with if that's the case.
2011
Subject: Re: [sipx-users] upgrade from 4.2.1 to 4.4.0
> I don't imagine there
> is an announcement that a backup/restore would work between versions. I
> would imagine not.
It works between minor versions, are you saying that we have to reconfigure
from scratch when a major
Content-Type: text/plain;
charset="utf-8"
Content-Transfer-Encoding: 8bit
Organization: SipXecs Forum
In-Reply-To: <2011128163613.087954@leena>
X-FUDforum: 08063afcdd00a6e76393c5b9527381e8 <56456>
Message-ID:
The most I've been able to do so far is a CSV export/import
from 4.2.1 to 4.4.0 and
> I don't imagine there
> is an announcement that a backup/restore would work between versions. I
> would imagine not.
It works between minor versions, are you saying that we have to reconfigure
from scratch when a major version such as 4.4 or 4.5 becomes available?
_
I don't know that updating from 4.2.1 to 4.4.x is supported yet. Typically
this would be announced when the beta was ready for use. Normally you would
run the 4.4 iso or install on a fresh system via rpm. I don't imagine there
is an announcement that a backup/restore would work between versions. I
Attempting to yum update to 4.4.0 from 4.2.1 and am getting a failure due to
some dependency issues.
Am I doing something wrong?
Thanks,
Charles
--> Running transaction check
---> Package erlang.i386 0:R13B04-1.3 set to be updated
---> Package freeswitch.i386 0:1.0.7-1441.g35129 set to be upda
14 matches
Mail list logo
