Bug 1430844 - build/packaging: Debian and Ubuntu don't have /usr/libexec/; results in bad packages
Summary: build/packaging: Debian and Ubuntu don't have /usr/libexec/; results in bad p...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: build
Version: 3.10
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kaleb KEITHLEY
QA Contact:
URL:
Whiteboard:
Depends On: 1430841
Blocks: glusterfs-3.10.1 1430845
TreeView+ depends on / blocked
 
Reported: 2017-03-09 17:12 UTC by Kaleb KEITHLEY
Modified: 2017-04-05 00:02 UTC (History)
1 user (show)

Fixed In Version: glusterfs-3.10.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1430841
: 1430845 (view as bug list)
Environment:
Last Closed: 2017-04-05 00:02:14 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Kaleb KEITHLEY 2017-03-09 17:12:08 UTC
+++ This bug was initially created as a clone of Bug #1430841 +++

Description of problem:

GLUSTERFS_LIBEXECDIR is effectively hard-coded to /usr/libexec/glusterfs in configure(.ac)

Debian-based distributions don't have a /usr/libexec/ directory

This issues is partially mitigated by the use of $libexecdir in some of the Makefile.am files, but even so the incorrectly defined GLUSTERFS_LIBEXECDIR results in various things such as gsyncd, glusterfind, eventsd, etc., trying to invoke other scripts and programs from a location that doesn't exist.

And once we correctly define GLUSTERFS_LIBEXECDIR, then we might as well use it appropriatedly.

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

all

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Worker Ant 2017-03-09 17:27:10 UTC
REVIEW: https://review.gluster.org/16881 (build/packaging: Debian and Ubuntu don't have /usr/libexec) posted (#1) for review on release-3.10 by Kaleb KEITHLEY (kkeithle)

Comment 2 Worker Ant 2017-03-09 20:10:36 UTC
REVIEW: https://review.gluster.org/16881 (build/packaging: Debian and Ubuntu don't have /usr/libexec) posted (#2) for review on release-3.10 by Kaleb KEITHLEY (kkeithle)

Comment 3 Worker Ant 2017-03-09 20:21:25 UTC
REVIEW: https://review.gluster.org/16881 (build/packaging: Debian and Ubuntu don't have /usr/libexec) posted (#3) for review on release-3.10 by Kaleb KEITHLEY (kkeithle)

Comment 4 Worker Ant 2017-03-13 14:19:03 UTC
COMMIT: https://review.gluster.org/16881 committed in release-3.10 by Shyamsundar Ranganathan (srangana) 
------
commit 18509e436f8a728ef522f3e76e2f2dc30e1bd8ac
Author: Kaleb S. KEITHLEY <kkeithle>
Date:   Thu Mar 9 12:24:30 2017 -0500

    build/packaging: Debian and Ubuntu don't have /usr/libexec
    
    GLUSTERFS_LIBEXECDIR is effectively hard-coded to /usr/libexec/glusterfs
    in configure(.ac)
    
    Debian-based distributions don't have a /usr/libexec/ directory
    
    This issues is partially mitigated by the use of $libexecdir in
    some of the Makefile.am files, but even so the incorrectly defined
    GLUSTERFS_LIBEXECDIR results in various things such as gsyncd,
    glusterfind, eventsd, etc., trying to invoke other scripts and
    programs from a location that doesn't exist.
    
    And once we correctly define GLUSTERFS_LIBEXECDIR, then we might as
    well use it appropriatedly.
    
    master change https://review.gluster.org/16880
    master BZ: 1430841
    
    Change-Id: If5219cadc51ae316f7ba2e2831d739235c77902d
    BUG: 1430844
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle>
    Reviewed-on: https://review.gluster.org/16881
    Smoke: Gluster Build System <jenkins.org>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>
    Reviewed-by: Milind Changire <mchangir>
    Reviewed-by: Shyamsundar Ranganathan <srangana>

Comment 5 Shyamsundar 2017-04-05 00:02:14 UTC
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.10.1, please open a new bug report.

glusterfs-3.10.1 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://lists.gluster.org/pipermail/gluster-users/2017-April/030494.html
[2] https://www.gluster.org/pipermail/gluster-users/


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