Bug 1141683 - The extras/MacOSX directory is no longer needed, and should be removed
Summary: The extras/MacOSX directory is no longer needed, and should be removed
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: build
Version: 3.6.0
Hardware: Unspecified
OS: Mac OS
medium
medium
Target Milestone: ---
Assignee: Justin Clift
QA Contact:
URL:
Whiteboard:
Depends On: 1141682
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-15 08:48 UTC by Justin Clift
Modified: 2015-07-13 04:35 UTC (History)
3 users (show)

Fixed In Version: glusterfs-3.6.0beta1
Clone Of: 1141682
Environment:
Last Closed: 2014-11-11 08:38:49 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Justin Clift 2014-09-15 08:48:34 UTC
+++ This bug was initially created as a clone of Bug #1141682 +++

Description of problem:

  The extras/MacOSX directory in upstream git source is from GlusterFS 2.x era,
  and is of no use with modern GlusterFS.  It should be removed.


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

  Upstream GlusterFS git master, as of Mon 15th September 2014.

Comment 1 Anand Avati 2014-09-15 08:58:09 UTC
REVIEW: http://review.gluster.org/8737 (osx: Remove legacy extras/MacOSX directory) posted (#1) for review on release-3.6 by Justin Clift (justin)

Comment 2 Anand Avati 2014-09-18 19:00:22 UTC
COMMIT: http://review.gluster.org/8737 committed in release-3.6 by Vijay Bellur (vbellur) 
------
commit acd7ebf257453f46be42c8592e2fd784c676a114
Author: Justin Clift <justin>
Date:   Mon Sep 15 09:48:05 2014 +0100

    osx: Remove legacy extras/MacOSX directory
    
    Backport of http://review.gluster.org/8736
    
    BUG: 1141683
    Change-Id: Ic37df769db856196727d2799396c1dbaf4bcdd1a
    Signed-off-by: Justin Clift <justin>
    Reviewed-on: http://review.gluster.org/8737
    Reviewed-by: Humble Devassy Chirammal <humble.devassy>
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Niels de Vos <ndevos>
    Reviewed-by: Vijay Bellur <vbellur>

Comment 3 Niels de Vos 2014-09-22 12:46:10 UTC
A beta release for GlusterFS 3.6.0 has been released. Please verify if the release solves this bug report for you. In case the glusterfs-3.6.0beta1 release does not have a resolution for this issue, leave a comment in this bug and move the status to ASSIGNED. If this release fixes the problem for you, leave a note and change the status to VERIFIED.

Packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update (possibly an "updates-testing" repository) infrastructure for your distribution.

[1] http://supercolony.gluster.org/pipermail/gluster-users/2014-September/018836.html
[2] http://supercolony.gluster.org/pipermail/gluster-users/

Comment 4 Niels de Vos 2014-11-11 08:38:49 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.6.1, please reopen this bug report.

glusterfs-3.6.1 has been announced [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://supercolony.gluster.org/pipermail/gluster-users/2014-November/019410.html
[2] http://supercolony.gluster.org/mailman/listinfo/gluster-users


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