Topic: Keeping SME up to date

[abovett]

Hi

What's the best way of keeping an SME server (6.0.1-01) patched up to date? Is there an equivalent of apt-get update/upgrade or yum update? Or is it a case of applying patches manually?

If the answer is manually, how do I determine when new patches are available and where do I get them?

Thanks

Andy B

[paul_sc]

Hi Abovett...I was looking for just the question you asked. Browsing the forum's etc...It is not clear to me what, if anything, *needs* to be updated on 6.0.1-01. I do have a few 6.0.1 that I have updated various components because I wanted to, but I don't know what needs to be done.

Looking here

http://mirror.contribs.org/smeserver/releases/6.0.1/updates-testing/i386

I don't know if I should download and run them all or not...The readme and update.txt don't really tell me anything and it seems "testing" would be updates not ready for a production server.

Quick searches in the forums brings up the unoffical update script..which I have used in the past, but again, maybe not needed. I am working on a test server now that seems to break PPTP when I install Update Script 3 on a fresh 6.0.1-01 install...I am able to connect pptp...but every time after about a minute traffic stops passing. I revert to 6.0.1-01 and all works fine

Right after I finish typing this note I plan to search again to see if anything is Listed as Required for security reasons...seems that info should  have high visibility in a faq, forum or in the DL section.

Please post if you find out any information...thanks

[paul_sc]

From the Administration FAQ

Code: [Select]

* Which updates do I need to apply to SME?

15 July: The updates structure and process is undergoing changes. This FAQ entry will be updated to reflect this soon.

SME should be updated regularly from the updates directory

ftp://ibiblio.org/pub/linux/distributions/smeserver/updates/6.0.1/i386/


It is important to install all the updates supported by Contribs.org: the reliability and the safety of your server can depend on it.

[July 8, 2005]
This tree has been relocated.
Please look under
    /smeserver/releases/<Release_Number>updates
for released updates, and
  /smeserver/releases/<Release_Number>/updates-testing
for updates undergoing testing.

It appears the Update Link in the FAQ needs to be updated to the new url.

Once arriving to 6.0.1 release, there is no update folder, just testing.

Does anyone know if all the testing rpm's should be installed?

[Saverio]

I did a clean 6.0.1 install then installed yum and then ran yum update and dhcpd broke... twice. (staticIP on external nic with dhcp on LAN)

I'm trying other stuff now ~ will try to let you know if I get it working

[paul_sc]

seems to be a common issue. I am hopeful once 6.5 or 7 are released keeping up to date won't be so obscure

http://forums.contribs.org/index.php?topic=27602.msg114509#msg114509

As far as I have seen, updating PHP and Open SSH seem important, although I don't see anything in updates or testing directories. I still have not found any feedback on the other files in the testing directory and I notice a few files in release, but not so sure I should rpm them in...any ideas?

Code: [Select]

Index of ftp://ibiblio.org/pub/linux/distributions/smeserver/releases/6.0.1/updates/i386
Up to higher level directory
Directory: headers 7/31/2005 3:43:00 AM
File: rpm-python-4.0.4-7x.18.i386.rpm 31 KB 7/31/2005 3:37:00 AM
File: yum-1.0.3-7sme02.noarch.rpm 107 KB 7/23/2005 9:46:00 PM

[wellsi]

At the moment the maintenance process for SME 6.0 & 6.0.1 is being restarted.

The process is now documented at http://no.longer.valid/phpwiki/index.php/Maintenance%20Process
(If you have any questions after reading this then let me know so that it can be updated)

The updates will be available via yum.

At the moment there are mainly Fedora Legacy updates (undergoing verification), but more will be published.

Until now it has not been widely published as there have been no verified updates, but thanks to encouragement from Charlie and the hard work of a few community members a large number of packages will be moving from updates-testing to updates.

Once there are packages in updates they will be more widely advertised. Please be patient just a little bit longer.

It is the intent of the maintenance team to have all updates available from the yum repository. The maintenance team is currently working to prepare the next batch of updates.

Please let me have all comments (and volunteer help if possible).

If you find any problems with the updates please make that known in the Bug Tracker - there is an entry for every update that the maintenance team has handled.

[ngomes]

The SME Server development (aka, the new releases) and maintenance (aka, the updates) depends entirely on the Contribs.org community.

Just to keep all of you up to date, Ian Wells, Floyd Hartog, Dave Kainer and Matthew Copple (sorry if I left someone out) are the people trying to give to this community the SME Server 6.x maintenance and bugfix updates and  bring to live the SME Server 6.5 final stable release.

Contribs.org needs your help on this project.
What can you do for Contribs.org?

# Read the maintenance process:
http://no.longer.valid/phpwiki/index.php/Maintenance%20Process

# Join the devinfo mailing list and offer your help to test, debug, etc:
http://lists.contribs.org/mailman/listinfo/devinfo

# Go to the Contribs.org Bug Tracker and study some of the listed bugs with new or feedback status, simulate them, give your feedback, try to find some sort of solution. Also if you have some packager skills try to build some rpm packages to the listed bugs with resolved or closed status:
http://no.longer.valid/mantis/view_all_bug_page.php

Finally, take these thoughts into seriously consideration (taken from Charlie Brady, a SME core developer):

If maintenance of distribution updates is not a "core role" for contribs.org, then what is?

Don't ask what contribs.org can do for me, ask what I can do for contribs.org.

-Nuno

[kruhm]

ngomes, stop posting this.

[ikeo]

Stupid question maybe but how is it supposed to work later on with updates.
I was qurious on how to get it to work so i tried to install yum and imidiately realized i should have installed python first  
after that small problem solved
I got it to work and did a yum update and realized that it checked in both folders the one for testing and the folder for release.
Is this the way it will be later on as well so you can somehowe choose if you want to install test and release updates?


//Ikeo

[wellsi]

Very soon the updates repository will be populated with verified updates and at that time the yum will change to only take packages from updates.

It is taking packages from updates-testing only in this initial testing stage.

Certainly I would not want the wider community to be automatically taking all packages from updates-testing in the future.

(you will be able to easily enable it if you wish)

[Black]

Dont fix it if it aint broken. I think Microsoft and their cronies have EVERYONE brainwashed into thinking  "you gotta have the latest updates"

fuck that.

[TheMonk]

Dont fix it if it aint broken. I think Microsoft and their cronies have EVERYONE brainwashed into thinking  "you gotta have the latest updates"

fuck that.

Isn't the question here how do I know or check if "it's broken"!?

-take that!