Bug 1680585

Summary:	remove glupy from code and build
Product:	[Community] GlusterFS	Reporter:	Niels de Vos <ndevos>
Component:	build	Assignee:	bugs <bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6	CC:	amukherj, bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-6.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-03-12 10:10:00 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:	1642810
Bug Blocks:	1672818, 1732875

Description Niels de Vos 2019-02-25 11:15:37 UTC

This bug was initially created as a copy of Bug #1642810

I am copying this bug because: 

The glupy removal removed too much. With this bug we'll add the pieces that should not have been removed.

Comment 1 Worker Ant 2019-02-25 11:17:51 UTC

REVIEW: https://review.gluster.org/22259 (build: include gluster/__init__.* files for python packaging) posted (#2) for review on release-6 by Niels de Vos

Comment 2 Worker Ant 2019-02-25 15:26:13 UTC

REVIEW: https://review.gluster.org/22259 (build: include gluster/__init__.* files for python packaging) merged (#2) on release-6 by Niels de Vos

Comment 3 Atin Mukherjee 2019-03-12 05:11:23 UTC

Is there anything pending on this bug? I still see the bug is in POST state even though the above patch is merged (as the commit had 'updates' tag).

Comment 4 Niels de Vos 2019-03-12 08:52:59 UTC

(In reply to Atin Mukherjee from comment #3)
> Is there anything pending on this bug? I still see the bug is in POST state
> even though the above patch is merged (as the commit had 'updates' tag).

I think this was the only thing that needed an extra backport.

Comment 5 Shyamsundar 2019-03-25 16:33:20 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-6.0, please open a new bug report.

glusterfs-6.0 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] https://lists.gluster.org/pipermail/announce/2019-March/000120.html
[2] https://www.gluster.org/pipermail/gluster-users/