Bug 582756

Summary:	Packages that require samba have a conflict when samba3x is installed
Product:	Red Hat Enterprise Linux 5	Reporter:	Justin Payne <jpayne>
Component:	samba3x	Assignee:	Guenther Deschner <gdeschner>
Status:	CLOSED ERRATA	QA Contact:	qe-baseos-daemons
Severity:	medium	Docs Contact:
Priority:	medium
Version:	5.5	CC:	azelinka, chekov, dpal, eliningt, rob.townley, shuff, ssorce, tao
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	samba3x-3.5.4-0.63.el5	Doc Type:	Bug Fix
Doc Text:	Packages requiring samba cannot recognize samba3x as an updated samba version. With this update, dependent packages recognize samba3x as the new samba version.	Story Points:	---
Clone Of:
Clones:	802546 (view as bug list)		Environment:
Last Closed:	2011-01-13 22:47:33 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	654252, 802546

Description Justin Payne 2010-04-15 18:18:44 UTC

Description of problem:
Packages that require samba will have a conflict if samba3x is installed. Since there is no "Provides: samba" in the samba3x spec file, packages that require samba will fail to install even though the newer version of samba (samba3x) is installed on the system.

Version-Release number of selected component (if applicable):

samba-3.3.8-0.51.el5

How reproducible:
Always

Steps to Reproduce:
1. Install samba3x on a 5.5 system
2. Attempt to install a package that requires samba, such as: http://packages.sw.be/smbldap-tools/
  
Actual results:
Install fails due to unresolvable dependency for samba.

Expected results:
Packages that require samba install without issue when samba3x is used on a system.

Additional info:

Comment 1 Justin Payne 2010-04-15 18:22:50 UTC

The samba3x spec file already has the following Provides:

Provides: samba-common = %{epoch}:%{samba_version}-%{release}

Packages needing samba-common will not have the reported issue. Can something similar be added for samba?

Comment 6 Alan 2010-09-09 23:15:32 UTC

this is true also of tdb-tools and nmbscan packages.
Bug 609578 seems to suggest people are thinking of adding the proper samba provides in RHEL 5.6 but this would be useful in 5.5.  smbldap-tools in particular is a necessity when running samba with an ldap backend...
-alan

Comment 8 Eva Kopalova 2010-12-15 08:11:49 UTC

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Packages requiring samba cannot recognize samba3x as an updated samba version. With this update, dependent packages recognize samba3x as the new samba version.

Comment 12 errata-xmlrpc 2011-01-13 22:47:33 UTC

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0054.html

Comment 13 Steve Huff 2011-06-01 21:13:38 UTC

Unfortunately, this issue is not completely resolved by RHBA-2011-0054.
The following packages still have potentially problematic metadata:

samba3x-client-3.5.4-0.70.el5_6.1
(this should provide 'samba-client = 0:3.5.4-0.70.el5_6.1')

samba3x-swat-3.5.4-0.70.el5_6.1
(this should provide 'samba-swat = 0:3.5.4-0.70.el5_6.1' and
'config(samba-swat) = 0:3.5.4-0.70.el5_6.1')

samba3x-3.5.4-0.70.el5_6.1
(this should provide 'config(samba) = 0:3.5.4-0.70.el5_6.1')

I have an open case with RH support that tracks this issue, and I have
reported this issue there as well.

-Steve