Bug 150756

Summary:	problematic version numbers for samba update
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Johannes Meixner <jsmeix>
Component:	Other	Assignee:	Guenther Deschner <gd>
Status:	RESOLVED FIXED	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	ihudak, samba-maintainers, suse-beta
Version:	Final
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Found By:	Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Johannes Meixner 2006-02-14 11:24:32 UTC

In bug #150746 Ivan Hudak <ihudak@usoftinc.com> reported:
---------------------------------------------------------------------
YOU wants to update samba 3.0.20-4 to 3.0.20b.3.1
When the update is complete samba server doesn't 
work (the clients cannot connect)
3.0.20-4 is newer but string "3.0.20b.3.1" is 
greater then "3.0.20-4" (because of letter 'b')
so YOU wants to downgrade samba
---------------------------------------------------------------------
I didn't reproduce it.
I verified only the following:
On Suse Linux 10.0 CDs there is samba version 3.0.20-4, see
/mounts/schnell/CD-ARCHIVE/10.0/SUSE-10.0-DVD-RC4/INDEX.gz
Because of bug #106335 there is a YOU update to version 3.0.20b-3.2, see
http://www.novell.com/linux/download/updates/100_i386.html

Comment 1 Guenther Deschner 2006-02-14 11:34:29 UTC

I'm sure Lars has some good ideas about this (IIRC he has already discussed this topic with the Samba release manager).

Lars, what can we do here?

Comment 2 Lars Müller 2006-02-17 22:07:49 UTC

3.0.20b-3.1 > 3.0.20-4 therefore the versioning of Samba.org is no problem.

Ivan: You intended to downgrade your 3.0.20b-3.1 to 3.0.20-4?

a) rpm --Uvh --oldpackage
b) YaST software installation -> select replace for the samba packages.

And please attach the log of the non starting 3.0.20b Samba daemons.  You find them in /var/log/samba/

Comment 3 Ivan Hudak 2006-02-22 09:52:11 UTC

Upgraded Samba to 3.0.20b-3.1 and it works well now.
Few days before I have updated the Linux Kernel. Maybe this is the reason.
But anyway, the problem is resolved and I believe it can be closed.
Thanks