Topic: the yum update failed with Error: samba3x

[mgb]

new sme 8
http://wiki.contribs.org/SME_Server_8#Considerations_before_installing
is ok
Step
rpm -q smeserver-yum
smeserver-yum-2.2.0-20.el5.sme

Step
is stop
rpm -q samba samba3x
package samba is not installed
samba3x-3.5.10-0.110.el5_8

rpm -e --nodeps libtalloc libtdb samba samba-client samba-common samba-winbind
error: package samba is not installed
error: package samba-client is not installed
error: package samba-common is not installed
error: package samba-winbind is not installed


yum update
Setting up Update Process
Resolving Dependencies
--> Running transaction check
---> Package bind-libs.i386 30:9.3.6-20.P1.el5_8.6 set to be updated
help to fix

[janet]

mgb

The samba notes in the link you provide, refer ONLY to earlier beta releases of sme8, in particular going from sme8beta5 to sme8beta6.
It very clearly says that in the wiki.

You should NOT be applying those to sme8.0 final.

[mgb]

 mary
Thanks for the quick response
sme8beta6. I installed

[janet]

mgb

sme8beta6. I installed

In your first post you said
"new sme 8", so I assumed sme 8.0 final

You should ONLY use the sme 8.0 final iso, DO NOT use beta releases once there is a final release.

Download the latest iso from here, see http://mirror.contribs.org/mirrors/

[mgb]

 Thank you
I can make an update of the existing installation
From SME eight new?
Tenth

[janet]

mgb

AIUI upgrades from beta releases to final versions are not supported (and never were), but do in most cases work OK.
Again AIUI the recommended upgrade path from beta releases to final releases is:
Backup (to USB) the beta version & verify your backup is good ie backup sme8beta6 using one of the default built in backup methods.
Then install sme 8.0 final from CD, overwriting & replacing any existing installation that may be on the same server equipment (ie do not select upgrade but select new install), then restore from the USB backup. You will need to reinstall all contribs, but contrib data & custom changes made via custom templates will be restored.

So, the correct order is:
Backup
Install new OS (final version)
Restore
Install contribs

[purvis]

FWIW

I installed a new server with the lastest download iso of sme 8.
The yum update problem occurs with samba3 or whatever the problem is also.
From my experiences, it is the updates from Cento OS.
IF you remove the Cento OS from the update list in the server-manager panel under install updates, there is not issue.
 

[Stefano]

@all: there's another topic open for the same issue

see

http://forums.contribs.org/index.php/topic,49456.0/topicseen.html

and follow up there
thank you

[mgb]

Thank you mary Stefano


I did not see
http://forums.contribs.org/index.php/topic,49456.0/topicseen.html
is ok  is work sme 8

 @http://wiki.contribs.org/SME_Server_8#Considerations_before_installing  It is confusing
 

[purvis]

I can never understand why anybody would upgrade a major os version change.
A new install is always the way to go.  Specially on a server.  I would not give one second of time devoted to upgrading major oases. It is all a waste of time.

Now running older software from the previous os on a new install is different.

This is where a lot of the confusion comes from in my opinion.

Bc sme  8 beta 6 was out for so long. I can understand a path upgrading from that to be acceptable.

[janet]

Dear All

For sme 8.0 final users, yum update samba errors associated with recent package releases has been fixed.
A normal
yum update
should work OK now & pull in a lot of updated packages.

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

[purvis]

On my last three servers to update last night that happened after the last post on this thread. All went well from the server-panel's Software installer menu.
I make the changes to not allow any CentOs updates, meaning I excluded two sources(repositories).
All went well on those 3 servers.

Who every jump on the fix. I want to thank them for their time

[janet]

purvis

I make the changes to not allow any CentOs updates, meaning I excluded two sources(repositories).

You should not have to disable any repos if you are using yum correctly, and if you had waited for the fix to be released.

You should ONLY have the standard repositories enabled, as per smeserver recommendations here
http://wiki.contribs.org/SME_Server:Documentation:FAQ#Which_repositories_should_be_enabled
which shows
CentOS - os
CentOS - updates
SME Server - addons
SME Server - extras
SME Server - os
SME Server - updates

Your advice to disable CentOS repos SHOULD NOT be followed by other users.
If you have any of the standard repos disabled, then you will not receive correct updates next time they are released.

You can see the names & enabled/disabled status of all repos you have configured on your server using this command
/sbin/e-smith/audittools/repositories

Here are the correct repos to have enabled, all others should be disabled by default.

base: enabled
updates: enabled
smeaddons: enabled
smeextras: enabled
smeos: enabled
smeupdates: enabled


To avoid possible confusion between differing names that are used, here are the equivalent names for the command line listing, & the FAQ/server manager entries

base = CentOS - os
updates = CentOS - updates
smeaddons = SME Server - addons
smeextras = SME Server - extras
smeos = SME Server - os
smeupdates = SME Server - updates


Note that other repos can & should only be used by invoking a command line switch ie
yum update --enablerepo=reponame

By disabling the CentOS repos, you implemented a workaround for the "temporary" yum update problem.
If you had waited the fix would have been released & no workaround would have been needed.

You (& anybody else) who disabled the CentOS repos should re-enable them immediately, so that future updates work correctly.

[purvis]

Mary
I should have said that Imade the change to  include those two centos repositories of centos after the yum update.

I was wondering whether to include or exclude centos updates on a permanent bases.
Your last post to include them settled that.