qtp-build-rpms v0.2.5
qtp-remove-pkgs v0.2.2
REMOVED spamassassin-toaster from sandbox (not for real)
Building spamassassin-toaster-3.2.4-1.3.14 ...
qtp-build-rpms - rpmbuild failed for spamassassin-toaster-3.2.4-1.3.14
qtp-build-rpms - see /mnt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log
Build failed, Exiting.

+ 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.79533 (%install)

 
Jack D. Martin, Jr. 



----- Original Message ----
From: Eric Shubert <[EMAIL PROTECTED]>
To: qmailtoaster-list@qmailtoaster.com
Sent: Tuesday, April 8, 2008 12:27:28 PM
Subject: Re: [qmailtoaster] upgrade question

What error (specifically) do you get with .14?

Jack Martin wrote:
> Helmut,
> 
> What did you finally do to upgrade spamassassin, I used .14, and still have 
> the file not creating.  
>  
> Jack D. Martin, Jr. 
> 
> 
> 
> ----- Original Message ----
> From: Helmut Fritz <[EMAIL PROTECTED]>
> To: qmailtoaster-list@qmailtoaster.com
> Sent: Tuesday, April 8, 2008 11:27:24 AM
> Subject: RE: [qmailtoaster] upgrade question
> 
> I just did a complete upgrade with qtp-mewmodel (found as part of qtp-plus
> package).  Once we got the spamassassin things straight it worked great.  If
> all the fixes are not in there you will need to do a copied sandbox (unless
> your system can do a unionfs sandbox).  It is easy to try as each iteration
> can be tested  - and if it fails you get to start over and you should remove
> your previous version of the sandbox.
> 
> Eric,
> Do you know if your changes are rolled out yet? 
> 
> -----Original Message-----
> From: Eric Shubert [mailto:[EMAIL PROTECTED] 
> Sent: Tuesday, April 08, 2008 8:52 AM
> To: qmailtoaster-list@qmailtoaster.com
> Subject: Re: [qmailtoaster] upgrade question
> 
> Igor Smitran wrote:
>> In case i want to upgrade packages to a new version one by one, is it 
>> enough just to do:
>> rpm -Uvh /usr/src/$BDIR/RPMS/$ARCH/package-name-*.rpm per package?
> 
> Short answer, no.
> 
>> Is there a procedure for an upgrade that gives minimum down time?
>>  
>> Thank you
> 
> Using the qtp-newmodel script (part of qmailtoaster-plus
> http://qtp.qmailtoaster.com) will absolutely minimize your down time.
> 
> You could use qtp-newmodel to do one package at a time, but that would be
> risky (sometimes there are package interdependencies), and would increase
> your total down time. IOW, it'd be pointless. Doing them all at once is
> best.
> 
> --
> -Eric 'shubes'
> 


-- 
-Eric 'shubes'

---------------------------------------------------------------------
    QmailToaster hosted by: VR Hosted <http://www.vr.org>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

---------------------------------------------------------------------
     QmailToaster hosted by: VR Hosted <http://www.vr.org>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to