Re: [qmailtoaster] CentOS 6 (and 5) rpms

2013-11-21 Thread Nikolay Mitev
Hi Eric, Perfectly job, Congratulations ! Best regards, Nikolay On Thu, Nov 21, 2013 at 9:53 AM, Sebastian Grewe wrote: > Hey Eric, > > This is great. Is that an actual repo that I can use in Chef to trigger a > regular RPM/YUM based installation? Then I will re-factor my cookbook and > start

Re: [qmailtoaster] CentOS 6 (and 5) rpms

2013-11-20 Thread Sebastian Grewe
Hey Eric, This is great. Is that an actual repo that I can use in Chef to trigger a regular RPM/YUM based installation? Then I will re-factor my cookbook and start using this - then it should work once we are on repoforge. Cheers, Sebastian On Nov 21, 2013, at 8:46 AM, Chandran Manikandan wro

Re: [qmailtoaster] CentOS 6 (and 5) rpms

2013-11-20 Thread Chandran Manikandan
Thanks Eric, Shall i do same installed procedure for centos 6 with qmailtoaster which is showing in Wiki for centos 5 qmailtoaster. On Wed, Nov 20, 2013 at 11:11 PM, Eric Shubert wrote: > Binary rpms can now be found at > http://mirrors.qmailtoaster.com/repos/testing > > While packages in /test

Re: [qmailtoaster] CentOS 6 (and 5) rpms

2013-11-20 Thread Constantin IOAJA
Pe 20.11.2013 17:27, Eric Broch a scris: On 11/20/2013 8:11 AM, Eric Shubert wrote: Binary rpms can now be found at http://mirrors.qmailtoaster.com/repos/testing While packages in /testing should be considered beta, when they end up being migrated to /current there will be no need to update the

Re: [qmailtoaster] CentOS 6 (and 5) rpms

2013-11-20 Thread Eric Broch
On 11/20/2013 8:11 AM, Eric Shubert wrote: > Binary rpms can now be found at > http://mirrors.qmailtoaster.com/repos/testing > > While packages in /testing should be considered beta, when they end up > being migrated to /current there will be no need to update them (so > long as you've installed th

[qmailtoaster] CentOS 6 (and 5) rpms

2013-11-20 Thread Eric Shubert
Binary rpms can now be found at http://mirrors.qmailtoaster.com/repos/testing While packages in /testing should be considered beta, when they end up being migrated to /current there will be no need to update them (so long as you've installed the final testing version). I'm presently getting t