On Fri, Aug 13, 2004 at 10:30:26PM -0300, Nicolás_Lichtmaier wrote:
> I'm trying to create rpm packages for Subversion 1.1rc2 and for
> RHEL3/WBEL. I've installed everything (except subversion itself) from
> http://summersoft.fay.ar.us/pub/subversion/latest/whitebox-el-3/bin/ . I
> went to the packages/rpm/wbel-3 directory and ran "make
> RELEASE=1.1.0.rc2". The compilation went fine, but at the end I've got this:
>
> Checking for unpackaged file(s): /usr/lib/rpm/check-files
> /root/rpms/tmp/subversion-1.1.0-1.1.0.rc2
> error: Installed (but unpackaged) file(s) found:
> /usr/bin/neon-config
> /usr/include/neon/ne_207.h
> /usr/include/neon/ne_acl.h
> /usr/include/neon/ne_alloc.h
> [...]
>
> RPM build errors:
> Installed (but unpackaged) file(s) found:
> /usr/bin/neon-config
> /usr/include/neon/ne_207.h
> /usr/include/neon/ne_acl.h
> /usr/include/neon/ne_alloc.h
> /usr/include/neon/ne_auth.h
> /usr/include/neon/ne_basic.h
> /usr/include/neon/ne_compress.h
> /usr/include/neon/ne_cookies.h
> [...]
> make: *** [build_rpm_files] Error 1
>
> I know nearly nothing about the RPM package building system (I would
> never choose RedHat over Debian =) ). Is there something wrong in the
> spec file?
RPM used to silently ignore uninstalled files. Now it errors out. If
the package isn't going to use a system neon lib and is going to build
the neon that comes with the subversion tarball it needs to either
package the development files or delete them in %install.
Probably the proper thing here is to delete the neon subdir in %prep
because I would bet you already have a neon package installed.
--
Ben Reser <ben@reser.org>
http://ben.reser.org
"Conscience is the inner voice which warns us somebody may be looking."
- H.L. Mencken
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Aug 14 05:05:37 2004