Description of problem: rpm build failing with following error Processing files: glusterfs-server-3.7dev-0.737.git0638857.el6.x86_64 error: File must begin with "/": install error: File must begin with "/": -p error: File must begin with "/": -m error: File must begin with "/": 0744 error: File must begin with "/": extras/snap_scheduler/snap_scheduler.py error: File must begin with "/": install error: File must begin with "/": -p error: File must begin with "/": -m error: File must begin with "/": 0744 error: File must begin with "/": extras/snap_scheduler/gcron.py Executing(%doc): /bin/sh -e /var/tmp/rpm-tmp.zRaV8O Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
REVIEW: http://review.gluster.org/9939 (gluster: rpm build failure for snap scheduler install) posted (#1) for review on master by Rajesh Joseph (rjoseph)
REVIEW: http://review.gluster.org/9939 (gluster: rpm build failure for snap scheduler install) posted (#2) for review on master by Rajesh Joseph (rjoseph)
REVIEW: http://review.gluster.org/9939 (build: correctly install the snap_scheduler tools) posted (#3) for review on master by Niels de Vos (ndevos)
COMMIT: http://review.gluster.org/9939 committed in master by Vijay Bellur (vbellur) ------ commit 61489c1725f048c2e34a08e73f0ab367bbf673c1 Author: Niels de Vos <ndevos> Date: Thu Mar 19 13:12:02 2015 +0100 build: correctly install the snap_scheduler tools The current way of installing the snap-scheduler tools breaks the building of RPMs. The tools should be installed in /usr/sbin and there is no need to change the attributes/permissions after the installation. Change-Id: I1b8e206748617fb000d956b1b5da52d126971c29 BUG: 1203557 Signed-off-by: Niels de Vos <ndevos> Reviewed-on: http://review.gluster.org/9939 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Vijay Bellur <vbellur>
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.7.0, please open a new bug report. glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user