Dan, It turns out there is a strange build order issue. I was able to build the rpm from source, but only if i make the original tarball available to the buildpkgs script and i do not run autogen or configure on the source tree beforehand.
If i let the buildpkgs script assemble the tarball for me it seems to bomb out. >From the logs it looks like rpmbuild is expecting the man pages to be in /usr/share/man, but if i look in the /var/tmp/rpmbuild install root, they're in /usr/man Sorry, i can't easily pull the logs as the systems are on a private network, but i'll try. On Wed, Jan 27, 2010 at 7:40 PM, Dan Locks <[email protected]> wrote: > Michael Di Domenico wrote: >> >> I'm trying to get RPM's built for 2.6.1p2, however, when i run the >> packaging/rpm/buildpkgs everything appears to be going fine, until >> then end where a bunch of errors are spit out about man pages >> installed but unpackaged. >> >> Is there a patch for this? >> > > Hmm, I couldn't reproduce this error either from code checked out from > https://amanda.svn.sourceforge.net/svnroot/amanda/amanda/tags/amanda261p2, > the 2.6.1 branch head, or the tarball available on sourceforge. Could you > give us a bit more information? Specifically: On what platform are you > building this rpm? Could you post the exact error messages? > Installed but unpackaged usually indicates a new manpage that has not yet > been listed in packaging/rpm/amanda.spec. The reverse error which would > look similar to "file not found: /foo/bar/man/man8/foo.8.gz" usually > indicates that manpages failed to build. > > Dan >
