Topic: SME 7 Pre1

[russs]

I see that SME 7 is now at pre1 stage.

I know you can't say for sure and I imagine you are sick of hearing this but, is there a likely date for it's final release?

It's just that I would like to implement our new Webserver based on SME7 but would prefer to hold on for official release. If it is still many months away, which I understand as you want to get it right, I will go ahead and use the pre1 version.

I imagine there are many others using your excellent piece of software who will want to know this answer!

Thanks

[stefan24]

I'm using SME 7 since Beta 8 as my production file server and mail server.
update to Beta 9 and Pre 1 went flawlessly (AFAICS).

[russs]

Thanks stefan24, that's all I needed to hear!
Any excuse and I'm on SME7.
I'll set it up tomorrow!

[CharlieBrady]

I'm using SME 7 since Beta 8 as my production file server and mail server.
update to Beta 9 and Pre 1 went flawlessly (AFAICS).

Had the system been upgraded by your "upgrade" script before you upgraded to beta9? If so, did it upgrade cleanly? If not, could you please report any issues to the bug tracker?

[stefan24]

Charlie,

No. It was a fresh install, since I wanted to use SATA and a new hardware.

I just installed a SME 6.01 server for a customer with the Plus Script. (updated from SME 5.6 with a manual backup, new install and a manual restore).
I will "update" this SME server some day to SME7 the same way: fresh install and manual restore of the files and mails.

[yehaah]

I see that SME 7 is now at pre1 stage.

I know you can't say for sure and I imagine you are sick of hearing this but, is there a likely date for it's final release?

It's just that I would like to implement our new Webserver based on SME7 but would prefer to hold on for official release. If it is still many months away, which I understand as you want to get it right, I will go ahead and use the pre1 version.

I'm in the same situation.

In the press release Gordon writes:

SME Server 7.0 pre-release 1 is on its way to the mirrors.

We decided not to call this one RC1 as we have a few bugs we'd like to squash first (see the bug tracker).

However, if you haven't made the move to 7.0, now is the time...

By move now, does this meen that we can move production servers to 7.0pre1 and not fear problems with upgrading to 7.0final later???

[russs]

God question Yehaah!
But I think I'll try it out, as that statement you quoted sounds pretty good to me!

[kenironside]

I'm using SME 7 since Beta 8 as my production file server and mail server.
update to Beta 9 and Pre 1 went flawlessly (AFAICS).

Hi Stephan,  Please forgive a newbie question but how exactly do you go about updating from beta 9 to pre 1?

Thanks, Ken

[stefan24]

I did a "yum update" on the shell, but the Software Installer in the server-manager panel should have done this automatically, if you have not changed the default: "Check for updates daily    Enabled"

[kenironside]

I did a "yum update" on the shell, but the Software Installer in the server-manager panel should have done this automatically, if you have not changed the default: "Check for updates daily    Enabled"

Thanks, I get the following when I run yum check-update. What do I need to chage the repositories to?

[root@silverdesk cur]# yum check-update
Setting up repositories
dungog                    100% |=========================|  951 B    00:00
smeaddons                 100% |=========================|  951 B    00:00
smeos                     100% |=========================|  951 B    00:00
smeupdates                100% |=========================|  951 B    00:00
Reading repository metadata in from local files
primary.xml.gz            100% |=========================| 245 kB    00:04
http://mirror.contribs.org/smeserver/releases/7/os/i386/repodata/primary.xml.gz: [Errno -1] Metadata file does not match checksum
Trying other mirror.
Error: failure: repodata/primary.xml.gz from smeos: [Errno 256] No more mirrors to try.

Thanks, Ken

[byte]

I'm using SME 7 since Beta 8 as my production file server and mail server.
update to Beta 9 and Pre 1 went flawlessly (AFAICS).

Had the system been upgraded by your "upgrade" script before you upgraded to beta9? If so, did it upgrade cleanly? If not, could you please report any issues to the bug tracker?

I did an upgrade from SME 7.0b8 to SME 7.0b9 then when SME 7.0pre1 came out again did upgrade via Yum and updated fine...

Great work guys!

[kenironside]

I did a "yum update" on the shell, but the Software Installer in the server-manager panel should have done this automatically, if you have not changed the default: "Check for updates daily    Enabled"

Thanks, I get the following when I run yum check-update. What do I need to chage the repositories to?

[root@silverdesk cur]# yum check-update
Setting up repositories
dungog                    100% |=========================|  951 B    00:00
smeaddons                 100% |=========================|  951 B    00:00
smeos                     100% |=========================|  951 B    00:00
smeupdates                100% |=========================|  951 B    00:00
Reading repository metadata in from local files
primary.xml.gz            100% |=========================| 245 kB    00:04
http://mirror.contribs.org/smeserver/releases/7/os/i386/repodata/primary.xml.gz: [Errno -1] Metadata file does not match checksum
Trying other mirror.
Error: failure: repodata/primary.xml.gz from smeos: [Errno 256] No more mirrors to try.

Thanks, Ken

[stefan24]

dungog                    100% |=========================|  951 B    00:00

You changed this to include Dungogs repository. How did you include it? Maybe you have produced a failure.

I don't know, wether my /home/e-smith/db/yum_repositories (from SME 7 pre1) is good for your SME 7 beta 8, but check any differences:

Code: [Select]

# DO NOT MODIFY THIS FILE.
# This file is automatically maintained by the Mitel Networks SME Server
# configuration software.  Manually editing this file may put your
# system in an unknown state.
#
# updated: Wed Jan 11 14:27:30 2006
addons=repository|BaseURL|http://mirror.centos.org/centos/4/addons/$basearch|EnableGroups|no|GPGCheck|yes|Name|CentOS - addons|Visible|yes|status|disabled
base=repository|BaseURL|http://mirror.centos.org/centos/4/os/$basearch|EnableGroups|no|GPGCheck|yes|Name|CentOS - os|Visible|yes|status|disabled
centosplus=repository|BaseURL|http://mirror.centos.org/centos/4/centosplus/$basearch|EnableGroups|no|GPGCheck|yes|Name|CentOS - centosplus|Visible|no|status|disabled
contrib=repository|BaseURL|http://mirror.centos.org/centos/4/contrib/$basearch|EnableGroups|no|GPGCheck|yes|Name|CentOS - contrib|Visible|yes|status|enabled
extras=repository|BaseURL|http://mirror.centos.org/centos/4/extras/$basearch|EnableGroups|no|GPGCheck|yes|Name|CentOS - extras|Visible|no|status|disabled
smeaddons=repository|BaseURL|http://mirror.contribs.org/smeserver/releases/7/addons/$basearch|EnableGroups|yes|GPGCheck|yes|Name|SME Server - addons|Visible|yes|status|enabled
smedev=repository|BaseURL|http://mirror.contribs.org/smeserver/releases/7/dev/$basearch|EnableGroups|yes|GPGCheck|yes|Name|SME Server - dev|Visible|no|status|disabled
smeos=repository|BaseURL|http://mirror.contribs.org/smeserver/releases/7/os/$basearch|EnableGroups|yes|GPGCheck|yes|Name|SME Server - os|Visible|yes|status|enabled
smetest=repository|BaseURL|http://mirror.contribs.org/smeserver/releases/7/test/$basearch|EnableGroups|yes|GPGCheck|yes|Name|SME Server - test|Visible|no|status|disabled
smeupdates=repository|BaseURL|http://mirror.contribs.org/smeserver/releases/7/updates/$basearch|EnableGroups|yes|GPGCheck|yes|Name|SME Server - updates|Visible|yes|status|enabled
smeupdates-testing=repository|BaseURL|http://mirror.contribs.org/smeserver/releases/7/updates-testing/$basearch|EnableGroups|yes|GPGCheck|yes|Name|SME Server - updates testing|Visible|no|status|disabled
testing=repository|BaseURL|http://mirror.centos.org/centos/4/testing/$basearch|EnableGroups|no|GPGCheck|yes|Name|CentOS - testing|Visible|no|status|disabled
updates=repository|BaseURL|http://mirror.centos.org/centos/4/updates/$basearch|EnableGroups|no|GPGCheck|yes|Name|CentOS - updates|Visible|yes|status|enabled


Also check for primary.xml.gz files in /var/cache/yum.
However, I don't know, what to do with them.

[kenironside]

The only difference is that the last line in my file reads updates=repository|BaseURL|http://mirror.centos.org/centos/4/updates/$basearch|EnableGroups|no|GPGCheck|yes|Name|CentOS - updates|Visible|no|status|disabled

updates are disabled wheras your updates line is enabled. I don't know if I can edit this file (warned not to in the header) or where it is modified from.

I have the Software Installed set to update daily but yum is experiencing errors: Here is the yum log:
2006-01-11 04:05:11.689600500 Error: failure: repodata/primary.xml.gz from smeos: [Errno 256] No more mirrors to try.
2006-01-11 04:05:11.784815500 yum list available status 256
2006-01-11 04:05:15.993473500 Error: No Groups on which to run command
2006-01-11 04:05:16.107879500 yum grouplist available status 256
2006-01-11 04:05:22.029671500 Error: No Groups on which to run command
2006-01-11 04:05:22.141911500 yum grouplist installed status 256
2006-01-11 04:05:30.444758500 Error: failure: repodata/primary.xml.gz from smeos: [Errno 256] No more mirrors to try.
2006-01-11 04:05:30.519850500 yum list updates status 256
2006-01-11 04:05:33.802961500 Error: No Groups on which to run command
2006-01-11 04:05:33.883173500 yum grouplist updates status 256

Any ideas?

[gizzmo2k1]

Upgrade from Beta 9 to Pre 1 worked like a charm.  Just had to remember to do the Reconfigure Reboot.  Beauty.