Hi again, Jim, I tested the SA install on COS6-64
I removed the latest SA (3.4.1) from my COS6-64 with the following command: # rpm --nodeps -e spamassassin Next I reinstalled spamassassin-3.4.0 from the QMT mirrors with the following command: # yum install spamassassin And, next upgraded to the latest spamassassin-3.4.1 with this command: # yum --enablerepo=whtc-qmt-testing update spamassassin Did a SA debug lint # spamassassin -D --lint > output.txt 2>&1 And, everything looks Okay. EricB. On 6/2/2015 5:01 PM, Eric Broch wrote: > Sorry, Jim > > 1 Should be: > > 1) rpm -Uvh > ftp://ftp.whitehorsetc.com/pub/repo/qmt/CentOS/6/current/noarch/whtc-qmt-6-1.noarch.rpm > > EricB > > On 6/2/2015 4:58 PM, Eric Broch wrote: >> It should work, though, I've not tested the upgrade on Spamassassin >> (SA) particularly, only Dovecot. >> I upgraded SA by using rpm method '# rpm >> 'ftp://<host>/<dir>/<pkg>.rpm' a while ago. >> >> So in order to do the latest SA on COS 6 install do: >> >> 1) >> ftp://ftp.whitehorsetc.com/pub/repo/qmt/CentOS/6/current/noarch/whtc-qmt-6-1.noarch.rpm >> 2) yum --enablerepo=whtc-qmt-testing update spamassassin >> >> And, that should take care of it. >> >> Let me know how it goes. >> >> EricB >> >> >> >> >> So, In order to get only the updates you want run the yum command >> with the package >> >> On 6/2/2015 12:15 PM, Jim Shupert wrote: >>> Thanks! >>> >>> so this gets the newest spamassassin ? >>> >>> SpamAssassin 3.4.1 ? >>> >>> >>> >>> >>> On 6/2/2015 10:08 AM, Eric Broch wrote: >>>> Update: >>>> There is a different whtc-qmt repo installer for each version of CentOS >>>> ftp://ftp.whitehorsetc.com/pub/repo/qmt/CentOS/5/current/noarch/whtc-qmt-5-1.noarch.rpm >>>> ftp://ftp.whitehorsetc.com/pub/repo/qmt/CentOS/6/current/noarch/whtc-qmt-6-1.noarch.rpm >>>> ftp://ftp.whitehorsetc.com/pub/repo/qmt/CentOS/7/current/noarch/whtc-qmt-7-1.noarch.rpm >>>> EricB >>>> >>>> On 6/1/2015 12:13 PM, Eric Broch wrote: >>>>> Hi Jim, >>>>> >>>>> If anyone is interested I have another way of updating QMT >>>>> packages from my own business repo. Follow the below procedure: >>>>> >>>>> 1) # yum install yum-protectbase >>>>> 2) # rpm -Uvh >>>>> ftp://ftp.whitehorsetc.com/pub/repo/qmt/CentOS/7/current/noarch/whtc-qmt-1-1.noarch.rpm >>>>> 3) # yum --enablerepo=whtc-qmt-testing update <pkg> >>>>> >>>>> This procedure can be used for CentOS 5, 6, and 7 >>>>> >>>>> All of the updated packages in CentOS 5 and 6 are in the testing >>>>> repo. I've not moved any over to current status though maybe I >>>>> should. If anyone thinks I should, let me know. >>>>> >>>>> I had to use yum-protectbase for CentOS 7 because the QMT >>>>> spamassassin and clamav packages where over-written by EPEL >>>>> packages on update. I'm not sure if it's necessary for CentOS 5 and 6. >>>>> >>>>> Anyway, I'd rather be adding these packages to the official QMT >>>>> mirrors rather than setting up a different repo (WHTC)*, but I >>>>> don't have the access to the main mirror. >>>>> >>>>> If you choose to update your QMT host using my repo and have any >>>>> problems, please let me know. >>>>> >>>>> EricB >>>>> >>>>> >>>>> >>>>> >>>>> * White Horse Technical Consulting. >>>>> >>>>> On 6/1/2015 7:36 AM, Jim Shupert wrote: >>>>>> >>>>>> >>>>>> On 6/1/2015 7:51 AM, Rajesh M wrote: >>>>>>> hi >>>>>>> >>>>>>> we are using qmailtoaster 64 bit on centos OS 64 bit version 6.6 >>>>>>> >>>>>>> i have installed qmailtoaster manually by downloading all the files >>>>>>> from here >>>>>>> >>>>>>> http://mirrors.qmailtoaster.com/current/SRPMS/ >>>>>>> >>>>>>> now i wish to upgrade spamassassin to version >>>>>>> >>>>>>> do i simply run the following to upgrade spamassassin >>>>>>> >>>>>>> rpmbuild --rebuild --define "dist .qt.el6" >>>>>>> spamassassin-3.4.0-2.qt.src.rpm >>>>>>> rpm -Uvh /root/rpmbuild/RPMS/x86_64/spamassassin-3.4.0-2.qt.src.rpm >>>>>>> >>>>>>> thanks >>>>>>> rajesh >>>>>> I also am intrested on the best suggested method of running the >>>>>> newest spamassassin with a recent >>>>>> qmailtoaster >>>>>> >>>>>> >>>>>>> >>>>>>> >>>>>>> --------------------------------------------------------------------- >>>>>>> To unsubscribe, e-mail: [email protected] >>>>>>> For additional commands, e-mail: [email protected] >>>>>> >>>>> >>>> >>> >> >
