Always use at own risk.

I'm running these packages on a few relatively small production hosts, with no problems.

There are a few dovecot settings you may need to tweek for *very* large implementations. EricB has found out about this and posted on the devel list. We may end up changing the dovecot config defaults as a result of this, but that's still in the works.

I'm also in the process of finishing up the install scripts, so they're still a little rough.

I hope to have this release promoted to 'current' by the end of March at the latest. I don't expect there will be many changes to the packages (except qmailtoaster-util) between now and then. When the packages are promoted to current, there will be no need to do any updating of QMT hosts that are already running the packages.

--
-Eric 'shubes'

On 02/22/2014 09:43 AM, Wicus Roets wrote:
Thanks

My assumption that the disclaimer: "Use at own risk is applicable", and not
advisable on a production machine prior to testing ?

:/

-----Original Message-----
From: Eric Shubert [mailto:[email protected]]
Sent: 22 February 2014 05:28 AM
To: [email protected]
Subject: [qmailtoaster] Re: qtp-newmodel dependencies failed

That's ok. You probably should be subscribed to the devel list though.
This has been covered there, as COS6 support isn't quite "official" yet. ;)

Edit the script to use /testing/ instead of /current/ and the script will
work.

Then you'll need to enable the testing repos, and yum should be good to go.

--
-Eric 'shubes'

On 02/21/2014 05:17 PM, Wicus Roets wrote:
Sorry Eric. I'm starting to feel like a nuisance.

...
Package yum-plugin-priorities-1.1.30-17.el6_5.noarch already installed
and latest version Nothing to do qmailtoaster-util - installing
qmailtoaster-release-2.0-1.qt.nodist.noarch.rpm (repo) ...
Retrieving
http://mirrors.qmailtoaster.com/current/nodist/qmailtoaster-release-2.
0-1.qt
.nodist.noarch.rpm
curl: (22) The requested URL returned error: 404 Not Found
error: skipping
http://mirrors.qmailtoaster.com/current/nodist/qmailtoaster-release-2.
0-1.qt
.nodist.noarch.rpm - transfer failed
qmailtoaster-util - installing qmailtoaster-util (scripts) ...
Loaded plugins: fastestmirror, presto, priorities Loading mirror
speeds from cached hostfile
   * base: dl.za.jsdaav.net
   * centosplus: dl.za.jsdaav.net
   * extras: dl.za.jsdaav.net
   * rpmforge: ftp.is.co.za
   * updates: dl.za.jsdaav.net
Setting up Install Process
No package qmailtoaster-util available.
Error: Nothing to do
qmailtoaster-util - completed

-----Original Message-----
From: Eric Shubert [mailto:[email protected]]
Sent: 22 February 2014 12:51 AM
To: [email protected]
Subject: [qmailtoaster] Re: qtp-newmodel dependencies failed

https://github.com/QMailToaster/qmailtoaster-util/blob/master/qt-boots
trap-2

On 02/21/2014 12:13 PM, Wicus Roets wrote:
Yum instead ... OK

Is there a specific repo I would only need to add ?


-----Original Message-----
From: Eric Shubert [mailto:[email protected]]
Sent: 21 February 2014 07:49 PM
To: [email protected]
Subject: [qmailtoaster] Re: qtp-newmodel dependencies failed

I see the problem now. You shouldn't be running qtp-newmodel on COS6.
You should be using yum instead.

--
-Eric 'shubes'

On 02/21/2014 10:40 AM, Wicus Roets wrote:
Quick edit of /usr/sbin/qtp-install-rpmforge and adding

...
      cnt6064 )
        rhver=el6
        rfver=el6
        rfarch=x86_64
        ;;
...

was a quick fix. Running qtp-newmodel once again.

...
No package dkms-fuse available.
Error: Nothing to do
qtp-mount-sandbox - installation of dependent packages failed
qtp-mount-sandbox - is your qmailtoaster-plus.repo package up to date?
...

# yum erase qmailtoaster-plus.repo qmailtoaster-plus

# rpm -Uvh http://qtp.qmailtoaster.com/trac/downloads/1

# yum install qmailtoaster-plus

# qtp-newmodel

failed again on dependencies

Removed compat-libf2c
                compat-libgcc
                compat-libsdc++-33
from qtp-dependencies

Added            cnt6064 )
                        rhver=el6
                rfver=el6
                        rfarch=x86_64
                        ;;
to qtp-install-rpmforge

Changed enabled=1 within qmailtoaster-plus.repo under [qtp-Centos]

Trying again ...

#qtp-newmodel

...

Setting up Install Process
No package dkms-fuse available.
Error: Nothing to do
qtp-mount-sandbox - installation of dependent packages failed
qtp-mount-sandbox - is your qmailtoaster-plus.repo package up to date?

qtp-newmodel - qtp-mount-sandbox failed, exiting

...


-----Original Message-----
From: Wicus Roets [mailto:[email protected]]
Sent: 21 February 2014 07:08 PM
To: [email protected]
Subject: RE: [qmailtoaster] Re: qtp-newmodel dependencies failed

# qtp-whatami

qtp-whatami v0.3.8 Fri Feb 21 19:06:49 SAST 2014 REAL_DIST=CentOS
DISTRO=CentOS
OSVER=6.5
QTARCH=x86_64
QTKERN=2.6.32-431.5.1.el6.centos.plus.x86_64
BUILD_DIST=cnt6064
BUILD_DIR=/usr/src/redhat
This machine's OS is supported and has been tested

though

# qtp-whatami -s

Has no response


-----Original Message-----
From: Wicus Roets [mailto:[email protected]]
Sent: 21 February 2014 06:55 PM
To: '[email protected]'
Subject: RE: [qmailtoaster] Re: qtp-newmodel dependencies failed

Eric,

RPM package "rpmforge-release-0.5.3-1.el6.rf.x86_64" is installed
though.

qtp-newmodel states:

...
qtp-dependencies v0.3.2
qtp-install-rpmforge v0.4.0 - getting latest version of
rpmforge-release
...
qtp-install-rpmforge - rpmforge-release-0.5.3-1.el6.rf.x86_64 is
installed, upgrading to 0.5.3-1 qtp-install-rpmforge - your
distro/ver is not supported by RPMforge, exiting.
...

Uninstalling rpmforge, followed by qtp-newmodel

qtp-install-rpmforge v0.4.0 - getting latest version of
rpmforge-release
...
qtp-install-rpmforge - rpmforge-release not installed, installing ...
qtp-install-rpmforge - your distro/ver is not supported by RPMforge,
exiting.

uname -r
2.6.32-431.5.1.el6.centos.plus.x86_64

-----Original Message-----
From: Eric Shubert [mailto:[email protected]]
Sent: 21 February 2014 06:40 PM
To: [email protected]
Subject: [qmailtoaster] Re: qtp-newmodel dependencies failed

On 02/20/2014 05:03 PM, Wicus Roets wrote:
        qtp-install-rpmforge -
https://raw.github.com/repoforge/rpms/master/specs/rpmforge-release
/ r p mforge -release.spec not found, please try again later.

I take it that rpmforge-release package isn't installed at all. That
would be a problem.

I've no idea why your host isn't finding this spec file. Unable to
access that site for some reason??

--
-Eric 'shubes'


--------------------------------------------------------------------
-
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]




--
-Eric 'shubes'


---------------------------------------------------------------------
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]

Reply via email to