Red Hat Bugzilla – Bug 661770
can't be rebuild in mock
Last modified: 2013-07-18 11:49:59 EDT
build always fail in mock with this error: Executing(%doc): /bin/sh -e /var/tmp/rpm-tmp.th4OHJ + umask 022 + cd /builddir/build/BUILD + cd foomatic-4.0.4 + DOCDIR=/builddir/build/BUILDROOT/foomatic-4.0.4-1.el6.i386/usr/share/doc/foomatic-4.0.4 + export DOCDIR + rm -rf /builddir/build/BUILDROOT/foomatic-4.0.4-1.el6.i386/usr/share/doc/foomatic-4.0.4 + /bin/mkdir -p /builddir/build/BUILDROOT/foomatic-4.0.4-1.el6.i386/usr/share/doc/foomatic-4.0.4 + cp -pr --parents foomatic-filters-4.0.4/COPYING /builddir/build/BUILDROOT/foomatic-4.0.4-1.el6.i386/usr/share/doc/foomatic-4.0.4 + cp -pr --parents foomatic-db-engine-4.0.4/COPYING /builddir/build/BUILDROOT/foomatic-4.0.4-1.el6.i386/usr/share/doc/foomatic-4.0.4 + exit 0 RPM build errors: Macro % has illegal name (%define) Macro % has illegal name (%define) File not found: /builddir/build/BUILDROOT/foomatic-4.0.4-1.el6.i386/usr/share/perl5/Foomatic
This Fedora commit fixes the problem http://pkgs.fedoraproject.org/gitweb/?p=foomatic.git;a=commitdiff;h=bf5532c5b6aa767e5cc9a2e1502af6e1ab416182
can we wait an update for rhel-6 too?
We hope to fix this in a future update to Red Hat Enterprise Linux. Thank you for reporting it.
and the above patch is wrong for two reason: - installvendorlib and installvendorarch by default - INSTALLSITELIB=$RPM_BUILD_ROOT/%{installvendorlib} should have to be INSTALLSITELIB=%{perl_vendorlib} without $RPM_BUILD_ROOT
Created attachment 470016 [details] foomatic-perl.patch Thanks. Here is a new proposed patch based on your suggestion.
that's exactly what i did.
Deferring to RHEL 6.3 for possible inclusion. We are unable to accommodate this for RHEL 6.2.
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. If you would like it considered as an exception in the current release, please ask your support representative.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-1084.html