An upgrade of spamassassin using qtp-newmodel fails (using small union) :

Building squirrelmail-toaster-1.4.17-1.3.12 ...
Installing squirrelmail-toaster-1.4.17-1.3.12 in the sandbox ...
Building spamassassin-toaster-3.2.5-1.3.15 ...
qtp-build-rpms - rpmbuild failed for spamassassin-toaster-3.2.5-1.3.15
qtp-build-rpms - see /mnt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log

Build failed, Exiting.



The logfile shows :

...
+ find /var/tmp/spamassassin-toaster-root/usr/lib/perl5/vendor_perl/5.8.8/Mail /var/tmp/spamassassin-toaster-root/usr/lib/perl5/vendor_perl/5.8.8/spamassassin-run.pod -type d -print
+ sed 's...@^/var/tmp/spamassassin-toaster-r...@%dir @g'
+ rm -f /var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/local.cf
+ rm -f /var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/init.pre
+ install -d /var/tmp/spamassassin-toaster-root/etc
+ install -d /var/tmp/spamassassin-toaster-root/etc/cron.hourly
+ install -d /var/tmp/spamassassin-toaster-root/var/qmail/supervise/spamd
+ install -d /var/tmp/spamassassin-toaster-root/var/qmail/supervise/spamd/log + install -d /var/tmp/spamassassin-toaster-root/var/qmail/supervise/spamd/supervise
+ install -d /var/tmp/spamassassin-toaster-root/var/log/qmail
+ install -d /var/tmp/spamassassin-toaster-root/var/log/qmail/spamd
+ rm -f /var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/local.cf
+ rm -f /var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/v310.pre
+ install -m 0644 /usr/src/redhat/SOURCES/qmailtoaster.local.cf.bz2 /var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/local.cf.bz2 install: cannot create regular file `/var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/local.cf.bz2': No such file or directory
error: Bad exit status from /var/tmp/rpm-tmp.25006 (%install)


RPM build errors:
   Bad exit status from /var/tmp/rpm-tmp.25006 (%install)




Any ideas what might be causing this ?


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to