≡ Menu

rpmbuild: error: Installed (but unpackaged) file(s) found Solution

I‘m trying to build a RHEL 6 rpm of nginx server. But, I get the following error:

+ /usr/lib/rpm/brp-strip-comment-note
Checking for unpackaged file(s): /usr/lib/rpm/check-files /root/rpmbuild/BUILDROOT/nginx-1.0.5-1.el6.x86_64
error: Installed (but unpackaged) file(s) found:


RPM build errors:
Installed (but unpackaged) file(s) found:


How do I fix this problem and build rpm file?

To fix this error you need to specify the list of files that will be installed. This is done usong “%files” section. The syntax is as follows:


The above files can be set as follows in your .spec file (add before %changelog):

%config(noreplace) /usr/local/nginx/conf/*

The %files section identifies what files and directories were added by the package. Save and close the file. Now, you can rebuild an rpm as follows:
$ rpmbuild --bb nginx.spec

Recommend readings:

Share this tutorial on:

Like this? Follow us on Twitter OR support us by using Patreon

{ 6 comments… add one }
  • Jerry McBride August 23, 2011, 4:21 pm

    You have to tell rpm to include your config files. A great place to beging learning this is at:http://www.ibm.com/developerworks/library/l-rpm1/

  • Stefan Lasiewski September 21, 2011, 12:09 am

    I got this error for a different reason. I defined my BuildRoot as %{_topdir}/%{name}-%{version}-root . rpmbuild had left some files in my BuildRoot , and didn’t remove them. I had to remove these files manually.

    Several people on IBM Developerworks had the same problem. See http://www.ibm.com/developerworks/linux/library/l-rpm1/index.html#icomments. The solution proposed by bluebloodpole worked for me, but so did a simple `rm`.

    In fact, the instructions in that article didn’t work for me without some modifications.

  • Adam October 10, 2011, 2:46 am

    nginx.org has binary rpms on their website with the basic modules installed. If you want extra modules just add them in the src rpm spec file and rebuild it.


  • sysadmin March 16, 2012, 11:54 am

    A had the same issue as Stefan Lasiewski. Simply cleaning the buildroot dir solves the problem (of course, steps described in the article should be done too).

  • gyre007 May 21, 2012, 4:23 pm

    If you don’t need those files/directories then just add %exclude macros with the paths and you are sorted – no need to delete from within spec file as when the RPM is built the buld and buildroot are deleted anyway …

  • Ramesh January 9, 2015, 10:09 am

    Nice artical…!!!

Security: Are you a robot or human?

Leave a Comment

You can use these HTML tags and attributes: <strong> <em> <pre> <code> <a href="" title="">

   Tagged with: , , , , , , , , ,