Please read the entire thread... On Mon, Jan 31, 2011 at 11:16 AM, xavier houghton <[email protected]>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 dependency issues, I did not see this from testing "from" 4.2.1). I say this because prior to 4.4... updates from "some" 4.3 and 4.4 versions to subsequent versions did not work. I started over, as it was not a production environment. I also do not understand if there "is" a db upgrade, and assuming the db upgrade script for postgres is included in a snapshot 4.4 to come from 4.2.1 how you can be "backward compatible" to go back to 4.2.1 without having a db issue. Is there a db schema change in 4.4 (from 4.2.1)? I recall there were changes to "branch" which would mean there is a db change. If you are not in a production environment I don't see how any of this matters though. I also suspect once a Beta of 4.4 is out to test updating against, a lot more can be known and/or shared. I never once stated or gave the impression a yum update would not be advisable from one stable version to another. I simply suggested both a backup and export of the current version (4.2.1) might be a good way to begin in the event things don't work out for an in-place upgrade (especially) as it pertains to a production system. I did, and will, give the user the idea that backing up and exporting their data is a good idea if they decide to take a production system to a snapshot or development version... I don't see why this is an issue. > > not used SIPx for a while but that seemd to be how to upgrade according > to the wiki > > In doing an yum update from 4.2.1 it properly fetches all the needed packages as long as you have the OS repo's so you can get all the dependencies.
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
