On 12/28/2009 06:48 PM, Mark Martinec wrote:
On Tuesday December 29 2009 00:00:35 Warren Togami wrote:
https://bugzilla.redhat.com/show_bug.cgi?id=550861
I'm currently unpacking the rule tarball into
$RPM_BUILD_ROOT/usr/share/spamassassin for my RPM package. The
resulting install seems to work just fine.
I assume this reported problem is because I am unpacking the tarball
instead of using sa-update to install the tarball? I couldn't figure
out how to successfully use sa-update to install to an arbitrary path.
The --updatedir is supposed to provide this functionality:
--updatedir path Directory to place updates, defaults to the
SpamAssassin site rules directory
(default: /var/lib/spamassassin/<version>)
If it doesn't work this way, it's probably a bug.
Mark
[war...@newcaprica Mail-SpamAssassin-3.3.0]$ ./sa-update --install
~/rpmbuild/SOURCES/Mail-SpamAssassin-rules-3.3.0-rc1.r893295.tgz
--updatedir
/home/warren/rpmbuild/BUILDROOT/spamassassin-3.3.0-0.27.rc1.fc12.x86_64/usr/share/spamassassin/
config: no configuration text or files found! do you need to run
'sa-update'?
check: no loaded plugin implements 'check_main': cannot scan!
Check the necessary '.pre' files are in the config directory.
sa-update when run from the unpacked source tarball fails when
spamassassin is not already installed. Any suggestions?
Warren
