[Bugs] [Bug 1169004] New: RPM building of glusterfs-3.6.1-3.fc22 src RPM on el5 is failing

bugzilla at redhat.com bugzilla at redhat.com
Fri Nov 28 19:55:14 UTC 2014


https://bugzilla.redhat.com/show_bug.cgi?id=1169004

            Bug ID: 1169004
           Summary: RPM building of glusterfs-3.6.1-3.fc22 src RPM on el5
                    is failing
           Product: GlusterFS
           Version: 3.6.1
         Component: build
          Severity: high
          Assignee: bugs at gluster.org
          Reporter: lmohanty at redhat.com
                CC: bugs at gluster.org, gluster-bugs at redhat.com



Description of problem:
Rebuilding glusterfs-3.6.1-3.fc22.src.rpm for el5 is failing with below error.

Installed (but unpackaged) file(s) found:
   /usr/share/glusterfs/scripts/generate-gfid-file.sh
   /usr/share/glusterfs/scripts/get-gfid.sh
   /usr/share/glusterfs/scripts/gsync-sync-gfid
   /usr/share/glusterfs/scripts/gsync-upgrade.sh
   /usr/share/glusterfs/scripts/slave-upgrade.sh
Child return code was: 1
EXCEPTION: Command failed. See logs for output.
 # ['bash', '--login', '-c', 'rpmbuild -bb --target ppc --nodeps 
builddir/build/SPECS/glusterfs.spec']
Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/mockbuild/trace_decorator.py", line
70, in trace
    result = func(*args, **kw)
  File "/usr/lib/python2.6/site-packages/mockbuild/util.py", line 378, in do
    raise mockbuild.exception.Error, ("Command failed. See logs for output.\n #
%s" % (command,), child.returncode)
Error: Command failed. See logs for output.
 # ['bash', '--login', '-c', 'rpmbuild -bb --target ppc --nodeps 
builddir/build/SPECS/glusterfs.spec']
LEAVE do --> EXCEPTION RAISED


glusterfs-3.6.1-3.fc22.src.rpm  can be found below

http://koji.fedoraproject.org/koji/buildinfo?buildID=594572

Version-Release number of selected component (if applicable):
3.6.1-3.fc22.

How reproducible:
Always

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

-- 
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