Hi again,
I should have spotted this before. Building Bacula from .spec requires
a patch file bacula-2.2.7-postgresql.patch, which is not apparently
available as a separate source download. It is a bit inconsistent that
building for rpm always includes it, while building from tarball does
not. If this is the same file as
patches/2.2.x/2.2.7-old-postgresql.patch in the tarball, it does not
need to be included as a separate source even if it is used.
Similarly, is it really necessary to require
Release_Notes-%{version}-%{release}.tar.gz as a separate source file
when ReleaseNotes is already part of the tarball?
Moray.
"To err is human. To purr, feline"
------------------------------------------------------------------------------
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
_______________________________________________
Bacula-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-devel
