Thanks! I managed to get qtp-newmodel working by changing the yum priorities, getting fuse from qtp. That is what I have done in the past, so it feels safest in production. I'll fire up a similar test instance and test the newer approach there.
-Erik ________________________________________ From: Eric Shubert <[email protected]> Sent: Sunday, June 22, 2014 3:06 PM To: [email protected] Subject: [qmailtoaster] Re: Problem with qtp-newmodel on CentOS 5.10 Sorry that the documentation isn't quite up to date yet. There is only one yum repo now, which is a combination of QMT and QTP (QTP is going away). I expect you'd be ok installing the qmailtoaster-release package on a COS5 QMT, but I haven't tested this. That package is in the nodist/noarch branch of the repo. (sources at https://github.com/QMailToaster/qmailtoaster-release) Let us know how that works for you. Thanks. -- -Eric 'shubes' On 06/22/2014 03:12 AM, Erik Wramner wrote: > Thanks! I'll try the yum installation, it would be much more convenient if it > works. > > Perhaps a stupid question, but I found different links in the mailing list > archive and I'd rather not make a mistake - where is the QMT repo? I have > http://qtp.qmailtoaster.com/repos/nodist active and I can enable > http://qtp.qmailtoaster.com/repos/centos/$releasever/$basearch, will that do > the trick or where can I find the .repo-file? > > -Erik > ________________________________________ > From: Eric Shubert <[email protected]> > Sent: Friday, June 20, 2014 5:40 PM > To: [email protected] > Subject: [qmailtoaster] Re: Problem with qtp-newmodel on CentOS 5.10 > > While qtp-newmodel is being deprecated, it still should work for > *-toaster packages. > > dkms-fuse is no longer needed, so that's not a problem. > > I think your fuse-unionfs package may be a problem. I have: > [root@mail ~]# rpm -qa | grep fuse > fuse-unionfs-0.23-2.qtp > fuse-2.8.0-1.qtp > [root@mail ~]# > > You appear to have picked up this package from .rf instead of .qtp. > > I just updated clamav-toaster-0.98.4-1.4.8 on 2 hosts using qtp-newmodel > and it worked ok. These are COS 5.6 and 5.8 hosts though, so that could > be an issue, but I wouldn't expect it to be. > > Would anyone else on COS 5.10 care to try updating clamav-toaster with > qtp-newmodel? > > Thanks. > > P.S. If you'd rather not mess with qtp-newmodel, you can find binary > packages for clamav-toaster in the QMT repo. You can update manually > with rpm, or set up a yum repo file and use yum to do the update. > > -- > -Eric 'shubes' > > On 06/20/2014 12:16 AM, [email protected] wrote: >> I am running qmail on CentOS 5.10. The present installation is fairly >> recent. I installed with >> http://www.qmailtoaster.com/centos/cnt50/cnt50-install-script.sh, which is >> what I have done at least three times before, and restored a backup with >> qtp-restore. There were no problems and the mail server has been running >> without issues since then. >> >> Now qtp-amiuptodate reports that there is a new clamav package available, >> so I tried qtp-newmodel. Unfortunately it fails. >> >> The first sign of failure is: >> >> No package dkms-fuse available. >> Resolving Dependencies >> --> Running transaction check >> ---> Package fuse-unionfs.i386 0:0.23-1.el5.rf set to be updated >> ... >> Installed: >> fuse-unionfs.i386 0:0.23-1.el5.rf >> >> ... >> >> Then the build fails with: >> >> mv: cannot create regular file `/mnt/qtp-sandbox/etc/mtab': Software >> caused connection abort >> /usr/sbin/qtp-mount-sandbox: line 172: /mnt/qtp-sandbox/boot/.qtp-sandbox: >> Software caused connection abort >> qtp-mount-sandbox: sandbox mounted successfully >> cat: /mnt/qtp-sandbox/boot/.qtp-sandbox: Transport endpoint is not connected >> >> I have tried a few times with a reboot in between and yum reports all >> packages up to date. >> >> Is this a known issue? Thanks in advance for any pointers! >> >> -Erik >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
