Jake Vickers wrote:
Dave Hallowell wrote:
Jake,
.rpm
I am following the Installing EMPF patch on the qmail wiki. I patched the spec file (step 4) manually like you suggested. I got the errors when performing step 5 - rebuild your qmail-toaster
rpmbuild -bb --rebuild --with 'cnt40' qmail-toaster.spec
Thanks,
Dave

Try:
rpmbuild -bs qmail-toaster.spec
Then:
rpmbuild --rebuild --with cnt40 /usr/src/redhat/SRPMS/qmail-toaster*


The build environment is set up for CentOS 5, so if you're using 4 you may edit the spec file again and under %default remove the version specifications for the offending libraries. I do not think this will affect the system in a negative manner.


Jake,
That worked. Just to reiterate what I did
.
1. I downloaded and installed the qmail-toaster src.rpm like this
rpm -ivh http://www.qmailtoaster.org/download/stable/qmail-toaster-1.03-1.3.16.src.rpm

2. Then I got my empF patch from here.
wget http://www.mail-archive.com/[email protected]/msg14117/1.3.15.tar.bz2

3. Ran the rpmbuild -bs qmail-toaster.spec
This created a source rpm in the SRPMS director and created a spec file for me to apply the patch 
changes to manually and edit the %default section - removing the version specifications for 
openssl-devel and krb5-devel.

4. Created the rpms from the source rpm like this
rpmbuild --rebuild --with cnt40 /usr/src/redhat/SRPMS/qmail-toaster* 
5. Stopped qmail.
cd /usr/src/redhat/RPMS/i386/
rpm -Uvh --replacefiles --replacepkgs qmail-toaster*.rpm qmail-pop3d*.rpm

6. Started qmail and tested.

I see it checking the policy file in the smtp log.

Thanks for being patient and helping me.

Dave
--------------------------------------------------------------------------------- Managed Qmailtoaster servers are now available Visit http://qmailtoaster.com/QMTManaged.html to order yours today! Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]

Reply via email to