Bug 150746

Summary:	java-1_4_2-sun* package conflicts after YOU update
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Ivan Hudak <ihudak>
Component:	Java	Assignee:	Daniel Bornkessel <dbornkessel>
Status:	RESOLVED DUPLICATE	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None
Version:	unspecified
Target Milestone:	---
Hardware:	x86-64
OS:	SuSE Linux 10.0
Whiteboard:
Found By:	Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Ivan Hudak 2006-02-14 10:59:37 UTC

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
2. YOU wants to update java-1_4_2-sun* pachages 
from version 1.4.2.06-5 to 1.4.2.10-2.1 (but does not update java-1_4_2-sun-src package).
After update I run YaST2->SoftWareManagement is see that 
the packages java-1_4_2-sun* conflict with each 
others, tomcat5 and struts-webapps-tomcat packages 
and YaST recommends to downgrade back to 1.4.2.06-
5. The possible reason: the -src package of Java has 
no update on server and it's version remains 1.4.
2.06-5

Comment 1 Stefan Hundhammer 2006-02-14 11:03:14 UTC

That version numbering looks pretty broken by design to me.

Comment 2 Johannes Meixner 2006-02-14 11:28:32 UTC

I split the samba part as seperated bug 150756, see
http://en.opensuse.org/Submitting_Bug_Reports
------------------------------------------------------------
When reporting a bug, please use one report for each defect
you want to report. Using a single bug report to address
several problems at once is really not a good idea because
it makes the handling very unhandy.
------------------------------------------------------------

I changed the subject/summary accordingly from
"Samba update and Java update"
to
"java-1_4_2-sun* package conflicts after YOU update"

Comment 3 Marcus Meissner 2006-02-15 10:21:56 UTC


*** This bug has been marked as a duplicate of 146501 ***