subject:"Re\: \[qmailtoaster\] upgrade question"

RE: [qmailtoaster] upgrade question

2008-04-10 Thread Helmut Fritz

Nope. Just install using yum.

-Original Message-
From: Jack Martin [mailto:[EMAIL PROTECTED] 
Sent: Thursday, April 10, 2008 6:50 AM
To: qmailtoaster-list@qmailtoaster.com
Subject: 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//va

Re: [qmailtoaster] upgrade question

2008-04-10 Thread Jack Martin

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/spamas

RE: [qmailtoaster] upgrade question

2008-04-09 Thread Helmut Fritz

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}"

Re: [qmailtoaster] upgrade question

2008-04-09 Thread Jack Martin

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/v

RE: [qmailtoaster] upgrade question

2008-04-09 Thread Helmut Fritz

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/

Re: [qmailtoaster] upgrade question

2008-04-09 Thread Eric Shubert

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/spa

Re: [qmailtoaster] upgrade question

2008-04-09 Thread Jack Martin

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, 
>> "
>> /usr/bin/perl build/preprocessor -Mvars -DVERSION="3.002004" -DPREFIX="/usr" 
>> -DDEF_RULES_DIR="/usr/share/spamassassin"

Re: [qmailtoaster] upgrade question

2008-04-09 Thread Eric Shubert

il 
> /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@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

2008-04-09 Thread David Rossbach

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: 
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, 
"
/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

Re: [qmailtoaster] upgrade question

2008-04-09 Thread Jack Martin

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

Re: [qmailtoaster] upgrade question

2008-04-09 Thread Eric Shubert

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

2008-04-09 Thread Jack Martin

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

2008-04-08 Thread Eric Shubert

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

2008-04-08 Thread Jack Martin

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

2008-04-08 Thread Eric Shubert

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

2008-04-08 Thread Helmut Fritz

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

2008-04-08 Thread Eric Shubert

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 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [qmailtoaster] upgrade question

Re: [qmailtoaster] upgrade question

RE: [qmailtoaster] upgrade question

Re: [qmailtoaster] upgrade question

RE: [qmailtoaster] upgrade question

Re: [qmailtoaster] upgrade question

Re: [qmailtoaster] upgrade question

Re: [qmailtoaster] upgrade question

Re: [qmailtoaster] upgrade question

Re: [qmailtoaster] upgrade question

Re: [qmailtoaster] upgrade question

Re: [qmailtoaster] upgrade question

Re: [qmailtoaster] upgrade question

Re: [qmailtoaster] upgrade question

Re: [qmailtoaster] upgrade question

RE: [qmailtoaster] upgrade question

Re: [qmailtoaster] upgrade question

17 matches

Site Navigation

Mail list logo

Footer information