Hi Dave, I think Scott answered this for me on Thursday: ************* > >Sorry - FC 6 is not one of the platforms that we built for 3.10.2; > >CentOS 5, F8, F7, and SUSE 10.2 are built. > > Thanks for the reply Scott. It is a little ambiguous though, could you > please clarify?
Yes, that was too brief. Some of the changes in 3.10.2 involved changes in external dependencies that are not available on FC6. Rather than add to the list of external things we need to build just to support a platform that Fedora itself considers EOL, we just stopped. I thought (though I may be miss-remembering this) that we had said so on the list quite a while ago - if I forgot to make that announcement, then I sincerely apologize. It has been our long-standing policy to stop supporting a Fedora release more or less when Fedora does, although there is usually some lag since we always want a window of 2 supported base releases. Yes - that means that once we've got an F9 build stable, we'll begin thinking about retiring F7. For production systems, this makes the CentOS platform more attractive, since there is less churn in those releases. > OK, so 3.10.0 and 3.10.1 are released and FC6 is supported and built. > Will there be a 3.10.2 for FC6? If not, it would be really helpful if > this had been stated in a roadmap or something. I, like a lot of > others I'm sure, find that there is not an easy upgrade from FC 6 to 7 > or 8 short of building a new system. That's not true. It's straightforward to upgrade within the Fedora series using yum. I've done it several times on my own system. Here are some instructions for the platform: http://www.ioncannon.net/linux/68/upgrading-from-fc6-to-fedora7-with-yum/ An even safer and easier method is to burn an F7 (or F8 for that matter) CD and install that - it will give you the option of upgrading the installation you have "in place", then after you've done that, rerun yum update to pick up the sipXecs updates (before you try to start sipXecs). Perhaps if you went and did the CD install of Centos 5 it would work for you by doing an inplace upgarde of the OS. http://wiki.centos.org/Migration/5 Then I would assume with sipx stopped, you could get the yum repo for Centos 5, and yum update sipxecs, which I assume "might" be able to update your Postgres schema, but you really should ask, and hence update the system. Alternately, you would have to create a dumpfile of the sipx databases and zip the directories with voicemail and custom prompts. Wipe the old system and install the Centos 5 sipx installer CD, then delete the sipx databases and restore the ones you have backed up so they go into the new format. Again, ask for clarification here, I'm not keen on whether the sipx schema detects an old-old version of the database and how it would handle it to use it properly. Then copy to proper voicemail and prompts back over. After that you probably would have to resiuue and install certiciates manually. In either case, you ought to make a backup of your DB's and voicemail stuff, plus whatever else you might have spent any time on (DHCP/DNS/NTP, making sure you get the dhcp.leases file too). >>> "Dave Deutschman" <[EMAIL PROTECTED]> 07/29/08 01:42PM >>> We have a customer that is planning the upgrade of a SIPxchange v3.6.8 system to v3.10.2. They are currently running v3.6.8 on CentOS 4 and would like to know if a build will be provided for CentOS 4? Sincerely, Dave Deutschman
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
