[Bugs] [Bug 1701337] New: issues with 'building' glusterfs packages if we do 'git clone --depth 1'

bugzilla at redhat.com bugzilla at redhat.com
Thu Apr 18 16:56:39 UTC 2019


            Bug ID: 1701337
           Summary: issues with 'building' glusterfs packages if we do
                    'git clone --depth 1'
           Product: GlusterFS
           Version: mainline
            Status: ASSIGNED
         Component: build
          Severity: urgent
          Priority: urgent
          Assignee: bugs at gluster.org
          Reporter: atumball at redhat.com
                CC: bugs at gluster.org
  Target Milestone: ---
    Classification: Community

Description of problem:
Right now, a full clone of glusterfs repo needs 148MB of size, but a clone with
'--depth 1' option needs just 4MB. It makes sense to use this option in many of
the smoke tests and CI/CD environments, so that we save time, bandwidth, and

But, right now, we can't 'build' any RPMs with this option.

Version-Release number of selected component (if applicable):
mainline (april-18th-2019)

How reproducible:

Steps to Reproduce:
1. git clone --depth 1 https://github.com/gluster/glusterfs.git
2. cd glusterfs-depth-1; ./autogen.sh && ./configure && make -C
extras/LinuxRPM/ glusterrpms
3. You see the error like below
rpmbuild --define '_topdir
-bs rpmbuild/SPECS/glusterfs.spec
error: line 231: Empty tag: Version:
make: *** [Makefile:573: srcrpm] Error 1


Expected results:
build should pass.

Additional info:
The issue is with executing ./build-aux/pkg-version script.

[atumball at localhost glusterfs-depth-1]$ ./build-aux/pkg-version --full
fatal: No names found, cannot describe anything.

[atumball at localhost glusterfs-depth-1]$ ./build-aux/pkg-version --version
<No output>

You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.

More information about the Bugs mailing list