On 5/25/2011 11:11 AM, m...@grounded.net wrote:
I haven't updated my 4.2.1 in a while so when doing it I get the following
error.
Thought I would check with the list before rebooting, just in case.
Transaction Check Error:
file /usr/local/freeswitch/bin/fsxs from install of
sipx-freeswitch
On Wed, 25 May 2011 14:46:39 -0400, Tony Graziano wrote:
> i think you might do well to test it against your trunks before deploying
> it.
I'll go that route if I have no other options I guess.
___
sipx-users mailing list
sipx-users@list.sipfoundry.org
L
i think you might do well to test it against your trunks before deploying
it.
On Wed, May 25, 2011 at 2:27 PM, m...@grounded.net wrote:
> Based on the ones you've done, do you think it would be safe to upgrade the
> 4.2.1 to 4.4.0.
>
>
> On Wed, 25 May 2011 14:23:58 -0400, Tony Graziano wrote:
>
Based on the ones you've done, do you think it would be safe to upgrade the
4.2.1 to 4.4.0.
On Wed, 25 May 2011 14:23:58 -0400, Tony Graziano wrote:
> you would never undo the last update.
> On May 25, 2011 1:18 PM, "m...@grounded.net" wrote:
>> Wait now, are you guys talking about doing an upg
you would never undo the last update.
On May 25, 2011 1:18 PM, "m...@grounded.net" wrote:
> Wait now, are you guys talking about doing an upgrade from 4.2.1 to 4.4.0?
> I just wanted to update a 4.2.1 system but I don't have a problem
upgrading if everyone feels it's safe to do so.
>
> My only ne
Wait now, are you guys talking about doing an upgrade from 4.2.1 to 4.4.0?
I just wanted to update a 4.2.1 system but I don't have a problem upgrading if
everyone feels it's safe to do so.
My only next concern is that I've already run the update earlier, still not
sure if everything will be ok
> um, look at the repo file on your system. it is probably the 4.2.1 repo.
> there was an small update pushed out to 4.2.1 yesterday i think, so if YOUR
> repo points to 4.2.1, it is doing exactly what the repo tells it to do.
It is the 4.2.1 repo. I would not have wanted to update directly betwee
On Wed, May 25, 2011 at 12:42 PM, Douglas Hubler wrote:
> On Wed, May 25, 2011 at 12:34 PM, m...@grounded.net
> wrote:
> > Well, interesting then because my system didn't get updated to 4.4.0 when
> I ran the update, it only updated 4.2.1.
>
> This is also a departure how sipxecs release eng ran
On Wed, May 25, 2011 at 12:34 PM, m...@grounded.net wrote:
> Well, interesting then because my system didn't get updated to 4.4.0 when I
> ran the update, it only updated 4.2.1.
This is also a departure how sipxecs release eng ran in the past I
think. You have to explicitly install a new sipxec
um, look at the repo file on your system. it is probably the 4.2.1 repo.
there was an small update pushed out to 4.2.1 yesterday i think, so if YOUR
repo points to 4.2.1, it is doing exactly what the repo tells it to do.
On Wed, May 25, 2011 at 12:34 PM, m...@grounded.net wrote:
> > ive always up
> ive always upgraded by removing the packages and updating to 4.4.0x.
>>Do you mean a full re-install?
> no, just the complaining freeswitch package and dependencies (which are all
> codecs). they reinstall when you update.
Well, interesting then because my system didn't get updated to 4.4.0 w
no, just the complaining freeswitch package and dependencies (which are all
codecs). they reinstall when you update.
On Wed, May 25, 2011 at 12:23 PM, m...@grounded.net wrote:
> On Wed, 25 May 2011 12:10:46 -0400, Tony Graziano wrote:
> > ive always upgraded by removing the packages and updating
On Wed, 25 May 2011 12:10:46 -0400, Tony Graziano wrote:
> ive always upgraded by removing the packages and updating to 4.4.0x.
Do you mean a full re-install?
Would I simply yum remove sipx?
How would I make sure that users/settings/vm's were not lost?
On the other hand, have you tried a backup/
ive always upgraded by removing the packages and updating to 4.4.0x.
On Wed, May 25, 2011 at 12:04 PM, m...@grounded.net wrote:
> So the real question is, since sipx-freeswitch was 32bit anyhow, it didn't
> get updated but is that a problem? Will it still work with the rest of the
> system which
So the real question is, since sipx-freeswitch was 32bit anyhow, it didn't get
updated but is that a problem? Will it still work with the rest of the system
which did get updated?
If so, then it's a non issue, I simply reboot, all the new things are put into
use but I don't get the 64 latest sip
rpm -ql sipx-freeswitch gives me;
/etc/ld.so.conf.d/freeswitch.ld.so.conf
/etc/monit.d
/etc/monit.d/freeswitch.monitrc
/etc/sysconfig/freeswitch
/usr/local/freeswitch/*
> then do
> rpm -e --justdb sipx-freeswitch-1.0.5-17188.16739.2.i386
Isn't there a problem with rpm or yum not always knowing w
On Wed, May 25, 2011 at 11:28 AM, m...@grounded.net wrote:
> Bit nervous about doing that because it removes others at the same time and
> I'm not sure if I should use nodeps or not.
> Too easy to break the system when things get into dep problems.
CAVEAT: I haven't tried this, just giving
> unfortunately sipxecs 4.2.1 yum repo mixes 32 and 64 bit archs and
> although the OS is supposed to do the right thing, often folks get
> into situations were system has 32 and 64 bit rpms installed. i'm not
> sure how it gets into this situation.
I didn't come across any problems when building
> Why would the package contain a 64 bit
> file when a 32 bit file is installed?
> Is this a 32 or 64 bit machine?
2.6.18-194.17.1.el5 #1 SMP Wed Sep 29 12:50:31 EDT 2010 x86_64 x86_64 x86_64
GNU/Linux
64bit hardware. It was built using the repo, not from ISO.
_
Bit nervous about doing that because it removes others at the same time and I'm
not sure if I should use nodeps or not.
Too easy to break the system when things get into dep problems.
On Wed, 25 May 2011 11:22:19 -0400, Tony Graziano wrote:
> you have to yum remove the package in order to upda
Why would the package contain a 64 bit file when a 32 bit file is
installed?
Is this a 32 or 64 bit machine?
Tony Graziano wrote on 25-05-2011 17:22:19:
> you have to yum remove the package in order to update properly i
think...
> On Wed, May 25, 2011 at 11:11 AM, m...@grounded.net
wrote:
On Wed, May 25, 2011 at 11:11 AM, m...@grounded.net wrote:
> I haven't updated my 4.2.1 in a while so when doing it I get the following
> error.
> Thought I would check with the list before rebooting, just in case.
>
>
> Transaction Check Error:
> file /usr/local/freeswitch/bin/fsxs from install
you have to yum remove the package in order to update properly i think...
On Wed, May 25, 2011 at 11:11 AM, m...@grounded.net wrote:
> I haven't updated my 4.2.1 in a while so when doing it I get the following
> error.
> Thought I would check with the list before rebooting, just in case.
>
>
> Tr
I haven't updated my 4.2.1 in a while so when doing it I get the following
error.
Thought I would check with the list before rebooting, just in case.
Transaction Check Error:
file /usr/local/freeswitch/bin/fsxs from install of
sipx-freeswitch-1.0.5-17188.16739.2.i386 conflicts with file from
24 matches
Mail list logo
