Error building RPM: Installed (but unpackaged) file(s) found

[dgurram]

Hi,

I have Fedora Core 3 with 2.6.10-1.741_FC3 kernel. My RPM version is 4.3.2. I am trying to install a couple of programs using RPM from the tarball. These programs are:
* log4cpp - http://log4cpp.sourceforge.net/
* Xerces C++ - http://xml.apache.org/xerces-c/build-misc.html#RPMLinux

However, doing rpmbuild -ta <tarball> in both cases results in a Installed (but unpackaged) file(s) found error.

I have looked at this thread: http://www.fedoraforum.org/forum/showthread.php?t=28691, but what is suggested there does not seem to work (if I have interpreted it correctly). I tried it with the log4cpp since I could locate the spec file for it in the tar ball (whereas for xerces I could not). I am working on the assumption that it is this spec file that RPM uses to build, but please correct me if you think otherwise. The "unpackaged" file that it was complaining about is /usr/share/aclocal/log4cpp.m4.

Here is an excerpt from the original (i.e unmodified) spec file:

%files
%defattr(-,root,root,755)
%attr(755,root,root) %prefix/lib/lib*.so.*
%doc AUTHORS COPYING INSTALL NEWS README THANKS ChangeLog

%files devel
%defattr(-,root,root,755)
%prefix/include/*
%prefix/man/*
%attr(755,root,root) %prefix/bin/log4cpp-config
%attr(755,root,root) %prefix/lib/lib*.so
%attr(644,root,root) %prefix/lib/*.*a

%files doc
%doc %prefix/doc/*

According to the solution suggested in the other thread I referred to above, adding the missing file to the %files section should solve the problem, so I added the following line to both the %files and %files devel sections:
%attr(644,root,root) %{_datadir}/aclocal/log4cpp.m4
(Apparently the /usr/share dir maps to the %{_datadir} RPM macro).

I then repacked the modified spec file into the tar ball and tried rpmbuild -ta again but unfortnately, same error. Can anyone see what I am doing wrong? I am quite a noob so some accompanying explanations with any ideas would be hugely appreciated!

Thanks,
dgurram

[Void Main]

Rather than repackaging the tarball just put the original tarball in your redhat/SOURCES directory and put a copy of the spec file in redhat/SPECS. Then in the SPECS dir use "rpmbuild -ba package.spec". You can modify the spec file and rerun the build command without repackaging the original tarball (which really isn't proper rpmbuilding etiquette anyway). When you do get your package to build, your version of the spec file will be included in the *.src.rpm.

EDIT: I just downloaded and built the log4cpp package by adding:

%attr(644,root,root) %prefix/share/aclocal/log4cpp.m4

right under:

%attr(755,root,root) %prefix/lib/lib*.so.*

in the %files section.

[Void Main]

Heh heh, just out of curiosity I tried what you tried as well (with the %{_datadir}) and it worked for me. :) I'm not sure what you might have done differently. Here's my spec file:

http://voidmain.is-a-geek.net/files/specs/log4cpp.spec

[Void Main]

One last note if you didn't already get it. I have specs that should work for you on both packages.

SPEC for log4cpp-0.3.4b.tar.gz:
http://voidmain.is-a-geek.net/files/...pp-0.3.4b.spec

SPEC for icu-3.2.tgz:
http://voidmain.is-a-geek.net/files/specs/icu-3.2.spec

Again, put these spec files in the redhat/SPECS dir and the the tgz files I mention go in redhat/SOURCES and then in the SPECS dir do an "rpmbuild -ba specfile" and everything should build under FC3.

The spec that is included with icu-3.2 as actually icu-3.0 specific (it's common for source distributions to not keep up their spec files). I updated all the version numbers accordingly and added a few new included files.

[dgurram]

Thanks Void Main, you're a champ. It helps a lot to know the right way to do things.

I copied the tar over to the /usr/src/redhat/SOURCES dir, but I found the log4cpp.spec file in the /usr/src/redhat/SPECS dir already there. And what's more, it was the original spec file, i.e without the "%attr(644,root,root) %{_datadir}/aclocal/log4cpp.m4" line. My suspiscion is that the first time I tried to build off the tarball, it must have copied the spec file from the tarball into the SPECS dir and from then on, it somehow failed to over-write the spec file after mods (although I'm not sure why it would not over-write).

So anyway, I modified the spec file in the SPECS dir to include the extra line the %files section and it worked like a charm.

Thanks again. I didn't think anyone would actually download and install those packages just to help me out, so your effort is doubly appeciated.

Cheers,
dgurram

[Void Main]

My pleasure.