[Bugs] [Bug 1680587] New: Building RPM packages with _for_fedora_koji_builds enabled fails on el6

bugzilla at redhat.com bugzilla at redhat.com
Mon Feb 25 11:32:13 UTC 2019


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

            Bug ID: 1680587
           Summary: Building RPM packages with _for_fedora_koji_builds
                    enabled fails on el6
           Product: GlusterFS
           Version: mainline
            Status: ASSIGNED
         Component: build
          Assignee: ndevos at redhat.com
          Reporter: ndevos at redhat.com
                CC: bugs at gluster.org
            Blocks: 1680586
  Target Milestone: ---
    Classification: Community



+++ This bug was initially created as a clone of Bug #1680586 +++

Description of problem:
Building RPM packages with _for_fedora_koji_builds enabled fails on el6. A mock
rebuild fails with these errors:

Checking for unpackaged file(s): /usr/lib/rpm/check-files
/builddir/build/BUILDROOT/glusterfs-6.0-0.1.rc0.el6.x86_64
BUILDSTDERR: error: Installed (but unpackaged) file(s) found:
BUILDSTDERR:    /etc/init.d/glusterfsd
BUILDSTDERR:    /etc/sysconfig/glusterd
BUILDSTDERR:    /etc/sysconfig/glusterfsd
BUILDSTDERR:     Installed (but unpackaged) file(s) found:
BUILDSTDERR:    /etc/init.d/glusterfsd
BUILDSTDERR:    /etc/sysconfig/glusterd
BUILDSTDERR:    /etc/sysconfig/glusterfsd


Version-Release number of selected component (if applicable):
glusterfs-6.0 RC0

How reproducible:
100%

Steps to Reproduce:
1. set _for_fedora_koji_builds to 1 in the glusterfs.spec.in
2. build RPMs against/on el6

Actual results:
Building RPMs fails

Expected results:
Building RPMs should succeed.

Additional info:
It seems that glusterfs-6 disables building the server (./configure
--without-server) and hence the installed but unpackaged files should not get
installed in the first place.


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1680586
[Bug 1680586] Building RPM packages with _for_fedora_koji_builds enabled fails
on el6
-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the Bugs mailing list