Bug 514830 - rpmbuild fails for private kernel build: missing generated files
Summary: rpmbuild fails for private kernel build: missing generated files
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 11
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 514407 515830 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-07-30 23:04 UTC by John Reiser
Modified: 2009-08-13 14:56 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-08-06 05:43:33 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description John Reiser 2009-07-30 23:04:39 UTC
Description of problem: rpmbuild fails to build the kernel.  brp-java-repack-jars complains about missing files that would have been generated (at least by a complete build such as -bb), and the same files are listed as missing in the "RPM build errors:" summary.  Indeed, the files are not there, even for a "-bb" build.


Version-Release number of selected component (if applicable):
kernel-2.6.29.6-213.fc11.x86_64


How reproducible: always


Steps to Reproduce:
1. rpm --install kernel-2.6.29.6-213.fc11.src.rpm
2. edit SPECS/kernel.spec for private build: "%define buildid .jfr"
3. rpmbuild -bp --with baseonly --target x86_64 kernel.spec
  (and also "rpmbuild -bb ..." with the same trailing parameters)
  
Actual results:
  [[snip]]
+ /usr/lib/rpm/find-debuginfo.sh --strict-build-id -p '/.*/2.6.29.6-213.jfr.fc11.x86_64/.*|/.*2.6.29.6-213.jfr.fc11.x86_64(.debug)?' -o debuginfo.list -p '/.*/2.6.29.6-213.jfr.fc11.x86_64.smp/.*|/.*2.6.29.6-213.jfr.fc11.x86_64.smp(.debug)?' -o debuginfosmp.list -p '/.*/2.6.29.6-213.jfr.fc11.x86_64.PAE/.*|/.*2.6.29.6-213.jfr.fc11.x86_64.PAE(.debug)?' -o debuginfoPAE.list -p '/.*/2.6.29.6-213.jfr.fc11.x86_64.PAEdebug/.*|/.*2.6.29.6-213.jfr.fc11.x86_64.PAEdebug(.debug)?' -o debuginfoPAEdebug.list -p '/.*/2.6.29.6-213.jfr.fc11.x86_64.debug/.*|/.*2.6.29.6-213.jfr.fc11.x86_64.debug(.debug)?' -o debuginfodebug.list -p '/.*/2.6.29.6-213.jfr.fc11.x86_64.kdump/.*|/.*2.6.29.6-213.jfr.fc11.x86_64.kdump(.debug)?' -o debuginfokdump.list /home2/jreiser-home2/rpmbuild/BUILD/kernel-2.6.29
find: `usr/lib/debug': No such file or directory
+ /usr/lib/rpm/check-buildroot
  [[snip]]
+ /usr/lib/rpm/redhat/brp-java-repack-jars
Processing files: kernel-2.6.29.6-213.jfr.fc11.x86_64
error: File not found: /home2/jreiser-home2/rpmbuild/BUILDROOT/kernel-2.6.29.6-213.jfr.fc11.x86_64/boot/vmlinuz-2.6.29.6-213.jfr.fc11.x86_64
  [[snip]]
RPM build errors:
    File not found: /home2/jreiser-home2/rpmbuild/BUILDROOT/kernel-2.6.29.6-213.jfr.fc11.x86_64/boot/vmlinuz-2.6.29.6-213.jfr.fc11.x86_64
  [[snip]]

Expected results: successful build.


Additional info: rpm-build-4.7.0-2.fc11.x86_64.
rpmbuild succeeds for a private build of the previous kernel-2.6.29.5-191.fc11.

Comment 1 Chuck Ebbert 2009-08-04 01:14:12 UTC
(In reply to comment #1)
> Additional info: rpm-build-4.7.0-2.fc11.x86_64.
> rpmbuild succeeds for a private build of the previous kernel-2.6.29.5-191.fc11.  

Succeeds now or succeeded in the past?

I think this was caused by an update of redhat-rpm-config and fixed in kernel -215

Comment 2 John Reiser 2009-08-04 02:07:55 UTC
My build of kernel-2.6.29.5-191.fc11 succeeded using then-current tools.  I will try -215 when it appears (problably next morning), after "yum update".

Comment 3 John Reiser 2009-08-04 15:40:09 UTC
Successful build this morning using:
kernel-2.6.29.6-217.2.3.fc11.src.rpm
rpm-4.7.1-1.fc11.i586
rpm-build-4.7.1-1.fc11.i586
redhat-rpm-config-9.0.3-10.fc11.noarch

Comment 4 Chuck Ebbert 2009-08-06 05:40:33 UTC
*** Bug 515830 has been marked as a duplicate of this bug. ***

Comment 5 Chuck Ebbert 2009-08-06 05:43:33 UTC
For the record, this line was added at the top of the specfile:

%global __spec_install_pre %{___build_pre}

Comment 6 Chuck Ebbert 2009-08-13 14:56:40 UTC
*** Bug 514407 has been marked as a duplicate of this bug. ***


Note You need to log in before you can comment on or make changes to this bug.