Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Trying to package up wget-1.13.tar.gz into a rpm (I am re-learning this process) and I'm running into these errors when I do a dry run.

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

There are more paths it complains about so this just a snippet but you should get the idea.

My Spec file is as follows:

Name:       wget
Version:    1.13    
Release:    1%{?dist}
Summary:    wget to get wget things

Group:      System Environment/Base
License:    GPL
Source0:    %{name}-%{version}.tar.gz
BuildRoot:  /tmp/%{name}-%{version}-%{release}-root 


Wget is a free software package for retrieving files using HTTP, HTTPS ... GNU   Wget        has many features to make retrieving large files

%setup -q

make %{?_smp_mflags}





So a basic spec file, where am I going wrong?

Also, the file structure my RPMS is $HOME/rpms/{BUILD,RPMS,SOURCES,SPECS,SRPMS}


share|improve this question

migrated from serverfault.com Aug 23 '12 at 16:43

This question came from our site for system and network administrators.

Now you need to populate %files so that the installed files are included in the resultant binary package.

share|improve this answer
The easiste way to create a RPM for a new version of something (wget is certainly available as RPM) is to grab the source RPM, unpack that and hack on the specfile. The SRPM usually contains patches to the pristine source, which you should consider for application to your package. – vonbrand Jan 23 '13 at 13:58

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.