Re: [qmailtoaster] upgrade qmailtoster old old
Giuseppe mandami un messaggio privato poi ci sentiamo al tel. Ciao -- Mandato da iPhone > On giovedì, nov 10, 2022 at 09:33, Giuseppe Perna (mailto:gpe...@srlsigea.eu)> wrote: > Hello everybody, > I would like to update my version of qmailtoaster with due caution ;-) these > are the installed versions: > > # cat /etc/redhat-release > CentOS release 5.8 (Final) > > # rpm -qa mysql > mysql-5.0.95-1.el5_7.1 > # rpm -qa httpd > httpd-2.2.3-65.el5.centos > > # spamdyke -v > spamdyke 4.3.1+TLS+CONFIGTEST+DEBUG (C)2012 Sam Clippinger, samc (at) silence > (dot) org > http://www.spamdyke.org/ > > > # rpm -qa qmail* > qmail-pop3d-toaster-1.03-1.3.22 > qmailtoaster-plus.repo-0.2-2 > qmailmrtg-toaster-4.2-1.3.7 > qmailtoaster-plus-0.3.2-1.4.19 > qmail-toaster-1.03-1.3.22 > qmailadmin-toaster-1.2.16-1.4.0 > [root@posta ~]# rpm -qa *toaster* > ucspi-tcp-toaster-0.88-1.3.9 > maildrop-toaster-2.0.3-1.3.8 > control-panel-toaster-0.5-1.4.0 > libdomainkeys-toaster-0.68-1.3.6 > qmail-pop3d-toaster-1.03-1.3.22 > squirrelmail-toaster-1.4.20-1.3.17 > qmailtoaster-plus.repo-0.2-2 > vpopmail-toaster-5.4.33-1.4.0 > daemontools-toaster-0.76-1.3.6 > libsrs2-toaster-1.0.18-1.3.6 > courier-authlib-toaster-0.59.2-1.3.10 > ripmime-toaster-1.4.0.6-1.3.6 > autorespond-toaster-2.0.5-1.4.0 > courier-imap-toaster-4.1.2-1.3.10 > isoqlog-toaster-2.1-1.3.7 > maildrop-toaster-devel-2.0.3-1.3.8 > qmailmrtg-toaster-4.2-1.3.7 > send-emails-toaster-0.5-1.4.0 > spamassassin-toaster-3.3.2-1.4.3 > vqadmin-toaster-2.3.7-1.4.1 > qmailtoaster-plus-0.3.2-1.4.19 > ezmlm-toaster-0.53.324-1.3.6 > qmail-toaster-1.03-1.3.22 > ezmlm-cgi-toaster-0.53.324-1.3.6 > qmailadmin-toaster-1.2.16-1.4.0 > simscan-toaster-1.4.0-1.4.0 > clamav-toaster-0.97.6-1.4.2 > > Please help me. > > thanks >
[qmailtoaster] upgrade qmailtoster old old
Hello everybody, I would like to update my version of qmailtoaster with due caution ;-) these are the installed versions: # cat /etc/redhat-release CentOS release 5.8 (Final) # rpm -qa mysql mysql-5.0.95-1.el5_7.1 # rpm -qa httpd httpd-2.2.3-65.el5.centos # spamdyke -v spamdyke 4.3.1+TLS+CONFIGTEST+DEBUG (C)2012 Sam Clippinger, samc (at) silence (dot) org http://www.spamdyke.org/ # rpm -qa qmail* qmail-pop3d-toaster-1.03-1.3.22 qmailtoaster-plus.repo-0.2-2 qmailmrtg-toaster-4.2-1.3.7 qmailtoaster-plus-0.3.2-1.4.19 qmail-toaster-1.03-1.3.22 qmailadmin-toaster-1.2.16-1.4.0 [root@posta ~]# rpm -qa *toaster* ucspi-tcp-toaster-0.88-1.3.9 maildrop-toaster-2.0.3-1.3.8 control-panel-toaster-0.5-1.4.0 libdomainkeys-toaster-0.68-1.3.6 qmail-pop3d-toaster-1.03-1.3.22 squirrelmail-toaster-1.4.20-1.3.17 qmailtoaster-plus.repo-0.2-2 vpopmail-toaster-5.4.33-1.4.0 daemontools-toaster-0.76-1.3.6 libsrs2-toaster-1.0.18-1.3.6 courier-authlib-toaster-0.59.2-1.3.10 ripmime-toaster-1.4.0.6-1.3.6 autorespond-toaster-2.0.5-1.4.0 courier-imap-toaster-4.1.2-1.3.10 isoqlog-toaster-2.1-1.3.7 maildrop-toaster-devel-2.0.3-1.3.8 qmailmrtg-toaster-4.2-1.3.7 send-emails-toaster-0.5-1.4.0 spamassassin-toaster-3.3.2-1.4.3 vqadmin-toaster-2.3.7-1.4.1 qmailtoaster-plus-0.3.2-1.4.19 ezmlm-toaster-0.53.324-1.3.6 qmail-toaster-1.03-1.3.22 ezmlm-cgi-toaster-0.53.324-1.3.6 qmailadmin-toaster-1.2.16-1.4.0 simscan-toaster-1.4.0-1.4.0 clamav-toaster-0.97.6-1.4.2 Please help me. thanks
Re: [qmailtoaster] Upgrade qmailtoaster to Centos 7
You don't absolutely HAVE to convert, but here's the wiki anyway:
http://wiki.qmailtoaster.com/index.php/Replacing_Courier_IMAP_with_Dovecot_IMAP
Thanks, Phil
On 4/7/2017 9:28 AM, Philip Nix Guru wrote:
Hello
I did use the convert script
courier-dovecot-migrate.pl
# ./courier-dovecot-migrate.pl -help
Usage: maildir-migrate [options]
Options:
--convert Perform conversion
--quiet Silence output
--overwrite Overwrite existing files
--recursive Recursively look through maildir for subaccounts
--to-dovecotConversion is from Courier to Dovecot
--to-courierConversion is from Dovecot to Courier
On 04/07/2017 05:15 PM, Eric Broch wrote:
I don't believe any conversion is necessary. You may just have to
resubscribe to the folders.
On 4/7/2017 9:09 AM, Rvaught wrote:
I am in a similar situation. I am running on a Centos 5 with Courier
and would like to move to a Centos 7 setup with Dovecot. I have a
mix of pop and imap clients.
What would be the best way to convert the mailboxes to Dovecot after
I copy them to the new machine?
Thanks,
Rick
-Original Message-
From: Sean Murphy [mailto:sean.mur...@mobilcom.net]
Sent: Friday, April 07, 2017 10:59 AM
To: qmailtoaster-list@qmailtoaster.com
Subject: Re: [qmailtoaster] Upgrade qmailtoaster to CentOS 7
Eric,
That list looks good, except:
/etc/spamassassin should be /etc/mail/spamassassin, unless it's
different on CentOS7.
I'm unsure as to the MariaDB admin password on the current machine
as my predecessor set it up.
I will poke around my docs and see if I can find anything. And, I
didn't realize rsync was not in default install in minimal. Weird.
Thanks again, Eric, this is very helpful. Everybody here is the best.
-Sean
On 4/7/2017 10:44 AM, Eric Broch wrote:
Hi Sean,
Off the top of my head I do the following:
On the QMT/COS7 Install make the MariaDB admin password the same as on
your old machine.
1) Install rsync on both machines
2) Make ssh work without password
# How to make the below rsync ssh command work without a password #
exec ssh-agent bash # ssh-keygen # ssh-copy-id 'new server ip'
# ssh 'new server ip'
3) I rsync the CONTENTS of the following folders, old server to new
/var/lib/squirrelmail/prefs
/usr/share/spamassassin
/etc/spamassassin
/etc/tcprules.d
/var/qmail/control
/var/qmail/users
/home/vpopmail/domains
rsync --progress --delete -var -e ssh ${folder}/
$REMOTEUSER@$REMOTEHOST:${folder}
4) Dump vpopmail mysql database on old server and restore on new.
At this point you should be able to connect to the new server from
mail clients.
5) Secure qmailadmin and vqadmin /etc/httpd/conf/toaster.conf for
CentOS 7 ( http://www.qmailtoaster.com/notes.html)
Hope I'm not forgetting anything.
Eric
On 4/7/2017 7:10 AM, Sean Murphy wrote:
Good day all,
I've finally acquired a "new" machine to house our current install of
the toaster, installed CentOS 7 and ran all available updates, and
rounded up the preparatory files for the install. I will most likely
install qmailtoaster and take it on a test drive before migrating our
current install to the new box. I would like to inquire on the best
way to do this, since the current install is on a CentOS 5 box and we
are running Courier instead of Dovecot. Should I restore from a
backup, or should I recreate the domain on the new box? I'm in no
hurry, the current install is performing like a champ, and I have a
backup machine in place should something go awry before the new
machine is ready. Any advice or horror stories would be greatly
appreciated.
Thanks!
-Sean
-
To unsubscribe, e-mail:
qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail:
qmailtoaster-list-h...@qmailtoaster.com
-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail:
qmailtoaster-list-h...@qmailtoaster.com
-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail:
qmailtoaster-list-h...@qmailtoaster.com
-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
--
Eric Broch, IMSO, DAM, NGOO, DITH, URTS
White Horse Technical Consulting (WHTC)
-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Upgrade qmailtoaster to Centos 7
Hello
I did use the convert script
courier-dovecot-migrate.pl
# ./courier-dovecot-migrate.pl -help
Usage: maildir-migrate [options]
Options:
--convert Perform conversion
--quiet Silence output
--overwrite Overwrite existing files
--recursive Recursively look through maildir for subaccounts
--to-dovecotConversion is from Courier to Dovecot
--to-courierConversion is from Dovecot to Courier
On 04/07/2017 05:15 PM, Eric Broch wrote:
I don't believe any conversion is necessary. You may just have to
resubscribe to the folders.
On 4/7/2017 9:09 AM, Rvaught wrote:
I am in a similar situation. I am running on a Centos 5 with Courier
and would like to move to a Centos 7 setup with Dovecot. I have a mix
of pop and imap clients.
What would be the best way to convert the mailboxes to Dovecot after
I copy them to the new machine?
Thanks,
Rick
-Original Message-
From: Sean Murphy [mailto:sean.mur...@mobilcom.net]
Sent: Friday, April 07, 2017 10:59 AM
To: qmailtoaster-list@qmailtoaster.com
Subject: Re: [qmailtoaster] Upgrade qmailtoaster to CentOS 7
Eric,
That list looks good, except:
/etc/spamassassin should be /etc/mail/spamassassin, unless it's
different on CentOS7.
I'm unsure as to the MariaDB admin password on the current machine as
my predecessor set it up.
I will poke around my docs and see if I can find anything. And, I
didn't realize rsync was not in default install in minimal. Weird.
Thanks again, Eric, this is very helpful. Everybody here is the best.
-Sean
On 4/7/2017 10:44 AM, Eric Broch wrote:
Hi Sean,
Off the top of my head I do the following:
On the QMT/COS7 Install make the MariaDB admin password the same as on
your old machine.
1) Install rsync on both machines
2) Make ssh work without password
# How to make the below rsync ssh command work without a password #
exec ssh-agent bash # ssh-keygen # ssh-copy-id 'new server ip'
# ssh 'new server ip'
3) I rsync the CONTENTS of the following folders, old server to new
/var/lib/squirrelmail/prefs
/usr/share/spamassassin
/etc/spamassassin
/etc/tcprules.d
/var/qmail/control
/var/qmail/users
/home/vpopmail/domains
rsync --progress --delete -var -e ssh ${folder}/
$REMOTEUSER@$REMOTEHOST:${folder}
4) Dump vpopmail mysql database on old server and restore on new.
At this point you should be able to connect to the new server from
mail clients.
5) Secure qmailadmin and vqadmin /etc/httpd/conf/toaster.conf for
CentOS 7 ( http://www.qmailtoaster.com/notes.html)
Hope I'm not forgetting anything.
Eric
On 4/7/2017 7:10 AM, Sean Murphy wrote:
Good day all,
I've finally acquired a "new" machine to house our current install of
the toaster, installed CentOS 7 and ran all available updates, and
rounded up the preparatory files for the install. I will most likely
install qmailtoaster and take it on a test drive before migrating our
current install to the new box. I would like to inquire on the best
way to do this, since the current install is on a CentOS 5 box and we
are running Courier instead of Dovecot. Should I restore from a
backup, or should I recreate the domain on the new box? I'm in no
hurry, the current install is performing like a champ, and I have a
backup machine in place should something go awry before the new
machine is ready. Any advice or horror stories would be greatly
appreciated.
Thanks!
-Sean
-
To unsubscribe, e-mail:
qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail:
qmailtoaster-list-h...@qmailtoaster.com
-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Upgrade qmailtoaster to CentOS 7
1) From looking at the install docs, I think rsync is included when QMT
is installed, but it is not part of default install as I just checked.
2) I will make the necessary adjustments when ready.
3) Suppose we'll find out, as I haven't found anything regarding this
admin pass.
Thanks again, Eric, I'll keep the list posted as to progress.
On 4/7/2017 11:12 AM, Eric Broch wrote:
1) I think I install rsync when QMT is installed, maybe its done by
default on minimal install, not sure.
2) Yes for spamassassin rsync from /etc/mail/spamassassin to
/etc/spamassassin this changed with QMT on CentOS 6
3) I suppose that the admin password does not have to be the same. I
must have had a mind slip. :-P
On 4/7/2017 8:59 AM, Sean Murphy wrote:
Eric,
That list looks good, except:
/etc/spamassassin should be /etc/mail/spamassassin, unless it's
different on CentOS7.
I'm unsure as to the MariaDB admin password on the current machine as
my predecessor set it up.
I will poke around my docs and see if I can find anything. And, I
didn't realize rsync was not in default install in minimal. Weird.
Thanks again, Eric, this is very helpful. Everybody here is the best.
-Sean
On 4/7/2017 10:44 AM, Eric Broch wrote:
Hi Sean,
Off the top of my head I do the following:
On the QMT/COS7 Install make the MariaDB admin password the same as
on your old machine.
1) Install rsync on both machines
2) Make ssh work without password
# How to make the below rsync ssh command work without a password
# exec ssh-agent bash
# ssh-keygen
# ssh-copy-id 'new server ip'
# ssh 'new server ip'
3) I rsync the CONTENTS of the following folders, old server to new
/var/lib/squirrelmail/prefs
/usr/share/spamassassin
/etc/spamassassin
/etc/tcprules.d
/var/qmail/control
/var/qmail/users
/home/vpopmail/domains
rsync --progress --delete -var -e ssh ${folder}/
$REMOTEUSER@$REMOTEHOST:${folder}
4) Dump vpopmail mysql database on old server and restore on new.
At this point you should be able to connect to the new server from
mail clients.
5) Secure qmailadmin and vqadmin /etc/httpd/conf/toaster.conf for
CentOS 7 ( http://www.qmailtoaster.com/notes.html)
Hope I'm not forgetting anything.
Eric
On 4/7/2017 7:10 AM, Sean Murphy wrote:
Good day all,
I've finally acquired a "new" machine to house our current install
of the toaster, installed CentOS 7 and ran all available updates,
and rounded up the preparatory files for the install. I will most
likely install qmailtoaster and take it on a test drive before
migrating our current install to the new box. I would like to
inquire on the best way to do this, since the current install is on
a CentOS 5 box and we are running Courier instead of Dovecot.
Should I restore from a backup, or should I recreate the domain on
the new box? I'm in no hurry, the current install is performing
like a champ, and I have a backup machine in place should something
go awry before the new machine is ready. Any advice or horror
stories would be greatly appreciated.
Thanks!
-Sean
-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail:
qmailtoaster-list-h...@qmailtoaster.com
-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Upgrade qmailtoaster to Centos 7
I don't believe any conversion is necessary. You may just have to
resubscribe to the folders.
On 4/7/2017 9:09 AM, Rvaught wrote:
I am in a similar situation. I am running on a Centos 5 with Courier and would
like to move to a Centos 7 setup with Dovecot. I have a mix of pop and imap
clients.
What would be the best way to convert the mailboxes to Dovecot after I copy
them to the new machine?
Thanks,
Rick
-Original Message-
From: Sean Murphy [mailto:sean.mur...@mobilcom.net]
Sent: Friday, April 07, 2017 10:59 AM
To: qmailtoaster-list@qmailtoaster.com
Subject: Re: [qmailtoaster] Upgrade qmailtoaster to CentOS 7
Eric,
That list looks good, except:
/etc/spamassassin should be /etc/mail/spamassassin, unless it's different on
CentOS7.
I'm unsure as to the MariaDB admin password on the current machine as my
predecessor set it up.
I will poke around my docs and see if I can find anything. And, I didn't
realize rsync was not in default install in minimal. Weird.
Thanks again, Eric, this is very helpful. Everybody here is the best.
-Sean
On 4/7/2017 10:44 AM, Eric Broch wrote:
Hi Sean,
Off the top of my head I do the following:
On the QMT/COS7 Install make the MariaDB admin password the same as on
your old machine.
1) Install rsync on both machines
2) Make ssh work without password
# How to make the below rsync ssh command work without a password #
exec ssh-agent bash # ssh-keygen # ssh-copy-id 'new server ip'
# ssh 'new server ip'
3) I rsync the CONTENTS of the following folders, old server to new
/var/lib/squirrelmail/prefs
/usr/share/spamassassin
/etc/spamassassin
/etc/tcprules.d
/var/qmail/control
/var/qmail/users
/home/vpopmail/domains
rsync --progress --delete -var -e ssh ${folder}/
$REMOTEUSER@$REMOTEHOST:${folder}
4) Dump vpopmail mysql database on old server and restore on new.
At this point you should be able to connect to the new server from
mail clients.
5) Secure qmailadmin and vqadmin /etc/httpd/conf/toaster.conf for
CentOS 7 ( http://www.qmailtoaster.com/notes.html)
Hope I'm not forgetting anything.
Eric
On 4/7/2017 7:10 AM, Sean Murphy wrote:
Good day all,
I've finally acquired a "new" machine to house our current install of
the toaster, installed CentOS 7 and ran all available updates, and
rounded up the preparatory files for the install. I will most likely
install qmailtoaster and take it on a test drive before migrating our
current install to the new box. I would like to inquire on the best
way to do this, since the current install is on a CentOS 5 box and we
are running Courier instead of Dovecot. Should I restore from a
backup, or should I recreate the domain on the new box? I'm in no
hurry, the current install is performing like a champ, and I have a
backup machine in place should something go awry before the new
machine is ready. Any advice or horror stories would be greatly
appreciated.
Thanks!
-Sean
-
To unsubscribe, e-mail:
qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail:
qmailtoaster-list-h...@qmailtoaster.com
-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
--
Eric Broch, IMSO, DAM, NGOO, DITH, URTS
White Horse Technical Consulting (WHTC)
-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Upgrade qmailtoaster to CentOS 7
1) I think I install rsync when QMT is installed, maybe its done by
default on minimal install, not sure.
2) Yes for spamassassin rsync from /etc/mail/spamassassin to
/etc/spamassassin this changed with QMT on CentOS 6
3) I suppose that the admin password does not have to be the same. I
must have had a mind slip. :-P
On 4/7/2017 8:59 AM, Sean Murphy wrote:
Eric,
That list looks good, except:
/etc/spamassassin should be /etc/mail/spamassassin, unless it's
different on CentOS7.
I'm unsure as to the MariaDB admin password on the current machine as
my predecessor set it up.
I will poke around my docs and see if I can find anything. And, I
didn't realize rsync was not in default install in minimal. Weird.
Thanks again, Eric, this is very helpful. Everybody here is the best.
-Sean
On 4/7/2017 10:44 AM, Eric Broch wrote:
Hi Sean,
Off the top of my head I do the following:
On the QMT/COS7 Install make the MariaDB admin password the same as
on your old machine.
1) Install rsync on both machines
2) Make ssh work without password
# How to make the below rsync ssh command work without a password
# exec ssh-agent bash
# ssh-keygen
# ssh-copy-id 'new server ip'
# ssh 'new server ip'
3) I rsync the CONTENTS of the following folders, old server to new
/var/lib/squirrelmail/prefs
/usr/share/spamassassin
/etc/spamassassin
/etc/tcprules.d
/var/qmail/control
/var/qmail/users
/home/vpopmail/domains
rsync --progress --delete -var -e ssh ${folder}/
$REMOTEUSER@$REMOTEHOST:${folder}
4) Dump vpopmail mysql database on old server and restore on new.
At this point you should be able to connect to the new server from
mail clients.
5) Secure qmailadmin and vqadmin /etc/httpd/conf/toaster.conf for
CentOS 7 ( http://www.qmailtoaster.com/notes.html)
Hope I'm not forgetting anything.
Eric
On 4/7/2017 7:10 AM, Sean Murphy wrote:
Good day all,
I've finally acquired a "new" machine to house our current install
of the toaster, installed CentOS 7 and ran all available updates,
and rounded up the preparatory files for the install. I will most
likely install qmailtoaster and take it on a test drive before
migrating our current install to the new box. I would like to
inquire on the best way to do this, since the current install is on
a CentOS 5 box and we are running Courier instead of Dovecot. Should
I restore from a backup, or should I recreate the domain on the new
box? I'm in no hurry, the current install is performing like a
champ, and I have a backup machine in place should something go awry
before the new machine is ready. Any advice or horror stories would
be greatly appreciated.
Thanks!
-Sean
-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail:
qmailtoaster-list-h...@qmailtoaster.com
-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
--
Eric Broch, IMSO, DAM, NGOO, DITH, URTS
White Horse Technical Consulting (WHTC)
-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
RE: [qmailtoaster] Upgrade qmailtoaster to Centos 7
I am in a similar situation. I am running on a Centos 5 with Courier and would
like to move to a Centos 7 setup with Dovecot. I have a mix of pop and imap
clients.
What would be the best way to convert the mailboxes to Dovecot after I copy
them to the new machine?
Thanks,
Rick
-Original Message-
From: Sean Murphy [mailto:sean.mur...@mobilcom.net]
Sent: Friday, April 07, 2017 10:59 AM
To: qmailtoaster-list@qmailtoaster.com
Subject: Re: [qmailtoaster] Upgrade qmailtoaster to CentOS 7
Eric,
That list looks good, except:
/etc/spamassassin should be /etc/mail/spamassassin, unless it's different on
CentOS7.
I'm unsure as to the MariaDB admin password on the current machine as my
predecessor set it up.
I will poke around my docs and see if I can find anything. And, I didn't
realize rsync was not in default install in minimal. Weird.
Thanks again, Eric, this is very helpful. Everybody here is the best.
-Sean
On 4/7/2017 10:44 AM, Eric Broch wrote:
> Hi Sean,
>
> Off the top of my head I do the following:
>
> On the QMT/COS7 Install make the MariaDB admin password the same as on
> your old machine.
>
> 1) Install rsync on both machines
>
> 2) Make ssh work without password
>
> # How to make the below rsync ssh command work without a password #
> exec ssh-agent bash # ssh-keygen # ssh-copy-id 'new server ip'
> # ssh 'new server ip'
>
> 3) I rsync the CONTENTS of the following folders, old server to new
>
> /var/lib/squirrelmail/prefs
> /usr/share/spamassassin
> /etc/spamassassin
> /etc/tcprules.d
> /var/qmail/control
> /var/qmail/users
> /home/vpopmail/domains
>
> rsync --progress --delete -var -e ssh ${folder}/
> $REMOTEUSER@$REMOTEHOST:${folder}
>
> 4) Dump vpopmail mysql database on old server and restore on new.
>
> At this point you should be able to connect to the new server from
> mail clients.
>
> 5) Secure qmailadmin and vqadmin /etc/httpd/conf/toaster.conf for
> CentOS 7 ( http://www.qmailtoaster.com/notes.html)
>
> Hope I'm not forgetting anything.
>
>
> Eric
>
>
>
>
>
>
> On 4/7/2017 7:10 AM, Sean Murphy wrote:
>> Good day all,
>>
>> I've finally acquired a "new" machine to house our current install of
>> the toaster, installed CentOS 7 and ran all available updates, and
>> rounded up the preparatory files for the install. I will most likely
>> install qmailtoaster and take it on a test drive before migrating our
>> current install to the new box. I would like to inquire on the best
>> way to do this, since the current install is on a CentOS 5 box and we
>> are running Courier instead of Dovecot. Should I restore from a
>> backup, or should I recreate the domain on the new box? I'm in no
>> hurry, the current install is performing like a champ, and I have a
>> backup machine in place should something go awry before the new
>> machine is ready. Any advice or horror stories would be greatly
>> appreciated.
>>
>> Thanks!
>>
>> -Sean
>>
>>
>> -
>> To unsubscribe, e-mail:
>> qmailtoaster-list-unsubscr...@qmailtoaster.com
>> For additional commands, e-mail:
>> qmailtoaster-list-h...@qmailtoaster.com
>>
>
-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Upgrade qmailtoaster to CentOS 7
Eric,
That list looks good, except:
/etc/spamassassin should be /etc/mail/spamassassin, unless it's
different on CentOS7.
I'm unsure as to the MariaDB admin password on the current machine as my
predecessor set it up.
I will poke around my docs and see if I can find anything. And, I
didn't realize rsync was not in default install in minimal. Weird.
Thanks again, Eric, this is very helpful. Everybody here is the best.
-Sean
On 4/7/2017 10:44 AM, Eric Broch wrote:
Hi Sean,
Off the top of my head I do the following:
On the QMT/COS7 Install make the MariaDB admin password the same as on
your old machine.
1) Install rsync on both machines
2) Make ssh work without password
# How to make the below rsync ssh command work without a password
# exec ssh-agent bash
# ssh-keygen
# ssh-copy-id 'new server ip'
# ssh 'new server ip'
3) I rsync the CONTENTS of the following folders, old server to new
/var/lib/squirrelmail/prefs
/usr/share/spamassassin
/etc/spamassassin
/etc/tcprules.d
/var/qmail/control
/var/qmail/users
/home/vpopmail/domains
rsync --progress --delete -var -e ssh ${folder}/
$REMOTEUSER@$REMOTEHOST:${folder}
4) Dump vpopmail mysql database on old server and restore on new.
At this point you should be able to connect to the new server from
mail clients.
5) Secure qmailadmin and vqadmin /etc/httpd/conf/toaster.conf for
CentOS 7 ( http://www.qmailtoaster.com/notes.html)
Hope I'm not forgetting anything.
Eric
On 4/7/2017 7:10 AM, Sean Murphy wrote:
Good day all,
I've finally acquired a "new" machine to house our current install of
the toaster, installed CentOS 7 and ran all available updates, and
rounded up the preparatory files for the install. I will most likely
install qmailtoaster and take it on a test drive before migrating our
current install to the new box. I would like to inquire on the best
way to do this, since the current install is on a CentOS 5 box and we
are running Courier instead of Dovecot. Should I restore from a
backup, or should I recreate the domain on the new box? I'm in no
hurry, the current install is performing like a champ, and I have a
backup machine in place should something go awry before the new
machine is ready. Any advice or horror stories would be greatly
appreciated.
Thanks!
-Sean
-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Upgrade qmailtoaster to CentOS 7
Hi Sean,
Off the top of my head I do the following:
On the QMT/COS7 Install make the MariaDB admin password the same as on
your old machine.
1) Install rsync on both machines
2) Make ssh work without password
# How to make the below rsync ssh command work without a password
# exec ssh-agent bash
# ssh-keygen
# ssh-copy-id 'new server ip'
# ssh 'new server ip'
3) I rsync the CONTENTS of the following folders, old server to new
/var/lib/squirrelmail/prefs
/usr/share/spamassassin
/etc/spamassassin
/etc/tcprules.d
/var/qmail/control
/var/qmail/users
/home/vpopmail/domains
rsync --progress --delete -var -e ssh ${folder}/
$REMOTEUSER@$REMOTEHOST:${folder}
4) Dump vpopmail mysql database on old server and restore on new.
At this point you should be able to connect to the new server from mail
clients.
5) Secure qmailadmin and vqadmin /etc/httpd/conf/toaster.conf for
CentOS 7 ( http://www.qmailtoaster.com/notes.html)
Hope I'm not forgetting anything.
Eric
On 4/7/2017 7:10 AM, Sean Murphy wrote:
Good day all,
I've finally acquired a "new" machine to house our current install of
the toaster, installed CentOS 7 and ran all available updates, and
rounded up the preparatory files for the install. I will most likely
install qmailtoaster and take it on a test drive before migrating our
current install to the new box. I would like to inquire on the best
way to do this, since the current install is on a CentOS 5 box and we
are running Courier instead of Dovecot. Should I restore from a
backup, or should I recreate the domain on the new box? I'm in no
hurry, the current install is performing like a champ, and I have a
backup machine in place should something go awry before the new
machine is ready. Any advice or horror stories would be greatly
appreciated.
Thanks!
-Sean
-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
--
Eric Broch, IMSO, DAM, NGOO, DITH, URTS
White Horse Technical Consulting (WHTC)
-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
[qmailtoaster] Upgrade qmailtoaster to CentOS 7
Good day all, I've finally acquired a "new" machine to house our current install of the toaster, installed CentOS 7 and ran all available updates, and rounded up the preparatory files for the install. I will most likely install qmailtoaster and take it on a test drive before migrating our current install to the new box. I would like to inquire on the best way to do this, since the current install is on a CentOS 5 box and we are running Courier instead of Dovecot. Should I restore from a backup, or should I recreate the domain on the new box? I'm in no hurry, the current install is performing like a champ, and I have a backup machine in place should something go awry before the new machine is ready. Any advice or horror stories would be greatly appreciated. Thanks! -Sean - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
[qmailtoaster] upgrade qmailtoaster dovecot
hi centos 5 qmailtoaster i had installed dovecot 1.2 using the dovecot-1.2.11-3_108.src.rpm now i wish to upgrade the same to version 2 from qtp repository should i remove the existing dovecot and then install version 2 or directly upgrade the same -- if so what is the command. i read the instructions in this link but it does not explicitly mention whether it is for upgrading from dovecot 1.2 to 2 http://wiki.qmailtoaster.com/index.php/Replacing_Courier_IMAP_with_Dovecot_IMAP can you please give me a few steps for this upgrade please. thanks and regards, rajesh - Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! - Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
[qmailtoaster] QmailToaster upgrade issue
Hi All, This is my first post on QmailToaster mailing list. I have upgraded qmail toaster on my mail server running on CentOS 4.5 version to latest release of QmailToaster using instructions posted on http://wiki.qmailtoaster.com/index.php/Upgrade.sh_script. After successful upgrade I have rebooted my server and there after I am having issues in receiving email in my mail client (ThunderBird). I need to restart Qmail service every time in order to receive email from the server. Only change I have noticed in Qmail SMTP logs is policy_check @40004ab769aa23cb69fc policy_check: local - local (UNAUTHENTICATED SENDER) @40004ab769aa23cb6de4 policy_check: policy allows transmission Please help me to resolve this issue Thanks Mahipal
Re: [qmailtoaster] QmailToaster upgrade issue
Mahipal Singh wrote: Hi All, This is my first post on QmailToaster mailing list. I have upgraded qmail toaster on my mail server running on CentOS 4.5 version to latest release of QmailToaster using instructions posted on http://wiki.qmailtoaster.com/index.php/Upgrade.sh_script. After successful upgrade I have rebooted my server and there after I am having issues in receiving email in my mail client (ThunderBird). I need to restart Qmail service every time in order to receive email from the server. Only change I have noticed in Qmail SMTP logs is policy_check @40004ab769aa23cb69fc policy_check: local - local (UNAUTHENTICATED SENDER) @40004ab769aa23cb6de4 policy_check: policy allows transmission Those entries are generated by eMPF and are benign. Did you configure eMPF? What did you change from your old config to the new? Either way we will need to see more of the logs for us to determine anything. - Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! - Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] QmailToaster upgrade issue
Hi Jack, I have compared the logs and only change I can see in SMTP. I can send email from in mail client and webmail and there is no pending email in local queue checked using qmHandle. The only issue I am facing right now is when I try to receive email my mail client says no new message but there are mails stored on mail server which I can only see after restarting qmail service. Please let me know the logs you want me to check. Thanks Mahipal Jake Vickers wrote: Mahipal Singh wrote: Hi All, This is my first post on QmailToaster mailing list. I have upgraded qmail toaster on my mail server running on CentOS 4.5 version to latest release of QmailToaster using instructions posted on http://wiki.qmailtoaster.com/index.php/Upgrade.sh_script. After successful upgrade I have rebooted my server and there after I am having issues in receiving email in my mail client (ThunderBird). I need to restart Qmail service every time in order to receive email from the server. Only change I have noticed in Qmail SMTP logs is policy_check @40004ab769aa23cb69fc policy_check: local - local (UNAUTHENTICATED SENDER) @40004ab769aa23cb6de4 policy_check: policy allows transmission Those entries are generated by eMPF and are benign. Did you configure eMPF? What did you change from your old config to the new? Either way we will need to see more of the logs for us to determine anything. - Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! - Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] QmailToaster upgrade issue
Mahipal Singh wrote: Hi Jack, I have compared the logs and only change I can see in SMTP. I can send email from in mail client and webmail and there is no pending email in local queue checked using qmHandle. The only issue I am facing right now is when I try to receive email my mail client says no new message but there are mails stored on mail server which I can only see after restarting qmail service. Please let me know the logs you want me to check. If they're using pop3, then check the pop3 logs. If they're using imap, check the imap logs.
Re: [qmailtoaster] QmailToaster upgrade issue
Hi Jake, We use IMAP mail protocol in our setup and I don't see anything in IMAP4 logs: @40004ab777ab1d6f166c tcpserver: status: 0/400 @40004ab777ab20913a14 tcpserver: status: 1/400 @40004ab777ab209462ac tcpserver: pid 32583 from 10.10.13.69 @40004ab777ab209b119c tcpserver: ok 32583 redmail.redalkemi.com:xxx.xxx.xxx.xxx :10.10.13.69::4697 @40004ab777ab20a3eb3c DEBUG: Connection, ip=[10.10.13.69] Not sure what went wrong here tried and checked all possible configuration. Mahipal Jake Vickers wrote: Mahipal Singh wrote: Hi Jack, I have compared the logs and only change I can see in SMTP. I can send email from in mail client and webmail and there is no pending email in local queue checked using qmHandle. The only issue I am facing right now is when I try to receive email my mail client says no new message but there are mails stored on mail server which I can only see after restarting qmail service. Please let me know the logs you want me to check. If they're using pop3, then check the pop3 logs. If they're using imap, check the imap logs. -- Regards *M*ahipal *S*ingh http://www.redalkemi.com/profiles/mahipal.singh/ Email: mahipal.si...@redalkemi.com mailto:mahipal.si...@redalkemi.com Website: www.redalkemi.com http://www.redalkemi.com/ Sales: +1-866-272-5127, +1-646-367-8179, +1-415-315-9555 Fax: +1-866-684-0610 UK: +44-208-099-9163 Dev Office: +91-172-2645904, 2645905 India Fax: +91-172-5009009 India Skype: RedAlkemi US Skype: RedAlkemiUSA *Red*Al*_k_*emi - *Delivering /Measurable /Online Success*
Re: [qmailtoaster] QmailToaster upgrade issue
Mahipal Singh wrote: Hi Jake, We use IMAP mail protocol in our setup and I don't see anything in IMAP4 logs: @40004ab777ab1d6f166c tcpserver: status: 0/400 @40004ab777ab20913a14 tcpserver: status: 1/400 @40004ab777ab209462ac tcpserver: pid 32583 from 10.10.13.69 @40004ab777ab209b119c tcpserver: ok 32583 redmail.redalkemi.com:xxx.xxx.xxx.xxx :10.10.13.69::4697 @40004ab777ab20a3eb3c DEBUG: Connection, ip=[10.10.13.69] Not sure what went wrong here tried and checked all possible configuration. Do the new messages show if you hit the Get Mail button (without restarting qmail)?
Re: [qmailtoaster] QmailToaster upgrade issue
Restart qmail service is only option to access new messages on the server and this is happening with all emails sent from local or remote. Thanks Mahipal Jake Vickers wrote: Mahipal Singh wrote: Hi Jake, We use IMAP mail protocol in our setup and I don't see anything in IMAP4 logs: @40004ab777ab1d6f166c tcpserver: status: 0/400 @40004ab777ab20913a14 tcpserver: status: 1/400 @40004ab777ab209462ac tcpserver: pid 32583 from 10.10.13.69 @40004ab777ab209b119c tcpserver: ok 32583 redmail.redalkemi.com:xxx.xxx.xxx.xxx :10.10.13.69::4697 @40004ab777ab20a3eb3c DEBUG: Connection, ip=[10.10.13.69] Not sure what went wrong here tried and checked all possible configuration. Do the new messages show if you hit the Get Mail button (without restarting qmail)? -- Regards *M*ahipal *S*ingh http://www.redalkemi.com/profiles/mahipal.singh/ Email: mahipal.si...@redalkemi.com mailto:mahipal.si...@redalkemi.com Website: www.redalkemi.com http://www.redalkemi.com/ Sales: +1-866-272-5127, +1-646-367-8179, +1-415-315-9555 Fax: +1-866-684-0610 UK: +44-208-099-9163 Dev Office: +91-172-2645904, 2645905 India Fax: +91-172-5009009 India Skype: RedAlkemi US Skype: RedAlkemiUSA *Red*Al*_k_*emi - *Delivering /Measurable /Online Success*
Re: [qmailtoaster] QmailToaster upgrade issue
Mahipal Singh wrote: Restart qmail service is only option to access new messages on the server and this is happening with all emails sent from local or remote. Are the services running? qmailctl stat
Re: [qmailtoaster] QmailToaster upgrade issue
Yes, All services are up and running, till the time I am forced to restart qmail service to access incoming email. authlib: up (pid 6483) 96 seconds clamd: up (pid 6429) 96 seconds imap4: up (pid 6478) 96 seconds imap4-ssl: up (pid 6485) 96 seconds pop3: up (pid 6453) 96 seconds pop3-ssl: up (pid 6411) 96 seconds send: up (pid 6402) 96 seconds smtp: up (pid 6423) 96 seconds smtp2: up (pid 6430) 96 seconds spamd: up (pid 6418) 96 seconds submission: up (pid 6443) 96 seconds authlib/log: up (pid 6484) 96 seconds clamd/log: up (pid 6433) 96 seconds imap4/log: up (pid 6479) 96 seconds imap4-ssl/log: up (pid 6439) 96 seconds pop3/log: up (pid 6456) 96 seconds pop3-ssl/log: up (pid 6422) 96 seconds send/log: up (pid 6417) 96 seconds smtp2/log: up (pid 6466) 96 seconds smtp/log: up (pid 6459) 96 seconds spamd/log: up (pid 6406) 96 seconds submission/log: up (pid 6449) 96 seconds Jake Vickers wrote: Mahipal Singh wrote: Restart qmail service is only option to access new messages on the server and this is happening with all emails sent from local or remote. Are the services running? qmailctl stat -- Regards *M*ahipal *S*ingh http://www.redalkemi.com/profiles/mahipal.singh/ Email: mahipal.si...@redalkemi.com mailto:mahipal.si...@redalkemi.com Website: www.redalkemi.com http://www.redalkemi.com/ Sales: +1-866-272-5127, +1-646-367-8179, +1-415-315-9555 Fax: +1-866-684-0610 UK: +44-208-099-9163 Dev Office: +91-172-2645904, 2645905 India Fax: +91-172-5009009 India Skype: RedAlkemi US Skype: RedAlkemiUSA *Red*Al*_k_*emi - *Delivering /Measurable /Online Success*
Re: [qmailtoaster] QmailToaster upgrade issue
Mahipal Singh wrote: Yes, All services are up and running, till the time I am forced to restart qmail service to access incoming email. Do the messages show in webmail? It would be helpful if you could send us more of your logs. When you cut your logs to what you thin may be important, you may be cutting out something that denotes the issue that other eyes may see.
Re: [qmailtoaster] QmailToaster upgrade issue
It seems re installation of qmailtoaster RPM has done the trick now I am able to send and receive email at the same time from local as well as remote. Jake I really appreciate your support and time devoted to resolve the issue. Thanks again for your kind support. Jake Vickers wrote: Mahipal Singh wrote: Restart qmail service is only option to access new messages on the server and this is happening with all emails sent from local or remote. Are the services running? qmailctl stat -- Regards *M*ahipal *S*ingh http://www.redalkemi.com/profiles/mahipal.singh/ Email: mahipal.si...@redalkemi.com mailto:mahipal.si...@redalkemi.com Website: www.redalkemi.com http://www.redalkemi.com/ Sales: +1-866-272-5127, +1-646-367-8179, +1-415-315-9555 Fax: +1-866-684-0610 UK: +44-208-099-9163 Dev Office: +91-172-2645904, 2645905 India Fax: +91-172-5009009 India Skype: RedAlkemi US Skype: RedAlkemiUSA *Red*Al*_k_*emi - *Delivering /Measurable /Online Success*
Re: [qmailtoaster] QmailToaster upgrade issue
Mahipal Singh wrote: Hi All, This is my first post on QmailToaster mailing list. I have upgraded qmail toaster on my mail server running on CentOS 4.5 version to latest release of QmailToaster using instructions posted on http://wiki.qmailtoaster.com/index.php/Upgrade.sh_script. After successful upgrade I have rebooted my server and there after I am having issues in receiving email in my mail client (ThunderBird). I need to restart Qmail service every time in order to receive email from the server. Only change I have noticed in Qmail SMTP logs is policy_check @40004ab769aa23cb69fc policy_check: local - local (UNAUTHENTICATED SENDER) @40004ab769aa23cb6de4 policy_check: policy allows transmission Please help me to resolve this issue Thanks Mahipal For future reference, the script you used is extremely old. The preferred way to upgrade is to use qtp-newmodel (http://qtp.qmailtoaster.com/trac/wiki/qtp-newmodel). I've made a note of this on the wiki. -- -Eric 'shubes' - Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! - Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
RE: [qmailtoaster] upgrade toaster
./qtp-newmodel: line 318: qtp-get-pkg-list: command not found That's what I get when attempting to run qtp-newmodel For some reason, I also do not have the normal path commands either. However my PATH does have /usr/sbin in it... also, I did use yum to install the package. Glen -Original Message- From: news [mailto:n...@ger.gmane.org] On Behalf Of Eric Shubert Sent: Wednesday, April 01, 2009 6:24 PM To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] upgrade toaster Just think of CentOS as a more mature, more stable Fedora. That's really what it is. Glen Vickers wrote: I have a personal fondness for fedora and your right. My server needs a good overhaul. No budget for it. I'll attempt your suggestion though. -Original Message- From: Eric Shubert e...@shubes.net Sent: Wednesday, April 01, 2009 4:07 PM To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] upgrade toaster Glen Vickers wrote: Just a simple quick question. Is there an easy way, using the scripts y'all wrote, to upgrade a toaster install for FR6? I'm having problems with the 5.5.4 chkuser again after a reboot of the server and now I can't send out any email through either squirrelmail or outlook client, both inside and outside network. So I was going to try upgrading the package as I haven't done that in quite a while. Glen Vickers MSITM VWorks Studios CEO 801 949 7371 FR6? Do you mean FedoraCore6? If so, qtp-newmodel should handle that just fine. You really should try to find a way to get your OS upgraded though. CentOS is a much better choice for the toaster, unless you have some reason for running Fedora. -- -Eric 'shubes' - 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: testing-unsubscr...@qmailtoaster.com For additional commands, e-mail: testing-h...@qmailtoaster.com - 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: testing-unsubscr...@qmailtoaster.com For additional commands, e-mail: testing-h...@qmailtoaster.com
RE: [qmailtoaster] upgrade toaster
Please disregard, I double checked my path and it was messed up.. its working now. -Original Message- From: Glen Vickers [mailto:ldwra...@xmission.com] Sent: Thursday, April 02, 2009 10:59 AM To: qmailtoaster-list@qmailtoaster.com Subject: RE: [qmailtoaster] upgrade toaster ./qtp-newmodel: line 318: qtp-get-pkg-list: command not found That's what I get when attempting to run qtp-newmodel For some reason, I also do not have the normal path commands either. However my PATH does have /usr/sbin in it... also, I did use yum to install the package. Glen -Original Message- From: news [mailto:n...@ger.gmane.org] On Behalf Of Eric Shubert Sent: Wednesday, April 01, 2009 6:24 PM To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] upgrade toaster Just think of CentOS as a more mature, more stable Fedora. That's really what it is. Glen Vickers wrote: I have a personal fondness for fedora and your right. My server needs a good overhaul. No budget for it. I'll attempt your suggestion though. -Original Message- From: Eric Shubert e...@shubes.net Sent: Wednesday, April 01, 2009 4:07 PM To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] upgrade toaster Glen Vickers wrote: Just a simple quick question. Is there an easy way, using the scripts y'all wrote, to upgrade a toaster install for FR6? I'm having problems with the 5.5.4 chkuser again after a reboot of the server and now I can't send out any email through either squirrelmail or outlook client, both inside and outside network. So I was going to try upgrading the package as I haven't done that in quite a while. Glen Vickers MSITM VWorks Studios CEO 801 949 7371 FR6? Do you mean FedoraCore6? If so, qtp-newmodel should handle that just fine. You really should try to find a way to get your OS upgraded though. CentOS is a much better choice for the toaster, unless you have some reason for running Fedora. -- -Eric 'shubes' - 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: testing-unsubscr...@qmailtoaster.com For additional commands, e-mail: testing-h...@qmailtoaster.com - 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: testing-unsubscr...@qmailtoaster.com For additional commands, e-mail: testing-h...@qmailtoaster.com - 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: testing-unsubscr...@qmailtoaster.com For additional commands, e-mail: testing-h...@qmailtoaster.com
[qmailtoaster] upgrade toaster
Just a simple quick question. Is there an easy way, using the scripts y'all wrote, to upgrade a toaster install for FR6? I'm having problems with the 5.5.4 chkuser again after a reboot of the server and now I can't send out any email through either squirrelmail or outlook client, both inside and outside network. So I was going to try upgrading the package as I haven't done that in quite a while. Glen Vickers MSITM VWorks Studios CEO 801 949 7371
Re: [qmailtoaster] upgrade toaster
Glen Vickers wrote: Just a simple quick question. Is there an easy way, using the scripts y’all wrote, to upgrade a toaster install for FR6? I’m having problems with the 5.5.4 chkuser again after a reboot of the server and now I can’t send out any email through either squirrelmail or outlook client, both inside and outside network. So I was going to try upgrading the package as I haven’t done that in quite a while. Glen Vickers MSITM VWorks Studios CEO 801 949 7371 FR6? Do you mean FedoraCore6? If so, qtp-newmodel should handle that just fine. You really should try to find a way to get your OS upgraded though. CentOS is a much better choice for the toaster, unless you have some reason for running Fedora. -- -Eric 'shubes' - 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: testing-unsubscr...@qmailtoaster.com For additional commands, e-mail: testing-h...@qmailtoaster.com
Re: [qmailtoaster] upgrade toaster
Just think of CentOS as a more mature, more stable Fedora. That's really what it is. Glen Vickers wrote: I have a personal fondness for fedora and your right. My server needs a good overhaul. No budget for it. I'll attempt your suggestion though. -Original Message- From: Eric Shubert e...@shubes.net Sent: Wednesday, April 01, 2009 4:07 PM To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] upgrade toaster Glen Vickers wrote: Just a simple quick question. Is there an easy way, using the scripts y’all wrote, to upgrade a toaster install for FR6? I’m having problems with the 5.5.4 chkuser again after a reboot of the server and now I can’t send out any email through either squirrelmail or outlook client, both inside and outside network. So I was going to try upgrading the package as I haven’t done that in quite a while. Glen Vickers MSITM VWorks Studios CEO 801 949 7371 FR6? Do you mean FedoraCore6? If so, qtp-newmodel should handle that just fine. You really should try to find a way to get your OS upgraded though. CentOS is a much better choice for the toaster, unless you have some reason for running Fedora. -- -Eric 'shubes' - 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: testing-unsubscr...@qmailtoaster.com For additional commands, e-mail: testing-h...@qmailtoaster.com
Re: [qmailtoaster] Upgrade using qtp-newmodel of spamassassin fails
I installed perl-5.8.8-15.el5_2.1 again (happened to be the same version you have) and now I get : START Executing(--clean): /bin/sh -e /var/tmp/rpm-tmp.66524 + umask 022 + cd /usr/src/redhat/BUILD + rm -rf Mail-SpamAssassin-3.2.5 + exit 0 Installing spamassassin-toaster-3.2.5-1.3.15 in the sandbox ... error: Failed dependencies: perl(HTTP::Date) is needed by spamassassin-toaster-3.2.5-1.3.15.x86_64 perl(LWP::UserAgent) is needed by spamassassin-toaster-3.2.5-1.3.15.x86_64 END When I try to install HTTP::Date or LWP::UserAgent via CPAN, I get : HTTP::Date is up to date. LWP::UserAgent is up to date. Eric Shubert wrote: No, you'll need the whole perl package. There are other interdependent modules in the perl package, you can't necessarily just pick the one file. That, and I'm not sure that 6.43 is quite old enough. 6.44 was just the first version we noticed the problem with. It might have been introduced anywhere between 6.30 and 6.44. I'd bet money that this is your problem. Same symptoms (error messages), exactly. Wim Godden wrote: Odd thing : I just download and installed MakeMaker 6.43, but I still get the same error : Checking if your kit is complete... Looks good 'ENABLE_SSL' is not a known MakeMaker parameter name. 'SYSCONFDIR' is not a known MakeMaker parameter name. Writing Makefile for Mail::SpamAssassin Makefile written by ExtUtils::MakeMaker 6.43 But still end up with : install: cannot create regular file `/var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/local.cf.bz2': No such file or directory error: Bad exit status from /var/tmp/rpm-tmp.6482 (%install) Maybe this problem isn't related to MakeMaker in my case ? Eric Shubert wrote: Download and reinstall the perl binary rpm that corresponds to your present version (mine is perl-5.8.8-15.el5_2.1), using the --replacefiles option: # rpm --replacefiles -Uvh perl-5.8.8.*.i386.rpm Wim Godden wrote: Eric, Is there some way to go back to pre-6.44 ? Or is there a patch that I can use to upgrade my system on 6.48 ? Kind regards, Wim Eric Shubert wrote: The problem is *caused* by updating the CPAN bundle. You need a pre-6.44 version of MakeMaker for it to work. Wim Godden wrote: Thanks for the quick reply, but the problem wasn't resolved by updating the CPAN bundle. I'm running CentOS 5.2 (i386). Previous runs of qtp-newmodel ran without a glitch. I have : ExtUtils::MakeMaker 6.48 and : cpan[2] install Bundle::CPAN Test::Harness is up to date (3.16). ExtUtils::CBuilder is up to date (0.24). ExtUtils::MakeMaker is up to date (6.48). Module::Build is up to date (0.32). File::Spec is up to date (3.29). File::Temp is up to date (0.21). Scalar::Util is up to date (1.19). Test::More is up to date (0.86). Data::Dumper is up to date (2.121_08). Digest::SHA is up to date (5.47). File::HomeDir is up to date (0.84). Compress::Raw::Zlib is up to date (2.015). IO::Compress::Base is up to date (2.015). IO::Uncompress::Gunzip is up to date (2.015). Compress::Zlib is up to date (2.015). IO::Zlib is up to date (1.09). Archive::Tar is up to date (1.46). Archive::Zip is up to date (1.26). Net::Cmd is up to date (2.29). Net::FTP is up to date (2.77). Term::ReadKey is up to date (2.30). Term::ReadLine::Perl is up to date (1.0302). YAML is up to date (0.68). Text::Glob is up to date (0.08). CPAN is up to date (1.9304). File::Which is up to date (0.05). Still the same error occurring. Eric Shubert wrote: Wim Godden wrote: An upgrade of spamassassin using qtp-newmodel fails (using small union) : Building squirrelmail-toaster-1.4.17-1.3.12 ... Installing squirrelmail-toaster-1.4.17-1.3.12 in the sandbox ... Building spamassassin-toaster-3.2.5-1.3.15 ... qtp-build-rpms - rpmbuild failed for spamassassin-toaster-3.2.5-1.3.15 qtp-build-rpms - see /mnt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log Build failed, Exiting. The logfile shows : ... + find /var/tmp/spamassassin-toaster-root/usr/lib/perl5/vendor_perl/5.8.8/Mail /var/tmp/spamassassin-toaster-root/usr/lib/perl5/vendor_perl/5.8.8/spamassassin-run.pod -type d -print + sed 's...@^/var/tmp/spamassassin-toaster-r...@%dir @g' + rm -f /var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/local.cf + rm -f /var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/init.pre + install -d /var/tmp/spamassassin-toaster-root/etc + install -d /var/tmp/spamassassin-toaster-root/etc/cron.hourly + install -d /var/tmp/spamassassin-toaster-root/var/qmail/supervise/spamd + install -d /var/tmp/spamassassin-toaster-root/var/qmail/supervise/spamd/log + install -d /var/tmp/spamassassin-toaster-root/var/qmail/supervise/spamd/supervise + install -d /var/tmp/spamassassin-toaster-root/var/log/qmail + install -d /var/tmp/spamassassin-toaster-root/var/log/qmail/spamd + rm -f /var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/local.cf + rm -f /var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/v310.pre + install -m 0644
Re: [qmailtoaster] Upgrade using qtp-newmodel of spamassassin fails
rpm doesn't recognize things that are installed via CPAN, because they're not reflected in rpm's database. Use yum and the rpmforge repo to install them, and you'll be good to go. Be sure to use a fresh sandbox after you've installed anything. P.S. I'm a little surprised that qtp-newmodel didn't install those modules for you. I've added them to the dependencies, so the next release of QTP will take care of those automatically. Wim Godden wrote: I installed perl-5.8.8-15.el5_2.1 again (happened to be the same version you have) and now I get : START Executing(--clean): /bin/sh -e /var/tmp/rpm-tmp.66524 + umask 022 + cd /usr/src/redhat/BUILD + rm -rf Mail-SpamAssassin-3.2.5 + exit 0 Installing spamassassin-toaster-3.2.5-1.3.15 in the sandbox ... error: Failed dependencies: perl(HTTP::Date) is needed by spamassassin-toaster-3.2.5-1.3.15.x86_64 perl(LWP::UserAgent) is needed by spamassassin-toaster-3.2.5-1.3.15.x86_64 END When I try to install HTTP::Date or LWP::UserAgent via CPAN, I get : HTTP::Date is up to date. LWP::UserAgent is up to date. Eric Shubert wrote: No, you'll need the whole perl package. There are other interdependent modules in the perl package, you can't necessarily just pick the one file. That, and I'm not sure that 6.43 is quite old enough. 6.44 was just the first version we noticed the problem with. It might have been introduced anywhere between 6.30 and 6.44. I'd bet money that this is your problem. Same symptoms (error messages), exactly. Wim Godden wrote: Odd thing : I just download and installed MakeMaker 6.43, but I still get the same error : Checking if your kit is complete... Looks good 'ENABLE_SSL' is not a known MakeMaker parameter name. 'SYSCONFDIR' is not a known MakeMaker parameter name. Writing Makefile for Mail::SpamAssassin Makefile written by ExtUtils::MakeMaker 6.43 But still end up with : install: cannot create regular file `/var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/local.cf.bz2': No such file or directory error: Bad exit status from /var/tmp/rpm-tmp.6482 (%install) Maybe this problem isn't related to MakeMaker in my case ? Eric Shubert wrote: Download and reinstall the perl binary rpm that corresponds to your present version (mine is perl-5.8.8-15.el5_2.1), using the --replacefiles option: # rpm --replacefiles -Uvh perl-5.8.8.*.i386.rpm Wim Godden wrote: Eric, Is there some way to go back to pre-6.44 ? Or is there a patch that I can use to upgrade my system on 6.48 ? Kind regards, Wim Eric Shubert wrote: The problem is *caused* by updating the CPAN bundle. You need a pre-6.44 version of MakeMaker for it to work. Wim Godden wrote: Thanks for the quick reply, but the problem wasn't resolved by updating the CPAN bundle. I'm running CentOS 5.2 (i386). Previous runs of qtp-newmodel ran without a glitch. I have : ExtUtils::MakeMaker 6.48 and : cpan[2] install Bundle::CPAN Test::Harness is up to date (3.16). ExtUtils::CBuilder is up to date (0.24). ExtUtils::MakeMaker is up to date (6.48). Module::Build is up to date (0.32). File::Spec is up to date (3.29). File::Temp is up to date (0.21). Scalar::Util is up to date (1.19). Test::More is up to date (0.86). Data::Dumper is up to date (2.121_08). Digest::SHA is up to date (5.47). File::HomeDir is up to date (0.84). Compress::Raw::Zlib is up to date (2.015). IO::Compress::Base is up to date (2.015). IO::Uncompress::Gunzip is up to date (2.015). Compress::Zlib is up to date (2.015). IO::Zlib is up to date (1.09). Archive::Tar is up to date (1.46). Archive::Zip is up to date (1.26). Net::Cmd is up to date (2.29). Net::FTP is up to date (2.77). Term::ReadKey is up to date (2.30). Term::ReadLine::Perl is up to date (1.0302). YAML is up to date (0.68). Text::Glob is up to date (0.08). CPAN is up to date (1.9304). File::Which is up to date (0.05). Still the same error occurring. Eric Shubert wrote: Wim Godden wrote: An upgrade of spamassassin using qtp-newmodel fails (using small union) : Building squirrelmail-toaster-1.4.17-1.3.12 ... Installing squirrelmail-toaster-1.4.17-1.3.12 in the sandbox ... Building spamassassin-toaster-3.2.5-1.3.15 ... qtp-build-rpms - rpmbuild failed for spamassassin-toaster-3.2.5-1.3.15 qtp-build-rpms - see /mnt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log Build failed, Exiting. The logfile shows : ... + find /var/tmp/spamassassin-toaster-root/usr/lib/perl5/vendor_perl/5.8.8/Mail /var/tmp/spamassassin-toaster-root/usr/lib/perl5/vendor_perl/5.8.8/spamassassin-run.pod -type d -print + sed 's...@^/var/tmp/spamassassin-toaster-r...@%dir @g' + rm -f /var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/local.cf + rm -f /var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/init.pre + install -d /var/tmp/spamassassin-toaster-root/etc + install -d /var/tmp/spamassassin-toaster-root/etc/cron.hourly + install -d /var/tmp/spamassassin-toaster-root/var/qmail/supervise/spamd + install -d
Re: [qmailtoaster] Upgrade using qtp-newmodel of spamassassin fails
Adding them manually through rpmforge did the job. However, a new problem turns up now. I can receive SMTP connections from most hosts, but when I try from an internal host, I get a timeout. What happens : telnet 192.168.1.138 110 Trying 192.168.1.138... Connected to local.vpn.home (192.168.1.138). Escape character is '^]'. +OK 3872.1237241...@brussels3.firstlinknetworks.com ^] telnet quit Connection closed. telnet 192.168.1.138 25 Trying 192.168.1.138... Connected to local.vpn.home (192.168.1.138). and then nothing happens. Although I'm connected, I get nothing. I thought it was a DNS problem, but doing an nslookup of the host works just fine. If I wait a very long time, I eventually get the greeting. But no mail client waits that long. Any ideas ? Eric Shubert wrote: rpm doesn't recognize things that are installed via CPAN, because they're not reflected in rpm's database. Use yum and the rpmforge repo to install them, and you'll be good to go. Be sure to use a fresh sandbox after you've installed anything. P.S. I'm a little surprised that qtp-newmodel didn't install those modules for you. I've added them to the dependencies, so the next release of QTP will take care of those automatically. Wim Godden wrote: I installed perl-5.8.8-15.el5_2.1 again (happened to be the same version you have) and now I get : START Executing(--clean): /bin/sh -e /var/tmp/rpm-tmp.66524 + umask 022 + cd /usr/src/redhat/BUILD + rm -rf Mail-SpamAssassin-3.2.5 + exit 0 Installing spamassassin-toaster-3.2.5-1.3.15 in the sandbox ... error: Failed dependencies: perl(HTTP::Date) is needed by spamassassin-toaster-3.2.5-1.3.15.x86_64 perl(LWP::UserAgent) is needed by spamassassin-toaster-3.2.5-1.3.15.x86_64 END When I try to install HTTP::Date or LWP::UserAgent via CPAN, I get : HTTP::Date is up to date. LWP::UserAgent is up to date. Eric Shubert wrote: No, you'll need the whole perl package. There are other interdependent modules in the perl package, you can't necessarily just pick the one file. That, and I'm not sure that 6.43 is quite old enough. 6.44 was just the first version we noticed the problem with. It might have been introduced anywhere between 6.30 and 6.44. I'd bet money that this is your problem. Same symptoms (error messages), exactly. Wim Godden wrote: Odd thing : I just download and installed MakeMaker 6.43, but I still get the same error : Checking if your kit is complete... Looks good 'ENABLE_SSL' is not a known MakeMaker parameter name. 'SYSCONFDIR' is not a known MakeMaker parameter name. Writing Makefile for Mail::SpamAssassin Makefile written by ExtUtils::MakeMaker 6.43 But still end up with : install: cannot create regular file `/var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/local.cf.bz2': No such file or directory error: Bad exit status from /var/tmp/rpm-tmp.6482 (%install) Maybe this problem isn't related to MakeMaker in my case ? Eric Shubert wrote: Download and reinstall the perl binary rpm that corresponds to your present version (mine is perl-5.8.8-15.el5_2.1), using the --replacefiles option: # rpm --replacefiles -Uvh perl-5.8.8.*.i386.rpm Wim Godden wrote: Eric, Is there some way to go back to pre-6.44 ? Or is there a patch that I can use to upgrade my system on 6.48 ? Kind regards, Wim Eric Shubert wrote: The problem is *caused* by updating the CPAN bundle. You need a pre-6.44 version of MakeMaker for it to work. Wim Godden wrote: Thanks for the quick reply, but the problem wasn't resolved by updating the CPAN bundle. I'm running CentOS 5.2 (i386). Previous runs of qtp-newmodel ran without a glitch. I have : ExtUtils::MakeMaker 6.48 and : cpan[2] install Bundle::CPAN Test::Harness is up to date (3.16). ExtUtils::CBuilder is up to date (0.24). ExtUtils::MakeMaker is up to date (6.48). Module::Build is up to date (0.32). File::Spec is up to date (3.29). File::Temp is up to date (0.21). Scalar::Util is up to date (1.19). Test::More is up to date (0.86). Data::Dumper is up to date (2.121_08). Digest::SHA is up to date (5.47). File::HomeDir is up to date (0.84). Compress::Raw::Zlib is up to date (2.015). IO::Compress::Base is up to date (2.015). IO::Uncompress::Gunzip is up to date (2.015). Compress::Zlib is up to date (2.015). IO::Zlib is up to date (1.09). Archive::Tar is up to date (1.46). Archive::Zip is up to date (1.26). Net::Cmd is up to date (2.29). Net::FTP is up to date (2.77). Term::ReadKey is up to date (2.30). Term::ReadLine::Perl is up to date (1.0302). YAML is up to date (0.68). Text::Glob is up to date (0.08). CPAN is up to date (1.9304). File::Which is up to date (0.05). Still the same error occurring. Eric Shubert wrote: Wim Godden wrote: An upgrade of spamassassin using qtp-newmodel fails (using small union) : Building squirrelmail-toaster-1.4.17-1.3.12 ... Installing squirrelmail-toaster-1.4.17-1.3.12 in the sandbox ... Building spamassassin-toaster-3.2.5-1.3.15 ... qtp-build-rpms -
Re: [qmailtoaster] Upgrade using qtp-newmodel of spamassassin fails
The default toaster firewall is a little over zealous (or retarded, depending on your perspective). You need to add a rule to your firewall.sh script to allow local traffic, like so: # shubes 5/16/06 - accept packets from local nets iptables -A INPUT -s 192.168.1.0/255.255.255.0 -j ACCEPT Then rerun the script to update iptables. Wim Godden wrote: Adding them manually through rpmforge did the job. However, a new problem turns up now. I can receive SMTP connections from most hosts, but when I try from an internal host, I get a timeout. What happens : telnet 192.168.1.138 110 Trying 192.168.1.138... Connected to local.vpn.home (192.168.1.138). Escape character is '^]'. +OK 3872.1237241...@brussels3.firstlinknetworks.com ^] telnet quit Connection closed. telnet 192.168.1.138 25 Trying 192.168.1.138... Connected to local.vpn.home (192.168.1.138). and then nothing happens. Although I'm connected, I get nothing. I thought it was a DNS problem, but doing an nslookup of the host works just fine. If I wait a very long time, I eventually get the greeting. But no mail client waits that long. Any ideas ? Eric Shubert wrote: rpm doesn't recognize things that are installed via CPAN, because they're not reflected in rpm's database. Use yum and the rpmforge repo to install them, and you'll be good to go. Be sure to use a fresh sandbox after you've installed anything. P.S. I'm a little surprised that qtp-newmodel didn't install those modules for you. I've added them to the dependencies, so the next release of QTP will take care of those automatically. Wim Godden wrote: I installed perl-5.8.8-15.el5_2.1 again (happened to be the same version you have) and now I get : START Executing(--clean): /bin/sh -e /var/tmp/rpm-tmp.66524 + umask 022 + cd /usr/src/redhat/BUILD + rm -rf Mail-SpamAssassin-3.2.5 + exit 0 Installing spamassassin-toaster-3.2.5-1.3.15 in the sandbox ... error: Failed dependencies: perl(HTTP::Date) is needed by spamassassin-toaster-3.2.5-1.3.15.x86_64 perl(LWP::UserAgent) is needed by spamassassin-toaster-3.2.5-1.3.15.x86_64 END When I try to install HTTP::Date or LWP::UserAgent via CPAN, I get : HTTP::Date is up to date. LWP::UserAgent is up to date. Eric Shubert wrote: No, you'll need the whole perl package. There are other interdependent modules in the perl package, you can't necessarily just pick the one file. That, and I'm not sure that 6.43 is quite old enough. 6.44 was just the first version we noticed the problem with. It might have been introduced anywhere between 6.30 and 6.44. I'd bet money that this is your problem. Same symptoms (error messages), exactly. Wim Godden wrote: Odd thing : I just download and installed MakeMaker 6.43, but I still get the same error : Checking if your kit is complete... Looks good 'ENABLE_SSL' is not a known MakeMaker parameter name. 'SYSCONFDIR' is not a known MakeMaker parameter name. Writing Makefile for Mail::SpamAssassin Makefile written by ExtUtils::MakeMaker 6.43 But still end up with : install: cannot create regular file `/var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/local.cf.bz2': No such file or directory error: Bad exit status from /var/tmp/rpm-tmp.6482 (%install) Maybe this problem isn't related to MakeMaker in my case ? Eric Shubert wrote: Download and reinstall the perl binary rpm that corresponds to your present version (mine is perl-5.8.8-15.el5_2.1), using the --replacefiles option: # rpm --replacefiles -Uvh perl-5.8.8.*.i386.rpm Wim Godden wrote: Eric, Is there some way to go back to pre-6.44 ? Or is there a patch that I can use to upgrade my system on 6.48 ? Kind regards, Wim Eric Shubert wrote: The problem is *caused* by updating the CPAN bundle. You need a pre-6.44 version of MakeMaker for it to work. Wim Godden wrote: Thanks for the quick reply, but the problem wasn't resolved by updating the CPAN bundle. I'm running CentOS 5.2 (i386). Previous runs of qtp-newmodel ran without a glitch. I have : ExtUtils::MakeMaker 6.48 and : cpan[2] install Bundle::CPAN Test::Harness is up to date (3.16). ExtUtils::CBuilder is up to date (0.24). ExtUtils::MakeMaker is up to date (6.48). Module::Build is up to date (0.32). File::Spec is up to date (3.29). File::Temp is up to date (0.21). Scalar::Util is up to date (1.19). Test::More is up to date (0.86). Data::Dumper is up to date (2.121_08). Digest::SHA is up to date (5.47). File::HomeDir is up to date (0.84). Compress::Raw::Zlib is up to date (2.015). IO::Compress::Base is up to date (2.015). IO::Uncompress::Gunzip is up to date (2.015). Compress::Zlib is up to date (2.015). IO::Zlib is up to date (1.09). Archive::Tar is up to date (1.46). Archive::Zip is up to date (1.26). Net::Cmd is up to date (2.29). Net::FTP is up to date (2.77). Term::ReadKey is up to date (2.30). Term::ReadLine::Perl is up to date (1.0302). YAML is up to date (0.68). Text::Glob is up to date (0.08). CPAN is up to date (1.9304).
Re: [qmailtoaster] Upgrade using qtp-newmodel of spamassassin fails
I can connect just fine, but it takes about 30 seconds for the greeting 220 brussels3.firstlinknetworks.com - Welcome to Qmail Toaster Ver. 1.3 SMTP Server ESMTP to show up on SMTP. On POP3, it shows right away. Could it have something to do with the blacklist in /var/qmail/control/blacklists : -r zen.spamhaus.org -r bl.spamcop.net -r list.dsbl.org -r cbl.abuseat.org Of these hosts, only 1 still exists ? Eric Shubert wrote: The default toaster firewall is a little over zealous (or retarded, depending on your perspective). You need to add a rule to your firewall.sh script to allow local traffic, like so: # shubes 5/16/06 - accept packets from local nets iptables -A INPUT -s 192.168.1.0/255.255.255.0 -j ACCEPT Then rerun the script to update iptables. Wim Godden wrote: Adding them manually through rpmforge did the job. However, a new problem turns up now. I can receive SMTP connections from most hosts, but when I try from an internal host, I get a timeout. What happens : telnet 192.168.1.138 110 Trying 192.168.1.138... Connected to local.vpn.home (192.168.1.138). Escape character is '^]'. +OK 3872.1237241...@brussels3.firstlinknetworks.com ^] telnet quit Connection closed. telnet 192.168.1.138 25 Trying 192.168.1.138... Connected to local.vpn.home (192.168.1.138). and then nothing happens. Although I'm connected, I get nothing. I thought it was a DNS problem, but doing an nslookup of the host works just fine. If I wait a very long time, I eventually get the greeting. But no mail client waits that long. Any ideas ? Eric Shubert wrote: rpm doesn't recognize things that are installed via CPAN, because they're not reflected in rpm's database. Use yum and the rpmforge repo to install them, and you'll be good to go. Be sure to use a fresh sandbox after you've installed anything. P.S. I'm a little surprised that qtp-newmodel didn't install those modules for you. I've added them to the dependencies, so the next release of QTP will take care of those automatically. Wim Godden wrote: I installed perl-5.8.8-15.el5_2.1 again (happened to be the same version you have) and now I get : START Executing(--clean): /bin/sh -e /var/tmp/rpm-tmp.66524 + umask 022 + cd /usr/src/redhat/BUILD + rm -rf Mail-SpamAssassin-3.2.5 + exit 0 Installing spamassassin-toaster-3.2.5-1.3.15 in the sandbox ... error: Failed dependencies: perl(HTTP::Date) is needed by spamassassin-toaster-3.2.5-1.3.15.x86_64 perl(LWP::UserAgent) is needed by spamassassin-toaster-3.2.5-1.3.15.x86_64 END When I try to install HTTP::Date or LWP::UserAgent via CPAN, I get : HTTP::Date is up to date. LWP::UserAgent is up to date. Eric Shubert wrote: No, you'll need the whole perl package. There are other interdependent modules in the perl package, you can't necessarily just pick the one file. That, and I'm not sure that 6.43 is quite old enough. 6.44 was just the first version we noticed the problem with. It might have been introduced anywhere between 6.30 and 6.44. I'd bet money that this is your problem. Same symptoms (error messages), exactly. Wim Godden wrote: Odd thing : I just download and installed MakeMaker 6.43, but I still get the same error : Checking if your kit is complete... Looks good 'ENABLE_SSL' is not a known MakeMaker parameter name. 'SYSCONFDIR' is not a known MakeMaker parameter name. Writing Makefile for Mail::SpamAssassin Makefile written by ExtUtils::MakeMaker 6.43 But still end up with : install: cannot create regular file `/var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/local.cf.bz2': No such file or directory error: Bad exit status from /var/tmp/rpm-tmp.6482 (%install) Maybe this problem isn't related to MakeMaker in my case ? Eric Shubert wrote: Download and reinstall the perl binary rpm that corresponds to your present version (mine is perl-5.8.8-15.el5_2.1), using the --replacefiles option: # rpm --replacefiles -Uvh perl-5.8.8.*.i386.rpm Wim Godden wrote: Eric, Is there some way to go back to pre-6.44 ? Or is there a patch that I can use to upgrade my system on 6.48 ? Kind regards, Wim Eric Shubert wrote: The problem is *caused* by updating the CPAN bundle. You need a pre-6.44 version of MakeMaker for it to work. Wim Godden wrote: Thanks for the quick reply, but the problem wasn't resolved by updating the CPAN bundle. I'm running CentOS 5.2 (i386). Previous runs of qtp-newmodel ran without a glitch. I have : ExtUtils::MakeMaker 6.48 and : cpan[2] install Bundle::CPAN Test::Harness is up to date (3.16). ExtUtils::CBuilder is up to date (0.24). ExtUtils::MakeMaker is up to date (6.48). Module::Build is up to date (0.32). File::Spec is up to date (3.29). File::Temp is up to date (0.21). Scalar::Util is up to date (1.19). Test::More is up to date (0.86). Data::Dumper is up to date (2.121_08). Digest::SHA is up to date (5.47). File::HomeDir is up to date (0.84). Compress::Raw::Zlib is up to date (2.015). IO::Compress::Base is up to
Re: [qmailtoaster] Upgrade using qtp-newmodel of spamassassin fails
Yeah. I'd get rid of the last 2 you have listed (for various reasons). Wim Godden wrote: I can connect just fine, but it takes about 30 seconds for the greeting 220 brussels3.firstlinknetworks.com - Welcome to Qmail Toaster Ver. 1.3 SMTP Server ESMTP to show up on SMTP. On POP3, it shows right away. Could it have something to do with the blacklist in /var/qmail/control/blacklists : -r zen.spamhaus.org -r bl.spamcop.net -r list.dsbl.org -r cbl.abuseat.org Of these hosts, only 1 still exists ? Eric Shubert wrote: The default toaster firewall is a little over zealous (or retarded, depending on your perspective). You need to add a rule to your firewall.sh script to allow local traffic, like so: # shubes 5/16/06 - accept packets from local nets iptables -A INPUT -s 192.168.1.0/255.255.255.0 -j ACCEPT Then rerun the script to update iptables. Wim Godden wrote: Adding them manually through rpmforge did the job. However, a new problem turns up now. I can receive SMTP connections from most hosts, but when I try from an internal host, I get a timeout. What happens : telnet 192.168.1.138 110 Trying 192.168.1.138... Connected to local.vpn.home (192.168.1.138). Escape character is '^]'. +OK 3872.1237241...@brussels3.firstlinknetworks.com ^] telnet quit Connection closed. telnet 192.168.1.138 25 Trying 192.168.1.138... Connected to local.vpn.home (192.168.1.138). and then nothing happens. Although I'm connected, I get nothing. I thought it was a DNS problem, but doing an nslookup of the host works just fine. If I wait a very long time, I eventually get the greeting. But no mail client waits that long. Any ideas ? Eric Shubert wrote: rpm doesn't recognize things that are installed via CPAN, because they're not reflected in rpm's database. Use yum and the rpmforge repo to install them, and you'll be good to go. Be sure to use a fresh sandbox after you've installed anything. P.S. I'm a little surprised that qtp-newmodel didn't install those modules for you. I've added them to the dependencies, so the next release of QTP will take care of those automatically. Wim Godden wrote: I installed perl-5.8.8-15.el5_2.1 again (happened to be the same version you have) and now I get : START Executing(--clean): /bin/sh -e /var/tmp/rpm-tmp.66524 + umask 022 + cd /usr/src/redhat/BUILD + rm -rf Mail-SpamAssassin-3.2.5 + exit 0 Installing spamassassin-toaster-3.2.5-1.3.15 in the sandbox ... error: Failed dependencies: perl(HTTP::Date) is needed by spamassassin-toaster-3.2.5-1.3.15.x86_64 perl(LWP::UserAgent) is needed by spamassassin-toaster-3.2.5-1.3.15.x86_64 END When I try to install HTTP::Date or LWP::UserAgent via CPAN, I get : HTTP::Date is up to date. LWP::UserAgent is up to date. Eric Shubert wrote: No, you'll need the whole perl package. There are other interdependent modules in the perl package, you can't necessarily just pick the one file. That, and I'm not sure that 6.43 is quite old enough. 6.44 was just the first version we noticed the problem with. It might have been introduced anywhere between 6.30 and 6.44. I'd bet money that this is your problem. Same symptoms (error messages), exactly. Wim Godden wrote: Odd thing : I just download and installed MakeMaker 6.43, but I still get the same error : Checking if your kit is complete... Looks good 'ENABLE_SSL' is not a known MakeMaker parameter name. 'SYSCONFDIR' is not a known MakeMaker parameter name. Writing Makefile for Mail::SpamAssassin Makefile written by ExtUtils::MakeMaker 6.43 But still end up with : install: cannot create regular file `/var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/local.cf.bz2': No such file or directory error: Bad exit status from /var/tmp/rpm-tmp.6482 (%install) Maybe this problem isn't related to MakeMaker in my case ? Eric Shubert wrote: Download and reinstall the perl binary rpm that corresponds to your present version (mine is perl-5.8.8-15.el5_2.1), using the --replacefiles option: # rpm --replacefiles -Uvh perl-5.8.8.*.i386.rpm Wim Godden wrote: Eric, Is there some way to go back to pre-6.44 ? Or is there a patch that I can use to upgrade my system on 6.48 ? Kind regards, Wim Eric Shubert wrote: The problem is *caused* by updating the CPAN bundle. You need a pre-6.44 version of MakeMaker for it to work. Wim Godden wrote: Thanks for the quick reply, but the problem wasn't resolved by updating the CPAN bundle. I'm running CentOS 5.2 (i386). Previous runs of qtp-newmodel ran without a glitch. I have : ExtUtils::MakeMaker 6.48 and : cpan[2] install Bundle::CPAN Test::Harness is up to date (3.16). ExtUtils::CBuilder is up to date (0.24). ExtUtils::MakeMaker is up to date (6.48). Module::Build is up to date (0.32). File::Spec is up to date (3.29). File::Temp is up to date (0.21). Scalar::Util is up to date (1.19). Test::More is up to date (0.86). Data::Dumper is up to date (2.121_08). Digest::SHA is up to date (5.47). File::HomeDir is
Re: [qmailtoaster] Upgrade using qtp-newmodel of spamassassin fails
Thanks for the quick reply, but the problem wasn't resolved by updating the CPAN bundle. I'm running CentOS 5.2 (i386). Previous runs of qtp-newmodel ran without a glitch. I have : ExtUtils::MakeMaker 6.48 and : cpan[2] install Bundle::CPAN Test::Harness is up to date (3.16). ExtUtils::CBuilder is up to date (0.24). ExtUtils::MakeMaker is up to date (6.48). Module::Build is up to date (0.32). File::Spec is up to date (3.29). File::Temp is up to date (0.21). Scalar::Util is up to date (1.19). Test::More is up to date (0.86). Data::Dumper is up to date (2.121_08). Digest::SHA is up to date (5.47). File::HomeDir is up to date (0.84). Compress::Raw::Zlib is up to date (2.015). IO::Compress::Base is up to date (2.015). IO::Uncompress::Gunzip is up to date (2.015). Compress::Zlib is up to date (2.015). IO::Zlib is up to date (1.09). Archive::Tar is up to date (1.46). Archive::Zip is up to date (1.26). Net::Cmd is up to date (2.29). Net::FTP is up to date (2.77). Term::ReadKey is up to date (2.30). Term::ReadLine::Perl is up to date (1.0302). YAML is up to date (0.68). Text::Glob is up to date (0.08). CPAN is up to date (1.9304). File::Which is up to date (0.05). Still the same error occurring. Eric Shubert wrote: Wim Godden wrote: An upgrade of spamassassin using qtp-newmodel fails (using small union) : Building squirrelmail-toaster-1.4.17-1.3.12 ... Installing squirrelmail-toaster-1.4.17-1.3.12 in the sandbox ... Building spamassassin-toaster-3.2.5-1.3.15 ... qtp-build-rpms - rpmbuild failed for spamassassin-toaster-3.2.5-1.3.15 qtp-build-rpms - see /mnt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log Build failed, Exiting. The logfile shows : ... + find /var/tmp/spamassassin-toaster-root/usr/lib/perl5/vendor_perl/5.8.8/Mail /var/tmp/spamassassin-toaster-root/usr/lib/perl5/vendor_perl/5.8.8/spamassassin-run.pod -type d -print + sed 's...@^/var/tmp/spamassassin-toaster-r...@%dir @g' + rm -f /var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/local.cf + rm -f /var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/init.pre + install -d /var/tmp/spamassassin-toaster-root/etc + install -d /var/tmp/spamassassin-toaster-root/etc/cron.hourly + install -d /var/tmp/spamassassin-toaster-root/var/qmail/supervise/spamd + install -d /var/tmp/spamassassin-toaster-root/var/qmail/supervise/spamd/log + install -d /var/tmp/spamassassin-toaster-root/var/qmail/supervise/spamd/supervise + install -d /var/tmp/spamassassin-toaster-root/var/log/qmail + install -d /var/tmp/spamassassin-toaster-root/var/log/qmail/spamd + rm -f /var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/local.cf + rm -f /var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/v310.pre + install -m 0644 /usr/src/redhat/SOURCES/qmailtoaster.local.cf.bz2 /var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/local.cf.bz2 install: cannot create regular file `/var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/local.cf.bz2': No such file or directory error: Bad exit status from /var/tmp/rpm-tmp.25006 (%install) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.25006 (%install) Any ideas what might be causing this ? Yep. http://www.mail-archive.com/qmailtoaster-list@qmailtoaster.com/msg18819.html Follow the thread. - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Upgrade using qtp-newmodel of spamassassin fails
The problem is *caused* by updating the CPAN bundle. You need a pre-6.44 version of MakeMaker for it to work. Wim Godden wrote: Thanks for the quick reply, but the problem wasn't resolved by updating the CPAN bundle. I'm running CentOS 5.2 (i386). Previous runs of qtp-newmodel ran without a glitch. I have : ExtUtils::MakeMaker 6.48 and : cpan[2] install Bundle::CPAN Test::Harness is up to date (3.16). ExtUtils::CBuilder is up to date (0.24). ExtUtils::MakeMaker is up to date (6.48). Module::Build is up to date (0.32). File::Spec is up to date (3.29). File::Temp is up to date (0.21). Scalar::Util is up to date (1.19). Test::More is up to date (0.86). Data::Dumper is up to date (2.121_08). Digest::SHA is up to date (5.47). File::HomeDir is up to date (0.84). Compress::Raw::Zlib is up to date (2.015). IO::Compress::Base is up to date (2.015). IO::Uncompress::Gunzip is up to date (2.015). Compress::Zlib is up to date (2.015). IO::Zlib is up to date (1.09). Archive::Tar is up to date (1.46). Archive::Zip is up to date (1.26). Net::Cmd is up to date (2.29). Net::FTP is up to date (2.77). Term::ReadKey is up to date (2.30). Term::ReadLine::Perl is up to date (1.0302). YAML is up to date (0.68). Text::Glob is up to date (0.08). CPAN is up to date (1.9304). File::Which is up to date (0.05). Still the same error occurring. Eric Shubert wrote: Wim Godden wrote: An upgrade of spamassassin using qtp-newmodel fails (using small union) : Building squirrelmail-toaster-1.4.17-1.3.12 ... Installing squirrelmail-toaster-1.4.17-1.3.12 in the sandbox ... Building spamassassin-toaster-3.2.5-1.3.15 ... qtp-build-rpms - rpmbuild failed for spamassassin-toaster-3.2.5-1.3.15 qtp-build-rpms - see /mnt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log Build failed, Exiting. The logfile shows : ... + find /var/tmp/spamassassin-toaster-root/usr/lib/perl5/vendor_perl/5.8.8/Mail /var/tmp/spamassassin-toaster-root/usr/lib/perl5/vendor_perl/5.8.8/spamassassin-run.pod -type d -print + sed 's...@^/var/tmp/spamassassin-toaster-r...@%dir @g' + rm -f /var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/local.cf + rm -f /var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/init.pre + install -d /var/tmp/spamassassin-toaster-root/etc + install -d /var/tmp/spamassassin-toaster-root/etc/cron.hourly + install -d /var/tmp/spamassassin-toaster-root/var/qmail/supervise/spamd + install -d /var/tmp/spamassassin-toaster-root/var/qmail/supervise/spamd/log + install -d /var/tmp/spamassassin-toaster-root/var/qmail/supervise/spamd/supervise + install -d /var/tmp/spamassassin-toaster-root/var/log/qmail + install -d /var/tmp/spamassassin-toaster-root/var/log/qmail/spamd + rm -f /var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/local.cf + rm -f /var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/v310.pre + install -m 0644 /usr/src/redhat/SOURCES/qmailtoaster.local.cf.bz2 /var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/local.cf.bz2 install: cannot create regular file `/var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/local.cf.bz2': No such file or directory error: Bad exit status from /var/tmp/rpm-tmp.25006 (%install) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.25006 (%install) Any ideas what might be causing this ? Yep. http://www.mail-archive.com/qmailtoaster-list@qmailtoaster.com/msg18819.html Follow the thread. -- -Eric 'shubes' - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Upgrade using qtp-newmodel of spamassassin fails
Eric, Is there some way to go back to pre-6.44 ? Or is there a patch that I can use to upgrade my system on 6.48 ? Kind regards, Wim Eric Shubert wrote: The problem is *caused* by updating the CPAN bundle. You need a pre-6.44 version of MakeMaker for it to work. Wim Godden wrote: Thanks for the quick reply, but the problem wasn't resolved by updating the CPAN bundle. I'm running CentOS 5.2 (i386). Previous runs of qtp-newmodel ran without a glitch. I have : ExtUtils::MakeMaker 6.48 and : cpan[2] install Bundle::CPAN Test::Harness is up to date (3.16). ExtUtils::CBuilder is up to date (0.24). ExtUtils::MakeMaker is up to date (6.48). Module::Build is up to date (0.32). File::Spec is up to date (3.29). File::Temp is up to date (0.21). Scalar::Util is up to date (1.19). Test::More is up to date (0.86). Data::Dumper is up to date (2.121_08). Digest::SHA is up to date (5.47). File::HomeDir is up to date (0.84). Compress::Raw::Zlib is up to date (2.015). IO::Compress::Base is up to date (2.015). IO::Uncompress::Gunzip is up to date (2.015). Compress::Zlib is up to date (2.015). IO::Zlib is up to date (1.09). Archive::Tar is up to date (1.46). Archive::Zip is up to date (1.26). Net::Cmd is up to date (2.29). Net::FTP is up to date (2.77). Term::ReadKey is up to date (2.30). Term::ReadLine::Perl is up to date (1.0302). YAML is up to date (0.68). Text::Glob is up to date (0.08). CPAN is up to date (1.9304). File::Which is up to date (0.05). Still the same error occurring. Eric Shubert wrote: Wim Godden wrote: An upgrade of spamassassin using qtp-newmodel fails (using small union) : Building squirrelmail-toaster-1.4.17-1.3.12 ... Installing squirrelmail-toaster-1.4.17-1.3.12 in the sandbox ... Building spamassassin-toaster-3.2.5-1.3.15 ... qtp-build-rpms - rpmbuild failed for spamassassin-toaster-3.2.5-1.3.15 qtp-build-rpms - see /mnt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log Build failed, Exiting. The logfile shows : ... + find /var/tmp/spamassassin-toaster-root/usr/lib/perl5/vendor_perl/5.8.8/Mail /var/tmp/spamassassin-toaster-root/usr/lib/perl5/vendor_perl/5.8.8/spamassassin-run.pod -type d -print + sed 's...@^/var/tmp/spamassassin-toaster-r...@%dir @g' + rm -f /var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/local.cf + rm -f /var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/init.pre + install -d /var/tmp/spamassassin-toaster-root/etc + install -d /var/tmp/spamassassin-toaster-root/etc/cron.hourly + install -d /var/tmp/spamassassin-toaster-root/var/qmail/supervise/spamd + install -d /var/tmp/spamassassin-toaster-root/var/qmail/supervise/spamd/log + install -d /var/tmp/spamassassin-toaster-root/var/qmail/supervise/spamd/supervise + install -d /var/tmp/spamassassin-toaster-root/var/log/qmail + install -d /var/tmp/spamassassin-toaster-root/var/log/qmail/spamd + rm -f /var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/local.cf + rm -f /var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/v310.pre + install -m 0644 /usr/src/redhat/SOURCES/qmailtoaster.local.cf.bz2 /var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/local.cf.bz2 install: cannot create regular file `/var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/local.cf.bz2': No such file or directory error: Bad exit status from /var/tmp/rpm-tmp.25006 (%install) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.25006 (%install) Any ideas what might be causing this ? Yep. http://www.mail-archive.com/qmailtoaster-list@qmailtoaster.com/msg18819.html Follow the thread. - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Upgrade using qtp-newmodel of spamassassin fails
Download and reinstall the perl binary rpm that corresponds to your present version (mine is perl-5.8.8-15.el5_2.1), using the --replacefiles option: # rpm --replacefiles -Uvh perl-5.8.8.*.i386.rpm Wim Godden wrote: Eric, Is there some way to go back to pre-6.44 ? Or is there a patch that I can use to upgrade my system on 6.48 ? Kind regards, Wim Eric Shubert wrote: The problem is *caused* by updating the CPAN bundle. You need a pre-6.44 version of MakeMaker for it to work. Wim Godden wrote: Thanks for the quick reply, but the problem wasn't resolved by updating the CPAN bundle. I'm running CentOS 5.2 (i386). Previous runs of qtp-newmodel ran without a glitch. I have : ExtUtils::MakeMaker 6.48 and : cpan[2] install Bundle::CPAN Test::Harness is up to date (3.16). ExtUtils::CBuilder is up to date (0.24). ExtUtils::MakeMaker is up to date (6.48). Module::Build is up to date (0.32). File::Spec is up to date (3.29). File::Temp is up to date (0.21). Scalar::Util is up to date (1.19). Test::More is up to date (0.86). Data::Dumper is up to date (2.121_08). Digest::SHA is up to date (5.47). File::HomeDir is up to date (0.84). Compress::Raw::Zlib is up to date (2.015). IO::Compress::Base is up to date (2.015). IO::Uncompress::Gunzip is up to date (2.015). Compress::Zlib is up to date (2.015). IO::Zlib is up to date (1.09). Archive::Tar is up to date (1.46). Archive::Zip is up to date (1.26). Net::Cmd is up to date (2.29). Net::FTP is up to date (2.77). Term::ReadKey is up to date (2.30). Term::ReadLine::Perl is up to date (1.0302). YAML is up to date (0.68). Text::Glob is up to date (0.08). CPAN is up to date (1.9304). File::Which is up to date (0.05). Still the same error occurring. Eric Shubert wrote: Wim Godden wrote: An upgrade of spamassassin using qtp-newmodel fails (using small union) : Building squirrelmail-toaster-1.4.17-1.3.12 ... Installing squirrelmail-toaster-1.4.17-1.3.12 in the sandbox ... Building spamassassin-toaster-3.2.5-1.3.15 ... qtp-build-rpms - rpmbuild failed for spamassassin-toaster-3.2.5-1.3.15 qtp-build-rpms - see /mnt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log Build failed, Exiting. The logfile shows : ... + find /var/tmp/spamassassin-toaster-root/usr/lib/perl5/vendor_perl/5.8.8/Mail /var/tmp/spamassassin-toaster-root/usr/lib/perl5/vendor_perl/5.8.8/spamassassin-run.pod -type d -print + sed 's...@^/var/tmp/spamassassin-toaster-r...@%dir @g' + rm -f /var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/local.cf + rm -f /var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/init.pre + install -d /var/tmp/spamassassin-toaster-root/etc + install -d /var/tmp/spamassassin-toaster-root/etc/cron.hourly + install -d /var/tmp/spamassassin-toaster-root/var/qmail/supervise/spamd + install -d /var/tmp/spamassassin-toaster-root/var/qmail/supervise/spamd/log + install -d /var/tmp/spamassassin-toaster-root/var/qmail/supervise/spamd/supervise + install -d /var/tmp/spamassassin-toaster-root/var/log/qmail + install -d /var/tmp/spamassassin-toaster-root/var/log/qmail/spamd + rm -f /var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/local.cf + rm -f /var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/v310.pre + install -m 0644 /usr/src/redhat/SOURCES/qmailtoaster.local.cf.bz2 /var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/local.cf.bz2 install: cannot create regular file `/var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/local.cf.bz2': No such file or directory error: Bad exit status from /var/tmp/rpm-tmp.25006 (%install) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.25006 (%install) Any ideas what might be causing this ? Yep. http://www.mail-archive.com/qmailtoaster-list@qmailtoaster.com/msg18819.html Follow the thread. -- -Eric 'shubes' - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Upgrade using qtp-newmodel of spamassassin fails
Odd thing : I just download and installed MakeMaker 6.43, but I still get the same error : Checking if your kit is complete... Looks good 'ENABLE_SSL' is not a known MakeMaker parameter name. 'SYSCONFDIR' is not a known MakeMaker parameter name. Writing Makefile for Mail::SpamAssassin Makefile written by ExtUtils::MakeMaker 6.43 But still end up with : install: cannot create regular file `/var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/local.cf.bz2': No such file or directory error: Bad exit status from /var/tmp/rpm-tmp.6482 (%install) Maybe this problem isn't related to MakeMaker in my case ? Eric Shubert wrote: Download and reinstall the perl binary rpm that corresponds to your present version (mine is perl-5.8.8-15.el5_2.1), using the --replacefiles option: # rpm --replacefiles -Uvh perl-5.8.8.*.i386.rpm Wim Godden wrote: Eric, Is there some way to go back to pre-6.44 ? Or is there a patch that I can use to upgrade my system on 6.48 ? Kind regards, Wim Eric Shubert wrote: The problem is *caused* by updating the CPAN bundle. You need a pre-6.44 version of MakeMaker for it to work. Wim Godden wrote: Thanks for the quick reply, but the problem wasn't resolved by updating the CPAN bundle. I'm running CentOS 5.2 (i386). Previous runs of qtp-newmodel ran without a glitch. I have : ExtUtils::MakeMaker 6.48 and : cpan[2] install Bundle::CPAN Test::Harness is up to date (3.16). ExtUtils::CBuilder is up to date (0.24). ExtUtils::MakeMaker is up to date (6.48). Module::Build is up to date (0.32). File::Spec is up to date (3.29). File::Temp is up to date (0.21). Scalar::Util is up to date (1.19). Test::More is up to date (0.86). Data::Dumper is up to date (2.121_08). Digest::SHA is up to date (5.47). File::HomeDir is up to date (0.84). Compress::Raw::Zlib is up to date (2.015). IO::Compress::Base is up to date (2.015). IO::Uncompress::Gunzip is up to date (2.015). Compress::Zlib is up to date (2.015). IO::Zlib is up to date (1.09). Archive::Tar is up to date (1.46). Archive::Zip is up to date (1.26). Net::Cmd is up to date (2.29). Net::FTP is up to date (2.77). Term::ReadKey is up to date (2.30). Term::ReadLine::Perl is up to date (1.0302). YAML is up to date (0.68). Text::Glob is up to date (0.08). CPAN is up to date (1.9304). File::Which is up to date (0.05). Still the same error occurring. Eric Shubert wrote: Wim Godden wrote: An upgrade of spamassassin using qtp-newmodel fails (using small union) : Building squirrelmail-toaster-1.4.17-1.3.12 ... Installing squirrelmail-toaster-1.4.17-1.3.12 in the sandbox ... Building spamassassin-toaster-3.2.5-1.3.15 ... qtp-build-rpms - rpmbuild failed for spamassassin-toaster-3.2.5-1.3.15 qtp-build-rpms - see /mnt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log Build failed, Exiting. The logfile shows : ... + find /var/tmp/spamassassin-toaster-root/usr/lib/perl5/vendor_perl/5.8.8/Mail /var/tmp/spamassassin-toaster-root/usr/lib/perl5/vendor_perl/5.8.8/spamassassin-run.pod -type d -print + sed 's...@^/var/tmp/spamassassin-toaster-r...@%dir @g' + rm -f /var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/local.cf + rm -f /var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/init.pre + install -d /var/tmp/spamassassin-toaster-root/etc + install -d /var/tmp/spamassassin-toaster-root/etc/cron.hourly + install -d /var/tmp/spamassassin-toaster-root/var/qmail/supervise/spamd + install -d /var/tmp/spamassassin-toaster-root/var/qmail/supervise/spamd/log + install -d /var/tmp/spamassassin-toaster-root/var/qmail/supervise/spamd/supervise + install -d /var/tmp/spamassassin-toaster-root/var/log/qmail + install -d /var/tmp/spamassassin-toaster-root/var/log/qmail/spamd + rm -f /var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/local.cf + rm -f /var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/v310.pre + install -m 0644 /usr/src/redhat/SOURCES/qmailtoaster.local.cf.bz2 /var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/local.cf.bz2 install: cannot create regular file `/var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/local.cf.bz2': No such file or directory error: Bad exit status from /var/tmp/rpm-tmp.25006 (%install) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.25006 (%install) Any ideas what might be causing this ? Yep. http://www.mail-archive.com/qmailtoaster-list@qmailtoaster.com/msg18819.html Follow the thread. - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Upgrade using qtp-newmodel of spamassassin fails
No, you'll need the whole perl package. There are other interdependent modules in the perl package, you can't necessarily just pick the one file. That, and I'm not sure that 6.43 is quite old enough. 6.44 was just the first version we noticed the problem with. It might have been introduced anywhere between 6.30 and 6.44. I'd bet money that this is your problem. Same symptoms (error messages), exactly. Wim Godden wrote: Odd thing : I just download and installed MakeMaker 6.43, but I still get the same error : Checking if your kit is complete... Looks good 'ENABLE_SSL' is not a known MakeMaker parameter name. 'SYSCONFDIR' is not a known MakeMaker parameter name. Writing Makefile for Mail::SpamAssassin Makefile written by ExtUtils::MakeMaker 6.43 But still end up with : install: cannot create regular file `/var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/local.cf.bz2': No such file or directory error: Bad exit status from /var/tmp/rpm-tmp.6482 (%install) Maybe this problem isn't related to MakeMaker in my case ? Eric Shubert wrote: Download and reinstall the perl binary rpm that corresponds to your present version (mine is perl-5.8.8-15.el5_2.1), using the --replacefiles option: # rpm --replacefiles -Uvh perl-5.8.8.*.i386.rpm Wim Godden wrote: Eric, Is there some way to go back to pre-6.44 ? Or is there a patch that I can use to upgrade my system on 6.48 ? Kind regards, Wim Eric Shubert wrote: The problem is *caused* by updating the CPAN bundle. You need a pre-6.44 version of MakeMaker for it to work. Wim Godden wrote: Thanks for the quick reply, but the problem wasn't resolved by updating the CPAN bundle. I'm running CentOS 5.2 (i386). Previous runs of qtp-newmodel ran without a glitch. I have : ExtUtils::MakeMaker 6.48 and : cpan[2] install Bundle::CPAN Test::Harness is up to date (3.16). ExtUtils::CBuilder is up to date (0.24). ExtUtils::MakeMaker is up to date (6.48). Module::Build is up to date (0.32). File::Spec is up to date (3.29). File::Temp is up to date (0.21). Scalar::Util is up to date (1.19). Test::More is up to date (0.86). Data::Dumper is up to date (2.121_08). Digest::SHA is up to date (5.47). File::HomeDir is up to date (0.84). Compress::Raw::Zlib is up to date (2.015). IO::Compress::Base is up to date (2.015). IO::Uncompress::Gunzip is up to date (2.015). Compress::Zlib is up to date (2.015). IO::Zlib is up to date (1.09). Archive::Tar is up to date (1.46). Archive::Zip is up to date (1.26). Net::Cmd is up to date (2.29). Net::FTP is up to date (2.77). Term::ReadKey is up to date (2.30). Term::ReadLine::Perl is up to date (1.0302). YAML is up to date (0.68). Text::Glob is up to date (0.08). CPAN is up to date (1.9304). File::Which is up to date (0.05). Still the same error occurring. Eric Shubert wrote: Wim Godden wrote: An upgrade of spamassassin using qtp-newmodel fails (using small union) : Building squirrelmail-toaster-1.4.17-1.3.12 ... Installing squirrelmail-toaster-1.4.17-1.3.12 in the sandbox ... Building spamassassin-toaster-3.2.5-1.3.15 ... qtp-build-rpms - rpmbuild failed for spamassassin-toaster-3.2.5-1.3.15 qtp-build-rpms - see /mnt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log Build failed, Exiting. The logfile shows : ... + find /var/tmp/spamassassin-toaster-root/usr/lib/perl5/vendor_perl/5.8.8/Mail /var/tmp/spamassassin-toaster-root/usr/lib/perl5/vendor_perl/5.8.8/spamassassin-run.pod -type d -print + sed 's...@^/var/tmp/spamassassin-toaster-r...@%dir @g' + rm -f /var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/local.cf + rm -f /var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/init.pre + install -d /var/tmp/spamassassin-toaster-root/etc + install -d /var/tmp/spamassassin-toaster-root/etc/cron.hourly + install -d /var/tmp/spamassassin-toaster-root/var/qmail/supervise/spamd + install -d /var/tmp/spamassassin-toaster-root/var/qmail/supervise/spamd/log + install -d /var/tmp/spamassassin-toaster-root/var/qmail/supervise/spamd/supervise + install -d /var/tmp/spamassassin-toaster-root/var/log/qmail + install -d /var/tmp/spamassassin-toaster-root/var/log/qmail/spamd + rm -f /var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/local.cf + rm -f /var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/v310.pre + install -m 0644 /usr/src/redhat/SOURCES/qmailtoaster.local.cf.bz2 /var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/local.cf.bz2 install: cannot create regular file `/var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/local.cf.bz2': No such file or directory error: Bad exit status from /var/tmp/rpm-tmp.25006 (%install) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.25006 (%install) Any ideas what might be causing this ? Yep. http://www.mail-archive.com/qmailtoaster-list@qmailtoaster.com/msg18819.html Follow the thread. -- -Eric 'shubes' - To unsubscribe,
[qmailtoaster] Upgrade using qtp-newmodel of spamassassin fails
An upgrade of spamassassin using qtp-newmodel fails (using small union) : Building squirrelmail-toaster-1.4.17-1.3.12 ... Installing squirrelmail-toaster-1.4.17-1.3.12 in the sandbox ... Building spamassassin-toaster-3.2.5-1.3.15 ... qtp-build-rpms - rpmbuild failed for spamassassin-toaster-3.2.5-1.3.15 qtp-build-rpms - see /mnt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log Build failed, Exiting. The logfile shows : ... + find /var/tmp/spamassassin-toaster-root/usr/lib/perl5/vendor_perl/5.8.8/Mail /var/tmp/spamassassin-toaster-root/usr/lib/perl5/vendor_perl/5.8.8/spamassassin-run.pod -type d -print + sed 's...@^/var/tmp/spamassassin-toaster-r...@%dir @g' + rm -f /var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/local.cf + rm -f /var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/init.pre + install -d /var/tmp/spamassassin-toaster-root/etc + install -d /var/tmp/spamassassin-toaster-root/etc/cron.hourly + install -d /var/tmp/spamassassin-toaster-root/var/qmail/supervise/spamd + install -d /var/tmp/spamassassin-toaster-root/var/qmail/supervise/spamd/log + install -d /var/tmp/spamassassin-toaster-root/var/qmail/supervise/spamd/supervise + install -d /var/tmp/spamassassin-toaster-root/var/log/qmail + install -d /var/tmp/spamassassin-toaster-root/var/log/qmail/spamd + rm -f /var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/local.cf + rm -f /var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/v310.pre + install -m 0644 /usr/src/redhat/SOURCES/qmailtoaster.local.cf.bz2 /var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/local.cf.bz2 install: cannot create regular file `/var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/local.cf.bz2': No such file or directory error: Bad exit status from /var/tmp/rpm-tmp.25006 (%install) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.25006 (%install) Any ideas what might be causing this ? - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Upgrade using qtp-newmodel of spamassassin fails
Wim Godden wrote: An upgrade of spamassassin using qtp-newmodel fails (using small union) : Building squirrelmail-toaster-1.4.17-1.3.12 ... Installing squirrelmail-toaster-1.4.17-1.3.12 in the sandbox ... Building spamassassin-toaster-3.2.5-1.3.15 ... qtp-build-rpms - rpmbuild failed for spamassassin-toaster-3.2.5-1.3.15 qtp-build-rpms - see /mnt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log Build failed, Exiting. The logfile shows : ... + find /var/tmp/spamassassin-toaster-root/usr/lib/perl5/vendor_perl/5.8.8/Mail /var/tmp/spamassassin-toaster-root/usr/lib/perl5/vendor_perl/5.8.8/spamassassin-run.pod -type d -print + sed 's...@^/var/tmp/spamassassin-toaster-r...@%dir @g' + rm -f /var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/local.cf + rm -f /var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/init.pre + install -d /var/tmp/spamassassin-toaster-root/etc + install -d /var/tmp/spamassassin-toaster-root/etc/cron.hourly + install -d /var/tmp/spamassassin-toaster-root/var/qmail/supervise/spamd + install -d /var/tmp/spamassassin-toaster-root/var/qmail/supervise/spamd/log + install -d /var/tmp/spamassassin-toaster-root/var/qmail/supervise/spamd/supervise + install -d /var/tmp/spamassassin-toaster-root/var/log/qmail + install -d /var/tmp/spamassassin-toaster-root/var/log/qmail/spamd + rm -f /var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/local.cf + rm -f /var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/v310.pre + install -m 0644 /usr/src/redhat/SOURCES/qmailtoaster.local.cf.bz2 /var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/local.cf.bz2 install: cannot create regular file `/var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/local.cf.bz2': No such file or directory error: Bad exit status from /var/tmp/rpm-tmp.25006 (%install) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.25006 (%install) Any ideas what might be causing this ? Yep. http://www.mail-archive.com/qmailtoaster-list@qmailtoaster.com/msg18819.html Follow the thread. -- -Eric 'shubes' - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] upgrade problems
Eduardo Henrique Albergone wrote: checking how to run the C++ preprocessor... /lib/cpp configure: error: C++ preprocessor /lib/cpp fails sanity check Your problem is here. Make sure you have all the deps installed.
Re: [qmailtoaster] Upgrade to the Latest RPMs
Eric Shubert wrote: Anil Aliyan wrote: Dear Jake, I am currently running the last versions of all the packages of Qmail Toaster. Now i want to upgrade to the newly uploaded rpms uploaded on the qmailtoaster website on 02/20/2009. CAN I UPGRADE DIRECTLY on the current installation? or is there any specific procedure i need to follow before installing new RPMs. Please guide me. Thanks Regards, Anil Aliyan Jake will correct me if I'm wrong, but I don't think there's any point in doing so. The newly uploaded rpms only add support for new distro releases. They don't add anything new functionality wise. What distro/version are you running? # qtp-whatami That is correct. The new packages only add support for Fedora 9, Fedora 10, and Suse 11.1. Nothing else. If you wish to upgrade you can either run the qtp-newmodel script and upgrade using that, or manually download, rebuild, and install each package. That is all. - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Upgrade to the Latest RPMs
I am using Fedora Core 5. Regards, Anil Aliyan - Original Message - From: Jake Vickers j...@qmailtoaster.com To: qmailtoaster-list@qmailtoaster.com; acali...@gnvfc.net Sent: Friday, February 27, 2009 5:35 PM Subject: Re: [qmailtoaster] Upgrade to the Latest RPMs Eric Shubert wrote: Anil Aliyan wrote: Dear Jake, I am currently running the last versions of all the packages of Qmail Toaster. Now i want to upgrade to the newly uploaded rpms uploaded on the qmailtoaster website on 02/20/2009. CAN I UPGRADE DIRECTLY on the current installation? or is there any specific procedure i need to follow before installing new RPMs. Please guide me. Thanks Regards, Anil Aliyan Jake will correct me if I'm wrong, but I don't think there's any point in doing so. The newly uploaded rpms only add support for new distro releases. They don't add anything new functionality wise. What distro/version are you running? # qtp-whatami That is correct. The new packages only add support for Fedora 9, Fedora 10, and Suse 11.1. Nothing else. If you wish to upgrade you can either run the qtp-newmodel script and upgrade using that, or manually download, rebuild, and install each package. That is all. - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Upgrade to the Latest RPMs
Anil Aliyan wrote: I am using Fedora Core 5. You would do better upgrading your distro to one that is currently supported or at least has been supported in the last couple years. Then use the backup and restore scripts in the QTP package to move your QMT data to the new server. - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Upgrade to the Latest RPMs
Jake Vickers wrote: Anil Aliyan wrote: I am using Fedora Core 5. You would do better upgrading your distro to one that is currently supported or at least has been supported in the last couple years. Then use the backup and restore scripts in the QTP package to move your QMT data to the new server. I might add that if this is a standalone toaster (there aren't any other apps running on the host), you'd be doing yourself a favor by switching to the CentOS distro. You'll be saving yourself some updating in the future. There are really no advantages to using Fedora instead of CentOS, and the disadvantage is that Fedora will become unsupported much sooner. -- -Eric 'shubes' - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
[qmailtoaster] Upgrade to the Latest RPMs
Dear Jake, I am currently running the last versions of all the packages of Qmail Toaster. Now i want to upgrade to the newly uploaded rpms uploaded on the qmailtoaster website on 02/20/2009. CAN I UPGRADE DIRECTLY on the current installation? or is there any specific procedure i need to follow before installing new RPMs. Please guide me. Thanks Regards, Anil Aliyan
Re: [qmailtoaster] Upgrade to the Latest RPMs
Anil Aliyan wrote: Dear Jake, I am currently running the last versions of all the packages of Qmail Toaster. Now i want to upgrade to the newly uploaded rpms uploaded on the qmailtoaster website on 02/20/2009. CAN I UPGRADE DIRECTLY on the current installation? or is there any specific procedure i need to follow before installing new RPMs. Please guide me. Thanks Regards, Anil Aliyan Jake will correct me if I'm wrong, but I don't think there's any point in doing so. The newly uploaded rpms only add support for new distro releases. They don't add anything new functionality wise. What distro/version are you running? # qtp-whatami -- -Eric 'shubes' - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] QMAILtoaster upgrade fails
Harry Zink wrote: Ditto here - same x86_64 architecture qtp-whatami v0.3 DISTRO=CentOS OSVER=4.6 QTARCH=x86_64 BUILD_DIST=cnt4064 BUILD_DIR=/usr/src/redhat Would be awesome if qtp whatami would actually also provide kernel version. That's an excellent suggestion Harry, with the addition of unionfs and all. I've committed the change to the repo, so it'll be in the next release. Kernel version, in my case, is: 2.6.9-67.0.22.ELsmp Linux xxx.fizbin.com 2.6.9-67.0.22.ELsmp #1 SMP Wed Jul 23 17:24:12 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux Sorry about the apparent flakeyness of qtp-newmodel with 64-bit machines. I don't have any 64-bit HW to test with, which makes support difficult. I agree with Harry that spamassassin's dependencies are annoying, but at the same time they are a good thing. Life without them would be worse than it is with them. -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] QMAILtoaster upgrade fails
I'm trying to understand what happened here. Read below. Harry Zink wrote: More data: Sandbox has been built successfully! qtp-newmodel - installing perl-Net-SMTP ... Loading protectbase plugin Setting up Install Process Setting up repositories rpmforge 100% |=| 1.1 kB00:00 update100% |=| 951 B00:00 qmailtoaster-plus 100% |=| 951 B00:00 base 100% |=| 1.1 kB00:00 addons100% |=| 951 B00:00 extras100% |=| 1.1 kB00:00 Reading repository metadata in from local files 216 packages excluded due to repository protections Parsing package install arguments No Match for argument: perl-Net-SMTP Nothing to do Starting to build the binary rpms ...(pizza anyone?) If you want to view compile messages, you can open another terminal and: # tail -f /mnt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log qtp-build-rpms v0.3 qtp-remove-pkgs v0.3.1 REMOVED clamav-toaster from sandbox (not for real) Building zlib-1.2.3-1.0.3 ... Installing zlib-1.2.3-1.0.3 in the sandbox ... Building squirrelmail-toaster-1.4.15-1.3.10 ... Installing squirrelmail-toaster-1.4.15-1.3.10 in the sandbox ... Building spamassassin-toaster-3.2.5-1.3.14 ... Installing spamassassin-toaster-3.2.5-1.3.14 in the sandbox ... qtp-build-rpms - rpm -Uvh failed for spamassassin-toaster-3.2.5-1.3.14 qtp-build-rpms - see /mnt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log Build failed, Exiting. -- No errors, up to this point, in the log file: Installing spamassassin-toaster-3.2.5-1.3.14 in the sandbox ... error: Failed dependencies: perl(HTML::Parser) = 3.43 is needed by spamassassin-toaster-3.2.5-1.3.14.x86_64 -- Frankly, all these perl dependency errors are really annoying :-( Despite downloading and installing (-Uvh) rpm -Uvh perl-HTML-Parser-3.56-1.el4.rf.x86_64.rpm , and confirming successful installation, re-running it all failed with the same error: Installing spamassassin-toaster-3.2.5-1.3.14 in the sandbox ... error: Failed dependencies: perl(HTML::Parser) = 3.43 is needed by spamassassin-toaster-3.2.5-1.3.14.x86_64 Did you select a fresh sandbox when you re-ran at this point? If you installed the perl-HTML-Parser-3.56 but did not use a fresh sandbox, the old version would still have been in the sandbox. :( Well, perl-HTML-Parser-3.56 is installed, which is certainly above the requested 3.43 or better, yet it continues to refuse to install. Is this because, once again, the packages do not take the x86_64 architecture into consideration, and the 'x86_64' portion of 'perl-HTML-Parser-3.56-1.el4.rf.x86_64.rpm' is not being recognized? Is there some way to force this process, though at this point, I might as well just perform the updates manually, as the obvious benefit of qtp-newmodel is kinda obviated :-( : zlib-1.2.3-1.0.3 squirrelmail-toaster-1.4.15-1.3.10 spamassassin-toaster-3.2.5-1.3.14 clamav-toaster-0.93.3-1.3.20 Of course, now trying to find instructions for the manual process - as I recall there was more needed than just turning qmailtoaster off, and running the updates. Wasn't there some additional stuff that needs to be done in order to satisfy spamassassin? (sadness :-( -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] QMAILtoaster upgrade fails
On Aug 12, 2008, at 9:33 AM, Eric Shubert wrote: Did you select a fresh sandbox when you re-ran at this point? If you installed the perl-HTML-Parser-3.56 but did not use a fresh sandbox, the old version would still have been in the sandbox. :( I redid fresh sandboxes every time I ran it. I ended up doing manual upgrades of the modules that needed updates -- albeit qtp still insists that my zlib is out of date (it is the latest version). Harry - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] QMAILtoaster upgrade fails
Harry Zink wrote: On Aug 12, 2008, at 9:33 AM, Eric Shubert wrote: Did you select a fresh sandbox when you re-ran at this point? If you installed the perl-HTML-Parser-3.56 but did not use a fresh sandbox, the old version would still have been in the sandbox. :( I redid fresh sandboxes every time I ran it. I ended up doing manual upgrades of the modules that needed updates -- albeit qtp still insists that my zlib is out of date (it is the latest version). Harry You're running the latest qtp? I seem to remember a bug related to zlib some while back. Perhaps it wasn't fixed entirely. -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] QMAILtoaster upgrade fails
On Aug 12, 2008, at 10:08 AM, Eric Shubert wrote: Harry Zink wrote: On Aug 12, 2008, at 9:33 AM, Eric Shubert wrote: Did you select a fresh sandbox when you re-ran at this point? If you installed the perl-HTML-Parser-3.56 but did not use a fresh sandbox, the old version would still have been in the sandbox. :( I redid fresh sandboxes every time I ran it. I ended up doing manual upgrades of the modules that needed updates -- albeit qtp still insists that my zlib is out of date (it is the latest version). Harry You're running the latest qtp? I seem to remember a bug related to zlib some while back. Perhaps it wasn't fixed entirely. Yes, latest qtp. qtp-ami-up2date New Qmail-Toaster Packages Available: zlib-1.2.3-1.0.3 Which is the version of zlib I'm running - furthermore, deinstalling zlib and reinstalling it makes no difference either. Harry - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] QMAILtoaster upgrade fails
Harry Zink wrote: On Aug 12, 2008, at 10:08 AM, Eric Shubert wrote: Harry Zink wrote: On Aug 12, 2008, at 9:33 AM, Eric Shubert wrote: Did you select a fresh sandbox when you re-ran at this point? If you installed the perl-HTML-Parser-3.56 but did not use a fresh sandbox, the old version would still have been in the sandbox. :( I redid fresh sandboxes every time I ran it. I ended up doing manual upgrades of the modules that needed updates -- albeit qtp still insists that my zlib is out of date (it is the latest version). Harry You're running the latest qtp? I seem to remember a bug related to zlib some while back. Perhaps it wasn't fixed entirely. Yes, latest qtp. qtp-ami-up2date New Qmail-Toaster Packages Available: zlib-1.2.3-1.0.3 Which is the version of zlib I'm running - furthermore, deinstalling zlib and reinstalling it makes no difference either. Harry If you'd've simply not selected it, you'd've gotten no errors. ;) I'd like to nail this one (once again, so it seems). You say this is the version you're running. Please post the results of: # rpm -q zlib # yum info zlib That might give me a clue as to what's going on with your toaster. -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] QMAILtoaster upgrade fails
On Aug 12, 2008, at 10:58 AM, Eric Shubert wrote: f you'd've simply not selected it, you'd've gotten no errors. ;) LOL I'd like to nail this one (once again, so it seems). You say this is the version you're running. Please post the results of: # rpm -q zlib # yum info zlib That might give me a clue as to what's going on with your toaster. Huh? From what these show, it seems there are two versions of zlib installed? Do you concur? rpm -q zlib zlib-1.2.1.2-1.2 zlib-1.2.3-1.0.3 yum info zlib Loading protectbase plugin Setting up repositories rpmforge 100% |=| 1.1 kB 00:00 update100% |=| 951 B 00:00 qmailtoaster-plus 100% |=| 951 B 00:00 base 100% |=| 1.1 kB 00:00 addons100% |=| 951 B 00:00 extras100% |=| 1.1 kB 00:00 Reading repository metadata in from local files primary.xml.gz100% |=| 3.2 MB 00:09 sqlite cache needs updating, reading in metadata rpmforge : # 9139/9140216 packages excluded due to repository protections Installed Packages Name : zlib Arch : i386 Version: 1.2.1.2 Release: 1.2 Size : 66 k Repo : installed Summary: The zlib compression and decompression library. Description: Zlib is a general-purpose, patent-free, lossless data compression library which is used by many different programs. Name : zlib Arch : x86_64 Version: 1.2.3 Release: 1.0.3 Size : 197 k Repo : installed Summary: The zlib compression and decompression library. Description: Zlib is a general-purpose, patent-free, lossless data compression library which is used by many different programs. Available Packages Name : zlib Arch : x86_64 Version: 1.2.1.2 Release: 1.2 Size : 47 k Repo : base Summary: The zlib compression and decompression library. Description: Zlib is a general-purpose, patent-free, lossless data compression library which is used by many different programs. - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] QMAILtoaster upgrade fails
Harry Zink wrote: On Aug 12, 2008, at 10:58 AM, Eric Shubert wrote: f you'd've simply not selected it, you'd've gotten no errors. ;) LOL I'd like to nail this one (once again, so it seems). You say this is the version you're running. Please post the results of: # rpm -q zlib # yum info zlib That might give me a clue as to what's going on with your toaster. Huh? From what these show, it seems there are two versions of zlib installed? Do you concur? Sure looks that way. Don't know how you managed that. I'd try # rpm -e zlib-1.2.1.2-1.2 to remove it. rpm -q zlib zlib-1.2.1.2-1.2 zlib-1.2.3-1.0.3 yum info zlib Loading protectbase plugin Setting up repositories rpmforge 100% |=| 1.1 kB00:00 update100% |=| 951 B00:00 qmailtoaster-plus 100% |=| 951 B00:00 base 100% |=| 1.1 kB00:00 addons100% |=| 951 B00:00 extras100% |=| 1.1 kB00:00 Reading repository metadata in from local files primary.xml.gz100% |=| 3.2 MB00:09 sqlite cache needs updating, reading in metadata rpmforge : # 9139/9140216 packages excluded due to repository protections Installed Packages Name : zlib Arch : i386 Version: 1.2.1.2 Release: 1.2 Size : 66 k Repo : installed Summary: The zlib compression and decompression library. Description: Zlib is a general-purpose, patent-free, lossless data compression library which is used by many different programs. Name : zlib Arch : x86_64 Version: 1.2.3 Release: 1.0.3 Size : 197 k Repo : installed Summary: The zlib compression and decompression library. Description: Zlib is a general-purpose, patent-free, lossless data compression library which is used by many different programs. Available Packages Name : zlib Arch : x86_64 Version: 1.2.1.2 Release: 1.2 Size : 47 k Repo : base Summary: The zlib compression and decompression library. Description: Zlib is a general-purpose, patent-free, lossless data compression library which is used by many different programs. - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] QMAILtoaster upgrade fails
On Aug 12, 2008, at 11:58 AM, Eric Shubert wrote: Sure looks that way. Don't know how you managed that. Neither do it - it's pretty much been a pain vanilla QMT box since inception. I'd try # rpm -e zlib-1.2.1.2-1.2 to remove it. Here we go again: rpm -e zlib-1.2.1.2-1.2 error: Failed dependencies: libz.so.1 is needed by (installed) curl-7.12.1-11.el4.i386 libz.so.1 is needed by (installed) freetype-2.1.9-8.el4.6.i386 libz.so.1 is needed by (installed) fontconfig-2.2.3-13.el4.i386 libz.so.1 is needed by (installed) xorg-x11-libs-6.8.2-1.EL.33.0.4.i386 libz.so.1 is needed by (installed) openssl-0.9.7a-43.17.el4_6.1.i686 Will it be safe to do a --nodeps remove? It should pick up from the remaining zlib, right? Harry - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] QMAILtoaster upgrade fails
On Aug 12, 2008, at 11:58 AM, Eric Shubert wrote: I'd try # rpm -e zlib-1.2.1.2-1.2 Yep, that did it -- all's back to being well in QMT land (well, until the next updates roll around :-) - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] QMAILtoaster upgrade fails
Hi Harry, Please check if both run files exists at the said location: /var/qmail/supervise/clamd/run /var/qmail/supervise/clamd/log/run if not please create them. # vi /var/qmail/supervise/clamd/run #!/bin/sh exec /usr/bin/setuidgid clamav /usr/sbin/clamd 21 # vi /var/qmail/supervise/clamd/log/run #!/bin/sh LOGSIZE=`cat /var/qmail/control/logsize` LOGCOUNT=`cat /var/qmail/control/logcount` exec /usr/bin/setuidgid qmaill /usr/bin/multilog t s$LOGSIZE n$LOGCOUNT /var/log/qmail/clamd Regards, Anil Aliyan - Original Message - From: Harry Zink [EMAIL PROTECTED] To: qmailtoaster-list@qmailtoaster.com Sent: Monday, August 11, 2008 8:44 AM Subject: Re: [qmailtoaster] QMAILtoaster upgrade fails Lastly, here's the current status: This is not going away: supervise: fatal: unable to start clamd/run: file does not exist supervise: fatal: unable to start log/run: file does not exist There is no appropriate 'run' file inside /var/qmail/supervise/clamd/ qmailctl stat shows: authlib: up (pid 11753) 311 seconds clamd: up (pid 12647) 1 seconds imap4: up (pid 11816) 311 seconds imap4-ssl: up (pid 11719) 311 seconds pop3: up (pid 11712) 311 seconds pop3-ssl: up (pid 11779) 311 seconds send: up (pid 11732) 311 seconds smtp: up (pid 11786) 311 seconds smtp-ofmipd: up (pid 11767) 311 seconds spamd: up (pid 12076) 224 seconds submission: up (pid 11726) 311 seconds authlib/log: up (pid 11758) 311 seconds clamd/log: up (pid 12648) 1 seconds imap4/log: up (pid 11752) 311 seconds imap4-ssl/log: up (pid 11722) 311 seconds pop3/log: up (pid 11713) 311 seconds pop3-ssl/log: up (pid 11782) 311 seconds send/log: up (pid 11742) 311 seconds smtp/log: up (pid 11789) 311 seconds smtp-ofmipd/log: up (pid 11814) 311 seconds spamd/log: up (pid 11736) 311 seconds submission/log: up (pid 11729) 311 seconds It *seems* everything is running, but because of the various errors, I can't really be sure. Any ideas ? - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] QMAILtoaster upgrade fails
Final summary - I did the updates manually - removed and deinstalled clamav and spamassassin, and then reinstalled from the rpm's left behind from the prior attempts. Restart qmailtoaster - works! - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] QMAILtoaster upgrade fails
Anil, Thanks for your help. In both cases, the run files were absent - it appears that somehow the perl dependencies hell has stopped the qtp-newmodel script from properly creating those and executing through the end, even after I had the dependencies fixed. Harry On Aug 10, 2008, at 11:22 PM, Anil Aliyan wrote: Hi Harry, Please check if both run files exists at the said location: /var/qmail/supervise/clamd/run /var/qmail/supervise/clamd/log/run if not please create them. # vi /var/qmail/supervise/clamd/run #!/bin/sh exec /usr/bin/setuidgid clamav /usr/sbin/clamd 21 # vi /var/qmail/supervise/clamd/log/run #!/bin/sh LOGSIZE=`cat /var/qmail/control/logsize` LOGCOUNT=`cat /var/qmail/control/logcount` exec /usr/bin/setuidgid qmaill /usr/bin/multilog t s$LOGSIZE n $LOGCOUNT /var/log/qmail/clamd Regards, Anil Aliyan - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] QMAILtoaster upgrade fails
Thanks for chiming in, Phil. 64-bit too? Phil Leinhauser wrote: Sorry about the blank replay a minute ago…. I have this same problem. I haven’t been able to get unionfs to work yet. I’m also on 2.6.18 kernel. I’ve just been using linked. I’m chasing the elusive pizza… -P *From:* James Ecker [mailto:[EMAIL PROTECTED] *Sent:* Saturday, August 09, 2008 4:54 PM *To:* qmailtoaster-list@qmailtoaster.com *Subject:* RE: [qmailtoaster] QMAILtoaster upgrade fails The distro is Centos 5.2 x86_64 kernel-2.6.18 Toaster 1.3 Linked sandbox seemed to work thank you. Date: Sat, 9 Aug 2008 11:51:35 -0700 From: [EMAIL PROTECTED] To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] QMAILtoaster upgrade fails James Ecker wrote: I have installed qmailtoaster-plus sucessfully, but when I run qtp-newmodel I receive the following error message chroot: cannot run command `qtp-build-rpms': No such file or directory. Does anyone have any ideas? That's unusual. Need more info to tell for sure, like distro version, toaster versions. If I had to guess, I'd say you're running an older kernel (2.6.9 or so) and you tried using a unionfs sandbox. If that's the case, I'd either upgrade to a newer kernel, or run qtp-newmodel with a copied or linked sandbox. -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Your PC, mobile phone, and online services work together like never before. See how Windows® fits your life http://clk.atdmt.com/MRT/go/108587394/direct/01/ -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] QMAILtoaster upgrade fails
Ditto here - same x86_64 architecture. qtp-whatami v0.3 DISTRO=CentOS OSVER=4.6 QTARCH=x86_64 BUILD_DIST=cnt4064 BUILD_DIR=/usr/src/redhat Would be awesome if qtp whatami would actually also provide kernel version. Kernel version, in my case, is: 2.6.9-67.0.22.ELsmp Linux xxx.fizbin.com 2.6.9-67.0.22.ELsmp #1 SMP Wed Jul 23 17:24:12 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux On Aug 9, 2008, at 5:58 PM, Phil Leinhauser wrote: Sorry about the blank replay a minute ago…. I have this same problem. I haven’t been able to get unionfs to work yet. I’m also on 2.6.18 kernel. I’ve just been using linked. I’m chasing the elusive pizza… -P From: James Ecker [mailto:[EMAIL PROTECTED] Sent: Saturday, August 09, 2008 4:54 PM To: qmailtoaster-list@qmailtoaster.com Subject: RE: [qmailtoaster] QMAILtoaster upgrade fails The distro is Centos 5.2 x86_64 kernel-2.6.18 Toaster 1.3 Linked sandbox seemed to work thank you. Date: Sat, 9 Aug 2008 11:51:35 -0700 From: [EMAIL PROTECTED] To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] QMAILtoaster upgrade fails James Ecker wrote: I have installed qmailtoaster-plus sucessfully, but when I run qtp-newmodel I receive the following error message chroot: cannot run command `qtp-build-rpms': No such file or directory. Does anyone have any ideas? That's unusual. Need more info to tell for sure, like distro version, toaster versions. If I had to guess, I'd say you're running an older kernel (2.6.9 or so) and you tried using a unionfs sandbox. If that's the case, I'd either upgrade to a newer kernel, or run qtp-newmodel with a copied or linked sandbox. -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Your PC, mobile phone, and online services work together like never before. See how Windows® fits your life
Re: [qmailtoaster] QMAILtoaster upgrade fails
More data: Sandbox has been built successfully! qtp-newmodel - installing perl-Net-SMTP ... Loading protectbase plugin Setting up Install Process Setting up repositories rpmforge 100% |=| 1.1 kB 00:00 update100% |=| 951 B 00:00 qmailtoaster-plus 100% |=| 951 B 00:00 base 100% |=| 1.1 kB 00:00 addons100% |=| 951 B 00:00 extras100% |=| 1.1 kB 00:00 Reading repository metadata in from local files 216 packages excluded due to repository protections Parsing package install arguments No Match for argument: perl-Net-SMTP Nothing to do Starting to build the binary rpms ...(pizza anyone?) If you want to view compile messages, you can open another terminal and: # tail -f /mnt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log qtp-build-rpms v0.3 qtp-remove-pkgs v0.3.1 REMOVED clamav-toaster from sandbox (not for real) Building zlib-1.2.3-1.0.3 ... Installing zlib-1.2.3-1.0.3 in the sandbox ... Building squirrelmail-toaster-1.4.15-1.3.10 ... Installing squirrelmail-toaster-1.4.15-1.3.10 in the sandbox ... Building spamassassin-toaster-3.2.5-1.3.14 ... Installing spamassassin-toaster-3.2.5-1.3.14 in the sandbox ... qtp-build-rpms - rpm -Uvh failed for spamassassin-toaster-3.2.5-1.3.14 qtp-build-rpms - see /mnt/qtp-sandbox/usr/src/qtp-upgrade/log/build- recent.log Build failed, Exiting. -- No errors, up to this point, in the log file: Installing spamassassin-toaster-3.2.5-1.3.14 in the sandbox ... error: Failed dependencies: perl(HTML::Parser) = 3.43 is needed by spamassassin- toaster-3.2.5-1.3.14.x86_64 -- Frankly, all these perl dependency errors are really annoying :-( Despite downloading and installing (-Uvh) rpm -Uvh perl-HTML- Parser-3.56-1.el4.rf.x86_64.rpm , and confirming successful installation, re-running it all failed with the same error: Installing spamassassin-toaster-3.2.5-1.3.14 in the sandbox ... error: Failed dependencies: perl(HTML::Parser) = 3.43 is needed by spamassassin- toaster-3.2.5-1.3.14.x86_64 Well, perl-HTML-Parser-3.56 is installed, which is certainly above the requested 3.43 or better, yet it continues to refuse to install. Is this because, once again, the packages do not take the x86_64 architecture into consideration, and the 'x86_64' portion of 'perl- HTML-Parser-3.56-1.el4.rf.x86_64.rpm' is not being recognized? Is there some way to force this process, though at this point, I might as well just perform the updates manually, as the obvious benefit of qtp-newmodel is kinda obviated :-( : zlib-1.2.3-1.0.3 squirrelmail-toaster-1.4.15-1.3.10 spamassassin-toaster-3.2.5-1.3.14 clamav-toaster-0.93.3-1.3.20 Of course, now trying to find instructions for the manual process - as I recall there was more needed than just turning qmailtoaster off, and running the updates. Wasn't there some additional stuff that needs to be done in order to satisfy spamassassin? (sadness :-( - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] QMAILtoaster upgrade fails
Lastly, here's the current status: This is not going away: supervise: fatal: unable to start clamd/run: file does not exist supervise: fatal: unable to start log/run: file does not exist There is no appropriate 'run' file inside /var/qmail/supervise/clamd/ qmailctl stat shows: authlib: up (pid 11753) 311 seconds clamd: up (pid 12647) 1 seconds imap4: up (pid 11816) 311 seconds imap4-ssl: up (pid 11719) 311 seconds pop3: up (pid 11712) 311 seconds pop3-ssl: up (pid 11779) 311 seconds send: up (pid 11732) 311 seconds smtp: up (pid 11786) 311 seconds smtp-ofmipd: up (pid 11767) 311 seconds spamd: up (pid 12076) 224 seconds submission: up (pid 11726) 311 seconds authlib/log: up (pid 11758) 311 seconds clamd/log: up (pid 12648) 1 seconds imap4/log: up (pid 11752) 311 seconds imap4-ssl/log: up (pid 11722) 311 seconds pop3/log: up (pid 11713) 311 seconds pop3-ssl/log: up (pid 11782) 311 seconds send/log: up (pid 11742) 311 seconds smtp/log: up (pid 11789) 311 seconds smtp-ofmipd/log: up (pid 11814) 311 seconds spamd/log: up (pid 11736) 311 seconds submission/log: up (pid 11729) 311 seconds It *seems* everything is running, but because of the various errors, I can't really be sure. Any ideas ? - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[qmailtoaster] QMAILtoaster upgrade fails
I have installed qmailtoaster-plus sucessfully, but when I run qtp-newmodel I receive the following error message chroot: cannot run command `qtp-build-rpms': No such file or directory. Does anyone have any ideas? _ Get Windows Live and get whatever you need, wherever you are. Start here. http://www.windowslive.com/default.html?ocid=TXT_TAGLM_WL_Home_082008
Re: [qmailtoaster] QMAILtoaster upgrade fails
James Ecker wrote: I have installed qmailtoaster-plus sucessfully, but when I run qtp-newmodel I receive the following error message chroot: cannot run command `qtp-build-rpms': No such file or directory. Does anyone have any ideas? That's unusual. Need more info to tell for sure, like distro version, toaster versions. If I had to guess, I'd say you're running an older kernel (2.6.9 or so) and you tried using a unionfs sandbox. If that's the case, I'd either upgrade to a newer kernel, or run qtp-newmodel with a copied or linked sandbox. -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [qmailtoaster] QMAILtoaster upgrade fails
The distro is Centos 5.2 x86_64 kernel-2.6.18 Toaster 1.3 Linked sandbox seemed to work thank you. Date: Sat, 9 Aug 2008 11:51:35 -0700 From: [EMAIL PROTECTED] To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] QMAILtoaster upgrade fails James Ecker wrote: I have installed qmailtoaster-plus sucessfully, but when I run qtp-newmodel I receive the following error message chroot: cannot run command `qtp-build-rpms': No such file or directory. Does anyone have any ideas? That's unusual. Need more info to tell for sure, like distro version, toaster versions. If I had to guess, I'd say you're running an older kernel (2.6.9 or so) and you tried using a unionfs sandbox. If that's the case, I'd either upgrade to a newer kernel, or run qtp-newmodel with a copied or linked sandbox. -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _ Your PC, mobile phone, and online services work together like never before. http://clk.atdmt.com/MRT/go/108587394/direct/01/
RE: [qmailtoaster] QMAILtoaster upgrade fails
_ From: James Ecker [mailto:[EMAIL PROTECTED] Sent: Saturday, August 09, 2008 11:18 AM To: qmailtoaster-list@qmailtoaster.com Subject: [qmailtoaster] QMAILtoaster upgrade fails I have installed qmailtoaster-plus sucessfully, but when I run qtp-newmodel I receive the following error message chroot: cannot run command `qtp-build-rpms': No such file or directory. Does anyone have any ideas? _ Get Windows Live and get whatever you need, wherever you are. Start here. http://www.windowslive.com/default.html?ocid=TXT_TAGLM_WL_Home_082008
RE: [qmailtoaster] QMAILtoaster upgrade fails
Sorry about the blank replay a minute ago.. I have this same problem. I haven't been able to get unionfs to work yet. I'm also on 2.6.18 kernel. I've just been using linked. I'm chasing the elusive pizza. -P _ From: James Ecker [mailto:[EMAIL PROTECTED] Sent: Saturday, August 09, 2008 4:54 PM To: qmailtoaster-list@qmailtoaster.com Subject: RE: [qmailtoaster] QMAILtoaster upgrade fails The distro is Centos 5.2 x86_64 kernel-2.6.18 Toaster 1.3 Linked sandbox seemed to work thank you. Date: Sat, 9 Aug 2008 11:51:35 -0700 From: [EMAIL PROTECTED] To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] QMAILtoaster upgrade fails James Ecker wrote: I have installed qmailtoaster-plus sucessfully, but when I run qtp-newmodel I receive the following error message chroot: cannot run command `qtp-build-rpms': No such file or directory. Does anyone have any ideas? That's unusual. Need more info to tell for sure, like distro version, toaster versions. If I had to guess, I'd say you're running an older kernel (2.6.9 or so) and you tried using a unionfs sandbox. If that's the case, I'd either upgrade to a newer kernel, or run qtp-newmodel with a copied or linked sandbox. -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _ Your PC, mobile phone, and online services work together like never before. See how Windows http://clk.atdmt.com/MRT/go/108587394/direct/01/ R fits your life
[qmailtoaster] upgrade to the lastest clamav
hello all I would like to upgrade to the lastest clamav. What is the procedure for upgrading just the clamav on centos 5 here is what I have done so far. Downloaded the src.rpm rpmbuild --rebuild --with cnt50 clamav.x.x.x.x.src.rpm Then when I go to install it it tells me that I am missing error: Failed dependencies: libclamunrar_iface.so.3 is needed by clamav-toaster-0.93-1.3.18.i386 How do I get that dependancy? I have tried yum and I have rpmforge installed I cannot seem to get this dependancy to install? Any suggestions thanks much q -- Thanks, Kyle Quillen Lightspeed Wireless [EMAIL PROTECTED] 330.473.1231 ext.202 - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] upgrade to the lastest clamav
Sweet so I just need to shut down with qmailctl stop and then do an rpm -e clamav.x.x.x.x Correct thanks q On Fri, 2008-06-06 at 09:03 -0700, Erik A. Espinoza wrote: Hey Kyle, Before building the new clamav, the old clamav has to be removed. Building the new clamav while the old clamav install will create a dependency on the older version of clamav. Erik On Fri, Jun 6, 2008 at 8:44 AM, Kyle Quillen [EMAIL PROTECTED] wrote: hello all I would like to upgrade to the lastest clamav. What is the procedure for upgrading just the clamav on centos 5 here is what I have done so far. Downloaded the src.rpm rpmbuild --rebuild --with cnt50 clamav.x.x.x.x.src.rpm Then when I go to install it it tells me that I am missing error: Failed dependencies: libclamunrar_iface.so.3 is needed by clamav-toaster-0.93-1.3.18.i386 How do I get that dependancy? I have tried yum and I have rpmforge installed I cannot seem to get this dependancy to install? Any suggestions thanks much q -- Thanks, Kyle Quillen Lightspeed Wireless [EMAIL PROTECTED] 330.473.1231 ext.202 - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Thanks, Kyle Quillen Lightspeed Wireless [EMAIL PROTECTED] 330.473.1231 ext.202 - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] upgrade to the lastest clamav
I went through this a few weeks ago and the best way (I was told) was to install the qmail toaster plus package, and then use the new model upgrade script. Worked great for me. d On 6-Jun-08, at 12:12 PM, Kyle Quillen wrote: Sweet so I just need to shut down with qmailctl stop and then do an rpm -e clamav.x.x.x.x Correct thanks q On Fri, 2008-06-06 at 09:03 -0700, Erik A. Espinoza wrote: Hey Kyle, Before building the new clamav, the old clamav has to be removed. Building the new clamav while the old clamav install will create a dependency on the older version of clamav. Erik On Fri, Jun 6, 2008 at 8:44 AM, Kyle Quillen [EMAIL PROTECTED] wrote: hello all I would like to upgrade to the lastest clamav. What is the procedure for upgrading just the clamav on centos 5 here is what I have done so far. Downloaded the src.rpm rpmbuild --rebuild --with cnt50 clamav.x.x.x.x.src.rpm Then when I go to install it it tells me that I am missing error: Failed dependencies: libclamunrar_iface.so.3 is needed by clamav- toaster-0.93-1.3.18.i386 How do I get that dependancy? I have tried yum and I have rpmforge installed I cannot seem to get this dependancy to install? Any suggestions thanks much q -- Thanks, Kyle Quillen Lightspeed Wireless [EMAIL PROTECTED] 330.473.1231 ext.202 - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: qmailtoaster-list- [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Thanks, Kyle Quillen Lightspeed Wireless [EMAIL PROTECTED] 330.473.1231 ext.202 - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[qmailtoaster] upgrade older toaster to new RPM qtp and spamdyke install
Hi there, Is there a recommended method for updating an existing toaster that has: - Older qtp-plus (prior to repo) - Spamdyke (3.01) that was a manual install My hopes are to get my qtp plus onto the repo. So I can add and install, but I am not sure if this may mess something up since the old version is there. And then with spamdyke, I have an install which has different paths and such and existing graylisting, etc going on. Would it be as simple to revert my qmail run file to the default, install spamdyke from the QTP-MENU, copy over my graylist folders and the file contents of various white lists, etc? Anything I should watch for? DNK - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] upgrade older toaster to new RPM qtp and spamdyke install
dnk wrote: Hi there, Is there a recommended method for updating an existing toaster that has: - Older qtp-plus (prior to repo) - Spamdyke (3.01) that was a manual install My hopes are to get my qtp plus onto the repo. So I can add and install, but I am not sure if this may mess something up since the old version is there. And then with spamdyke, I have an install which has different paths and such and existing graylisting, etc going on. Would it be as simple to revert my qmail run file to the default, install spamdyke from the QTP-MENU, copy over my graylist folders and the file contents of various white lists, etc? You can install the repo for QTP and just upgrade it. It will overwrite/upgrade any old files. I can't say about spamdyke though. - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] upgrade older toaster to new RPM qtp and spamdyke install
Jake Vickers wrote: dnk wrote: Hi there, Is there a recommended method for updating an existing toaster that has: - Older qtp-plus (prior to repo) - Spamdyke (3.01) that was a manual install My hopes are to get my qtp plus onto the repo. So I can add and install, but I am not sure if this may mess something up since the old version is there. And then with spamdyke, I have an install which has different paths and such and existing graylisting, etc going on. Would it be as simple to revert my qmail run file to the default, install spamdyke from the QTP-MENU, copy over my graylist folders and the file contents of various white lists, etc? You can install the repo for QTP and just upgrade it. It will overwrite/upgrade any old files. I can't say about spamdyke though. I can. ;) I think you've got it right. At the very least be sure to revert to the default run file, as the install scripts uses it to build the new one. You'll also want to tailor any configuration settings that vary from what you're presently running. You could let spamdyke rebuild the graylist directory if you like instead of moving it - shouldn't matter much either way. -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] upgrade older toaster to new RPM qtp and spamdyke install
On 2008.05.07, at 20:38, Jake Vickers wrote: dnk wrote: Hi there, Is there a recommended method for updating an existing toaster that has: - Older qtp-plus (prior to repo) - Spamdyke (3.01) that was a manual install My hopes are to get my qtp plus onto the repo. So I can add and install, but I am not sure if this may mess something up since the old version is there. And then with spamdyke, I have an install which has different paths and such and existing graylisting, etc going on. Would it be as simple to revert my qmail run file to the default, install spamdyke from the QTP-MENU, copy over my graylist folders and the file contents of various white lists, etc? You can install the repo for QTP and just upgrade it. It will overwrite/upgrade any old files. I can't say about spamdyke though. Confirm for QTP upgrade (CentOS 4.6 32bit - current) Upgrade works smoothly but i didn't have spamdyke, so can't say also. - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] smime.p7s Description: S/MIME cryptographic signature
Re: [qmailtoaster] upgrade question
Once I install them using Yum, do I just uninstall the perl modules?
Jack D. Martin, Jr.
Magic Wireless Internet Service Provider, LLC
[EMAIL PROTECTED]
P.O. Box 278
Oilton, OK 74052
(918) 862-1065
(918) 605-9552 cellular
- Original Message
From: Helmut Fritz [EMAIL PROTECTED]
To: qmailtoaster-list@qmailtoaster.com
Sent: Wednesday, April 9, 2008 4:59:59 PM
Subject: RE: [qmailtoaster] upgrade question
Not easier...'bout the same. Some modules are just not on cpan - that is
the issue. Up until I did the upgrade for qmt, I have always used cpan as
well.
You also do not have to uninstall and reinstall... Just get the repository
rpm, install it and then use yum...
-Original Message-
From: Jack Martin [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 09, 2008 2:26 PM
To: qmailtoaster-list@qmailtoaster.com
Subject: Re: [qmailtoaster] upgrade question
Most of my modules are installed using CPAN, so I am not going to un-install
and re-install them. I have started using the rpmforge repo for all new
modules, just because it seems easier to install and maintain.
Jack D. Martin, Jr.
Magic Wireless Internet Service Provider, LLC [EMAIL PROTECTED]
P.O. Box 278 Oilton, OK 74052
(918) 862-1065
(918) 605-9552 cellular
- Original Message
From: Helmut Fritz [EMAIL PROTECTED]
To: qmailtoaster-list@qmailtoaster.com
Sent: Wednesday, April 9, 2008 4:10:35 PM
Subject: RE: [qmailtoaster] upgrade question
Jack,
I highly suggest using the rpmforge repository/yum to update Cpan just
does not seem to have the latest stuff...
-Original Message-
From: Jack Martin [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 09, 2008 1:59 PM
To: qmailtoaster-list@qmailtoaster.com
Subject: Re: [qmailtoaster] upgrade question
Before I do it - I am upgrading my perl modules just to see if that could
possibly be the problem.
Jack D. Martin, Jr.
Magic Wireless Internet Service Provider, LLC [EMAIL PROTECTED]
P.O. Box 278 Oilton, OK 74052
(918) 862-1065
(918) 605-9552 cellular
- Original Message
From: Eric Shubert [EMAIL PROTECTED]
To: qmailtoaster-list@qmailtoaster.com
Sent: Wednesday, April 9, 2008 3:30:37 PM
Subject: Re: [qmailtoaster] upgrade question
I did a little more testing, and it appears that the problematic parameter
to the %makeinstall command isn't needed at all. I remove it and the package
appears to have built with the local rules files in the desired location.
Attached is the source rpm with the problematic parameter removed. Jack,
will you give it a try?
Once again, my apologies for the large attachment to the list.
Eric Shubert wrote:
The command:
/usr/bin/perl -MExtUtils::Command -e mkpath
/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/
etc/mail/spamassassin was supposed to create the directory that's
missing, but it appears to have prepended the %{buildroot} directory,
which is incorrect.
Now here's the weird thing. The 'bug' before that I attempted to fix
was that the %{buildroot} directory wasn't there, so I added it. Now
it appears to be there again, in addition to the one I added. So
sometimes rpmbuild (or SA's Makefile.PL more specifically) includes
the %{buildroot} directory, and sometimes it doesn't. Weird.
I can understand that something's different which causes %{buildroot}
to sometimes be there and sometimes not on different machines, but on
the same machine it's sorta baffling.
Jack, can you try the 1.3.13 version again on your toaster? I'm
wondering if it might work now. In any case, I'm thinking that either
one or the other should work. I still have yet to figure out why
%{buildroot} is included sometimes and other times not.
Jack Martin wrote:
This is the rpm that you attached last week, yes. Here are the logs
starting where you said to start:
Installing /var/tmp/spamassassin-toaster-root/usr/bin/sa-compile
Installing /var/tmp/spamassassin-toaster-root/usr/bin/sa-update
Installing /var/tmp/spamassassin-toaster-root/usr/bin/spamd
Installing /var/tmp/spamassassin-toaster-root/usr/bin/sa-learn
Writing
/var/tmp/spamassassin-toaster-root//usr/lib/perl5/vendor_perl/5.8.5/i
386-linux-thread-multi/auto/Mail/SpamAssassin/.packlist
Appending installation info to
/var/tmp/spamassassin-toaster-root//usr/lib/perl5/5.8.5/i386-linux-th
read-multi/perllocal.pod /usr/bin/perl -MExtUtils::Command -e
mkpath
/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root
/etc/mail/spamassassin /usr/bin/perl -MFile::Copy -e
copy(q{rules/local.cf},
q{/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/etc/
mail/spamassassin/local.cf}) unless -f
q{/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/etc/
mail/spamassassin/local.cf}
/usr/bin/perl -MFile::Copy -e copy(q{rules/init.pre},
q{/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/etc/
mail/spamassassin/init.pre}) unless -f
q{/var/tmp/spamassassin-toaster-root
Re: [qmailtoaster] upgrade question
qtp-build-rpms v0.2.5 qtp-remove-pkgs v0.2.2 REMOVED spamassassin-toaster from sandbox (not for real) Building spamassassin-toaster-3.2.4-1.3.14 ... qtp-build-rpms - rpmbuild failed for spamassassin-toaster-3.2.4-1.3.14 qtp-build-rpms - see /mnt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log Build failed, Exiting. + install -m 0644 /usr/src/redhat/SOURCES/qmailtoaster.local.cf.bz2 /var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/local.cf.bz2 install: cannot create regular file `/var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/local.cf.bz2': No such file or directory error: Bad exit status from /var/tmp/rpm-tmp.79533 (%install) Jack D. Martin, Jr. - Original Message From: Eric Shubert [EMAIL PROTECTED] To: qmailtoaster-list@qmailtoaster.com Sent: Tuesday, April 8, 2008 12:27:28 PM Subject: Re: [qmailtoaster] upgrade question What error (specifically) do you get with .14? Jack Martin wrote: Helmut, What did you finally do to upgrade spamassassin, I used .14, and still have the file not creating. Jack D. Martin, Jr. - Original Message From: Helmut Fritz [EMAIL PROTECTED] To: qmailtoaster-list@qmailtoaster.com Sent: Tuesday, April 8, 2008 11:27:24 AM Subject: RE: [qmailtoaster] upgrade question I just did a complete upgrade with qtp-mewmodel (found as part of qtp-plus package). Once we got the spamassassin things straight it worked great. If all the fixes are not in there you will need to do a copied sandbox (unless your system can do a unionfs sandbox). It is easy to try as each iteration can be tested - and if it fails you get to start over and you should remove your previous version of the sandbox. Eric, Do you know if your changes are rolled out yet? -Original Message- From: Eric Shubert [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 08, 2008 8:52 AM To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] upgrade question Igor Smitran wrote: In case i want to upgrade packages to a new version one by one, is it enough just to do: rpm -Uvh /usr/src/$BDIR/RPMS/$ARCH/package-name-*.rpm per package? Short answer, no. Is there a procedure for an upgrade that gives minimum down time? Thank you Using the qtp-newmodel script (part of qmailtoaster-plus http://qtp.qmailtoaster.com) will absolutely minimize your down time. You could use qtp-newmodel to do one package at a time, but that would be risky (sometimes there are package interdependencies), and would increase your total down time. IOW, it'd be pointless. Doing them all at once is best. -- -Eric 'shubes' -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] upgrade question
H. I presume this is the version I posted to the list, right? If so, please post more of the contents at the end of build-recent.log, beginning with: Installing /var/tmp/spamassassin-toaster-root/usr/bin/sa-compile Jack Martin wrote: qtp-build-rpms v0.2.5 qtp-remove-pkgs v0.2.2 REMOVED spamassassin-toaster from sandbox (not for real) Building spamassassin-toaster-3.2.4-1.3.14 ... qtp-build-rpms - rpmbuild failed for spamassassin-toaster-3.2.4-1.3.14 qtp-build-rpms - see /mnt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log Build failed, Exiting. + install -m 0644 /usr/src/redhat/SOURCES/qmailtoaster.local.cf.bz2 /var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/local.cf.bz2 install: cannot create regular file `/var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/local.cf.bz2': No such file or directory error: Bad exit status from /var/tmp/rpm-tmp.79533 (%install) Jack D. Martin, Jr. - Original Message From: Eric Shubert [EMAIL PROTECTED] To: qmailtoaster-list@qmailtoaster.com Sent: Tuesday, April 8, 2008 12:27:28 PM Subject: Re: [qmailtoaster] upgrade question What error (specifically) do you get with .14? Jack Martin wrote: Helmut, What did you finally do to upgrade spamassassin, I used .14, and still have the file not creating. Jack D. Martin, Jr. - Original Message From: Helmut Fritz [EMAIL PROTECTED] To: qmailtoaster-list@qmailtoaster.com Sent: Tuesday, April 8, 2008 11:27:24 AM Subject: RE: [qmailtoaster] upgrade question I just did a complete upgrade with qtp-mewmodel (found as part of qtp-plus package). Once we got the spamassassin things straight it worked great. If all the fixes are not in there you will need to do a copied sandbox (unless your system can do a unionfs sandbox). It is easy to try as each iteration can be tested - and if it fails you get to start over and you should remove your previous version of the sandbox. Eric, Do you know if your changes are rolled out yet? -Original Message- From: Eric Shubert [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 08, 2008 8:52 AM To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] upgrade question Igor Smitran wrote: In case i want to upgrade packages to a new version one by one, is it enough just to do: rpm -Uvh /usr/src/$BDIR/RPMS/$ARCH/package-name-*.rpm per package? Short answer, no. Is there a procedure for an upgrade that gives minimum down time? Thank you Using the qtp-newmodel script (part of qmailtoaster-plus http://qtp.qmailtoaster.com) will absolutely minimize your down time. You could use qtp-newmodel to do one package at a time, but that would be risky (sometimes there are package interdependencies), and would increase your total down time. IOW, it'd be pointless. Doing them all at once is best. -- -Eric 'shubes' -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] upgrade question
::AsyncLoop.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Timeout.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin::Hashcash.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::PluginHandler.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Message::Node.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Conf.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Bayes.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin::Rule2XSBody.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::AICache.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin::Pyzor.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::DnsResolver.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin::RelayCountry.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::PerMsgStatus.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin::AntiVirus.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Util::Progress.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin::DomainKeys.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::BayesStore.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin::URIDetail.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Logger.3pm.gz /usr/share/man/man3/Mail::SpamAssassin.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin::WhiteListSubject.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Message.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Conf::Parser.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Logger::File.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin::SPF.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::BayesStore::SQL.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Conf::LDAP.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin::MIMEHeader.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin::ASN.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Message::Metadata.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin::ReplaceTags.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::SQLBasedAddrList.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin::Shortcircuit.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin::AccessDB.3pm.gzX' = X ']' + find /var/tmp/spamassassin-toaster-root/usr/lib/perl5/vendor_perl/5.8.5/Mail /var/tmp/spamassassin-toaster-root/usr/lib/perl5/vendor_perl/5.8.5/spamassassin-run.pod -type d -print + sed '[EMAIL PROTECTED]/var/tmp/[EMAIL PROTECTED] @g' + install -d /var/tmp/spamassassin-toaster-root/etc/cron.hourly + install -d /var/tmp/spamassassin-toaster-root/var/qmail/supervise/spamd + install -d /var/tmp/spamassassin-toaster-root/var/qmail/supervise/spamd/log + install -d /var/tmp/spamassassin-toaster-root/var/qmail/supervise/spamd/supervise + install -d /var/tmp/spamassassin-toaster-root/var/log/qmail + install -d /var/tmp/spamassassin-toaster-root/var/log/qmail/spamd + rm -f /var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/local.cf + rm -f /var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/v310.pre + install -m 0644 /usr/src/redhat/SOURCES/qmailtoaster.local.cf.bz2 /var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/local.cf.bz2 install: cannot create regular file `/var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/local.cf.bz2': No such file or directory error: Bad exit status from /var/tmp/rpm-tmp.5436 (%install) Jack D. Martin, Jr. Magic Wireless Internet Service Provider, LLC [EMAIL PROTECTED] P.O. Box 278 Oilton, OK 74052 (918) 862-1065 (918) 605-9552 cellular - Original Message From: Eric Shubert [EMAIL PROTECTED] To: qmailtoaster-list@qmailtoaster.com Sent: Wednesday, April 9, 2008 11:40:53 AM Subject: Re: [qmailtoaster] upgrade question H. I presume this is the version I posted to the list, right? If so, please post more of the contents at the end of build-recent.log, beginning with: Installing /var/tmp/spamassassin-toaster-root/usr/bin/sa-compile Jack Martin wrote: qtp-build-rpms v0.2.5 qtp-remove-pkgs v0.2.2 REMOVED spamassassin-toaster from sandbox (not for real) Building spamassassin-toaster-3.2.4-1.3.14 ... qtp-build-rpms - rpmbuild failed for spamassassin-toaster-3.2.4-1.3.14 qtp-build-rpms - see /mnt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log Build failed, Exiting. + install -m 0644 /usr/src/redhat/SOURCES/qmailtoaster.local.cf.bz2 /var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/local.cf.bz2 install: cannot create regular file `/var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/local.cf.bz2': No such file or directory error: Bad exit status from /var/tmp/rpm-tmp.79533 (%install) Jack D. Martin, Jr. - Original Message From: Eric Shubert [EMAIL PROTECTED] To: qmailtoaster-list@qmailtoaster.com Sent: Tuesday, April 8, 2008 12:27:28 PM Subject: Re: [qmailtoaster] upgrade question What error (specifically) do you get with .14? Jack Martin wrote: Helmut, What did you finally do to upgrade spamassassin, I used .14, and still have the file not creating. Jack D. Martin, Jr. - Original Message From: Helmut Fritz [EMAIL PROTECTED] To: qmailtoaster-list
Re: [qmailtoaster] upgrade question
Yoa.. what cspan perl mods do you have installed? make sure that they are
the current mod that spamassassin wants.. I had an issue with this upgrade
as well and after I updated the mods all installed fine?
perldoc perllocal
Let me know
Dave
- Original Message -
From: Jack Martin [EMAIL PROTECTED]
To: qmailtoaster-list@qmailtoaster.com
Sent: Wednesday, April 09, 2008 12:27 PM
Subject: Re: [qmailtoaster] upgrade question
This is the rpm that you attached last week, yes. Here are the logs
starting where you said to start:
Installing /var/tmp/spamassassin-toaster-root/usr/bin/sa-compile
Installing /var/tmp/spamassassin-toaster-root/usr/bin/sa-update
Installing /var/tmp/spamassassin-toaster-root/usr/bin/spamd
Installing /var/tmp/spamassassin-toaster-root/usr/bin/sa-learn
Writing
/var/tmp/spamassassin-toaster-root//usr/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi/auto/Mail/SpamAssassin/.packlist
Appending installation info to
/var/tmp/spamassassin-toaster-root//usr/lib/perl5/5.8.5/i386-linux-thread-multi/perllocal.pod
/usr/bin/perl -MExtUtils::Command -e mkpath
/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/etc/mail/spamassassin
/usr/bin/perl -MFile::Copy -e copy(q{rules/local.cf},
q{/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/local.cf})
unless -f
q{/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/local.cf}
/usr/bin/perl -MFile::Copy -e copy(q{rules/init.pre},
q{/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/init.pre})
unless -f
q{/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/init.pre}
/usr/bin/perl -MFile::Copy -e copy(q{rules/v310.pre},
q{/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/v310.pre})
unless -f
q{/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/v310.pre}
/usr/bin/perl -MFile::Copy -e copy(q{rules/v312.pre},
q{/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/v312.pre})
unless -f
q{/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/v312.pre}
/usr/bin/perl -MFile::Copy -e copy(q{rules/v320.pre},
q{/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/v320.pre})
unless -f
q{/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/v320.pre}
/usr/bin/perl -MExtUtils::Command -e mkpath
/var/tmp/spamassassin-toaster-root//usr/share/spamassassin
/usr/bin/perl -e map unlink,
/var/tmp/spamassassin-toaster-root//usr/share/spamassassin/*
/usr/bin/perl
build/preprocessor -Mvars -DVERSION=3.002004 -DPREFIX=/usr -DDEF_RULES_DIR=/usr/share/spamassassin
-DLOCAL_RULES_DIR=/var/tmp/spamassassin-toaster-root/etc/mail/spamassassin -DLOCAL_STATE_DIR=/var/lib/spamassassin -DINSTALLSITELIB=/usr/lib/perl5/vendor_perl/5.8.5 -DCONTACT_ADDRESS=the administrator of thatsystem -m644 -Irules -O/var/tmp/spamassassin-toaster-root//usr/share/spamassassin 10_default_prefs.cf 20_advance_fee.cf 20_body_tests.cf20_compensate.cf 20_dnsbl_tests.cf 20_drugs.cf 20_dynrdns.cf20_fake_helo_tests.cf 20_head_tests.cf 20_html_tests.cf 20_imageinfo.cf20_meta_tests.cf 20_net_tests.cf 20_phrases.cf 20_porn.cf 20_ratware.cf20_uri_tests.cf 20_vbounce.cf 23_bayes.cf 25_accessdb.cf 25_antivirus.cf25_asn.cf 25_dcc.cf 25_dkim.cf 25_domainkeys.cf 25_hashcash.cf 25_pyzor.cf25_razor2.cf 25_replace.cf 25_spf.cf 25_textcat.cf 25_uribl.cf 30_text_de.cf30_text_fr.cf 30_text_it.cf 30_text_nl.cf 30_text_pl.cf 30_text_pt_br.cf 50_scores.cf 60_awl.cf 60_shortcircuit.cf 60_whitelist.cf60_whitelist_dk.cf 60_whitelist_dkim.cf 60_whitelist_spf.cf60_whitelist_subject.cf 72_active.cf user_prefs.template languagessa-update-pubkey.txt chmod 755 /var/tmp/spamassassin-toaster-root//usr/share/spamassassin + chmod 755 /var/tmp/spamassassin-toaster-root/usr/bin/sa-compile/var/tmp/spamassassin-toaster-root/usr/bin/sa-learn/var/tmp/spamassassin-toaster-root/usr/bin/sa-update/var/tmp/spamassassin-toaster-root/usr/bin/spamassassin/var/tmp/spamassassin-toaster-root/usr/bin/spamc/var/tmp/spamassassin-toaster-root/usr/bin/spamd + '[' -x /usr/lib/rpm/brp-compress ']' + /usr/lib/rpm/brp-compress + find /var/tmp/spamassassin-toaster-root '(' -name perllocal.pod -o -name.packlist ')' -exec rm -v '{}' ';' removed`/var/tmp/spamassassin-toaster-root/usr/lib/perl5/5.8.5/i386-linux-thread-multi/perllocal.pod' removed`/var/tmp/spamassassin-toaster-root/usr/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi/auto/Mail/SpamAssassin/.packlist' + find /var/tmp/spamassassin-toaster-root -type d -depth -exec rmdir '{}'';' + find /var/tmp/spamassassin-toaster-root/usr -type f -print + sed '[EMAIL PROTECTED]/var/tmp/spamassassin-toaster-root@@g' + grep -v perllocal.pod + grep -v '\.packlist' ++ cat
Re: [qmailtoaster] upgrade question
::SpamAssassin::BayesStore::PgSQL.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::AutoWhitelist.3pm.gz /usr/share/man/man3/spamassassin-run.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Client.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Logger::Stderr.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin::AWL.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin::OneLineBodyRuleType.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin::URIDNSBL.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin::DCC.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::ArchiveIterator.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::BayesStore::MySQL.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin::Razor2.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin::Test.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Util.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin::DKIM.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin::TextCat.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin::AutoLearnThreshold.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::SubProcBackChannel.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::PersistentAddrList.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin::BodyRuleBaseExtractor.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::AsyncLoop.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Timeout.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin::Hashcash.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::PluginHandler.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Message::Node.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Conf.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Bayes.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin::Rule2XSBody.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::AICache.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin::Pyzor.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::DnsResolver.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin::RelayCountry.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::PerMsgStatus.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin::AntiVirus.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Util::Progress.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin::DomainKeys.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::BayesStore.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin::URIDetail.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Logger.3pm.gz /usr/share/man/man3/Mail::SpamAssassin.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin::WhiteListSubject.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Message.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Conf::Parser.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Logger::File.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin::SPF.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::BayesStore::SQL.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Conf::LDAP.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin::MIMEHeader.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin::ASN.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Message::Metadata.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin::ReplaceTags.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::SQLBasedAddrList.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin::Shortcircuit.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin::AccessDB.3pm.gzX' = X ']' + find /var/tmp/spamassassin-toaster-root/usr/lib/perl5/vendor_perl/5.8.5/Mail /var/tmp/spamassassin-toaster-root/usr/lib/perl5/vendor_perl/5.8.5/spamassassin-run.pod -type d -print + sed '[EMAIL PROTECTED]/var/tmp/[EMAIL PROTECTED] @g' + install -d /var/tmp/spamassassin-toaster-root/etc/cron.hourly + install -d /var/tmp/spamassassin-toaster-root/var/qmail/supervise/spamd + install -d /var/tmp/spamassassin-toaster-root/var/qmail/supervise/spamd/log + install -d /var/tmp/spamassassin-toaster-root/var/qmail/supervise/spamd/supervise + install -d /var/tmp/spamassassin-toaster-root/var/log/qmail + install -d /var/tmp/spamassassin-toaster-root/var/log/qmail/spamd + rm -f /var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/local.cf + rm -f /var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/v310.pre + install -m 0644 /usr/src/redhat/SOURCES/qmailtoaster.local.cf.bz2 /var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/local.cf.bz2 install: cannot create regular file `/var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/local.cf.bz2': No such file or directory error: Bad exit status from /var/tmp/rpm-tmp.5436 (%install) Jack D. Martin, Jr. Magic Wireless Internet Service Provider, LLC [EMAIL PROTECTED] P.O. Box 278 Oilton, OK 74052 (918) 862-1065 (918) 605-9552 cellular - Original Message From: Eric Shubert [EMAIL PROTECTED] To: qmailtoaster-list@qmailtoaster.com Sent: Wednesday, April 9, 2008 11:40:53 AM Subject: Re: [qmailtoaster] upgrade question H. I presume this is the version I
Re: [qmailtoaster] upgrade question
Before I do it - I am upgrading my perl modules just to see if that could
possibly be the problem.
Jack D. Martin, Jr.
Magic Wireless Internet Service Provider, LLC
[EMAIL PROTECTED]
P.O. Box 278
Oilton, OK 74052
(918) 862-1065
(918) 605-9552 cellular
- Original Message
From: Eric Shubert [EMAIL PROTECTED]
To: qmailtoaster-list@qmailtoaster.com
Sent: Wednesday, April 9, 2008 3:30:37 PM
Subject: Re: [qmailtoaster] upgrade question
I did a little more testing, and it appears that the problematic parameter
to the %makeinstall command isn't needed at all. I remove it and the package
appears to have built with the local rules files in the desired location.
Attached is the source rpm with the problematic parameter removed. Jack,
will you give it a try?
Once again, my apologies for the large attachment to the list.
Eric Shubert wrote:
The command:
/usr/bin/perl -MExtUtils::Command -e mkpath
/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/etc/mail/spamassassin
was supposed to create the directory that's missing, but it appears to have
prepended the %{buildroot} directory, which is incorrect.
Now here's the weird thing. The 'bug' before that I attempted to fix was
that the %{buildroot} directory wasn't there, so I added it. Now it appears
to be there again, in addition to the one I added. So sometimes rpmbuild (or
SA's Makefile.PL more specifically) includes the %{buildroot} directory, and
sometimes it doesn't. Weird.
I can understand that something's different which causes %{buildroot} to
sometimes be there and sometimes not on different machines, but on the same
machine it's sorta baffling.
Jack, can you try the 1.3.13 version again on your toaster? I'm wondering if
it might work now. In any case, I'm thinking that either one or the other
should work. I still have yet to figure out why %{buildroot} is included
sometimes and other times not.
Jack Martin wrote:
This is the rpm that you attached last week, yes. Here are the logs
starting where you said to start:
Installing /var/tmp/spamassassin-toaster-root/usr/bin/sa-compile
Installing /var/tmp/spamassassin-toaster-root/usr/bin/sa-update
Installing /var/tmp/spamassassin-toaster-root/usr/bin/spamd
Installing /var/tmp/spamassassin-toaster-root/usr/bin/sa-learn
Writing
/var/tmp/spamassassin-toaster-root//usr/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi/auto/Mail/SpamAssassin/.packlist
Appending installation info to
/var/tmp/spamassassin-toaster-root//usr/lib/perl5/5.8.5/i386-linux-thread-multi/perllocal.pod
/usr/bin/perl -MExtUtils::Command -e mkpath
/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/etc/mail/spamassassin
/usr/bin/perl -MFile::Copy -e copy(q{rules/local.cf},
q{/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/local.cf})
unless -f
q{/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/local.cf}
/usr/bin/perl -MFile::Copy -e copy(q{rules/init.pre},
q{/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/init.pre})
unless -f
q{/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/init.pre}
/usr/bin/perl -MFile::Copy -e copy(q{rules/v310.pre},
q{/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/v310.pre})
unless -f
q{/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/v310.pre}
/usr/bin/perl -MFile::Copy -e copy(q{rules/v312.pre},
q{/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/v312.pre})
unless -f
q{/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/v312.pre}
/usr/bin/perl -MFile::Copy -e copy(q{rules/v320.pre},
q{/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/v320.pre})
unless -f
q{/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/v320.pre}
/usr/bin/perl -MExtUtils::Command -e mkpath
/var/tmp/spamassassin-toaster-root//usr/share/spamassassin
/usr/bin/perl -e map unlink,
/var/tmp/spamassassin-toaster-root//usr/share/spamassassin/*
/usr/bin/perl build/preprocessor -Mvars -DVERSION=3.002004 -DPREFIX=/usr
-DDEF_RULES_DIR=/usr/share/spamassassin
-DLOCAL_RULES_DIR=/var/tmp/spamassassin-toaster-root/etc/mail/spamassassin
-DLOCAL_STATE_DIR=/var/lib/spamassassin
-DINSTALLSITELIB=/usr/lib/perl5/vendor_perl/5.8.5 -DCONTACT_ADDRESS=the
administrator of that system -m644 -Irules
-O/var/tmp/spamassassin-toaster-root//usr/share/spamassassin
10_default_prefs.cf 20_advance_fee.cf 20_body_tests.cf 20_compensate.cf
20_dnsbl_tests.cf 20_drugs.cf 20_dynrdns.cf 20_fake_helo_tests.cf
20_head_tests.cf 20_html_tests.cf 20_imageinfo.cf 20_meta_tests.cf
20_net_tests.cf 20_phrases.cf 20_porn.cf
Re: [qmailtoaster] upgrade question
Fine. The only perl module I suspect might make a difference would be MakeMaker.
Jack Martin wrote:
Before I do it - I am upgrading my perl modules just to see if that could
possibly be the problem.
Jack D. Martin, Jr.
Magic Wireless Internet Service Provider, LLC
[EMAIL PROTECTED]
P.O. Box 278
Oilton, OK 74052
(918) 862-1065
(918) 605-9552 cellular
- Original Message
From: Eric Shubert [EMAIL PROTECTED]
To: qmailtoaster-list@qmailtoaster.com
Sent: Wednesday, April 9, 2008 3:30:37 PM
Subject: Re: [qmailtoaster] upgrade question
I did a little more testing, and it appears that the problematic parameter
to the %makeinstall command isn't needed at all. I remove it and the package
appears to have built with the local rules files in the desired location.
Attached is the source rpm with the problematic parameter removed. Jack,
will you give it a try?
Once again, my apologies for the large attachment to the list.
Eric Shubert wrote:
The command:
/usr/bin/perl -MExtUtils::Command -e mkpath
/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/etc/mail/spamassassin
was supposed to create the directory that's missing, but it appears to have
prepended the %{buildroot} directory, which is incorrect.
Now here's the weird thing. The 'bug' before that I attempted to fix was
that the %{buildroot} directory wasn't there, so I added it. Now it appears
to be there again, in addition to the one I added. So sometimes rpmbuild (or
SA's Makefile.PL more specifically) includes the %{buildroot} directory, and
sometimes it doesn't. Weird.
I can understand that something's different which causes %{buildroot} to
sometimes be there and sometimes not on different machines, but on the same
machine it's sorta baffling.
Jack, can you try the 1.3.13 version again on your toaster? I'm wondering if
it might work now. In any case, I'm thinking that either one or the other
should work. I still have yet to figure out why %{buildroot} is included
sometimes and other times not.
Jack Martin wrote:
This is the rpm that you attached last week, yes. Here are the logs
starting where you said to start:
Installing /var/tmp/spamassassin-toaster-root/usr/bin/sa-compile
Installing /var/tmp/spamassassin-toaster-root/usr/bin/sa-update
Installing /var/tmp/spamassassin-toaster-root/usr/bin/spamd
Installing /var/tmp/spamassassin-toaster-root/usr/bin/sa-learn
Writing
/var/tmp/spamassassin-toaster-root//usr/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi/auto/Mail/SpamAssassin/.packlist
Appending installation info to
/var/tmp/spamassassin-toaster-root//usr/lib/perl5/5.8.5/i386-linux-thread-multi/perllocal.pod
/usr/bin/perl -MExtUtils::Command -e mkpath
/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/etc/mail/spamassassin
/usr/bin/perl -MFile::Copy -e copy(q{rules/local.cf},
q{/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/local.cf})
unless -f
q{/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/local.cf}
/usr/bin/perl -MFile::Copy -e copy(q{rules/init.pre},
q{/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/init.pre})
unless -f
q{/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/init.pre}
/usr/bin/perl -MFile::Copy -e copy(q{rules/v310.pre},
q{/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/v310.pre})
unless -f
q{/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/v310.pre}
/usr/bin/perl -MFile::Copy -e copy(q{rules/v312.pre},
q{/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/v312.pre})
unless -f
q{/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/v312.pre}
/usr/bin/perl -MFile::Copy -e copy(q{rules/v320.pre},
q{/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/v320.pre})
unless -f
q{/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/v320.pre}
/usr/bin/perl -MExtUtils::Command -e mkpath
/var/tmp/spamassassin-toaster-root//usr/share/spamassassin
/usr/bin/perl -e map unlink,
/var/tmp/spamassassin-toaster-root//usr/share/spamassassin/*
/usr/bin/perl build/preprocessor -Mvars -DVERSION=3.002004
-DPREFIX=/usr -DDEF_RULES_DIR=/usr/share/spamassassin
-DLOCAL_RULES_DIR=/var/tmp/spamassassin-toaster-root/etc/mail/spamassassin
-DLOCAL_STATE_DIR=/var/lib/spamassassin
-DINSTALLSITELIB=/usr/lib/perl5/vendor_perl/5.8.5 -DCONTACT_ADDRESS=the
administrator of that system -m644 -Irules
-O/var/tmp/spamassassin-toaster-root//usr/share/spamassassin
10_default_prefs.cf 20_advance_fee.cf 20_body_tests.cf 20_compensate.cf
20_dnsbl_tests.cf 20_drugs.cf 20_dynrdns.cf
RE: [qmailtoaster] upgrade question
Jack,
I highly suggest using the rpmforge repository/yum to update Cpan just
does not seem to have the latest stuff...
-Original Message-
From: Jack Martin [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 09, 2008 1:59 PM
To: qmailtoaster-list@qmailtoaster.com
Subject: Re: [qmailtoaster] upgrade question
Before I do it - I am upgrading my perl modules just to see if that could
possibly be the problem.
Jack D. Martin, Jr.
Magic Wireless Internet Service Provider, LLC [EMAIL PROTECTED]
P.O. Box 278 Oilton, OK 74052
(918) 862-1065
(918) 605-9552 cellular
- Original Message
From: Eric Shubert [EMAIL PROTECTED]
To: qmailtoaster-list@qmailtoaster.com
Sent: Wednesday, April 9, 2008 3:30:37 PM
Subject: Re: [qmailtoaster] upgrade question
I did a little more testing, and it appears that the problematic parameter
to the %makeinstall command isn't needed at all. I remove it and the package
appears to have built with the local rules files in the desired location.
Attached is the source rpm with the problematic parameter removed. Jack,
will you give it a try?
Once again, my apologies for the large attachment to the list.
Eric Shubert wrote:
The command:
/usr/bin/perl -MExtUtils::Command -e mkpath
/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/
etc/mail/spamassassin was supposed to create the directory that's
missing, but it appears to have prepended the %{buildroot} directory,
which is incorrect.
Now here's the weird thing. The 'bug' before that I attempted to fix
was that the %{buildroot} directory wasn't there, so I added it. Now
it appears to be there again, in addition to the one I added. So
sometimes rpmbuild (or SA's Makefile.PL more specifically) includes
the %{buildroot} directory, and sometimes it doesn't. Weird.
I can understand that something's different which causes %{buildroot}
to sometimes be there and sometimes not on different machines, but on
the same machine it's sorta baffling.
Jack, can you try the 1.3.13 version again on your toaster? I'm
wondering if it might work now. In any case, I'm thinking that either
one or the other should work. I still have yet to figure out why
%{buildroot} is included sometimes and other times not.
Jack Martin wrote:
This is the rpm that you attached last week, yes. Here are the logs
starting where you said to start:
Installing /var/tmp/spamassassin-toaster-root/usr/bin/sa-compile
Installing /var/tmp/spamassassin-toaster-root/usr/bin/sa-update
Installing /var/tmp/spamassassin-toaster-root/usr/bin/spamd
Installing /var/tmp/spamassassin-toaster-root/usr/bin/sa-learn
Writing
/var/tmp/spamassassin-toaster-root//usr/lib/perl5/vendor_perl/5.8.5/i
386-linux-thread-multi/auto/Mail/SpamAssassin/.packlist
Appending installation info to
/var/tmp/spamassassin-toaster-root//usr/lib/perl5/5.8.5/i386-linux-th
read-multi/perllocal.pod /usr/bin/perl -MExtUtils::Command -e
mkpath
/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root
/etc/mail/spamassassin /usr/bin/perl -MFile::Copy -e
copy(q{rules/local.cf},
q{/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/etc/
mail/spamassassin/local.cf}) unless -f
q{/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/etc/
mail/spamassassin/local.cf}
/usr/bin/perl -MFile::Copy -e copy(q{rules/init.pre},
q{/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/etc/
mail/spamassassin/init.pre}) unless -f
q{/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/etc/
mail/spamassassin/init.pre}
/usr/bin/perl -MFile::Copy -e copy(q{rules/v310.pre},
q{/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/etc/
mail/spamassassin/v310.pre}) unless -f
q{/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/etc/
mail/spamassassin/v310.pre}
/usr/bin/perl -MFile::Copy -e copy(q{rules/v312.pre},
q{/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/etc/
mail/spamassassin/v312.pre}) unless -f
q{/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/etc/
mail/spamassassin/v312.pre}
/usr/bin/perl -MFile::Copy -e copy(q{rules/v320.pre},
q{/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/etc/
mail/spamassassin/v320.pre}) unless -f
q{/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/etc/
mail/spamassassin/v320.pre}
/usr/bin/perl -MExtUtils::Command -e mkpath
/var/tmp/spamassassin-toaster-root//usr/share/spamassassin
/usr/bin/perl -e map unlink,
/var/tmp/spamassassin-toaster-root//usr/share/spamassassin/*
/usr/bin/perl build/preprocessor -Mvars -DVERSION=3.002004
-DPREFIX=/usr -DDEF_RULES_DIR=/usr/share/spamassassin
-DLOCAL_RULES_DIR=/var/tmp/spamassassin-toaster-root/etc/mail/spamas
sassin -DLOCAL_STATE_DIR=/var/lib/spamassassin
-DINSTALLSITELIB=/usr/lib/perl5/vendor_perl/5.8.5
-DCONTACT_ADDRESS=the administrator of that system -m644 -Irules
-O
Re: [qmailtoaster] upgrade question
Most of my modules are installed using CPAN, so I am not going to un-install
and re-install them. I have started using the rpmforge repo for all new
modules, just because it seems easier to install and maintain.
Jack D. Martin, Jr.
Magic Wireless Internet Service Provider, LLC
[EMAIL PROTECTED]
P.O. Box 278
Oilton, OK 74052
(918) 862-1065
(918) 605-9552 cellular
- Original Message
From: Helmut Fritz [EMAIL PROTECTED]
To: qmailtoaster-list@qmailtoaster.com
Sent: Wednesday, April 9, 2008 4:10:35 PM
Subject: RE: [qmailtoaster] upgrade question
Jack,
I highly suggest using the rpmforge repository/yum to update Cpan just
does not seem to have the latest stuff...
-Original Message-
From: Jack Martin [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 09, 2008 1:59 PM
To: qmailtoaster-list@qmailtoaster.com
Subject: Re: [qmailtoaster] upgrade question
Before I do it - I am upgrading my perl modules just to see if that could
possibly be the problem.
Jack D. Martin, Jr.
Magic Wireless Internet Service Provider, LLC [EMAIL PROTECTED]
P.O. Box 278 Oilton, OK 74052
(918) 862-1065
(918) 605-9552 cellular
- Original Message
From: Eric Shubert [EMAIL PROTECTED]
To: qmailtoaster-list@qmailtoaster.com
Sent: Wednesday, April 9, 2008 3:30:37 PM
Subject: Re: [qmailtoaster] upgrade question
I did a little more testing, and it appears that the problematic parameter
to the %makeinstall command isn't needed at all. I remove it and the package
appears to have built with the local rules files in the desired location.
Attached is the source rpm with the problematic parameter removed. Jack,
will you give it a try?
Once again, my apologies for the large attachment to the list.
Eric Shubert wrote:
The command:
/usr/bin/perl -MExtUtils::Command -e mkpath
/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/
etc/mail/spamassassin was supposed to create the directory that's
missing, but it appears to have prepended the %{buildroot} directory,
which is incorrect.
Now here's the weird thing. The 'bug' before that I attempted to fix
was that the %{buildroot} directory wasn't there, so I added it. Now
it appears to be there again, in addition to the one I added. So
sometimes rpmbuild (or SA's Makefile.PL more specifically) includes
the %{buildroot} directory, and sometimes it doesn't. Weird.
I can understand that something's different which causes %{buildroot}
to sometimes be there and sometimes not on different machines, but on
the same machine it's sorta baffling.
Jack, can you try the 1.3.13 version again on your toaster? I'm
wondering if it might work now. In any case, I'm thinking that either
one or the other should work. I still have yet to figure out why
%{buildroot} is included sometimes and other times not.
Jack Martin wrote:
This is the rpm that you attached last week, yes. Here are the logs
starting where you said to start:
Installing /var/tmp/spamassassin-toaster-root/usr/bin/sa-compile
Installing /var/tmp/spamassassin-toaster-root/usr/bin/sa-update
Installing /var/tmp/spamassassin-toaster-root/usr/bin/spamd
Installing /var/tmp/spamassassin-toaster-root/usr/bin/sa-learn
Writing
/var/tmp/spamassassin-toaster-root//usr/lib/perl5/vendor_perl/5.8.5/i
386-linux-thread-multi/auto/Mail/SpamAssassin/.packlist
Appending installation info to
/var/tmp/spamassassin-toaster-root//usr/lib/perl5/5.8.5/i386-linux-th
read-multi/perllocal.pod /usr/bin/perl -MExtUtils::Command -e
mkpath
/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root
/etc/mail/spamassassin /usr/bin/perl -MFile::Copy -e
copy(q{rules/local.cf},
q{/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/etc/
mail/spamassassin/local.cf}) unless -f
q{/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/etc/
mail/spamassassin/local.cf}
/usr/bin/perl -MFile::Copy -e copy(q{rules/init.pre},
q{/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/etc/
mail/spamassassin/init.pre}) unless -f
q{/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/etc/
mail/spamassassin/init.pre}
/usr/bin/perl -MFile::Copy -e copy(q{rules/v310.pre},
q{/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/etc/
mail/spamassassin/v310.pre}) unless -f
q{/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/etc/
mail/spamassassin/v310.pre}
/usr/bin/perl -MFile::Copy -e copy(q{rules/v312.pre},
q{/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/etc/
mail/spamassassin/v312.pre}) unless -f
q{/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/etc/
mail/spamassassin/v312.pre}
/usr/bin/perl -MFile::Copy -e copy(q{rules/v320.pre},
q{/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/etc/
mail/spamassassin/v320.pre}) unless -f
q{/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/etc/
mail
RE: [qmailtoaster] upgrade question
Not easier...'bout the same. Some modules are just not on cpan - that is
the issue. Up until I did the upgrade for qmt, I have always used cpan as
well.
You also do not have to uninstall and reinstall... Just get the repository
rpm, install it and then use yum...
-Original Message-
From: Jack Martin [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 09, 2008 2:26 PM
To: qmailtoaster-list@qmailtoaster.com
Subject: Re: [qmailtoaster] upgrade question
Most of my modules are installed using CPAN, so I am not going to un-install
and re-install them. I have started using the rpmforge repo for all new
modules, just because it seems easier to install and maintain.
Jack D. Martin, Jr.
Magic Wireless Internet Service Provider, LLC [EMAIL PROTECTED]
P.O. Box 278 Oilton, OK 74052
(918) 862-1065
(918) 605-9552 cellular
- Original Message
From: Helmut Fritz [EMAIL PROTECTED]
To: qmailtoaster-list@qmailtoaster.com
Sent: Wednesday, April 9, 2008 4:10:35 PM
Subject: RE: [qmailtoaster] upgrade question
Jack,
I highly suggest using the rpmforge repository/yum to update Cpan just
does not seem to have the latest stuff...
-Original Message-
From: Jack Martin [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 09, 2008 1:59 PM
To: qmailtoaster-list@qmailtoaster.com
Subject: Re: [qmailtoaster] upgrade question
Before I do it - I am upgrading my perl modules just to see if that could
possibly be the problem.
Jack D. Martin, Jr.
Magic Wireless Internet Service Provider, LLC [EMAIL PROTECTED]
P.O. Box 278 Oilton, OK 74052
(918) 862-1065
(918) 605-9552 cellular
- Original Message
From: Eric Shubert [EMAIL PROTECTED]
To: qmailtoaster-list@qmailtoaster.com
Sent: Wednesday, April 9, 2008 3:30:37 PM
Subject: Re: [qmailtoaster] upgrade question
I did a little more testing, and it appears that the problematic parameter
to the %makeinstall command isn't needed at all. I remove it and the package
appears to have built with the local rules files in the desired location.
Attached is the source rpm with the problematic parameter removed. Jack,
will you give it a try?
Once again, my apologies for the large attachment to the list.
Eric Shubert wrote:
The command:
/usr/bin/perl -MExtUtils::Command -e mkpath
/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/
etc/mail/spamassassin was supposed to create the directory that's
missing, but it appears to have prepended the %{buildroot} directory,
which is incorrect.
Now here's the weird thing. The 'bug' before that I attempted to fix
was that the %{buildroot} directory wasn't there, so I added it. Now
it appears to be there again, in addition to the one I added. So
sometimes rpmbuild (or SA's Makefile.PL more specifically) includes
the %{buildroot} directory, and sometimes it doesn't. Weird.
I can understand that something's different which causes %{buildroot}
to sometimes be there and sometimes not on different machines, but on
the same machine it's sorta baffling.
Jack, can you try the 1.3.13 version again on your toaster? I'm
wondering if it might work now. In any case, I'm thinking that either
one or the other should work. I still have yet to figure out why
%{buildroot} is included sometimes and other times not.
Jack Martin wrote:
This is the rpm that you attached last week, yes. Here are the logs
starting where you said to start:
Installing /var/tmp/spamassassin-toaster-root/usr/bin/sa-compile
Installing /var/tmp/spamassassin-toaster-root/usr/bin/sa-update
Installing /var/tmp/spamassassin-toaster-root/usr/bin/spamd
Installing /var/tmp/spamassassin-toaster-root/usr/bin/sa-learn
Writing
/var/tmp/spamassassin-toaster-root//usr/lib/perl5/vendor_perl/5.8.5/i
386-linux-thread-multi/auto/Mail/SpamAssassin/.packlist
Appending installation info to
/var/tmp/spamassassin-toaster-root//usr/lib/perl5/5.8.5/i386-linux-th
read-multi/perllocal.pod /usr/bin/perl -MExtUtils::Command -e
mkpath
/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root
/etc/mail/spamassassin /usr/bin/perl -MFile::Copy -e
copy(q{rules/local.cf},
q{/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/etc/
mail/spamassassin/local.cf}) unless -f
q{/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/etc/
mail/spamassassin/local.cf}
/usr/bin/perl -MFile::Copy -e copy(q{rules/init.pre},
q{/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/etc/
mail/spamassassin/init.pre}) unless -f
q{/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/etc/
mail/spamassassin/init.pre}
/usr/bin/perl -MFile::Copy -e copy(q{rules/v310.pre},
q{/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/etc/
mail/spamassassin/v310.pre}) unless -f
q{/var/tmp/spamassassin-toaster-root//var/tmp/spamassassin-toaster-root/etc/
mail/spamassassin/v310.pre}
/usr/bin/perl -MFile::Copy -e copy(q{rules/v312.pre},
q{/var/tmp/spamassassin
[qmailtoaster] upgrade question
In case i want to upgrade packages to a new version one by one, is it enough just to do: rpm -Uvh /usr/src/$BDIR/RPMS/$ARCH/package-name-*.rpm per package? Is there a procedure for an upgrade that gives minimum down time? Thank you
Re: [qmailtoaster] upgrade question
Igor Smitran wrote: In case i want to upgrade packages to a new version one by one, is it enough just to do: rpm -Uvh /usr/src/$BDIR/RPMS/$ARCH/package-name-*.rpm per package? Short answer, no. Is there a procedure for an upgrade that gives minimum down time? Thank you Using the qtp-newmodel script (part of qmailtoaster-plus http://qtp.qmailtoaster.com) will absolutely minimize your down time. You could use qtp-newmodel to do one package at a time, but that would be risky (sometimes there are package interdependencies), and would increase your total down time. IOW, it'd be pointless. Doing them all at once is best. -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [qmailtoaster] upgrade question
I just did a complete upgrade with qtp-mewmodel (found as part of qtp-plus package). Once we got the spamassassin things straight it worked great. If all the fixes are not in there you will need to do a copied sandbox (unless your system can do a unionfs sandbox). It is easy to try as each iteration can be tested - and if it fails you get to start over and you should remove your previous version of the sandbox. Eric, Do you know if your changes are rolled out yet? -Original Message- From: Eric Shubert [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 08, 2008 8:52 AM To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] upgrade question Igor Smitran wrote: In case i want to upgrade packages to a new version one by one, is it enough just to do: rpm -Uvh /usr/src/$BDIR/RPMS/$ARCH/package-name-*.rpm per package? Short answer, no. Is there a procedure for an upgrade that gives minimum down time? Thank you Using the qtp-newmodel script (part of qmailtoaster-plus http://qtp.qmailtoaster.com) will absolutely minimize your down time. You could use qtp-newmodel to do one package at a time, but that would be risky (sometimes there are package interdependencies), and would increase your total down time. IOW, it'd be pointless. Doing them all at once is best. -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] upgrade question
The latest fixes are not yet packaged. Jake said that he hoped to get to it by the end of this week or over this coming weekend. Helmut Fritz wrote: I just did a complete upgrade with qtp-mewmodel (found as part of qtp-plus package). Once we got the spamassassin things straight it worked great. If all the fixes are not in there you will need to do a copied sandbox (unless your system can do a unionfs sandbox). It is easy to try as each iteration can be tested - and if it fails you get to start over and you should remove your previous version of the sandbox. Eric, Do you know if your changes are rolled out yet? -Original Message- From: Eric Shubert [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 08, 2008 8:52 AM To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] upgrade question Igor Smitran wrote: In case i want to upgrade packages to a new version one by one, is it enough just to do: rpm -Uvh /usr/src/$BDIR/RPMS/$ARCH/package-name-*.rpm per package? Short answer, no. Is there a procedure for an upgrade that gives minimum down time? Thank you Using the qtp-newmodel script (part of qmailtoaster-plus http://qtp.qmailtoaster.com) will absolutely minimize your down time. You could use qtp-newmodel to do one package at a time, but that would be risky (sometimes there are package interdependencies), and would increase your total down time. IOW, it'd be pointless. Doing them all at once is best. -- -Eric 'shubes' -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] upgrade question
Helmut, What did you finally do to upgrade spamassassin, I used .14, and still have the file not creating. Jack D. Martin, Jr. - Original Message From: Helmut Fritz [EMAIL PROTECTED] To: qmailtoaster-list@qmailtoaster.com Sent: Tuesday, April 8, 2008 11:27:24 AM Subject: RE: [qmailtoaster] upgrade question I just did a complete upgrade with qtp-mewmodel (found as part of qtp-plus package). Once we got the spamassassin things straight it worked great. If all the fixes are not in there you will need to do a copied sandbox (unless your system can do a unionfs sandbox). It is easy to try as each iteration can be tested - and if it fails you get to start over and you should remove your previous version of the sandbox. Eric, Do you know if your changes are rolled out yet? -Original Message- From: Eric Shubert [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 08, 2008 8:52 AM To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] upgrade question Igor Smitran wrote: In case i want to upgrade packages to a new version one by one, is it enough just to do: rpm -Uvh /usr/src/$BDIR/RPMS/$ARCH/package-name-*.rpm per package? Short answer, no. Is there a procedure for an upgrade that gives minimum down time? Thank you Using the qtp-newmodel script (part of qmailtoaster-plus http://qtp.qmailtoaster.com) will absolutely minimize your down time. You could use qtp-newmodel to do one package at a time, but that would be risky (sometimes there are package interdependencies), and would increase your total down time. IOW, it'd be pointless. Doing them all at once is best. -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] upgrade question
What error (specifically) do you get with .14? Jack Martin wrote: Helmut, What did you finally do to upgrade spamassassin, I used .14, and still have the file not creating. Jack D. Martin, Jr. - Original Message From: Helmut Fritz [EMAIL PROTECTED] To: qmailtoaster-list@qmailtoaster.com Sent: Tuesday, April 8, 2008 11:27:24 AM Subject: RE: [qmailtoaster] upgrade question I just did a complete upgrade with qtp-mewmodel (found as part of qtp-plus package). Once we got the spamassassin things straight it worked great. If all the fixes are not in there you will need to do a copied sandbox (unless your system can do a unionfs sandbox). It is easy to try as each iteration can be tested - and if it fails you get to start over and you should remove your previous version of the sandbox. Eric, Do you know if your changes are rolled out yet? -Original Message- From: Eric Shubert [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 08, 2008 8:52 AM To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] upgrade question Igor Smitran wrote: In case i want to upgrade packages to a new version one by one, is it enough just to do: rpm -Uvh /usr/src/$BDIR/RPMS/$ARCH/package-name-*.rpm per package? Short answer, no. Is there a procedure for an upgrade that gives minimum down time? Thank you Using the qtp-newmodel script (part of qmailtoaster-plus http://qtp.qmailtoaster.com) will absolutely minimize your down time. You could use qtp-newmodel to do one package at a time, but that would be risky (sometimes there are package interdependencies), and would increase your total down time. IOW, it'd be pointless. Doing them all at once is best. -- -Eric 'shubes' -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] upgrade Centos and Qmailtoaster
You don't have any comments on my questions? Istvan Köpe wrote: Hello, I have two Qmailtoaster servers running on Centos 4.3 x86_64. I would like install on them to Centos 5.1. Now I have two questions: Based on your experience is there a difference in performance between x86_64 and i386 Centos distributions? Or is there any other sensible difference between the 32 and 64 bit distributions? What do you recommend? How can I make this upgrade without loosing the email accounts on these servers? I intend to format both servers. Please give me a few guide lines, to now screw up something. I intend to do the following: - install QmailToaster-Plus - backup the existing QmailToaster - save the backup - format the servers and install Centos 5.1 - install the latest QmailToaster - install QmailToaster-Plus - restore QmailToaster It will work like this?? Istvan - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] upgrade Centos and Qmailtoaster
just my opinion. - as long as CentOS still provide update for version 4, I am not planning an upgrade to version 5. - if your server hardware is x86_64 capable why not using x86_64 version You don't have any comments on my questions? Istvan Köpe wrote: Hello, I have two Qmailtoaster servers running on Centos 4.3 x86_64. I would like install on them to Centos 5.1. Now I have two questions: Based on your experience is there a difference in performance between x86_64 and i386 Centos distributions? Or is there any other sensible difference between the 32 and 64 bit distributions? What do you recommend? How can I make this upgrade without loosing the email accounts on these servers? I intend to format both servers. Please give me a few guide lines, to now screw up something. I intend to do the following: - install QmailToaster-Plus - backup the existing QmailToaster - save the backup - format the servers and install Centos 5.1 - install the latest QmailToaster - install QmailToaster-Plus - restore QmailToaster It will work like this?? - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[qmailtoaster] upgrade Centos and Qmailtoaster
Hello, I have two Qmailtoaster servers running on Centos 4.3 x86_64. I would like install on them to Centos 5.1. Now I have two questions: Based on your experience is there a difference in performance between x86_64 and i386 Centos distributions? Or is there any other sensible difference between the 32 and 64 bit distributions? What do you recommend? How can I make this upgrade without loosing the email accounts on these servers? I intend to format both servers. Please give me a few guide lines, to now screw up something. I intend to do the following: - install QmailToaster-Plus - backup the existing QmailToaster - save the backup - format the servers and install Centos 5.1 - install the latest QmailToaster - install QmailToaster-Plus - restore QmailToaster It will work like this?? Istvan - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[qmailtoaster] Upgrade Error
I receive this error when trying to run qtp-newmodel on my server: Installing control-panel-toaster-0.5-1.3.4 in the sandbox ... error: Failed dependencies: vpopmail-toaster = 5.4.17 is needed by send-emails-toaster-0.5-1.3.4.noarch vpopmail-toaster is included in the update packages. It appears there is an order issue here. Anyone know how I correct? [EMAIL PROTECTED] ~]# qtp-newmodel qtp-newmodel v0.2.7 starting Tue Oct 16 09:40:25 PDT 2007 qtp-whatami v0.2.3 DISTRO=CentOS OSVER=4.5 ARCH=i686 BUILD_DIST=cnt40 BUILD_DIR=/usr/src/redhat This machine's OS is supported, but this version/arch has not been tested. If your OS is not current, you should consider upgrading it. Do you want to proceed at your own risk? (yes, no) y/[n] : y Ok, here we go ... The following packages have already been selected: autorespond-toaster-2.0.4-1.3.3.src.rpm clamav-toaster-0.90.1-1.3.13.src.rpm control-panel-toaster-0.5-1.3.4.src.rpm courier-authlib-toaster-0.59.2-1.3.6.src.rpm courier-imap-toaster-4.1.2-1.3.7.src.rpm daemontools-toaster-0.76-1.3.3.src.rpm ezmlm-toaster-0.53.324-1.3.3.src.rpm isoqlog-toaster-2.1-1.3.4.src.rpm libdomainkeys-toaster-0.68-1.3.3.src.rpm libsrs2-toaster-1.0.18-1.3.3.src.rpm maildrop-toaster-2.0.3-1.3.5.src.rpm qmailadmin-toaster-1.2.11-1.3.4.src.rpm qmailmrtg-toaster-4.2-1.3.3.src.rpm qmail-toaster-1.03-1.3.15.src.rpm ripmime-toaster-1.4.0.6-1.3.3.src.rpm simscan-toaster-1.3.1-1.3.6.src.rpm spamassassin-toaster-3.1.8-1.3.8.src.rpm squirrelmail-toaster-1.4.9a-1.3.6.src.rpm ucspi-tcp-toaster-0.88-1.3.5.src.rpm vpopmail-toaster-5.4.17-1.3.4.src.rpm vqadmin-toaster-2.3.4-1.3.3.src.rpm Do you want to process this selection? Shall we continue? (yes, no|skip, batch, quit) [y] / n|s / b / q :
