Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 609578 - Version the conflicts against samba-X
Version the conflicts against samba-X
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: samba3x (Show other bugs)
5.5
All Linux
low Severity medium
: rc
: ---
Assigned To: Guenther Deschner
qe-baseos-daemons
:
Depends On:
Blocks: 654252
  Show dependency treegraph
 
Reported: 2010-06-30 12:15 EDT by Enrico Scholz
Modified: 2011-01-13 17:48 EST (History)
3 users (show)

See Also:
Fixed In Version: samba3x-3.5.4-0.63.el5
Doc Type: Bug Fix
Doc Text:
Previously, the samba3x package considered any samba package a conflicting package. With this update, samba3x checks for possible non-conflicting versions of the samba package.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2011-01-13 17:48:09 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:0054 normal SHIPPED_LIVE samba3x bug fix and enhancement update 2011-01-12 12:15:21 EST

  None (edit)
Description Enrico Scholz 2010-06-30 12:15:32 EDT
Description of problem:

Please make the conflicts against the samba-X package versioned; e.g. write

| Conflicts: samba < 3.3

instead of plain

| Conflicts: samba


I understand that 'samba3x' can not provide 'samba' due to unclear/unwanted packages upgrade effects. But the change above makes it possible to provide local adapter packages which satisfy 'samba' requirements by providing 'samba = 3.3' and requiring 'samba3x'.


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


How reproducible:

samba3x-3.3.8-0.52.el5_5.x86_64.rpm
Comment 1 Guenther Deschner 2010-06-30 13:30:44 EDT
Sorry, it is not quite clear to me what you want to achieve. Do you just want to be able to satisfy the requires: samba while using samba3x ?
Comment 3 Enrico Scholz 2010-06-30 16:33:14 EDT
yes

because there are probably reasons that samba3x does not have samba provides I want to solve this with a local helper package which has

| Requires:       samba3x > 3.3
| Provides:       samba = 3.3



But this does not work due to the unversioned 'Conflicts: samba' in samba3x.

(ditto for -client)
Comment 4 Dmitri Pal 2010-06-30 18:43:14 EDT
Can we mark this as a dup of https://bugzilla.redhat.com/show_bug.cgi?id=582756 then?

We plan to try to resolve it for 5.6.
Comment 5 Enrico Scholz 2010-07-01 01:56:39 EDT
The "Provides: samba" suggested by 582756 are an issue which should not be done in 5.5.

But I would like to use samba3x in 5.5 and the versioned conflicts do not have sideeffects so they can be applied in 5.5.
Comment 6 Jeremy West 2010-07-01 23:44:41 EDT
Enrico,

Please note that although Red Hat welcomes bug reports and feedback in our public bugzilla database, we request that you contact technical support for help/assistance on obtaining officially supported packages.  

Thanks
Red Hat GSS Supervisor
Comment 11 Eva Kopalova 2010-12-15 03:41:10 EST
    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:
Previously, the samba3x package considered any samba package a conflicting package. With this update, samba3x checks for possible non-conflicting versions of the samba package.
Comment 13 errata-xmlrpc 2011-01-13 17:48:09 EST
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

Note You need to log in before you can comment on or make changes to this bug.