Topic: SME 7 base Updates obsolete? SME 8 still Beta?? Time to work hard on..

[linuxhelp]

ftp://mirror.fraunhofer.de/centos.org/4.9/os/i386/repodata/repomd.xml: [Errno 4] IOError: [Errno ftp error] 550 os: No such file or directory
Trying other mirror.
http://wftp.tu-chemnitz.de/pub/linux/centos/4.9/os/i386/repodata/repomd.xml: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://ftp.plusline.de/centos/4.9/os/i386/repodata/repomd.xml: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://mirror.silyus.net/centos/4.9/os/i386/repodata/repomd.xml: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://mirror.atrpms.net/centos/4.9/os/i386/repodata/repomd.xml: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://ftp.hosteurope.de/mirror/centos.org/4.9/os/i386/repodata/repomd.xml: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://mirror.mserverz.de/4.9/os/i386/repodata/repomd.xml: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://mirror.softaculous.com/centos/4.9/os/i386/repodata/repomd.xml: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://mirror.de.leaseweb.net/centos/4.9/os/i386/repodata/repomd.xml: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://centos.bio.lmu.de/4.9/os/i386/repodata/repomd.xml: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://centos.copahost.com/4.9/os/i386/repodata/repomd.xml: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://be.mirror.eurid.eu/centos/4.9/os/i386/repodata/repomd.xml: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://ftp.halifax.rwth-aachen.de/centos/4.9/os/i386/repodata/repomd.xml: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://ftp-stud.fht-esslingen.de/pub/Mirrors/centos/4.9/os/i386/repodata/repomd.xml: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://centos.mirror.connexeon.net/4.9/os/i386/repodata/repomd.xml: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://ftp.belnet.be/packages/centos/4.9/os/i386/repodata/repomd.xml: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://centos.intergenia.de/4.9/os/i386/repodata/repomd.xml: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://centos.psw.net/centos/4.9/os/i386/repodata/repomd.xml: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://mirror.netcologne.de/centos/4.9/os/i386/repodata/repomd.xml: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://centos.vieth-server.de/4.9/os/i386/repodata/repomd.xml: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
Cannot open/read repomd.xml file for repository: base
failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
Error: failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.

does it be changed by new mirrorlists? see Readme Redhat..

This directory (and version of CentOS) is depreciated. 

CentOS-4 is now past EOL

You can get the last released version of centos 4.9 here:

http://vault.centos.org/4.9/

[byte]

Please raise a new bug and report your findings there.

Thanks.

[janet]

linuxhelp

As a temporary workaround pending mirror updates or whatever the final outcome may be, I did this

db yum_repositories setprop base status disabled
db yum_repositories setprop updates status disabled

/sbin/e-smith/db yum_repositories set base-vault repository \
Name 'Centos - os-vault' \
BaseURL 'http://vault.centos.org/4.9/os/$basearch' \
EnableGroups no \
GPGCheck yes \
Visible yes \
Exclude kernel,kernel-smp,kernel-xenU,mkinitrd,mdadm,initscripts \
status enabled

/sbin/e-smith/db yum_repositories set updates-vault repository \
Name 'Centos - updates-vault' \
BaseURL 'http://vault.centos.org/4.9/updates/$basearch' \
EnableGroups no \
GPGCheck yes \
Visible yes \
Exclude kernel,kernel-smp,kernel-xenU,mkinitrd,mdadm,initscripts \
status enabled

signal-event yum-modify
yum clean all

Seems to work OK now without errors

[linuxhelp]

Hi Mary,

thanks for help, did anyone post bug report?
if not i will do.. SEE Bug 6869

http://bugs.contribs.org/show_bug.cgi?id=6869

when will sme 8 be freezed?

Thanks to all..

[chris burnat]

The original bug report for this problem is Bug #6868, thanks to Ray Mitchell for identifying this issue and coming with a workaround:
http://bugs.contribs.org/show_bug.cgi?id=6868

Please refer and follow there for update, no need for further post on this topic at this stage.

Check also this post for a new workaround recommended by the Dev Team (Charlie):
http://forums.contribs.org/index.php/topic,48409.0.html

[chris burnat]

Remedial action has been implemented by the Dev Team, please refer: http://forums.contribs.org/index.php/topic,48424.0.html for details.
Thanks.

[kb-ohnemus]

I'm really worried that by the time SME8 gets 1.0 Centos5 will be obsolete.. This is not meant being insulting.

[marsa_matruh]

Red Hat Enterprise Linux 5 and 6 are offered with 10 years of Production Phase support.

See Red Hat Enterprise Linux Life Cycle

[erroneus]

I'm really worried that by the time SME8 gets 1.0 Centos5 will be obsolete.. This is not meant being insulting.

I'm worried about the same thing.

I seriously think that as long as things are going to be in beta, they might as well move the SME 8 series over to CentOS 6.x.  At the very least begin work at making SME 8.5.x based on 6.x.  As long as there are going to be delays, it might as well be "buffered."

Besides that, I have this feeling that moving from Cent5 to Cent6 will not be that big of a deal and will probably have many positive side-effects.

[janet]

erroneus

Developers and testers are seriously working on releasing SME 8 RC1 (Release Candidate 1), expected very soon now.
At that point development of SME8.0 will essentially freeze, so that sme8.0 final can be released after sufficient testing of RC1.

Suddenly jumping to CentOS 6.x would significantly delay the next SME server release.

Moving from CentOS 5 to CentOS 6 will require significant developer input, despite your "feelings". You underestimate greatly the complexity and degree of effort & testing required to create a stable release of SME based on CentOS.

The buffering process you request is to release a SME Server version 8.0 based on CentOS 5.x.
Then later when deemed necessary and as developer and volunteer effort are contributed, a move to a SME 9 based on CentOS 6 can be considered.
The timing of that in the future, will be based upon when good people choose to donate their time and effort to the furtherance of the SME Server project.

So stop worrying, stop expecting instantaneous major changes, and contrib some time or money to the efforts to get sme8.0 final released.

[cactus]

At the very least begin work at making SME 8.5.x based on 6.x.

If we only had the resources to do so... the resources of the SME Server development and test team are severely limited and all work is done by just over a handful of people in their spare time, without financial reward. So I think you need to adjust you expectations a little. If we are also to work on the release after the next, we wouldn´t get either released IMHO.

Apart from that it would then be called SME Server 9 and not SME Server 8.5.

[janet]

This appears to be the basis of the final fix soon to be released for the yum update vault EOL issue, ie to modify the original base and updates repositories
Refer bug 6873

db yum_repositories setprop base BaseURL 'http://vault.centos.org/4.9/os/$basearch'
db yum_repositories setprop updates BaseURL 'http://vault.centos.org/4.9/updates/$basearch'
db yum_repositories delprop base MirrorList
db yum_repositories delprop updates MirrorList
db yum_repositories setprop base status enabled
db yum_repositories setprop updates status enabled
signal-event yum-modify
yum clean all

yum update should then work correctly and normally

Edit: to be more exact, "will work correctly until a reconfiguration is done, at which time default values will return the repository settings back to original default values".
So the above solution is only a temporary workaround until an official update is released.

I did say it was the basis for the final fix soon to be released.
While suggested as being misinformation in bugzilla, I saw it as information that indicated to users what was being done to fix the yum update problem, so users could update older systems that were not "up to date" prior to an official fix being released.

[CharlieBrady]

yum update should then work correctly and normally

No, this is not correct. Because there are 'default' db properties, Mirrorlist properties will return during reconfiguration.

This can only be corrected via a software update. People should use the already published workaround, and then wait for official announcement of an update.

Mary, please do not spread misinformation.

[chris burnat]

I did say it was the basis for the final fix soon to be released.
While suggested as being misinformation in bugzilla, I saw it as information that indicated to users what was being done to fix the yum update problem, so users could update older systems that were not "up to date" prior to an official fix being released.

Thanks for your hard work in the wee hours of the morning Mary!   
All of this makes sense, and in then end, all is well since a new package has been released today.
For more info, check:
http://forums.contribs.org/index.php/topic,48424.msg240515.html#msg240515

Thanks and regards

[stabilys]

We certainly do need the SME 8 ASAP as Win 7 w/s issues are pressing.

Other than checking the current beta (downloading for testing right now - have tested previous betas too), is there anything else that the team needs to facilitate the release? Or is there a list somewhere to check? IE, is there anything we can do to help?

ty