On 08/06/2012 06:29 PM, Eric Shubert wrote:
On 08/06/2012 06:07 AM, Dan McAllister wrote:
On 8/6/2012 4:30 AM, Philip wrote:
On 8/6/2012 12:10 AM, Eric Shubert wrote:
On 08/05/2012 02:52 PM, Philip Nix Guru wrote:
On 08/05/2012 09:55 PM, Eric Shubert wrote:
The subject software upgrades for QMT are now available. These long
awaited upgrades are seriously overdue, as QMT has been using the
same
version of vpopmail since I built my first QMT over 6 years ago.
I'm happy to say that this brings QMT up to date with all of the
upstream software (TTBOMK - someone please notify if something newer
is out there), and completes work on v1.4.x until such time as
another
upstream update becomes available. If I'm lucky, QMT v1.5.0 (CentOS
6.x compatibility) will be available before then.
The recommended upgrade procedure is as follows:
# yum update qmailtoaster-plus
# qtp-newmodel
If you're running the QTP version of dovecot:
# yum update dovecot
If you're running spamdyke (you should be if you're not):
# qtp-install-spamdyke
# service qmail restart
If you choose to do things the hard way (manually), here are some
notes off the top of my head.
In addition to the 3 vpopmail related packages, the following
packages
should be rebuilt and reinstalled (qtp-newmodel will do this
automatically):
qmail-toaster
courier-authlib-toaster
courier-imap-toaster
If you're running a dovecot version that you built yourself, you
should rebuild and reinstall this as well after installing vpopmail.
There are vpopmail database changes required by vpopmail-5.4.18+.
You
should run the qtp-convert script which will do them for you
(qtp-newmodel does this as well).
TTBOMK, all problems with vqadmin have been fixed. If you have a
problem with it, let us know and we'll see if it can't be fixed.
Likewise with vpopmail and quotas. There might be some database
fixing
that needs to be done to put things in sync for you, but we can
cross
those bridges as they come.
As always, if you have any problems with this, please post here.
Thanks to everyone who's helped along the way with this, especially
our own Bharath, and Matt at inter7 (the present vpopmail
maintainer).
That's great
usually I do compile all manually or even mod a bit the spec files
but for once I just started the qtp-newmodel
was for updating a "normal" not modified qmt
Well I guess I ll have to do it manually :)
.....
qtp-build-rpms v0.3.5
qtp-remove-pkgs v0.3.1
REMOVED control-panel-toaster from sandbox (not for real)
Building daemontools-toaster-0.76-1.3.6 ...
Installing daemontools-toaster-0.76-1.3.6 in the sandbox ...
qtp-build-rpms - binary rpm not found for
daemontools-toaster-0.76-1.3.6
qtp-build-rpms - Script Error - aborting.
Build failed, Exiting.
Wrote:
/root/src/rpm/RPMS/x86_64/daemontools-toaster-0.76-1.3.6.x86_64.rpm
Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.97447
+ umask 022
+ cd /root/src/rpm/BUILD
+ cd daemontools-0.76
+ '[' -n /var/tmp/daemontools-toaster-0.76 -a
/var/tmp/daemontools-toaster-0.76 '!=' / ']'
+ rm -rf /var/tmp/daemontools-toaster-0.76
+ '[' -d /root/src/rpm/BUILD/daemontools-0.76 ']'
+ rm -rf /root/src/rpm/BUILD/daemontools-0.76
+ exit 0
Executing(--clean): /bin/sh -e /var/tmp/rpm-tmp.97447
+ umask 022
+ cd /root/src/rpm/BUILD
+ rm -rf daemontools-0.76
+ exit 0
Installing daemontools-toaster-0.76-1.3.6 in the sandbox ...
Conclusion
Then script is not handling .rpmmacros env variables
that's a fault in my opinion
Any idea why it put the rpm in /root/src/ instead of /usr/src/?
That's appears to me to be the problem.
What does
# qtp-whatami
show?
It shouldn't be tough to fix this, even though your setup isn't
apparently typical.
Hey :)
sure I know heheh, I am always using .rpmmacros to define where I want
my rpms
I am building rpms for different projects and I want mine in my
homedir not in the usual /usr/src
before I validate them for release.
It is is a typical way to define by user where to store .
But no worry I can disable it when using qtp-newmodel, just passing
the infos for those who may get that error
Thx for your great work
Just an FYI -- that is the DEFAULT behavior of rpmbuild in RHEL/COS 6!
The normal build location becomes /root/rpmbuild/*
Dan
--
That did ring a bell after I sent the reply. Thanks for the
confirmation, Dan. I need to modify qtp-whatami for this.
Philip, you can change qtp-whatami to set BUILD_DIR to whatever your
preference is.
Since I have to change qtp-whatami anyhow for COS6, if you post the
format of your .rpmmacros (hidden file in /root/ I'm presuming, yes?)
I can have qtp-whatami check for this, and set the variable accordingly.
Thanks.
Hello Eric
yes .rpmmacros is in the root of the user's dir
# cat .rpmmacros
%_topdir /root/src/rpm
# ls /root/src/rpm/
BUILD RPMS SOURCES SPECS SRPMS
