Bug 1320390 - build: spec file conflict resolution
Summary: build: spec file conflict resolution
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: build
Version: rhgs-3.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: RHGS 3.1.3
Assignee: Milind Changire
QA Contact: Rahul Hinduja
URL:
Whiteboard:
Depends On:
Blocks: 1311817
TreeView+ depends on / blocked
 
Reported: 2016-03-23 06:03 UTC by Milind Changire
Modified: 2016-06-23 05:13 UTC (History)
5 users (show)

Fixed In Version: glusterfs-3.7.9-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-23 05:13:49 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1240 0 normal SHIPPED_LIVE Red Hat Gluster Storage 3.1 Update 3 2016-06-23 08:51:28 UTC

Description Milind Changire 2016-03-23 06:03:21 UTC 
Missed conflict resolution for removing references to
    gluster.conf.example as mentioned in patch titled:
    packaging: gratuitous dependencies on rsyslog-mm{count,jsonparse}
    by Kaleb
    
    References to hook scripts S31ganesha-start.sh and
    S31ganesha-reset.sh got lost in the downstream only
    patch conflict resolution.
    
    Commented blanket reference to %{_sharedsstatedir}/glusterd/*
    in section %files server to avoid rpmbuild warning related to
    multiple references to hook scripts and other files under
    /var/lib/glusterd.
Comment 2 Rahul Hinduja 2016-04-05 10:49:36 UTC 
Received build: glusterfs-3.7.9-1 Moving the bug to verified state.
Comment 4 errata-xmlrpc 2016-06-23 05:13:49 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2016:1240
Note You need to log in before you can comment on or make changes to this bug.