Bug 600358 - rpmbuild auto delete the packaged files in BUILDROOT.
Summary: rpmbuild auto delete the packaged files in BUILDROOT.
Alias: None
Product: Fedora
Classification: Fedora
Component: rpm
Version: 13
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Panu Matilainen
QA Contact: Fedora Extras Quality Assurance
Keywords: Upstream
Depends On:
TreeView+ depends on / blocked
Reported: 2010-06-04 14:44 UTC by ebird98
Modified: 2010-06-08 01:47 UTC (History)
4 users (show)

Clone Of:
Last Closed: 2010-06-07 06:16:57 UTC

Attachments (Terms of Use)

Description ebird98 2010-06-04 14:44:13 UTC
Description of problem:
There is no %clean/%build section in my .spec files.
but rpmbuild deleted my files in the BUILDROOT when I used "rpmbuild -bb".

Version-Release number of selected component (if applicable):
rpm.i686            4.8.0-14.fc13   @anaconda-InstallationRepo-201005130056.i386
rpm-build.i686      4.8.0-14.fc13   @anaconda-InstallationRepo-201005130056.i386
rpm-devel.i686      4.8.0-14.fc13   @anaconda-InstallationRepo-201005130056.i386
rpm-libs.i686       4.8.0-14.fc13   @anaconda-InstallationRepo-201005130056.i386
rpm-python.i686     4.8.0-14.fc13   @anaconda-InstallationRepo-201005130056.i386
rpmdevtools.noarch  7.8-1.fc13      @anaconda-InstallationRepo-201005130056.i386

Steps to Reproduce:
1.rpmbuild a binary RPM. (BIN files has build already, so use "-bb" switch)
Actual results:
All of the files packaged has been deleted.

Expected results:
Should not delete any files, when NO %clean/%build section in my .spec file.

Comment 1 Jeff Johnson 2010-06-05 12:50:39 UTC
Yes. BUILDROOT is now configured and managed as a build system
element, not a per-package option.

Running "rpmbuild -bi foo.spec" will build and install (but not remove)
the files in the buildroot.

Comment 2 Panu Matilainen 2010-06-07 06:16:57 UTC
This is indeed the intended behavior and not a bug.

Comment 3 ebird98 2010-06-08 01:47:29 UTC
Thanks,I got a way to KEEP the files.:)
So different between 4.8 and 4.6...

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