Description of problem: RPM build errors: File not found: /builddir/build/BUILDROOT/glusterfs-3.9dev-0.262.git203f952.el7.centos.x86_64/var/lib/glusterd/hooks/1/delete/post/S57glusterfind-delete-post.pyc File not found: /builddir/build/BUILDROOT/glusterfs-3.9dev-0.262.git203f952.el7.centos.x86_64/var/lib/glusterd/hooks/1/delete/post/S57glusterfind-delete-post.pyo
S57glusterfind-delete-post.py* is packaged in $LIBEXEC/glusterfs/glusterfind directory, symlink created to /var/lib/glusterd/hooks directory ln -s $(libexecdir)/glusterfs/glusterfind/S57glusterfind-delete-post.py \ $(DESTDIR)$(GLUSTERD_WORKDIR)/hooks/1/delete/post/S57glusterfind-delete-post.py ".py" should be removed from symlink target so that build system will not try to compile the symlink files and generate .pyc/.pyo files.
REVIEW: http://review.gluster.org/14928 (packaging: Remove ".py" extension from symlink target) posted (#1) for review on master by Aravinda VK (avishwan)
COMMIT: http://review.gluster.org/14928 committed in master by Jeff Darcy (jdarcy) ------ commit db4f4f1500372ee9f5a1c8faff5081d2a95652e3 Author: Aravinda VK <avishwan> Date: Fri Jul 15 13:15:21 2016 +0530 packaging: Remove ".py" extension from symlink target S57glusterfind-delete-post.py* is packaged in $LIBEXEC/glusterfs/glusterfind directory, symlink created to /var/lib/glusterd/hooks directory ln -s $(libexecdir)/glusterfs/glusterfind/S57glusterfind-delete-post.py \ $(DESTDIR)$(GLUSTERD_WORKDIR)/hooks/1/delete/post/S57glusterfind-delete-post.py ".py" should be removed from symlink target so that build system will not try to compile the symlink files and generate .pyc/.pyo files. BUG: 1356868 Change-Id: I9155378aa72eb8559ba8af76d91a4985f69f38f9 Signed-off-by: Aravinda VK <avishwan> Reviewed-on: http://review.gluster.org/14928 Smoke: Gluster Build System <jenkins.org> Reviewed-by: Kotresh HR <khiremat> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: Kaleb KEITHLEY <kkeithle>
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.9.0, please open a new bug report. glusterfs-3.9.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] http://lists.gluster.org/pipermail/gluster-users/2016-November/029281.html [2] https://www.gluster.org/pipermail/gluster-users/