Re: [qmailtoaster] Errors in Logs

[Eric Broch]

Try...

mail_max_userip_connections = 20

service imap-login {
   service_count = 0
}

and

auth_verbose = yes
auth_verbose_passwords = yes
auth_debug = yes
auth_debug_passwords = yes

On 12/31/2020 12:00 AM, ChandranManikandan wrote:

Hi Craig,

I usually check the logs for routine work, Meantime i got the messages 
above which posted here.

Does anything go wrong on the server or any patch.

On Thu, Dec 31, 2020 at 2:30 AM Craig McLaughlin 
mailto:craig.p.mclaugh...@gmail.com>> 
wrote:



What have you done to research / investigate these and where are
you stuck?

--Craig

On 12/29/20 11:54 PM, ChandranManikandan wrote:

Hi Friends,

I have noticed the logs below on COS 7.9 with QMT

/var/log/dovecot.log

Dec 30 14:27:46 auth-worker: Error: vmysql: sql error[3]: Table
'vpopmail.imap_domain_net' doesn't exist
Dec 30 14:27:46 auth-worker: Error: Attempting to rebuild
connection to SQL server
Dec 30 14:27:46 auth-worker: Error: vmysql: connection rebuild
failed: Table 'vpopmail.imap_domain_net' doesn't exist

/var/log/qmail/smtp/current

clamdscan: error while loading shared libraries: libtasn1.so.6:
failed to map segment from shared object: Cannot allocate memory

/var/log/qmail/send/current

warning: trouble opening remote/20/2953058156; will try again later
@40005fec1fcb01845034 warning: trouble opening
remote/19/2953058155; will try again later

Appreciate your help.
-- 
*/Regards,

Manikandan.C
/*




--
*/Regards,
Manikandan.C
/*

Re: [qmailtoaster] Errors in Logs

[ChandranManikandan]

Hi Craig,

I usually check the logs for routine work, Meantime i got the messages
above which posted here.
Does anything go wrong on the server or any patch.

On Thu, Dec 31, 2020 at 2:30 AM Craig McLaughlin <
craig.p.mclaugh...@gmail.com> wrote:

>
> What have you done to research / investigate these and where are you stuck?
>
> --Craig
> On 12/29/20 11:54 PM, ChandranManikandan wrote:
>
> Hi Friends,
>
> I have noticed the logs below on COS 7.9 with QMT
>
> /var/log/dovecot.log
>
> Dec 30 14:27:46 auth-worker: Error: vmysql: sql error[3]: Table
> 'vpopmail.imap_domain_net' doesn't exist
> Dec 30 14:27:46 auth-worker: Error: Attempting to rebuild connection to
> SQL server
> Dec 30 14:27:46 auth-worker: Error: vmysql: connection rebuild failed:
> Table 'vpopmail.imap_domain_net' doesn't exist
>
> /var/log/qmail/smtp/current
>
> clamdscan: error while loading shared libraries: libtasn1.so.6: failed to
> map segment from shared object: Cannot allocate memory
>
> /var/log/qmail/send/current
>
> warning: trouble opening remote/20/2953058156; will try again later
> @40005fec1fcb01845034 warning: trouble opening remote/19/2953058155;
> will try again later
>
> Appreciate your help.
> --
>
>
> *Regards, Manikandan.C *
>
>

-- 


*Regards,Manikandan.C*

Re: [qmailtoaster] Errors in Logs

[Craig McLaughlin]

What have you done to research / investigate these and where are you stuck?

--Craig

On 12/29/20 11:54 PM, ChandranManikandan wrote:

Hi Friends,

I have noticed the logs below on COS 7.9 with QMT

/var/log/dovecot.log

Dec 30 14:27:46 auth-worker: Error: vmysql: sql error[3]: Table 
'vpopmail.imap_domain_net' doesn't exist
Dec 30 14:27:46 auth-worker: Error: Attempting to rebuild connection 
to SQL server
Dec 30 14:27:46 auth-worker: Error: vmysql: connection rebuild failed: 
Table 'vpopmail.imap_domain_net' doesn't exist


/var/log/qmail/smtp/current

clamdscan: error while loading shared libraries: libtasn1.so.6: failed 
to map segment from shared object: Cannot allocate memory


/var/log/qmail/send/current

warning: trouble opening remote/20/2953058156; will try again later
@40005fec1fcb01845034 warning: trouble opening 
remote/19/2953058155; will try again later


Appreciate your help.
--
*/Regards,
Manikandan.C
/*

[qmailtoaster] Errors in Logs

[ChandranManikandan]

Hi Friends,

I have noticed the logs below on COS 7.9 with QMT

/var/log/dovecot.log

Dec 30 14:27:46 auth-worker: Error: vmysql: sql error[3]: Table
'vpopmail.imap_domain_net' doesn't exist
Dec 30 14:27:46 auth-worker: Error: Attempting to rebuild connection to SQL
server
Dec 30 14:27:46 auth-worker: Error: vmysql: connection rebuild failed:
Table 'vpopmail.imap_domain_net' doesn't exist

/var/log/qmail/smtp/current

clamdscan: error while loading shared libraries: libtasn1.so.6: failed to
map segment from shared object: Cannot allocate memory

/var/log/qmail/send/current

warning: trouble opening remote/20/2953058156; will try again later
@40005fec1fcb01845034 warning: trouble opening remote/19/2953058155;
will try again later

Appreciate your help.
-- 


*Regards,Manikandan.C*

[qmailtoaster] errors

[System Admin]

HI all,

A client is loggin in to squirrelmail,
Clicking on sub folders, and get this error, But not all folders give 
the error?


*ERROR:**ERROR: Could not complete request.*
Query: SELECT "INBOX.Dave"
Reason Given: Mailbox does not exist, or must be subscribed to.

All folders worked previously.
The client alsi say getting error with these folders in Outlook ( set up 
with IMAP )

Please advise

Thanks

Re: [qmailtoaster] errors

[Martin Waschbüsch]

Hi,

Can you verify if the content of /var/qmail/control//me is indeed a FQDN that 
resolves into your IP and also matches the greeting in 
/var/qmail/control/smtpgreeting?

Thanks,

Martin

--
Martin Waschbüsch
IT-Dienstleistungen
Lautensackstr. 16
80687 München

Telefon: +49 89 57005708
Fax: +49 89 57868023
Mobil: +49 170 2189794
mar...@waschbuesch.de
http://martin.waschbuesch.de

Am 08.12.2010 um 23:10 schrieb sysad...@tricubemedia.com:

> Hi List
> 
> Getting this error from one domain.
> 
> *.*.*.* does not like recipient.
> Remote host said: 554 5.7.1 This message has been blocked because the
> HELO/EHLO domain is invalid.
> Giving up on *.*.*.*
> 
> does this mean the recipient sis blocking our emails?
> 
> Thanks
> 
> 
> 
> -
> 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 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] errors

[sysadmin]

Hi List

Getting this error from one domain.

*.*.*.* does not like recipient.
Remote host said: 554 5.7.1 This message has been blocked because the
HELO/EHLO domain is invalid.
Giving up on *.*.*.*

does this mean the recipient sis blocking our emails?

Thanks



-
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] Errors showing up: Trouble Opening Remote

[[EMAIL PROTECTED]]

Found that answer just after I posted, of course :).

Thanks much.

Mike


On Sat, 20 Oct 2007 19:39:20 -0400, Jake Vickers wrote:
> [EMAIL PROTECTED] wrote:
>
>> Anyone know what these errors are? I see many thoughts in email lists but
>> before I mess with things, thought I'd ask here.
>>
>> Thanks.
>>
>>
>> 2007-10-20 14:17:25.898511500 warning: trouble opening remote/17/275143;
>> will
>> try again later
>> 2007-10-20 14:19:29.84500 warning: trouble opening remote/17/275143;
>> will
>> try again later
>> 2007-10-20 14:21:33.857021500 warning: trouble opening remote/17/275143;
>> will
>> try again later
>> 2007-10-20 14:23:37.836296500 warning: trouble opening remote/17/275143;
>> will
>> try again later
>> 2007-10-20 14:25:41.815544500 warning: trouble opening remote/17/275143;
>> will
>> try again later
>>
>
> I think that has to do with your queue getting messed up a little. Try
> running queue-fix on it and see if that resolves the issue.




-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] Errors showing up: Trouble Opening Remote

[Jake Vickers]

[EMAIL PROTECTED] wrote:
Anyone know what these errors are? I see many thoughts in email lists but 
before I mess with things, thought I'd ask here.


Thanks.


2007-10-20 14:17:25.898511500 warning: trouble opening remote/17/275143; will 
try again later
2007-10-20 14:19:29.84500 warning: trouble opening remote/17/275143; will 
try again later
2007-10-20 14:21:33.857021500 warning: trouble opening remote/17/275143; will 
try again later
2007-10-20 14:23:37.836296500 warning: trouble opening remote/17/275143; will 
try again later
2007-10-20 14:25:41.815544500 warning: trouble opening remote/17/275143; will 
try again later
  


I think that has to do with your queue getting messed up a little. Try 
running queue-fix on it and see if that resolves the issue.


smime.p7s
Description: S/MIME Cryptographic Signature

[qmailtoaster] Errors showing up: Trouble Opening Remote

[[EMAIL PROTECTED]]

Anyone know what these errors are? I see many thoughts in email lists but
before I mess with things, thought I'd ask here.

Thanks.


2007-10-20 14:17:25.898511500 warning: trouble opening remote/17/275143; will
try again later
2007-10-20 14:19:29.84500 warning: trouble opening remote/17/275143; will
try again later
2007-10-20 14:21:33.857021500 warning: trouble opening remote/17/275143; will
try again later
2007-10-20 14:23:37.836296500 warning: trouble opening remote/17/275143; will
try again later
2007-10-20 14:25:41.815544500 warning: trouble opening remote/17/275143; will
try again later
2007-10-20 14:27:45.794804500 warning: trouble opening remote/17/275143; will
try again later
2007-10-20 14:29:49.774070500 warning: trouble opening remote/17/275143; will
try again later
2007-10-20 14:31:53.753320500 warning: trouble opening remote/17/275143; will
try again later
2007-10-20 14:33:57.732612500 warning: trouble opening remote/17/275143; will
try again later
2007-10-20 14:35:29.261905500 warning: unable to utime remote/17/275143;
message will be retried too soon



-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] errors during upgrading qt

[Francisco Paco Peralta]

Erik,I would try this on my system but it is a live system and the last time I had this libtool issue I was off the air for a couple of days until the issue was resolved with the help of "Shubes".  Sometimes I just wish I had a sandbox to play in!Erik Espinoza <[EMAIL PROTECTED]> wrote: Could someone on FC4 give this a try:http://devel.qmailtoaster.com/download/courier-authlib-toaster-0.58-1.3.2.src.rpmIf you downloaded and attempted to test this yesterday, please re-download.I should have some virtual machines available all the time soon,thanks to Kyle and Wifi7.com.Thanks,ErikOn 10/25/06, Eric Shubes <[EMAIL PROTECTED]> wrote:> That's interesting.>> So, on FC4 (at least), libltdl.so is provided by the courier-authlib-toaster> package,
 while on CentOS4 (at least) it is provided by the standard> libtool-libs package.>> I'm guessing that there must be some patch to libltdl.so that was necessary> to get courier-authlib-toaster working on FC4.>> So the answer to original question (is libtool-ltdl or libtool-libs> necessary?), the answer (apparently) is that it depends on your> distro/release. If you have dependent packages and can't remove libtool-ltdl> (or libtool-libs) cleanly, I'm guessing that you can remove it with --nodeps> before installing courier-authlib-toaster, which will replace the dependent> file(s). Now whether or not the dependent package will actually work or not> with the courier-authlib-toaster versions might be subject to testing.>> This illustrates why it is prudent to run the toaster on CentOS instead of> FedoraCore.>> Francisco Paco Peralta wrote:> > # ls -l
 `rpm -ql courier-authlib-toaster | grep libltdl`> > -rwxr-xr-x  1 root root 27004 Sep 19 14:54 /usr/lib/libltdl.a> > -rwxr-xr-x  1 root root   789 Sep 19 14:53 /usr/lib/libltdl.la> > lrwxrwxrwx  1 root root16 Sep 19 19:08 /usr/lib/libltdl.so ->> > libltdl.so.3.1.0> > lrwxrwxrwx  1 root root16 Sep 19 19:08 /usr/lib/libltdl.so.3 ->> > libltdl.so.3.1.0> > -rwxr-xr-x  1 root root 70144 Sep 19 14:53 /usr/lib/libltdl.so.3.1.0> >> >> > Francisco "Paco" Peralta> >> >> > - Original Message > > From: "Eric "Shubes"" <[EMAIL PROTECTED]>> > To: qmailtoaster-list@qmailtoaster.com> > Sent: Tuesday, October 24, 2006 5:44:39 PM> > Subject: Re: [qmailtoaster] errors during upgrading qt> >> > Bingo.> >> > So, when upgrading the toaster, one might need to>
 > # rpm -e --nodeps libtools-ltdl> > in order to install courier-authlib-toaster.> >> > Paco,> > what does> > # ls -l `rpm -ql courier-authlib-toaster | grep libltdl`> > show?> >> > (BTW, thanks for checking this stuff!)> >> > Francisco Paco Peralta wrote:> >> Here are the results:> >>> >> # rpm -qf /usr/lib/libltdl.so.3> >> courier-authlib-toaster-0.58-1.3.1> >>> >> # rpm -qf /usr/lib/ltdl.so.3.1.0> >> error: file /usr/lib/ltdl.so.3.1.0: No such file or directory> >>> >> Francisco "Paco" Peralta> >>> >>> >> - Original Message > >> From: "Eric "Shubes"" <[EMAIL PROTECTED]>> >> To: qmailtoaster-list@qmailtoaster.com> >> Sent: Tuesday, October 24, 2006 4:51:51 PM>
 >> Subject: Re: [qmailtoaster] errors during upgrading qt> >>> >> That's interesting. I seem to remember now that the file(s) was> > included in> >> the courier-authlib package for that particular (FC4) distro.> >>> >> The files (one file, one link) in question are:> >> lrwxrwxrwx  1 root root16 Sep 11 19:10 /usr/lib/libltdl.so.3 ->> >> libltdl.so.3.1.0> >> -rwxr-xr-x  1 root root 24588 Aug 13 00:13 /usr/lib/libltdl.so.3.1.0> >>> >> Paco, what does> >> # rpm -qf /usr/lib/libltdl.so.3> >> tell you? Does that file exist on your system?> >> Please do the same for /usr/lib/ltdl.so.3.1.0 just for yuks.> >>> >> Francisco Paco Peralta wrote:> >>> Hey Guys,> >>>> >>> All right.  I ran the following command as
 requested:> >>>> >>> # rpm -qa | grep libtool> >>> libtool-1.5.16.multilib2-3> >>>> >>> # rpm -ql libtool-libs> >>> package libtool-libs is not installed> >>>> >>> Eric,> >>>> >>> I believe the way we got around this problem might have been by finding> >>> a copy of the missing file and putting it in the directory.  Is there a> >>> way to tell which rpm installed the package?> >>>> >>> Francisco "Paco" Peralta> >>>> >>>> >>> >> --> >> -Eric 'shubes'> >>>>> --> -Eric 'shubes'>> ->  QmailToaster hosted by: VR Hosted >
 -> To unsubscribe, e-mail: [EMAIL PROTECTED]> For additional commands, e-mail: [EMAIL PROTECTED]>>- QmailToaster hosted by: VR Hosted -To unsubscribe, e-mail: [EMAIL PROTECTED]For additional commands, e-mail: [EMAIL PROTECTED]Francisco "Paco" Peralta

Re: [qmailtoaster] errors during upgrading qt

[ldap]

These errors are sent to my postmaster account, they are more than 40 in
12 hours.

crispin
> This is a qmailmrtg error. How many have you gotten?
>
> On 10/26/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>> I have just a message before I saw this thread. The server was down for
>> the past 24 hours.
>>
>> I am running qt on FC5.
>> I removed libtool-ltdl to be able to install courier-authlib. I am
>> however
>> getting the following errors and would like to know if there is anything
>> I
>> need to do to rescue this situation.
>>
>> WARNING: Problem with External get '/usr/bin/qmailmrtg S
>> /var/log/qmail/spamd':
>>
>> Expected a Number for 'in' but got 'failed to open dir
>> /var/log/qmail/spamd'
>>
>> WARNING: Problem with External get '/usr/bin/qmailmrtg S
>> /var/log/qmail/spamd':
>>
>> Expected a Number for 'out' but nothing'
>>
>> ERROR: Target[spamd][_IN_] ' $target->[3]{$mode} ' did not eval into
>> defined data
>> ERROR: Target[spamd][_OUT_] ' $target->[3]{$mode} ' did not eval into
>> defined dat
>>
>>
>>
>>
>> > Could someone on FC4 give this a try:
>> >
>> > http://devel.qmailtoaster.com/download/courier-authlib-toaster-0.58-1.3.2.src.rpm
>> >
>> > If you downloaded and attempted to test this yesterday, please
>> > re-download.
>> >
>> > I should have some virtual machines available all the time soon,
>> > thanks to Kyle and Wifi7.com.
>> >
>> > Thanks,
>> > Erik
>> >
>> > On 10/25/06, Eric Shubes <[EMAIL PROTECTED]> wrote:
>> >> That's interesting.
>> >>
>> >> So, on FC4 (at least), libltdl.so is provided by the
>> >> courier-authlib-toaster
>> >> package, while on CentOS4 (at least) it is provided by the standard
>> >> libtool-libs package.
>> >>
>> >> I'm guessing that there must be some patch to libltdl.so that was
>> >> necessary
>> >> to get courier-authlib-toaster working on FC4.
>> >>
>> >> So the answer to original question (is libtool-ltdl or libtool-libs
>> >> necessary?), the answer (apparently) is that it depends on your
>> >> distro/release. If you have dependent packages and can't remove
>> >> libtool-ltdl
>> >> (or libtool-libs) cleanly, I'm guessing that you can remove it with
>> >> --nodeps
>> >> before installing courier-authlib-toaster, which will replace the
>> >> dependent
>> >> file(s). Now whether or not the dependent package will actually work
>> or
>> >> not
>> >> with the courier-authlib-toaster versions might be subject to
>> testing.
>> >>
>> >> This illustrates why it is prudent to run the toaster on CentOS
>> instead
>> >> of
>> >> FedoraCore.
>> >>
>> >> Francisco Paco Peralta wrote:
>> >> > # ls -l `rpm -ql courier-authlib-toaster | grep libltdl`
>> >> > -rwxr-xr-x  1 root root 27004 Sep 19 14:54 /usr/lib/libltdl.a
>> >> > -rwxr-xr-x  1 root root   789 Sep 19 14:53 /usr/lib/libltdl.la
>> >> > lrwxrwxrwx  1 root root16 Sep 19 19:08 /usr/lib/libltdl.so ->
>> >> > libltdl.so.3.1.0
>> >> > lrwxrwxrwx  1 root root16 Sep 19 19:08 /usr/lib/libltdl.so.3 ->
>> >> > libltdl.so.3.1.0
>> >> > -rwxr-xr-x  1 root root 70144 Sep 19 14:53
>> /usr/lib/libltdl.so.3.1.0
>> >> >
>> >> >
>> >> > Francisco "Paco" Peralta
>> >> >
>> >> >
>> >> > - Original Message 
>> >> > From: "Eric "Shubes"" <[EMAIL PROTECTED]>
>> >> > To: qmailtoaster-list@qmailtoaster.com
>> >> > Sent: Tuesday, October 24, 2006 5:44:39 PM
>> >> > Subject: Re: [qmailtoaster] errors during upgrading qt
>> >> >
>> >> > Bingo.
>> >> >
>> >> > So, when upgrading the toaster, one might need to
>> >> > # rpm -e --nodeps libtools-ltdl
>> >> > in order to install courier-authlib-toaster.
>> >> >
>> >> > Paco,
>> >> > what does
>> >> > # ls -l `rpm -ql courier-authlib-toaster | grep libltdl`
>> >> > show?
>> >> >
>> >> > (BTW, thanks fo

Re: [qmailtoaster] errors during upgrading qt

[Erik Espinoza]

This is a qmailmrtg error. How many have you gotten?

On 10/26/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:

I have just a message before I saw this thread. The server was down for
the past 24 hours.

I am running qt on FC5.
I removed libtool-ltdl to be able to install courier-authlib. I am however
getting the following errors and would like to know if there is anything I
need to do to rescue this situation.

WARNING: Problem with External get '/usr/bin/qmailmrtg S
/var/log/qmail/spamd':

Expected a Number for 'in' but got 'failed to open dir /var/log/qmail/spamd'

WARNING: Problem with External get '/usr/bin/qmailmrtg S
/var/log/qmail/spamd':

Expected a Number for 'out' but nothing'

ERROR: Target[spamd][_IN_] ' $target->[3]{$mode} ' did not eval into
defined data
ERROR: Target[spamd][_OUT_] ' $target->[3]{$mode} ' did not eval into
defined dat




> Could someone on FC4 give this a try:
>
> 
http://devel.qmailtoaster.com/download/courier-authlib-toaster-0.58-1.3.2.src.rpm
>
> If you downloaded and attempted to test this yesterday, please
> re-download.
>
> I should have some virtual machines available all the time soon,
> thanks to Kyle and Wifi7.com.
>
> Thanks,
> Erik
>
> On 10/25/06, Eric Shubes <[EMAIL PROTECTED]> wrote:
>> That's interesting.
>>
>> So, on FC4 (at least), libltdl.so is provided by the
>> courier-authlib-toaster
>> package, while on CentOS4 (at least) it is provided by the standard
>> libtool-libs package.
>>
>> I'm guessing that there must be some patch to libltdl.so that was
>> necessary
>> to get courier-authlib-toaster working on FC4.
>>
>> So the answer to original question (is libtool-ltdl or libtool-libs
>> necessary?), the answer (apparently) is that it depends on your
>> distro/release. If you have dependent packages and can't remove
>> libtool-ltdl
>> (or libtool-libs) cleanly, I'm guessing that you can remove it with
>> --nodeps
>> before installing courier-authlib-toaster, which will replace the
>> dependent
>> file(s). Now whether or not the dependent package will actually work or
>> not
>> with the courier-authlib-toaster versions might be subject to testing.
>>
>> This illustrates why it is prudent to run the toaster on CentOS instead
>> of
>> FedoraCore.
>>
>> Francisco Paco Peralta wrote:
>> > # ls -l `rpm -ql courier-authlib-toaster | grep libltdl`
>> > -rwxr-xr-x  1 root root 27004 Sep 19 14:54 /usr/lib/libltdl.a
>> > -rwxr-xr-x  1 root root   789 Sep 19 14:53 /usr/lib/libltdl.la
>> > lrwxrwxrwx  1 root root16 Sep 19 19:08 /usr/lib/libltdl.so ->
>> > libltdl.so.3.1.0
>> > lrwxrwxrwx  1 root root    16 Sep 19 19:08 /usr/lib/libltdl.so.3 ->
>> > libltdl.so.3.1.0
>> > -rwxr-xr-x  1 root root 70144 Sep 19 14:53 /usr/lib/libltdl.so.3.1.0
>> >
>> >
>> > Francisco "Paco" Peralta
>> >
>> >
>> > - Original Message 
>> > From: "Eric "Shubes"" <[EMAIL PROTECTED]>
>> > To: qmailtoaster-list@qmailtoaster.com
>> > Sent: Tuesday, October 24, 2006 5:44:39 PM
>> > Subject: Re: [qmailtoaster] errors during upgrading qt
>> >
>> > Bingo.
>> >
>> > So, when upgrading the toaster, one might need to
>> > # rpm -e --nodeps libtools-ltdl
>> > in order to install courier-authlib-toaster.
>> >
>> > Paco,
>> > what does
>> > # ls -l `rpm -ql courier-authlib-toaster | grep libltdl`
>> > show?
>> >
>> > (BTW, thanks for checking this stuff!)
>> >
>> > Francisco Paco Peralta wrote:
>> >> Here are the results:
>> >>
>> >> # rpm -qf /usr/lib/libltdl.so.3
>> >> courier-authlib-toaster-0.58-1.3.1
>> >>
>> >> # rpm -qf /usr/lib/ltdl.so.3.1.0
>> >> error: file /usr/lib/ltdl.so.3.1.0: No such file or directory
>> >>
>> >> Francisco "Paco" Peralta
>> >>
>> >>
>> >> - Original Message 
>> >> From: "Eric "Shubes"" <[EMAIL PROTECTED]>
>> >> To: qmailtoaster-list@qmailtoaster.com
>> >> Sent: Tuesday, October 24, 2006 4:51:51 PM
>> >> Subject: Re: [qmailtoaster] errors during upgrading qt
>> >>
>> >> That's interesting. I seem to remember now that the file(s) was
>> > included in
>> >> the courier-authlib package for that particular (FC4) distro.
&

Re: [qmailtoaster] errors during upgrading qt

[ldap]

I have just a message before I saw this thread. The server was down for
the past 24 hours.

I am running qt on FC5.
I removed libtool-ltdl to be able to install courier-authlib. I am however
getting the following errors and would like to know if there is anything I
need to do to rescue this situation.

WARNING: Problem with External get '/usr/bin/qmailmrtg S
/var/log/qmail/spamd':

Expected a Number for 'in' but got 'failed to open dir /var/log/qmail/spamd'

WARNING: Problem with External get '/usr/bin/qmailmrtg S
/var/log/qmail/spamd':

Expected a Number for 'out' but nothing'

ERROR: Target[spamd][_IN_] ' $target->[3]{$mode} ' did not eval into
defined data
ERROR: Target[spamd][_OUT_] ' $target->[3]{$mode} ' did not eval into
defined dat




> Could someone on FC4 give this a try:
>
> http://devel.qmailtoaster.com/download/courier-authlib-toaster-0.58-1.3.2.src.rpm
>
> If you downloaded and attempted to test this yesterday, please
> re-download.
>
> I should have some virtual machines available all the time soon,
> thanks to Kyle and Wifi7.com.
>
> Thanks,
> Erik
>
> On 10/25/06, Eric Shubes <[EMAIL PROTECTED]> wrote:
>> That's interesting.
>>
>> So, on FC4 (at least), libltdl.so is provided by the
>> courier-authlib-toaster
>> package, while on CentOS4 (at least) it is provided by the standard
>> libtool-libs package.
>>
>> I'm guessing that there must be some patch to libltdl.so that was
>> necessary
>> to get courier-authlib-toaster working on FC4.
>>
>> So the answer to original question (is libtool-ltdl or libtool-libs
>> necessary?), the answer (apparently) is that it depends on your
>> distro/release. If you have dependent packages and can't remove
>> libtool-ltdl
>> (or libtool-libs) cleanly, I'm guessing that you can remove it with
>> --nodeps
>> before installing courier-authlib-toaster, which will replace the
>> dependent
>> file(s). Now whether or not the dependent package will actually work or
>> not
>> with the courier-authlib-toaster versions might be subject to testing.
>>
>> This illustrates why it is prudent to run the toaster on CentOS instead
>> of
>> FedoraCore.
>>
>> Francisco Paco Peralta wrote:
>> > # ls -l `rpm -ql courier-authlib-toaster | grep libltdl`
>> > -rwxr-xr-x  1 root root 27004 Sep 19 14:54 /usr/lib/libltdl.a
>> > -rwxr-xr-x  1 root root   789 Sep 19 14:53 /usr/lib/libltdl.la
>> > lrwxrwxrwx  1 root root16 Sep 19 19:08 /usr/lib/libltdl.so ->
>> > libltdl.so.3.1.0
>> > lrwxrwxrwx  1 root root16 Sep 19 19:08 /usr/lib/libltdl.so.3 ->
>> > libltdl.so.3.1.0
>> > -rwxr-xr-x  1 root root 70144 Sep 19 14:53 /usr/lib/libltdl.so.3.1.0
>> >
>> >
>> > Francisco "Paco" Peralta
>> >
>> >
>> > - Original Message 
>> > From: "Eric "Shubes"" <[EMAIL PROTECTED]>
>> > To: qmailtoaster-list@qmailtoaster.com
>> > Sent: Tuesday, October 24, 2006 5:44:39 PM
>> > Subject: Re: [qmailtoaster] errors during upgrading qt
>> >
>> > Bingo.
>> >
>> > So, when upgrading the toaster, one might need to
>> > # rpm -e --nodeps libtools-ltdl
>> > in order to install courier-authlib-toaster.
>> >
>> > Paco,
>> > what does
>> > # ls -l `rpm -ql courier-authlib-toaster | grep libltdl`
>> > show?
>> >
>> > (BTW, thanks for checking this stuff!)
>> >
>> > Francisco Paco Peralta wrote:
>> >> Here are the results:
>> >>
>> >> # rpm -qf /usr/lib/libltdl.so.3
>> >> courier-authlib-toaster-0.58-1.3.1
>> >>
>> >> # rpm -qf /usr/lib/ltdl.so.3.1.0
>> >> error: file /usr/lib/ltdl.so.3.1.0: No such file or directory
>> >>
>> >> Francisco "Paco" Peralta
>> >>
>> >>
>> >> - Original Message 
>> >> From: "Eric "Shubes"" <[EMAIL PROTECTED]>
>> >> To: qmailtoaster-list@qmailtoaster.com
>> >> Sent: Tuesday, October 24, 2006 4:51:51 PM
>> >> Subject: Re: [qmailtoaster] errors during upgrading qt
>> >>
>> >> That's interesting. I seem to remember now that the file(s) was
>> > included in
>> >> the courier-authlib package for that particular (FC4) distro.
>> >>
>> >> The files (one file, one link) in question are:
>> >> lrwxrwxrwx  1 root root16 

Re: [qmailtoaster] errors during upgrading qt

[Erik Espinoza]

Could someone on FC4 give this a try:

http://devel.qmailtoaster.com/download/courier-authlib-toaster-0.58-1.3.2.src.rpm

If you downloaded and attempted to test this yesterday, please re-download.

I should have some virtual machines available all the time soon,
thanks to Kyle and Wifi7.com.

Thanks,
Erik

On 10/25/06, Eric Shubes <[EMAIL PROTECTED]> wrote:

That's interesting.

So, on FC4 (at least), libltdl.so is provided by the courier-authlib-toaster
package, while on CentOS4 (at least) it is provided by the standard
libtool-libs package.

I'm guessing that there must be some patch to libltdl.so that was necessary
to get courier-authlib-toaster working on FC4.

So the answer to original question (is libtool-ltdl or libtool-libs
necessary?), the answer (apparently) is that it depends on your
distro/release. If you have dependent packages and can't remove libtool-ltdl
(or libtool-libs) cleanly, I'm guessing that you can remove it with --nodeps
before installing courier-authlib-toaster, which will replace the dependent
file(s). Now whether or not the dependent package will actually work or not
with the courier-authlib-toaster versions might be subject to testing.

This illustrates why it is prudent to run the toaster on CentOS instead of
FedoraCore.

Francisco Paco Peralta wrote:
> # ls -l `rpm -ql courier-authlib-toaster | grep libltdl`
> -rwxr-xr-x  1 root root 27004 Sep 19 14:54 /usr/lib/libltdl.a
> -rwxr-xr-x  1 root root   789 Sep 19 14:53 /usr/lib/libltdl.la
> lrwxrwxrwx  1 root root16 Sep 19 19:08 /usr/lib/libltdl.so ->
> libltdl.so.3.1.0
> lrwxrwxrwx  1 root root16 Sep 19 19:08 /usr/lib/libltdl.so.3 ->
> libltdl.so.3.1.0
> -rwxr-xr-x  1 root root 70144 Sep 19 14:53 /usr/lib/libltdl.so.3.1.0
>
>
> Francisco "Paco" Peralta
>
>
> - Original Message 
> From: "Eric "Shubes"" <[EMAIL PROTECTED]>
> To: qmailtoaster-list@qmailtoaster.com
> Sent: Tuesday, October 24, 2006 5:44:39 PM
> Subject: Re: [qmailtoaster] errors during upgrading qt
>
> Bingo.
>
> So, when upgrading the toaster, one might need to
> # rpm -e --nodeps libtools-ltdl
> in order to install courier-authlib-toaster.
>
> Paco,
> what does
> # ls -l `rpm -ql courier-authlib-toaster | grep libltdl`
> show?
>
> (BTW, thanks for checking this stuff!)
>
> Francisco Paco Peralta wrote:
>> Here are the results:
>>
>> # rpm -qf /usr/lib/libltdl.so.3
>> courier-authlib-toaster-0.58-1.3.1
>>
>> # rpm -qf /usr/lib/ltdl.so.3.1.0
>> error: file /usr/lib/ltdl.so.3.1.0: No such file or directory
>>
>> Francisco "Paco" Peralta
>>
>>
>> - Original Message 
>> From: "Eric "Shubes"" <[EMAIL PROTECTED]>
>> To: qmailtoaster-list@qmailtoaster.com
>> Sent: Tuesday, October 24, 2006 4:51:51 PM
>> Subject: Re: [qmailtoaster] errors during upgrading qt
>>
>> That's interesting. I seem to remember now that the file(s) was
> included in
>> the courier-authlib package for that particular (FC4) distro.
>>
>> The files (one file, one link) in question are:
>> lrwxrwxrwx  1 root root16 Sep 11 19:10 /usr/lib/libltdl.so.3 ->
>> libltdl.so.3.1.0
>> -rwxr-xr-x  1 root root 24588 Aug 13 00:13 /usr/lib/libltdl.so.3.1.0
>>
>> Paco, what does
>> # rpm -qf /usr/lib/libltdl.so.3
>> tell you? Does that file exist on your system?
>> Please do the same for /usr/lib/ltdl.so.3.1.0 just for yuks.
>>
>> Francisco Paco Peralta wrote:
>>> Hey Guys,
>>>
>>> All right.  I ran the following command as requested:
>>>
>>> # rpm -qa | grep libtool
>>> libtool-1.5.16.multilib2-3
>>>
>>> # rpm -ql libtool-libs
>>> package libtool-libs is not installed
>>>
>>> Eric,
>>>
>>> I believe the way we got around this problem might have been by finding
>>> a copy of the missing file and putting it in the directory.  Is there a
>>> way to tell which rpm installed the package?
>>>
>>> Francisco "Paco" Peralta
>>>
>>>
>>
>> --
>> -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] errors during upgrading qt

[Eric \"Shubes\"]

That's interesting.

So, on FC4 (at least), libltdl.so is provided by the courier-authlib-toaster
package, while on CentOS4 (at least) it is provided by the standard
libtool-libs package.

I'm guessing that there must be some patch to libltdl.so that was necessary
to get courier-authlib-toaster working on FC4.

So the answer to original question (is libtool-ltdl or libtool-libs
necessary?), the answer (apparently) is that it depends on your
distro/release. If you have dependent packages and can't remove libtool-ltdl
(or libtool-libs) cleanly, I'm guessing that you can remove it with --nodeps
before installing courier-authlib-toaster, which will replace the dependent
file(s). Now whether or not the dependent package will actually work or not
with the courier-authlib-toaster versions might be subject to testing.

This illustrates why it is prudent to run the toaster on CentOS instead of
FedoraCore.

Francisco Paco Peralta wrote:
> # ls -l `rpm -ql courier-authlib-toaster | grep libltdl`
> -rwxr-xr-x  1 root root 27004 Sep 19 14:54 /usr/lib/libltdl.a
> -rwxr-xr-x  1 root root   789 Sep 19 14:53 /usr/lib/libltdl.la
> lrwxrwxrwx  1 root root16 Sep 19 19:08 /usr/lib/libltdl.so ->
> libltdl.so.3.1.0
> lrwxrwxrwx  1 root root16 Sep 19 19:08 /usr/lib/libltdl.so.3 ->
> libltdl.so.3.1.0
> -rwxr-xr-x  1 root root 70144 Sep 19 14:53 /usr/lib/libltdl.so.3.1.0
> 
>  
> Francisco "Paco" Peralta
> 
> 
> - Original Message 
> From: "Eric "Shubes"" <[EMAIL PROTECTED]>
> To: qmailtoaster-list@qmailtoaster.com
> Sent: Tuesday, October 24, 2006 5:44:39 PM
> Subject: Re: [qmailtoaster] errors during upgrading qt
> 
> Bingo.
> 
> So, when upgrading the toaster, one might need to
> # rpm -e --nodeps libtools-ltdl
> in order to install courier-authlib-toaster.
> 
> Paco,
> what does
> # ls -l `rpm -ql courier-authlib-toaster | grep libltdl`
> show?
> 
> (BTW, thanks for checking this stuff!)
> 
> Francisco Paco Peralta wrote:
>> Here are the results:
>>
>> # rpm -qf /usr/lib/libltdl.so.3
>> courier-authlib-toaster-0.58-1.3.1
>>
>> # rpm -qf /usr/lib/ltdl.so.3.1.0
>> error: file /usr/lib/ltdl.so.3.1.0: No such file or directory
>>  
>> Francisco "Paco" Peralta
>>
>>
>> - Original Message 
>> From: "Eric "Shubes"" <[EMAIL PROTECTED]>
>> To: qmailtoaster-list@qmailtoaster.com
>> Sent: Tuesday, October 24, 2006 4:51:51 PM
>> Subject: Re: [qmailtoaster] errors during upgrading qt
>>
>> That's interesting. I seem to remember now that the file(s) was
> included in
>> the courier-authlib package for that particular (FC4) distro.
>>
>> The files (one file, one link) in question are:
>> lrwxrwxrwx  1 root root16 Sep 11 19:10 /usr/lib/libltdl.so.3 ->
>> libltdl.so.3.1.0
>> -rwxr-xr-x  1 root root 24588 Aug 13 00:13 /usr/lib/libltdl.so.3.1.0
>>
>> Paco, what does
>> # rpm -qf /usr/lib/libltdl.so.3
>> tell you? Does that file exist on your system?
>> Please do the same for /usr/lib/ltdl.so.3.1.0 just for yuks.
>>
>> Francisco Paco Peralta wrote:
>>> Hey Guys,
>>>
>>> All right.  I ran the following command as requested:
>>>
>>> # rpm -qa | grep libtool
>>> libtool-1.5.16.multilib2-3
>>>
>>> # rpm -ql libtool-libs
>>> package libtool-libs is not installed
>>>
>>> Eric,
>>>
>>> I believe the way we got around this problem might have been by finding
>>> a copy of the missing file and putting it in the directory.  Is there a
>>> way to tell which rpm installed the package?
>>>  
>>> Francisco "Paco" Peralta
>>>
>>>
>>
>> --
>> -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] errors during upgrading qt

[Francisco Paco Peralta]

# ls -l `rpm -ql courier-authlib-toaster | grep libltdl`-rwxr-xr-x  1 root root 27004 Sep 19 14:54 /usr/lib/libltdl.a-rwxr-xr-x  1 root root   789 Sep 19 14:53 /usr/lib/libltdl.lalrwxrwxrwx  1 root root    16 Sep 19 19:08 /usr/lib/libltdl.so -> libltdl.so.3.1.0lrwxrwxrwx  1 root root    16 Sep 19 19:08 /usr/lib/libltdl.so.3 -> libltdl.so.3.1.0-rwxr-xr-x  1 root root 70144 Sep 19 14:53 /usr/lib/libltdl.so.3.1.0 Francisco "Paco" Peralta- Original Message From: "Eric "Shubes"" <[EMAIL PROTECTED]>To:
 qmailtoaster-list@qmailtoaster.comSent: Tuesday, October 24, 2006 5:44:39 PMSubject: Re: [qmailtoaster] errors during upgrading qtBingo.So, when upgrading the toaster, one might need to# rpm -e --nodeps libtools-ltdlin order to install courier-authlib-toaster.Paco,what does# ls -l `rpm -ql courier-authlib-toaster | grep libltdl`show?(BTW, thanks for checking this stuff!)Francisco Paco Peralta wrote:> Here are the results:> > # rpm -qf /usr/lib/libltdl.so.3> courier-authlib-toaster-0.58-1.3.1> > # rpm -qf /usr/lib/ltdl.so.3.1.0> error: file /usr/lib/ltdl.so.3.1.0: No such file or directory>  > Francisco "Paco" Peralta> > > - Original Message > From: "Eric "Shubes"" <[EMAIL PROTECTED]>> To: qmailtoaster-list@qmailtoaster.com> Sent: Tuesday, October 24, 2006 4:51:51 PM>
 Subject: Re: [qmailtoaster] errors during upgrading qt> > That's interesting. I seem to remember now that the file(s) was included in> the courier-authlib package for that particular (FC4) distro.> > The files (one file, one link) in question are:> lrwxrwxrwx  1 root root16 Sep 11 19:10 /usr/lib/libltdl.so.3 ->> libltdl.so.3.1.0> -rwxr-xr-x  1 root root 24588 Aug 13 00:13 /usr/lib/libltdl.so.3.1.0> > Paco, what does> # rpm -qf /usr/lib/libltdl.so.3> tell you? Does that file exist on your system?> Please do the same for /usr/lib/ltdl.so.3.1.0 just for yuks.> > Francisco Paco Peralta wrote:>> Hey Guys,>>>> All right.  I ran the following command as requested:>>>> # rpm -qa | grep libtool>> libtool-1.5.16.multilib2-3>>>> # rpm -ql
 libtool-libs>> package libtool-libs is not installed>>>> Eric,>>>> I believe the way we got around this problem might have been by finding>> a copy of the missing file and putting it in the directory.  Is there a>> way to tell which rpm installed the package?>>  >> Francisco "Paco" Peralta>>>>> > -- > -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] errors during upgrading qt

[Eric \"Shubes\"]

Bingo.

So, when upgrading the toaster, one might need to
# rpm -e --nodeps libtools-ltdl
in order to install courier-authlib-toaster.

Paco,
what does
# ls -l `rpm -ql courier-authlib-toaster | grep libltdl`
show?

(BTW, thanks for checking this stuff!)

Francisco Paco Peralta wrote:
> Here are the results:
> 
> # rpm -qf /usr/lib/libltdl.so.3
> courier-authlib-toaster-0.58-1.3.1
> 
> # rpm -qf /usr/lib/ltdl.so.3.1.0
> error: file /usr/lib/ltdl.so.3.1.0: No such file or directory
>  
> Francisco "Paco" Peralta
> 
> 
> - Original Message 
> From: "Eric "Shubes"" <[EMAIL PROTECTED]>
> To: qmailtoaster-list@qmailtoaster.com
> Sent: Tuesday, October 24, 2006 4:51:51 PM
> Subject: Re: [qmailtoaster] errors during upgrading qt
> 
> That's interesting. I seem to remember now that the file(s) was included in
> the courier-authlib package for that particular (FC4) distro.
> 
> The files (one file, one link) in question are:
> lrwxrwxrwx  1 root root16 Sep 11 19:10 /usr/lib/libltdl.so.3 ->
> libltdl.so.3.1.0
> -rwxr-xr-x  1 root root 24588 Aug 13 00:13 /usr/lib/libltdl.so.3.1.0
> 
> Paco, what does
> # rpm -qf /usr/lib/libltdl.so.3
> tell you? Does that file exist on your system?
> Please do the same for /usr/lib/ltdl.so.3.1.0 just for yuks.
> 
> Francisco Paco Peralta wrote:
>> Hey Guys,
>>
>> All right.  I ran the following command as requested:
>>
>> # rpm -qa | grep libtool
>> libtool-1.5.16.multilib2-3
>>
>> # rpm -ql libtool-libs
>> package libtool-libs is not installed
>>
>> Eric,
>>
>> I believe the way we got around this problem might have been by finding
>> a copy of the missing file and putting it in the directory.  Is there a
>> way to tell which rpm installed the package?
>>  
>> Francisco "Paco" Peralta
>>
>>
> 
> -- 
> -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] errors during upgrading qt

[Francisco Paco Peralta]

Here are the results:# rpm -qf /usr/lib/libltdl.so.3courier-authlib-toaster-0.58-1.3.1# rpm -qf /usr/lib/ltdl.so.3.1.0error: file /usr/lib/ltdl.so.3.1.0: No such file or directory Francisco "Paco" Peralta- Original Message From: "Eric "Shubes"" <[EMAIL PROTECTED]>To: qmailtoaster-list@qmailtoaster.comSent: Tuesday, October 24, 2006 4:51:51 PMSubject: Re: [qmailtoaster] errors during upgrading qtThat's interesting. I seem to remember now that the file(s) was included inthe courier-authlib package for that particular (FC4) distro.The files (one file, one
 link) in question are:lrwxrwxrwx  1 root root16 Sep 11 19:10 /usr/lib/libltdl.so.3 ->libltdl.so.3.1.0-rwxr-xr-x  1 root root 24588 Aug 13 00:13 /usr/lib/libltdl.so.3.1.0Paco, what does# rpm -qf /usr/lib/libltdl.so.3tell you? Does that file exist on your system?Please do the same for /usr/lib/ltdl.so.3.1.0 just for yuks.Francisco Paco Peralta wrote:> Hey Guys,> > All right.  I ran the following command as requested:> > # rpm -qa | grep libtool> libtool-1.5.16.multilib2-3> > # rpm -ql libtool-libs> package libtool-libs is not installed> > Eric,> > I believe the way we got around this problem might have been by finding> a copy of the missing file and putting it in the directory.  Is there a> way to tell which rpm installed the package?>  >
 Francisco "Paco" Peralta> > -- -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] errors during upgrading qt

[Eric \"Shubes\"]

That's interesting. I seem to remember now that the file(s) was included in
the courier-authlib package for that particular (FC4) distro.

The files (one file, one link) in question are:
lrwxrwxrwx  1 root root16 Sep 11 19:10 /usr/lib/libltdl.so.3 ->
libltdl.so.3.1.0
-rwxr-xr-x  1 root root 24588 Aug 13 00:13 /usr/lib/libltdl.so.3.1.0

Paco, what does
# rpm -qf /usr/lib/libltdl.so.3
tell you? Does that file exist on your system?
Please do the same for /usr/lib/ltdl.so.3.1.0 just for yuks.

Francisco Paco Peralta wrote:
> Hey Guys,
> 
> All right.  I ran the following command as requested:
> 
> # rpm -qa | grep libtool
> libtool-1.5.16.multilib2-3
> 
> # rpm -ql libtool-libs
> package libtool-libs is not installed
> 
> Eric,
> 
> I believe the way we got around this problem might have been by finding
> a copy of the missing file and putting it in the directory.  Is there a
> way to tell which rpm installed the package?
>  
> Francisco "Paco" Peralta
> 
> 

-- 
-Eric 'shubes'

-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] errors during upgrading qt

[Francisco Paco Peralta]

Hey Guys,All right.  I ran the following command as requested:# rpm -qa | grep libtoollibtool-1.5.16.multilib2-3# rpm -ql libtool-libspackage libtool-libs is not installedEric,I believe the way we got around this problem might have been by finding a copy of the missing file and putting it in the directory.  Is there a way to tell which rpm installed the package? Francisco "Paco" Peralta- Original Message From: "Eric "Shubes"" <[EMAIL PROTECTED]>To: qmailtoaster-list@qmailtoaster.comSent: Tuesday, October 24, 2006 4:21:53 PMSubject: Re:
 [qmailtoaster] errors during upgrading qtFWIW, here's what I seem to remember (take it w/ a grain of salt).The libtools-ltdl package is essentially the same as libtools-libs. Theyboth contain 1 file and 1 symlink (if I remember correctly). When/why it wasrenamed I don't know.I see from the archives, when doing# yum install libtools-libson FC4, it tried to install libtools-ltdl instead.libtools-libs exists happily on my centos4.4 toaster. It contains one fileand one symlink:# ls -l `rpm -ql libtool-libs`lrwxrwxrwx  1 root root16 Sep 11 19:10 /usr/lib/libltdl.so.3 ->libltdl.so.3.1.0-rwxr-xr-x  1 root root 24588 Aug 13 00:13 /usr/lib/libltdl.so.3.1.0I sure wish I could remember what I did to get Paco's toaster going.Hey Paco, if you're here, what's your toaster give you for the abovecommand? What do you have for "# rpm -qa | grep
 libtool"?Erik Espinoza wrote:> I'll work  on this with Nick. We are working to support Mandriva 2006.1> and FC6.> > Thanks,> Erik> > On 10/24/06, Samuel Díaz García <[EMAIL PROTECTED]> wrote:>> I'm having the same problem with FC5.>>>> I can't uninstall the libs because are being used by freeradius and>> another FC5 components that I have installed.>>>> I reported this problem some months ago.>>>> Regards>>>> -- >> Samuel Díaz García>> ArcosCom Wireless, S.L.L.>>>> CIF: B11828068>> c/ Romero Gago, 19>> Arcos de la Frontera>> 11630 - Cadiz>>>> http://www.arcoscom.com>>>> mailto:[EMAIL PROTECTED]>> msn:
 [EMAIL PROTECTED]>>>> Tlfn.: 956 70 13 15>> Fax:   956 70 34 83>>>>>> El Mar, 24 de Octubre de 2006, 20:21, Eric \"Shubes\" escribió:>> > Hey Crispin,>> >>> > Paco had this same issue about a month ago. I got his toaster fixed up,>> > but>> > don't remember the specifics. I can't seem to find a solution in the>> list>> > archives either.>> >>> > What distro/version/arch are you running?>> >>> > Short answer to your question: no, not with the current toaster.>> >>> > [EMAIL PROTECTED] wrote:>> >> I had to use obsolete upgrading script instead of new model. I however>> >> encounter the following issues>> >>>> >> courier imap failed to build because courier-authlib was
 requiered. I>> >> continued upgrading the rest of the packages and come back back to>> >> upgrade>> >> courier-authlib manually which also gave me issues.>> >>>> >> 1. libtool-ltdl confilcts with courier-authlib.>> >>>> >> Since I was in a hurry as the server was down, I had to remove>> >> libtool-ltdl which I cannot reinstall it as it still conflicts with>> >> courier-authlib.>> >>>> >> 2. after removing libtool-ltdl, I still failed to install>> >> courier-authlib>> >> as you can see bellow;>> >>>> >> # rpm -Uvh>> >> /usr/src/redhat/RPMS/i386/courier-authlib-toaster-0.58-1.3.1.i386.rpm>> >> error: Failed dependencies:>> >>
 courier-imap-toaster >= 3.0.3-1.2.1 is needed by (installed)>> >> control-panel-toaster-0.5-1.3.1.noarch>> >>>> >> [EMAIL PROTECTED] qtms-upgrade]# rpm -aq |grep courier-au>> >> [EMAIL PROTECTED] qtms-upgrade]# rpm -aq |grep courier-im>> >> courier-imap-toaster-3.0.8-1.2.10>> >>>> >> I had to remove, (again), control-pannel-toaster to be able to install>> >> courier-authlib then reinstalled control-pannel-toaster.>> >>>> >> My question is, is libtool-ltdl neccessary? if yes, what can I do stop>> >> the>> >> conflict?>> >>>> >> I will very much appreciate your help on this.>> >>>> >> Crispin.>> >>>> >>> > -->> > -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] errors during upgrading qt

[Erik Espinoza]

Give this one a shot:
http://devel.qmailtoaster.com/download/courier-authlib-toaster-0.58-1.3.2.src.rpm

Thanks,
Erik

On 10/24/06, Eric Shubes <[EMAIL PROTECTED]> wrote:

FWIW, here's what I seem to remember (take it w/ a grain of salt).

The libtools-ltdl package is essentially the same as libtools-libs. They
both contain 1 file and 1 symlink (if I remember correctly). When/why it was
renamed I don't know.

I see from the archives, when doing
# yum install libtools-libs
on FC4, it tried to install libtools-ltdl instead.

libtools-libs exists happily on my centos4.4 toaster. It contains one file
and one symlink:
# ls -l `rpm -ql libtool-libs`
lrwxrwxrwx  1 root root16 Sep 11 19:10 /usr/lib/libltdl.so.3 ->
libltdl.so.3.1.0
-rwxr-xr-x  1 root root 24588 Aug 13 00:13 /usr/lib/libltdl.so.3.1.0

I sure wish I could remember what I did to get Paco's toaster going.
Hey Paco, if you're here, what's your toaster give you for the above
command? What do you have for "# rpm -qa | grep libtool"?

Erik Espinoza wrote:
> I'll work  on this with Nick. We are working to support Mandriva 2006.1
> and FC6.
>
> Thanks,
> Erik
>
> On 10/24/06, Samuel Díaz García <[EMAIL PROTECTED]> wrote:
>> I'm having the same problem with FC5.
>>
>> I can't uninstall the libs because are being used by freeradius and
>> another FC5 components that I have installed.
>>
>> I reported this problem some months ago.
>>
>> Regards
>>
>> --
>> Samuel Díaz García
>> ArcosCom Wireless, S.L.L.
>>
>> CIF: B11828068
>> c/ Romero Gago, 19
>> Arcos de la Frontera
>> 11630 - Cadiz
>>
>> http://www.arcoscom.com
>>
>> mailto:[EMAIL PROTECTED]
>> msn: [EMAIL PROTECTED]
>>
>> Tlfn.: 956 70 13 15
>> Fax:   956 70 34 83
>>
>>
>> El Mar, 24 de Octubre de 2006, 20:21, Eric \"Shubes\" escribió:
>> > Hey Crispin,
>> >
>> > Paco had this same issue about a month ago. I got his toaster fixed up,
>> > but
>> > don't remember the specifics. I can't seem to find a solution in the
>> list
>> > archives either.
>> >
>> > What distro/version/arch are you running?
>> >
>> > Short answer to your question: no, not with the current toaster.
>> >
>> > [EMAIL PROTECTED] wrote:
>> >> I had to use obsolete upgrading script instead of new model. I however
>> >> encounter the following issues
>> >>
>> >> courier imap failed to build because courier-authlib was requiered. I
>> >> continued upgrading the rest of the packages and come back back to
>> >> upgrade
>> >> courier-authlib manually which also gave me issues.
>> >>
>> >> 1. libtool-ltdl confilcts with courier-authlib.
>> >>
>> >> Since I was in a hurry as the server was down, I had to remove
>> >> libtool-ltdl which I cannot reinstall it as it still conflicts with
>> >> courier-authlib.
>> >>
>> >> 2. after removing libtool-ltdl, I still failed to install
>> >> courier-authlib
>> >> as you can see bellow;
>> >>
>> >> # rpm -Uvh
>> >> /usr/src/redhat/RPMS/i386/courier-authlib-toaster-0.58-1.3.1.i386.rpm
>> >> error: Failed dependencies:
>> >> courier-imap-toaster >= 3.0.3-1.2.1 is needed by (installed)
>> >> control-panel-toaster-0.5-1.3.1.noarch
>> >>
>> >> [EMAIL PROTECTED] qtms-upgrade]# rpm -aq |grep courier-au
>> >> [EMAIL PROTECTED] qtms-upgrade]# rpm -aq |grep courier-im
>> >> courier-imap-toaster-3.0.8-1.2.10
>> >>
>> >> I had to remove, (again), control-pannel-toaster to be able to install
>> >> courier-authlib then reinstalled control-pannel-toaster.
>> >>
>> >> My question is, is libtool-ltdl neccessary? if yes, what can I do stop
>> >> the
>> >> conflict?
>> >>
>> >> I will very much appreciate your help on this.
>> >>
>> >> Crispin.
>> >>
>> >
>> > --
>> > -Eric 'shubes'
>> >


--
-Eric 'shubes'

-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] errors during upgrading qt

[Eric \"Shubes\"]

FWIW, here's what I seem to remember (take it w/ a grain of salt).

The libtools-ltdl package is essentially the same as libtools-libs. They
both contain 1 file and 1 symlink (if I remember correctly). When/why it was
renamed I don't know.

I see from the archives, when doing
# yum install libtools-libs
on FC4, it tried to install libtools-ltdl instead.

libtools-libs exists happily on my centos4.4 toaster. It contains one file
and one symlink:
# ls -l `rpm -ql libtool-libs`
lrwxrwxrwx  1 root root16 Sep 11 19:10 /usr/lib/libltdl.so.3 ->
libltdl.so.3.1.0
-rwxr-xr-x  1 root root 24588 Aug 13 00:13 /usr/lib/libltdl.so.3.1.0

I sure wish I could remember what I did to get Paco's toaster going.
Hey Paco, if you're here, what's your toaster give you for the above
command? What do you have for "# rpm -qa | grep libtool"?

Erik Espinoza wrote:
> I'll work  on this with Nick. We are working to support Mandriva 2006.1
> and FC6.
> 
> Thanks,
> Erik
> 
> On 10/24/06, Samuel Díaz García <[EMAIL PROTECTED]> wrote:
>> I'm having the same problem with FC5.
>>
>> I can't uninstall the libs because are being used by freeradius and
>> another FC5 components that I have installed.
>>
>> I reported this problem some months ago.
>>
>> Regards
>>
>> -- 
>> Samuel Díaz García
>> ArcosCom Wireless, S.L.L.
>>
>> CIF: B11828068
>> c/ Romero Gago, 19
>> Arcos de la Frontera
>> 11630 - Cadiz
>>
>> http://www.arcoscom.com
>>
>> mailto:[EMAIL PROTECTED]
>> msn: [EMAIL PROTECTED]
>>
>> Tlfn.: 956 70 13 15
>> Fax:   956 70 34 83
>>
>>
>> El Mar, 24 de Octubre de 2006, 20:21, Eric \"Shubes\" escribió:
>> > Hey Crispin,
>> >
>> > Paco had this same issue about a month ago. I got his toaster fixed up,
>> > but
>> > don't remember the specifics. I can't seem to find a solution in the
>> list
>> > archives either.
>> >
>> > What distro/version/arch are you running?
>> >
>> > Short answer to your question: no, not with the current toaster.
>> >
>> > [EMAIL PROTECTED] wrote:
>> >> I had to use obsolete upgrading script instead of new model. I however
>> >> encounter the following issues
>> >>
>> >> courier imap failed to build because courier-authlib was requiered. I
>> >> continued upgrading the rest of the packages and come back back to
>> >> upgrade
>> >> courier-authlib manually which also gave me issues.
>> >>
>> >> 1. libtool-ltdl confilcts with courier-authlib.
>> >>
>> >> Since I was in a hurry as the server was down, I had to remove
>> >> libtool-ltdl which I cannot reinstall it as it still conflicts with
>> >> courier-authlib.
>> >>
>> >> 2. after removing libtool-ltdl, I still failed to install
>> >> courier-authlib
>> >> as you can see bellow;
>> >>
>> >> # rpm -Uvh
>> >> /usr/src/redhat/RPMS/i386/courier-authlib-toaster-0.58-1.3.1.i386.rpm
>> >> error: Failed dependencies:
>> >> courier-imap-toaster >= 3.0.3-1.2.1 is needed by (installed)
>> >> control-panel-toaster-0.5-1.3.1.noarch
>> >>
>> >> [EMAIL PROTECTED] qtms-upgrade]# rpm -aq |grep courier-au
>> >> [EMAIL PROTECTED] qtms-upgrade]# rpm -aq |grep courier-im
>> >> courier-imap-toaster-3.0.8-1.2.10
>> >>
>> >> I had to remove, (again), control-pannel-toaster to be able to install
>> >> courier-authlib then reinstalled control-pannel-toaster.
>> >>
>> >> My question is, is libtool-ltdl neccessary? if yes, what can I do stop
>> >> the
>> >> conflict?
>> >>
>> >> I will very much appreciate your help on this.
>> >>
>> >> Crispin.
>> >>
>> >
>> > --
>> > -Eric 'shubes'
>> >


-- 
-Eric 'shubes'

-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] errors during upgrading qt

[Erik Espinoza]

I'll work  on this with Nick. We are working to support Mandriva 2006.1 and FC6.

Thanks,
Erik

On 10/24/06, Samuel Díaz García <[EMAIL PROTECTED]> wrote:

I'm having the same problem with FC5.

I can't uninstall the libs because are being used by freeradius and
another FC5 components that I have installed.

I reported this problem some months ago.

Regards

--
Samuel Díaz García
ArcosCom Wireless, S.L.L.

CIF: B11828068
c/ Romero Gago, 19
Arcos de la Frontera
11630 - Cadiz

http://www.arcoscom.com

mailto:[EMAIL PROTECTED]
msn: [EMAIL PROTECTED]

Tlfn.: 956 70 13 15
Fax:   956 70 34 83


El Mar, 24 de Octubre de 2006, 20:21, Eric \"Shubes\" escribió:
> Hey Crispin,
>
> Paco had this same issue about a month ago. I got his toaster fixed up,
> but
> don't remember the specifics. I can't seem to find a solution in the list
> archives either.
>
> What distro/version/arch are you running?
>
> Short answer to your question: no, not with the current toaster.
>
> [EMAIL PROTECTED] wrote:
>> I had to use obsolete upgrading script instead of new model. I however
>> encounter the following issues
>>
>> courier imap failed to build because courier-authlib was requiered. I
>> continued upgrading the rest of the packages and come back back to
>> upgrade
>> courier-authlib manually which also gave me issues.
>>
>> 1. libtool-ltdl confilcts with courier-authlib.
>>
>> Since I was in a hurry as the server was down, I had to remove
>> libtool-ltdl which I cannot reinstall it as it still conflicts with
>> courier-authlib.
>>
>> 2. after removing libtool-ltdl, I still failed to install
>> courier-authlib
>> as you can see bellow;
>>
>> # rpm -Uvh
>> /usr/src/redhat/RPMS/i386/courier-authlib-toaster-0.58-1.3.1.i386.rpm
>> error: Failed dependencies:
>> courier-imap-toaster >= 3.0.3-1.2.1 is needed by (installed)
>> control-panel-toaster-0.5-1.3.1.noarch
>>
>> [EMAIL PROTECTED] qtms-upgrade]# rpm -aq |grep courier-au
>> [EMAIL PROTECTED] qtms-upgrade]# rpm -aq |grep courier-im
>> courier-imap-toaster-3.0.8-1.2.10
>>
>> I had to remove, (again), control-pannel-toaster to be able to install
>> courier-authlib then reinstalled control-pannel-toaster.
>>
>> My question is, is libtool-ltdl neccessary? if yes, what can I do stop
>> the
>> conflict?
>>
>> I will very much appreciate your help on this.
>>
>> Crispin.
>>
>
> --
> -Eric 'shubes'
>
> -
>  QmailToaster hosted by: VR Hosted 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>



-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] errors during upgrading qt

[Samuel Díaz García]

I'm having the same problem with FC5.

I can't uninstall the libs because are being used by freeradius and
another FC5 components that I have installed.

I reported this problem some months ago.

Regards

-- 
Samuel Díaz García
ArcosCom Wireless, S.L.L.

CIF: B11828068
c/ Romero Gago, 19
Arcos de la Frontera
11630 - Cadiz

http://www.arcoscom.com

mailto:[EMAIL PROTECTED]
msn: [EMAIL PROTECTED]

Tlfn.: 956 70 13 15
Fax:   956 70 34 83


El Mar, 24 de Octubre de 2006, 20:21, Eric \"Shubes\" escribió:
> Hey Crispin,
>
> Paco had this same issue about a month ago. I got his toaster fixed up,
> but
> don't remember the specifics. I can't seem to find a solution in the list
> archives either.
>
> What distro/version/arch are you running?
>
> Short answer to your question: no, not with the current toaster.
>
> [EMAIL PROTECTED] wrote:
>> I had to use obsolete upgrading script instead of new model. I however
>> encounter the following issues
>>
>> courier imap failed to build because courier-authlib was requiered. I
>> continued upgrading the rest of the packages and come back back to
>> upgrade
>> courier-authlib manually which also gave me issues.
>>
>> 1. libtool-ltdl confilcts with courier-authlib.
>>
>> Since I was in a hurry as the server was down, I had to remove
>> libtool-ltdl which I cannot reinstall it as it still conflicts with
>> courier-authlib.
>>
>> 2. after removing libtool-ltdl, I still failed to install
>> courier-authlib
>> as you can see bellow;
>>
>> # rpm -Uvh
>> /usr/src/redhat/RPMS/i386/courier-authlib-toaster-0.58-1.3.1.i386.rpm
>> error: Failed dependencies:
>> courier-imap-toaster >= 3.0.3-1.2.1 is needed by (installed)
>> control-panel-toaster-0.5-1.3.1.noarch
>>
>> [EMAIL PROTECTED] qtms-upgrade]# rpm -aq |grep courier-au
>> [EMAIL PROTECTED] qtms-upgrade]# rpm -aq |grep courier-im
>> courier-imap-toaster-3.0.8-1.2.10
>>
>> I had to remove, (again), control-pannel-toaster to be able to install
>> courier-authlib then reinstalled control-pannel-toaster.
>>
>> My question is, is libtool-ltdl neccessary? if yes, what can I do stop
>> the
>> conflict?
>>
>> I will very much appreciate your help on this.
>>
>> Crispin.
>>
>
> --
> -Eric 'shubes'
>
> -
>  QmailToaster hosted by: VR Hosted 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>



-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] errors during upgrading qt

[Erik Espinoza]

Hey Crispin, I assume you are using FC4 w/ i386. Why can't you just
remove libtool-ltdl?

Thanks,
Erik

On 10/24/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:

I had to use obsolete upgrading script instead of new model. I however
encounter the following issues

courier imap failed to build because courier-authlib was requiered. I
continued upgrading the rest of the packages and come back back to upgrade
courier-authlib manually which also gave me issues.

1. libtool-ltdl confilcts with courier-authlib.

Since I was in a hurry as the server was down, I had to remove
libtool-ltdl which I cannot reinstall it as it still conflicts with
courier-authlib.

2. after removing libtool-ltdl, I still failed to install courier-authlib
as you can see bellow;

# rpm -Uvh
/usr/src/redhat/RPMS/i386/courier-authlib-toaster-0.58-1.3.1.i386.rpm
error: Failed dependencies:
courier-imap-toaster >= 3.0.3-1.2.1 is needed by (installed)
control-panel-toaster-0.5-1.3.1.noarch

[EMAIL PROTECTED] qtms-upgrade]# rpm -aq |grep courier-au
[EMAIL PROTECTED] qtms-upgrade]# rpm -aq |grep courier-im
courier-imap-toaster-3.0.8-1.2.10

I had to remove, (again), control-pannel-toaster to be able to install
courier-authlib then reinstalled control-pannel-toaster.

My question is, is libtool-ltdl neccessary? if yes, what can I do stop the
conflict?

I will very much appreciate your help on this.

Crispin.

> Dear All,
>
> I got the same error while trying to upgrade.  It seems the problem came
> from the parameter sequence in "qtp-build-rpms".  The original program
> looks
> like this (~line 194):
>
> me=`basename $0`
> myver=0.1.3
> echo "$me $myver"
> ARCH=$1
> BUILD_DIST=$2
> BUILD_DIR=$3
> UPGRADE_DIR=$4
> CURRENT_PACKAGES=$5
> logfile=$6
> SANDBOX=$7
>
> While I think it should be:
>
> me=`basename $0`
> myver=0.1.3
> echo "$me $myver"
> *SANDBOX=$1
> *ARCH=$2
> BUILD_DIST=$3
> BUILD_DIR=$4
> UPGRADE_DIR=$5
> CURRENT_PACKAGES=$6
> logfile=$7
>
> It works for me after I've made such change.
>
> Best regards,
> Bill
>
>
> [EMAIL PROTECTED] wrote:
>
> The order of parameters passed from qtp-newmodel to qtp-build-rpms was
> changed at some point. One of these scripts is apparently not up to date.
>
> You should have:
> qtp-newmodel v0.1.10
> qtp-whatami v0.1.1
> qtp-build-sandbox v0.1.1
> qtp-build-rpms v0.1.3
>
> --
> -Eric 'shubes'
>
>
> I am still getting the same errors as you can see below. I downloaded ver
> 1.2 as you instructed.
>
> Creating /opt/qtp-sandbox/home/vpopmail ...
> Creating /opt/qtp-sandbox/ misc directories ...
> Sandbox has been built successfully!
>
> Starting to build the binary rpms ...(pizza anyone?)
>
> If you want to view compile messages, you can open another terminal and:
> # tail -f /opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log
>
> qtp-build-rpms 0.1.3
> cat: /usr/src/qtp-upgrade: Is a directory
> qtp-build-rpms Error - package list not found
> Build failed, Exiting.
> [EMAIL PROTECTED] upgrading]#
>
>
>
> -
>  QmailToaster hosted by: VR Hosted 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>



-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] errors during upgrading qt

[Eric \"Shubes\"]

Hey Crispin,

Paco had this same issue about a month ago. I got his toaster fixed up, but
don't remember the specifics. I can't seem to find a solution in the list
archives either.

What distro/version/arch are you running?

Short answer to your question: no, not with the current toaster.

[EMAIL PROTECTED] wrote:
> I had to use obsolete upgrading script instead of new model. I however
> encounter the following issues
> 
> courier imap failed to build because courier-authlib was requiered. I
> continued upgrading the rest of the packages and come back back to upgrade
> courier-authlib manually which also gave me issues.
> 
> 1. libtool-ltdl confilcts with courier-authlib.
> 
> Since I was in a hurry as the server was down, I had to remove
> libtool-ltdl which I cannot reinstall it as it still conflicts with
> courier-authlib.
> 
> 2. after removing libtool-ltdl, I still failed to install courier-authlib
> as you can see bellow;
> 
> # rpm -Uvh
> /usr/src/redhat/RPMS/i386/courier-authlib-toaster-0.58-1.3.1.i386.rpm
> error: Failed dependencies:
> courier-imap-toaster >= 3.0.3-1.2.1 is needed by (installed)
> control-panel-toaster-0.5-1.3.1.noarch
> 
> [EMAIL PROTECTED] qtms-upgrade]# rpm -aq |grep courier-au
> [EMAIL PROTECTED] qtms-upgrade]# rpm -aq |grep courier-im
> courier-imap-toaster-3.0.8-1.2.10
> 
> I had to remove, (again), control-pannel-toaster to be able to install
> courier-authlib then reinstalled control-pannel-toaster.
> 
> My question is, is libtool-ltdl neccessary? if yes, what can I do stop the
> conflict?
>
> I will very much appreciate your help on this.
> 
> Crispin.
> 

-- 
-Eric 'shubes'

-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] errors during upgrading qt

[ldap]

I had to use obsolete upgrading script instead of new model. I however
encounter the following issues

courier imap failed to build because courier-authlib was requiered. I
continued upgrading the rest of the packages and come back back to upgrade
courier-authlib manually which also gave me issues.

1. libtool-ltdl confilcts with courier-authlib.

Since I was in a hurry as the server was down, I had to remove
libtool-ltdl which I cannot reinstall it as it still conflicts with
courier-authlib.

2. after removing libtool-ltdl, I still failed to install courier-authlib
as you can see bellow;

# rpm -Uvh
/usr/src/redhat/RPMS/i386/courier-authlib-toaster-0.58-1.3.1.i386.rpm
error: Failed dependencies:
courier-imap-toaster >= 3.0.3-1.2.1 is needed by (installed)
control-panel-toaster-0.5-1.3.1.noarch

[EMAIL PROTECTED] qtms-upgrade]# rpm -aq |grep courier-au
[EMAIL PROTECTED] qtms-upgrade]# rpm -aq |grep courier-im
courier-imap-toaster-3.0.8-1.2.10

I had to remove, (again), control-pannel-toaster to be able to install
courier-authlib then reinstalled control-pannel-toaster.

My question is, is libtool-ltdl neccessary? if yes, what can I do stop the
conflict?

I will very much appreciate your help on this.

Crispin.

> Dear All,
>
> I got the same error while trying to upgrade.  It seems the problem came
> from the parameter sequence in "qtp-build-rpms".  The original program
> looks
> like this (~line 194):
>
> me=`basename $0`
> myver=0.1.3
> echo "$me $myver"
> ARCH=$1
> BUILD_DIST=$2
> BUILD_DIR=$3
> UPGRADE_DIR=$4
> CURRENT_PACKAGES=$5
> logfile=$6
> SANDBOX=$7
>
> While I think it should be:
>
> me=`basename $0`
> myver=0.1.3
> echo "$me $myver"
> *SANDBOX=$1
> *ARCH=$2
> BUILD_DIST=$3
> BUILD_DIR=$4
> UPGRADE_DIR=$5
> CURRENT_PACKAGES=$6
> logfile=$7
>
> It works for me after I've made such change.
>
> Best regards,
> Bill
>
>
> [EMAIL PROTECTED] wrote:
>
> The order of parameters passed from qtp-newmodel to qtp-build-rpms was
> changed at some point. One of these scripts is apparently not up to date.
>
> You should have:
> qtp-newmodel v0.1.10
> qtp-whatami v0.1.1
> qtp-build-sandbox v0.1.1
> qtp-build-rpms v0.1.3
>
> --
> -Eric 'shubes'
>
>
> I am still getting the same errors as you can see below. I downloaded ver
> 1.2 as you instructed.
>
> Creating /opt/qtp-sandbox/home/vpopmail ...
> Creating /opt/qtp-sandbox/ misc directories ...
> Sandbox has been built successfully!
>
> Starting to build the binary rpms ...(pizza anyone?)
>
> If you want to view compile messages, you can open another terminal and:
> # tail -f /opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log
>
> qtp-build-rpms 0.1.3
> cat: /usr/src/qtp-upgrade: Is a directory
> qtp-build-rpms Error - package list not found
> Build failed, Exiting.
> [EMAIL PROTECTED] upgrading]#
>
>
>
> -
>  QmailToaster hosted by: VR Hosted 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>



-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] errors during upgrading qt

[Eric \"Shubes\"]

That is correct, Bill.

Instead of modifying the script though, I'd recommend downloading the
current set of scripts. There may have been minor changes that may or may
not affect your particular toaster. It appears that I neglected to tick the
version number when I made this correction. Sorry about that (blush). I'll
try not to do that again! ;)

FYI any of you x86_64 folks thinking of upgrading, we found a bug in
qtp-whatami yesterday that affected this architecture. It was not harmful,
it just wouldn't build some packages (vpopmail in particular). Please grab
the corrected version of qtp-whatami from the web before doing any upgrades.

Bill Kwok wrote:
> Dear All,
>  
> I got the same error while trying to upgrade.  It seems the problem came
> from the parameter sequence in "qtp-build-rpms".  The original program
> looks like this (~line 194):
>  
> me=`basename $0`
> myver=0.1.3
> echo "$me $myver"
> ARCH=$1
> BUILD_DIST=$2
> BUILD_DIR=$3
> UPGRADE_DIR=$4
> CURRENT_PACKAGES=$5
> logfile=$6
> SANDBOX=$7
>  
> While I think it should be:
>  
> me=`basename $0`
> myver=0.1.3
> echo "$me $myver"
> *SANDBOX=$1
> *ARCH=$2
> BUILD_DIST=$3
> BUILD_DIR=$4
> UPGRADE_DIR=$5
> CURRENT_PACKAGES=$6
> logfile=$7
>  
> It works for me after I've made such change.
>  
> Best regards,
> Bill
>  
>  
> [EMAIL PROTECTED]  wrote:
>>> The order of parameters passed from qtp-newmodel to qtp-build-rpms was
>>> changed at some point. One of these scripts is apparently not up to date.
>>>
>>> You should have:
>>> qtp-newmodel v0.1.10
>>>
>>> qtp-whatami v0.1.1
>>> qtp-build-sandbox v0.1.1
>>> qtp-build-rpms v0.1.3
>>>
>>> --
>>> -Eric 'shubes'
>>
>> I am still getting the same errors as you can see below. I downloaded ver
>> 1.2 as you instructed.
>>
>>
>> Creating /opt/qtp-sandbox/home/vpopmail ...
>> Creating /opt/qtp-sandbox/ misc directories ...
>> Sandbox has been built successfully!
>>
>> Starting to build the binary rpms ...(pizza anyone?)
>>
>> If you want to view compile messages, you can open another terminal and:
>>
>> # tail -f /opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log
>>
>> qtp-build-rpms 0.1.3
>> cat: /usr/src/qtp-upgrade: Is a directory
>> qtp-build-rpms Error - package list not found
>> Build failed, Exiting.
>>
>> [EMAIL PROTECTED] upgrading]#
>>


-- 
-Eric 'shubes'

-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] errors during upgrading qt

[Bill Kwok]

Dear All,
 
I got the same error while trying to upgrade.  It seems the problem came from the parameter sequence in "qtp-build-rpms".  The original program looks like this (~line 194):
 
me=`basename $0`myver=0.1.3echo "$me $myver"ARCH=$1BUILD_DIST=$2BUILD_DIR=$3UPGRADE_DIR=$4CURRENT_PACKAGES=$5logfile=$6SANDBOX=$7 
While I think it should be:
 
me=`basename $0`myver=0.1.3echo "$me $myver"SANDBOX=$1ARCH=$2BUILD_DIST=$3BUILD_DIR=$4UPGRADE_DIR=$5CURRENT_PACKAGES=$6logfile=$7 
It works for me after I've made such change.
 
Best regards,
Bill
 
 
[EMAIL PROTECTED] wrote: 

The order of parameters passed from qtp-newmodel to qtp-build-rpms waschanged at some point. One of these scripts is apparently not up to date.You should have:qtp-newmodel v0.1.10
qtp-whatami v0.1.1qtp-build-sandbox v0.1.1qtp-build-rpms v0.1.3---Eric 'shubes'I am still getting the same errors as you can see below. I downloaded ver1.2 as you instructed.
Creating /opt/qtp-sandbox/home/vpopmail ...Creating /opt/qtp-sandbox/ misc directories ...Sandbox has been built successfully!Starting to build the binary rpms ...(pizza anyone?)If you want to view compile messages, you can open another terminal and:
# tail -f /opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.logqtp-build-rpms 0.1.3cat: /usr/src/qtp-upgrade: Is a directoryqtp-build-rpms Error - package list not foundBuild failed, Exiting.
[EMAIL PROTECTED] upgrading]#- QmailToaster hosted by: VR Hosted -
To unsubscribe, e-mail: [EMAIL PROTECTED]For additional commands, e-mail: 
[EMAIL PROTECTED]

Re: [qmailtoaster] errors during upgrading qt

[Erik Espinoza]

Looks like you are using packages frm a different clam distribution.

You may want to resolve that before attempting to apply our patches.

Erik

On 10/18/06, Lucian Cristian <[EMAIL PROTECTED]> wrote:

Eric "Shubes" wrote:
> Lucian Cristian wrote:
>
>> Eric "Shubes" wrote:
>>
>>> Lucian Cristian wrote:
>>>
>>>
 Eric "Shubes" wrote:


> Lucian Cristian wrote:
>
>
>
>> I tried to do a linked sandbox and I got the following output:
>>
>> ..
>> ..
>> Starting to build the binary rpms ...(pizza anyone?)
>>
>> If you want to view compile messages, you can open another terminal
>> and:
>> # tail -f /opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log
>>
>> qtp-build-rpms v0.1.3
>> Building spamassassin-toaster-3.1.5-1.3.3 ...
>> qtp-build-rpms - rpmbuild failed for spamassassin-toaster-3.1.5-1.3.3
>> qtp-build-rpms - see
>> /opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log
>> Build failed, Exiting.
>> [EMAIL PROTECTED] qmailtoaster-plus]#
>> [EMAIL PROTECTED] qmailtoaster-plus]#  tail -f
>> /opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log
>> Building spamassassin-toaster-3.1.5-1.3.3 ...
>> error: Unable to open temp file.
>> Installing
>> /usr/src/qtp-upgrade/SRPMS/spamassassin-toaster-3.1.5-1.3.3.src.rpm
>> Building target platforms: i686
>> Building for target i686
>>
>>
>> RPM build errors:
>>Unable to open temp file.
>>
>>
>>
> I can't recreate this error. In build-recent.log I get:
> Building spamassassin-toaster-3.1.5-1.3.3 ...
> Installing
> /usr/src/qtp-upgrade/SRPMS/spamassassin-toaster-3.1.5-1.3.3.src.rpm
> Building target platforms: i686
> Building for target i686
> Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.13427
>
> I'm not sure what temp file you're bombing on. What does
> # ls -ld /var/tmp
> # ls -ld /opt/qtp-sandbox/var/tmp
> show you? I have
> drwxrwxrwt  2 root root 4096 Oct 15 11:12 /var/tmp
> and
> drwxr-xr-x  2 root root 4096 Oct 18 12:33 /opt/qtp-sandbox/var/tmp
> respectively.
>
> Please verify that you are running the current scripts:
> qtp-build-rpms:myver=v0.1.3
> qtp-build-sandbox:myver=v0.1.2
> qtp-newmodel:myver=v0.1.10
> qtp-whatami:myver=v0.1.1
>
> If that all checks out, I'd try running again and letting it
> recreate the
> sandbox.
>
> Please let me know how you make out.
>
>
 I have this output:
 [EMAIL PROTECTED] qmailtoaster-plus]# ls -ld /var/tmp
 lrwxrwxrwx  1 root root 8 Aug  5 23:32 /var/tmp -> /usr/tmp
 [EMAIL PROTECTED] qmailtoaster-plus]# ls -ld /opt/qtp-sandbox/var/tmp
 lrwxrwxrwx  1 root root 8 Oct 18 19:49 /opt/qtp-sandbox/var/tmp ->
 /usr/tmp

 the files are

 qtp-build-rpms:myver=v0.1.3
 qtp-build-sandbox:myver=v0.1.2
 qtp-newmodel:myver=v0.1.10
 qtp-whatami:myver=v0.1.1


 I tried 3-4 times using only linked because currently I don't have
 enough space on this machine to make a copy.



>>> That's why I made a linked option. ;)
>>> None the less, the sandbox could use some trimming to get rid of some
>>> of the
>>> bloat.
>>>
>>> Anywise, I notice that your /var/tmp is a symlink to /usr/tmp:
>>> lrwxrwxrwx  1 root root 8 Aug  5 23:32 /var/tmp -> /usr/tmp
>>> and likewise in the sandbox, as the sandbox should be the same.
>>>
>>> What does
>>> # ls -ld /usr/tmp
>>> show you?
>>>
>>> What distro/version are you running? On CentOS4, I have /var/tmp being
>>> the
>>> real directory with a /usr/tmp symlink pointing to it, FWIW.
>>>
>>> I'm just searching here. Something's gotta be somehow different. Show me
>>> # df -h
>>> while we're at it.
>>>
>>>
>>>
>> here they are:
>>
>> [EMAIL PROTECTED] qmailtoaster-plus]# ls -ld /usr/tmp
>> drwxr-xr-x  3 root root 4096 Oct 17 21:52 /usr/tmp
>>
>>
>> [EMAIL PROTECTED] qmailtoaster-plus]# df -h
>> FilesystemSize  Used Avail Use% Mounted on
>> /dev/sda2 7.8G  5.0G  2.6G  66% /
>> none  252M 0  252M   0% /dev/shm
>>
>> I have another 2 partitions, but are not mounted because I don't need
>> them for sandbox
>>
>> Indeed I have /var/tmp is a symlink to /usr/tmp.. I'll switch the link
>> (I don't remember how and why I changed them)
>>
>> Distro will be always the latest CentOS.
>>
>> Regards!
>>
>>
> Please let me know your result.
>
>
It seems that is working, but I have to manually remove freshclam file
from logrotate.d
..

qtp-build-rpms v0.1.3
REMOVED spamassassin-toaster from sandbox (not for real)
Building spamassassin-toaster-3.1.5-1.3.3 ...
Installing spamassassin-toaster-3.1.5-1.3.3 in the sandbox ...
Building clamav-toaster-0.88.4-1.3.3 ...
Installing clamav-toaster-0.88.4-1.3.3 in the sandbox ...
qtp-build-rpms - rpm -Uvh failed for clamav-toaster-0.88.4-1.3.3
qtp-build-rpms - see
/opt/qtp-sandbox/u

Re: [qmailtoaster] errors during upgrading qt

[Lucian Cristian]

Eric "Shubes" wrote:

Lucian Cristian wrote:
  

Eric "Shubes" wrote:


Lucian Cristian wrote:
 
  

Eric "Shubes" wrote:
   


Lucian Cristian wrote:
 
 
  

I tried to do a linked sandbox and I got the following output:

..
..
Starting to build the binary rpms ...(pizza anyone?)

If you want to view compile messages, you can open another terminal
and:
# tail -f /opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log

qtp-build-rpms v0.1.3
Building spamassassin-toaster-3.1.5-1.3.3 ...
qtp-build-rpms - rpmbuild failed for spamassassin-toaster-3.1.5-1.3.3
qtp-build-rpms - see
/opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log
Build failed, Exiting.
[EMAIL PROTECTED] qmailtoaster-plus]#
[EMAIL PROTECTED] qmailtoaster-plus]#  tail -f
/opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log
Building spamassassin-toaster-3.1.5-1.3.3 ...
error: Unable to open temp file.
Installing
/usr/src/qtp-upgrade/SRPMS/spamassassin-toaster-3.1.5-1.3.3.src.rpm
Building target platforms: i686
Building for target i686


RPM build errors:
   Unable to open temp file.




I can't recreate this error. In build-recent.log I get:
Building spamassassin-toaster-3.1.5-1.3.3 ...
Installing
/usr/src/qtp-upgrade/SRPMS/spamassassin-toaster-3.1.5-1.3.3.src.rpm
Building target platforms: i686
Building for target i686
Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.13427

I'm not sure what temp file you're bombing on. What does
# ls -ld /var/tmp
# ls -ld /opt/qtp-sandbox/var/tmp
show you? I have
drwxrwxrwt  2 root root 4096 Oct 15 11:12 /var/tmp
and
drwxr-xr-x  2 root root 4096 Oct 18 12:33 /opt/qtp-sandbox/var/tmp
respectively.

Please verify that you are running the current scripts:
qtp-build-rpms:myver=v0.1.3
qtp-build-sandbox:myver=v0.1.2
qtp-newmodel:myver=v0.1.10
qtp-whatami:myver=v0.1.1

If that all checks out, I'd try running again and letting it
recreate the
sandbox.

Please let me know how you make out.

  

I have this output:
[EMAIL PROTECTED] qmailtoaster-plus]# ls -ld /var/tmp
lrwxrwxrwx  1 root root 8 Aug  5 23:32 /var/tmp -> /usr/tmp
[EMAIL PROTECTED] qmailtoaster-plus]# ls -ld /opt/qtp-sandbox/var/tmp
lrwxrwxrwx  1 root root 8 Oct 18 19:49 /opt/qtp-sandbox/var/tmp ->
/usr/tmp

the files are

qtp-build-rpms:myver=v0.1.3
qtp-build-sandbox:myver=v0.1.2
qtp-newmodel:myver=v0.1.10
qtp-whatami:myver=v0.1.1


I tried 3-4 times using only linked because currently I don't have
enough space on this machine to make a copy.




That's why I made a linked option. ;)
None the less, the sandbox could use some trimming to get rid of some
of the
bloat.

Anywise, I notice that your /var/tmp is a symlink to /usr/tmp:
lrwxrwxrwx  1 root root 8 Aug  5 23:32 /var/tmp -> /usr/tmp
and likewise in the sandbox, as the sandbox should be the same.

What does
# ls -ld /usr/tmp
show you?

What distro/version are you running? On CentOS4, I have /var/tmp being
the
real directory with a /usr/tmp symlink pointing to it, FWIW.

I'm just searching here. Something's gotta be somehow different. Show me
# df -h
while we're at it.

  
  

here they are:

[EMAIL PROTECTED] qmailtoaster-plus]# ls -ld /usr/tmp
drwxr-xr-x  3 root root 4096 Oct 17 21:52 /usr/tmp


[EMAIL PROTECTED] qmailtoaster-plus]# df -h
FilesystemSize  Used Avail Use% Mounted on
/dev/sda2 7.8G  5.0G  2.6G  66% /
none  252M 0  252M   0% /dev/shm

I have another 2 partitions, but are not mounted because I don't need
them for sandbox

Indeed I have /var/tmp is a symlink to /usr/tmp.. I'll switch the link
(I don't remember how and why I changed them)

Distro will be always the latest CentOS.

Regards!



Please let me know your result.

  
It seems that is working, but I have to manually remove freshclam file 
from logrotate.d

..

qtp-build-rpms v0.1.3
REMOVED spamassassin-toaster from sandbox (not for real)
Building spamassassin-toaster-3.1.5-1.3.3 ...
Installing spamassassin-toaster-3.1.5-1.3.3 in the sandbox ...
Building clamav-toaster-0.88.4-1.3.3 ...
Installing clamav-toaster-0.88.4-1.3.3 in the sandbox ...
qtp-build-rpms - rpm -Uvh failed for clamav-toaster-0.88.4-1.3.3
qtp-build-rpms - see 
/opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log

Build failed, Exiting.
[EMAIL PROTECTED] qmailtoaster-plus]#
[EMAIL PROTECTED] qmailtoaster-plus]#  tail -f 
/opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log

+ exit 0
Executing(--clean): /bin/sh -e /var/tmp/rpm-tmp.57783
+ umask 022
+ cd /usr/src/redhat/BUILD
+ rm -rf clamav-0.88.4
+ exit 0
Installing clamav-toaster-0.88.4-1.3.3 in the sandbox ...
Preparing...
##
   file /etc/cron.daily/freshclam from install of 
clamav-toaster-0.88.4-1.3.3 conflicts with file from package 
clamav-db-0.88.1-1.el4.rf
   file /etc/logrotate.d/freshclam from install of 
clamav-toaster-0.88.4-1.3.3 conflicts with file from package 
clamav-db-0.88.1-1.e

Re: [qmailtoaster] errors during upgrading qt

[Eric \"Shubes\"]

Lucian Cristian wrote:
> Eric "Shubes" wrote:
>> Lucian Cristian wrote:
>>  
>>> Eric "Shubes" wrote:
>>>
 Lucian Cristian wrote:
  
  
> I tried to do a linked sandbox and I got the following output:
>
> ..
> ..
> Starting to build the binary rpms ...(pizza anyone?)
>
> If you want to view compile messages, you can open another terminal
> and:
> # tail -f /opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log
>
> qtp-build-rpms v0.1.3
> Building spamassassin-toaster-3.1.5-1.3.3 ...
> qtp-build-rpms - rpmbuild failed for spamassassin-toaster-3.1.5-1.3.3
> qtp-build-rpms - see
> /opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log
> Build failed, Exiting.
> [EMAIL PROTECTED] qmailtoaster-plus]#
> [EMAIL PROTECTED] qmailtoaster-plus]#  tail -f
> /opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log
> Building spamassassin-toaster-3.1.5-1.3.3 ...
> error: Unable to open temp file.
> Installing
> /usr/src/qtp-upgrade/SRPMS/spamassassin-toaster-3.1.5-1.3.3.src.rpm
> Building target platforms: i686
> Building for target i686
>
>
> RPM build errors:
>Unable to open temp file.
>
> 
 I can't recreate this error. In build-recent.log I get:
 Building spamassassin-toaster-3.1.5-1.3.3 ...
 Installing
 /usr/src/qtp-upgrade/SRPMS/spamassassin-toaster-3.1.5-1.3.3.src.rpm
 Building target platforms: i686
 Building for target i686
 Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.13427

 I'm not sure what temp file you're bombing on. What does
 # ls -ld /var/tmp
 # ls -ld /opt/qtp-sandbox/var/tmp
 show you? I have
 drwxrwxrwt  2 root root 4096 Oct 15 11:12 /var/tmp
 and
 drwxr-xr-x  2 root root 4096 Oct 18 12:33 /opt/qtp-sandbox/var/tmp
 respectively.

 Please verify that you are running the current scripts:
 qtp-build-rpms:myver=v0.1.3
 qtp-build-sandbox:myver=v0.1.2
 qtp-newmodel:myver=v0.1.10
 qtp-whatami:myver=v0.1.1

 If that all checks out, I'd try running again and letting it
 recreate the
 sandbox.

 Please let me know how you make out.
 
>>> I have this output:
>>> [EMAIL PROTECTED] qmailtoaster-plus]# ls -ld /var/tmp
>>> lrwxrwxrwx  1 root root 8 Aug  5 23:32 /var/tmp -> /usr/tmp
>>> [EMAIL PROTECTED] qmailtoaster-plus]# ls -ld /opt/qtp-sandbox/var/tmp
>>> lrwxrwxrwx  1 root root 8 Oct 18 19:49 /opt/qtp-sandbox/var/tmp ->
>>> /usr/tmp
>>>
>>> the files are
>>>
>>> qtp-build-rpms:myver=v0.1.3
>>> qtp-build-sandbox:myver=v0.1.2
>>> qtp-newmodel:myver=v0.1.10
>>> qtp-whatami:myver=v0.1.1
>>>
>>>
>>> I tried 3-4 times using only linked because currently I don't have
>>> enough space on this machine to make a copy.
>>>
>>> 
>>
>> That's why I made a linked option. ;)
>> None the less, the sandbox could use some trimming to get rid of some
>> of the
>> bloat.
>>
>> Anywise, I notice that your /var/tmp is a symlink to /usr/tmp:
>> lrwxrwxrwx  1 root root 8 Aug  5 23:32 /var/tmp -> /usr/tmp
>> and likewise in the sandbox, as the sandbox should be the same.
>>
>> What does
>> # ls -ld /usr/tmp
>> show you?
>>
>> What distro/version are you running? On CentOS4, I have /var/tmp being
>> the
>> real directory with a /usr/tmp symlink pointing to it, FWIW.
>>
>> I'm just searching here. Something's gotta be somehow different. Show me
>> # df -h
>> while we're at it.
>>
>>   
> here they are:
> 
> [EMAIL PROTECTED] qmailtoaster-plus]# ls -ld /usr/tmp
> drwxr-xr-x  3 root root 4096 Oct 17 21:52 /usr/tmp
> 
> 
> [EMAIL PROTECTED] qmailtoaster-plus]# df -h
> FilesystemSize  Used Avail Use% Mounted on
> /dev/sda2 7.8G  5.0G  2.6G  66% /
> none  252M 0  252M   0% /dev/shm
> 
> I have another 2 partitions, but are not mounted because I don't need
> them for sandbox
> 
> Indeed I have /var/tmp is a symlink to /usr/tmp.. I'll switch the link
> (I don't remember how and why I changed them)
> 
> Distro will be always the latest CentOS.
> 
> Regards!
> 
Please let me know your result.

-- 
-Eric 'shubes'

-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] errors during upgrading qt

[Lucian Cristian]

Eric "Shubes" wrote:

Lucian Cristian wrote:
  

Eric "Shubes" wrote:


Lucian Cristian wrote:
 
  

I tried to do a linked sandbox and I got the following output:

..
..
Starting to build the binary rpms ...(pizza anyone?)

If you want to view compile messages, you can open another terminal and:
# tail -f /opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log

qtp-build-rpms v0.1.3
Building spamassassin-toaster-3.1.5-1.3.3 ...
qtp-build-rpms - rpmbuild failed for spamassassin-toaster-3.1.5-1.3.3
qtp-build-rpms - see
/opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log
Build failed, Exiting.
[EMAIL PROTECTED] qmailtoaster-plus]#
[EMAIL PROTECTED] qmailtoaster-plus]#  tail -f
/opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log
Building spamassassin-toaster-3.1.5-1.3.3 ...
error: Unable to open temp file.
Installing
/usr/src/qtp-upgrade/SRPMS/spamassassin-toaster-3.1.5-1.3.3.src.rpm
Building target platforms: i686
Building for target i686


RPM build errors:
   Unable to open temp file.




I can't recreate this error. In build-recent.log I get:
Building spamassassin-toaster-3.1.5-1.3.3 ...
Installing
/usr/src/qtp-upgrade/SRPMS/spamassassin-toaster-3.1.5-1.3.3.src.rpm
Building target platforms: i686
Building for target i686
Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.13427

I'm not sure what temp file you're bombing on. What does
# ls -ld /var/tmp
# ls -ld /opt/qtp-sandbox/var/tmp
show you? I have
drwxrwxrwt  2 root root 4096 Oct 15 11:12 /var/tmp
and
drwxr-xr-x  2 root root 4096 Oct 18 12:33 /opt/qtp-sandbox/var/tmp
respectively.

Please verify that you are running the current scripts:
qtp-build-rpms:myver=v0.1.3
qtp-build-sandbox:myver=v0.1.2
qtp-newmodel:myver=v0.1.10
qtp-whatami:myver=v0.1.1

If that all checks out, I'd try running again and letting it recreate the
sandbox.

Please let me know how you make out.
  
  

I have this output:
[EMAIL PROTECTED] qmailtoaster-plus]# ls -ld /var/tmp
lrwxrwxrwx  1 root root 8 Aug  5 23:32 /var/tmp -> /usr/tmp
[EMAIL PROTECTED] qmailtoaster-plus]# ls -ld /opt/qtp-sandbox/var/tmp
lrwxrwxrwx  1 root root 8 Oct 18 19:49 /opt/qtp-sandbox/var/tmp -> /usr/tmp

the files are

qtp-build-rpms:myver=v0.1.3
qtp-build-sandbox:myver=v0.1.2
qtp-newmodel:myver=v0.1.10
qtp-whatami:myver=v0.1.1


I tried 3-4 times using only linked because currently I don't have
enough space on this machine to make a copy.




That's why I made a linked option. ;)
None the less, the sandbox could use some trimming to get rid of some of the
bloat.

Anywise, I notice that your /var/tmp is a symlink to /usr/tmp:
lrwxrwxrwx  1 root root 8 Aug  5 23:32 /var/tmp -> /usr/tmp
and likewise in the sandbox, as the sandbox should be the same.

What does
# ls -ld /usr/tmp
show you?

What distro/version are you running? On CentOS4, I have /var/tmp being the
real directory with a /usr/tmp symlink pointing to it, FWIW.

I'm just searching here. Something's gotta be somehow different. Show me
# df -h
while we're at it.

  

here they are:

[EMAIL PROTECTED] qmailtoaster-plus]# ls -ld /usr/tmp
drwxr-xr-x  3 root root 4096 Oct 17 21:52 /usr/tmp


[EMAIL PROTECTED] qmailtoaster-plus]# df -h
FilesystemSize  Used Avail Use% Mounted on
/dev/sda2 7.8G  5.0G  2.6G  66% /
none  252M 0  252M   0% /dev/shm

I have another 2 partitions, but are not mounted because I don't need 
them for sandbox


Indeed I have /var/tmp is a symlink to /usr/tmp.. I'll switch the link 
(I don't remember how and why I changed them)


Distro will be always the latest CentOS.

Regards!

-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] errors during upgrading qt

[Eric \"Shubes\"]

Lucian Cristian wrote:
> Eric "Shubes" wrote:
>> Lucian Cristian wrote:
>>  
>>> I tried to do a linked sandbox and I got the following output:
>>>
>>> ..
>>> ..
>>> Starting to build the binary rpms ...(pizza anyone?)
>>>
>>> If you want to view compile messages, you can open another terminal and:
>>> # tail -f /opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log
>>>
>>> qtp-build-rpms v0.1.3
>>> Building spamassassin-toaster-3.1.5-1.3.3 ...
>>> qtp-build-rpms - rpmbuild failed for spamassassin-toaster-3.1.5-1.3.3
>>> qtp-build-rpms - see
>>> /opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log
>>> Build failed, Exiting.
>>> [EMAIL PROTECTED] qmailtoaster-plus]#
>>> [EMAIL PROTECTED] qmailtoaster-plus]#  tail -f
>>> /opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log
>>> Building spamassassin-toaster-3.1.5-1.3.3 ...
>>> error: Unable to open temp file.
>>> Installing
>>> /usr/src/qtp-upgrade/SRPMS/spamassassin-toaster-3.1.5-1.3.3.src.rpm
>>> Building target platforms: i686
>>> Building for target i686
>>>
>>>
>>> RPM build errors:
>>>Unable to open temp file.
>>>
>>> 
>>
>> I can't recreate this error. In build-recent.log I get:
>> Building spamassassin-toaster-3.1.5-1.3.3 ...
>> Installing
>> /usr/src/qtp-upgrade/SRPMS/spamassassin-toaster-3.1.5-1.3.3.src.rpm
>> Building target platforms: i686
>> Building for target i686
>> Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.13427
>>
>> I'm not sure what temp file you're bombing on. What does
>> # ls -ld /var/tmp
>> # ls -ld /opt/qtp-sandbox/var/tmp
>> show you? I have
>> drwxrwxrwt  2 root root 4096 Oct 15 11:12 /var/tmp
>> and
>> drwxr-xr-x  2 root root 4096 Oct 18 12:33 /opt/qtp-sandbox/var/tmp
>> respectively.
>>
>> Please verify that you are running the current scripts:
>> qtp-build-rpms:myver=v0.1.3
>> qtp-build-sandbox:myver=v0.1.2
>> qtp-newmodel:myver=v0.1.10
>> qtp-whatami:myver=v0.1.1
>>
>> If that all checks out, I'd try running again and letting it recreate the
>> sandbox.
>>
>> Please let me know how you make out.
>>   
> I have this output:
> [EMAIL PROTECTED] qmailtoaster-plus]# ls -ld /var/tmp
> lrwxrwxrwx  1 root root 8 Aug  5 23:32 /var/tmp -> /usr/tmp
> [EMAIL PROTECTED] qmailtoaster-plus]# ls -ld /opt/qtp-sandbox/var/tmp
> lrwxrwxrwx  1 root root 8 Oct 18 19:49 /opt/qtp-sandbox/var/tmp -> /usr/tmp
> 
> the files are
> 
> qtp-build-rpms:myver=v0.1.3
> qtp-build-sandbox:myver=v0.1.2
> qtp-newmodel:myver=v0.1.10
> qtp-whatami:myver=v0.1.1
> 
> 
> I tried 3-4 times using only linked because currently I don't have
> enough space on this machine to make a copy.
> 

That's why I made a linked option. ;)
None the less, the sandbox could use some trimming to get rid of some of the
bloat.

Anywise, I notice that your /var/tmp is a symlink to /usr/tmp:
lrwxrwxrwx  1 root root 8 Aug  5 23:32 /var/tmp -> /usr/tmp
and likewise in the sandbox, as the sandbox should be the same.

What does
# ls -ld /usr/tmp
show you?

What distro/version are you running? On CentOS4, I have /var/tmp being the
real directory with a /usr/tmp symlink pointing to it, FWIW.

I'm just searching here. Something's gotta be somehow different. Show me
# df -h
while we're at it.

-- 
-Eric 'shubes'

-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] errors during upgrading qt

[Lucian Cristian]

Eric "Shubes" wrote:

Lucian Cristian wrote:
  

Eric "Shubes" wrote:


Lucian Cristian wrote:
 
  

Eric "Shubes" wrote:
   


Lucian Cristian wrote:
 
 
  

Eric "Shubes" wrote:
  


Forget the new thread. I think I found the problem. It's in
qtp-build-sandbox (I broke something). I'll get it fixed and tested
right away.

Eric "Shubes" wrote:
 
  
  

I'm having this same problem now, and am tracking it down. At first
glance
it appears to be outside of the qtp- scripts.

I'll start a new thread for this one.

Lucian Cristian wrote:
 


Eric "Shubes" wrote:
   
  

Lucian Cristian wrote:
 
 


I've looked into the file and it-s saying that is
v0.1.1 who knows what's happening, i'll remove all
qtp-build-sandbox
files if there are others (I haven't check that yet)
from the server and download them again.
  
  

Please download them directly from svn.shubes.net or
qtp.shubes.net.
Do not
use the 0.1 qt-plus versions. This should all be ironed out with
the 0.2
release of qt-plus (in a few weeks).

 
 


so far this are my results
after  unmounting /var/named/chroot/proc
  
  

I wouldn't unmount /var/named/chroot/proc, especially on a live
server. It
should no longer be necessary.

 
 


Creating /opt/qtp-sandbox/var ...
Unexpected named pipe: /var/gdm/.gdmfifo
prw-rw  1 root root 0 Oct 18  2005 /var/gdm/.gdmfifo
Continuing ...
  
  

I added code that should handle this. I'm guessing that this was
still
v0.1

 
 


Creating /opt/qtp-sandbox/home/vpopmail ...
Creating /opt/qtp-sandbox/ misc directories ...
Sandbox has been built successfully!
  
  
 
 


Starting to build the binary rpms ...(pizza anyone?)

If you want to view compile messages, you can open another
terminal and:
# tail -f
/opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log

qtp-build-rpms 0.1.3
cat: /usr/src/qtp-upgrade: Is a directory
qtp-build-rpms Error - package list not found
Build failed, Exiting.

  
  

The order of parameters passed from qtp-newmodel to
qtp-build-rpms was
changed at some point. One of these scripts is apparently not
up to
date.

You should have:
qtp-newmodel v0.1.10
qtp-whatami v0.1.1
qtp-build-sandbox v0.1.1
qtp-build-rpms v0.1.3

  


here's my run for today ;)

bash-3.00# ./qtp-newmodel
qtp-newmodel v0.1.10 starting Thu Oct 12 21:31:24 EEST 2006
qtp-whatami v0.1.1
DISTRO=CentOS
OSVER=4.4
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 ...
Getting package list ...

qmail Toaster is an integrated distribution.
Packages are preconfigured for the whole distro.
As a result, a partial install might be misconfigured.
Upgrading all packages to their latest version is strongly
recommended.
Now that you've been warned, we will proceed with package
selection ...
..
..
Creating /opt/qtp-sandbox/var ...
Creating /opt/qtp-sandbox/home/vpopmail ...
Creating /opt/qtp-sandbox/ misc directories ...
cp: cannot copy a directory, `/opt/qtp-sandbox', into itself,
`/opt/qtp-sandbox/opt/./qtp-sandbox'
cp: cannot copy a directory, `/opt/qtp-sandbox', into itself,
`/opt/qtp-sandbox/opt/./qtp-sandbox'
Sandbox has been built successfully!

Starting to build the binary rpms ...(pizza anyone?)

If you want to view compile messages, you can open another terminal
and:
# tail -f /opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log

qtp-build-rpms v0.1.3
REMOVED spamassassin-toaster from sandbox (not for real)
Building vpopmail-toaster-5.4.13-1.3.2 ...
qtp-build-rpms - rpmbuild failed for vpopmail-toaster-5.4.13-1.3.2
qtp-build-rpms - see
/opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log
Build failed, Exiting.
bash-3.00#
bash-3.00# tail -f
/opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for gawk... (cached) gawk
checking for gcc... gcc
checking for C compiler default output... configure: error: C
compiler
cannot create executables
error: Bad exit status from /var/tmp/rpm-tmp.32546 (%build)


RPM build errors:
   Bad exit status fro

Re: [qmailtoaster] errors during upgrading qt

[Eric \"Shubes\"]

Lucian Cristian wrote:
> Eric "Shubes" wrote:
>> Lucian Cristian wrote:
>>  
>>> Eric "Shubes" wrote:
>>>
 Lucian Cristian wrote:
  
  
> Eric "Shubes" wrote:
>   
>> Forget the new thread. I think I found the problem. It's in
>> qtp-build-sandbox (I broke something). I'll get it fixed and tested
>> right away.
>>
>> Eric "Shubes" wrote:
>>  
>>   
>>> I'm having this same problem now, and am tracking it down. At first
>>> glance
>>> it appears to be outside of the qtp- scripts.
>>>
>>> I'll start a new thread for this one.
>>>
>>> Lucian Cristian wrote:
>>>  
 Eric "Shubes" wrote:

> Lucian Cristian wrote:
>  
>  
>> I've looked into the file and it-s saying that is
>> v0.1.1 who knows what's happening, i'll remove all
>> qtp-build-sandbox
>> files if there are others (I haven't check that yet)
>> from the server and download them again.
>>   
> Please download them directly from svn.shubes.net or
> qtp.shubes.net.
> Do not
> use the 0.1 qt-plus versions. This should all be ironed out with
> the 0.2
> release of qt-plus (in a few weeks).
>
>  
>  
>> so far this are my results
>> after  unmounting /var/named/chroot/proc
>>   
> I wouldn't unmount /var/named/chroot/proc, especially on a live
> server. It
> should no longer be necessary.
>
>  
>  
>> Creating /opt/qtp-sandbox/var ...
>> Unexpected named pipe: /var/gdm/.gdmfifo
>> prw-rw  1 root root 0 Oct 18  2005 /var/gdm/.gdmfifo
>> Continuing ...
>>   
> I added code that should handle this. I'm guessing that this was
> still
> v0.1
>
>  
>  
>> Creating /opt/qtp-sandbox/home/vpopmail ...
>> Creating /opt/qtp-sandbox/ misc directories ...
>> Sandbox has been built successfully!
>>   
>  
>  
>> Starting to build the binary rpms ...(pizza anyone?)
>>
>> If you want to view compile messages, you can open another
>> terminal and:
>> # tail -f
>> /opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log
>>
>> qtp-build-rpms 0.1.3
>> cat: /usr/src/qtp-upgrade: Is a directory
>> qtp-build-rpms Error - package list not found
>> Build failed, Exiting.
>>
>>   
> The order of parameters passed from qtp-newmodel to
> qtp-build-rpms was
> changed at some point. One of these scripts is apparently not
> up to
> date.
>
> You should have:
> qtp-newmodel v0.1.10
> qtp-whatami v0.1.1
> qtp-build-sandbox v0.1.1
> qtp-build-rpms v0.1.3
>
>   
 here's my run for today ;)

 bash-3.00# ./qtp-newmodel
 qtp-newmodel v0.1.10 starting Thu Oct 12 21:31:24 EEST 2006
 qtp-whatami v0.1.1
 DISTRO=CentOS
 OSVER=4.4
 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 ...
 Getting package list ...

 qmail Toaster is an integrated distribution.
 Packages are preconfigured for the whole distro.
 As a result, a partial install might be misconfigured.
 Upgrading all packages to their latest version is strongly
 recommended.
 Now that you've been warned, we will proceed with package
 selection ...
 ..
 ..
 Creating /opt/qtp-sandbox/var ...
 Creating /opt/qtp-sandbox/home/vpopmail ...
 Creating /opt/qtp-sandbox/ misc directories ...
 cp: cannot copy a directory, `/opt/qtp-sandbox', into itself,
 `/opt/qtp-sandbox/opt/./qtp-sandbox'
 cp: cannot copy a directory, `/opt/qtp-sandbox', into itself,
 `/opt/qtp-sandbox/opt/./qtp-sandbox'
 Sandbox has been built successfully!

 Starting to build the binary rpms ...(pizza anyone?)

 If you want to view comp

Re: [qmailtoaster] errors during upgrading qt

[Lucian Cristian]

Eric "Shubes" wrote:

Lucian Cristian wrote:
  

Eric "Shubes" wrote:


Lucian Cristian wrote:
 
  

Eric "Shubes" wrote:
   


Forget the new thread. I think I found the problem. It's in
qtp-build-sandbox (I broke something). I'll get it fixed and tested
right away.

Eric "Shubes" wrote:
 
 
  

I'm having this same problem now, and am tracking it down. At first
glance
it appears to be outside of the qtp- scripts.

I'll start a new thread for this one.

Lucian Cristian wrote:
  


Eric "Shubes" wrote:
  
  

Lucian Cristian wrote:
 
  


I've looked into the file and it-s saying that is
v0.1.1 who knows what's happening, i'll remove all 
qtp-build-sandbox

files if there are others (I haven't check that yet)
from the server and download them again.

  

Please download them directly from svn.shubes.net or qtp.shubes.net.
Do not
use the 0.1 qt-plus versions. This should all be ironed out with
the 0.2
release of qt-plus (in a few weeks).

 
  


so far this are my results
after  unmounting /var/named/chroot/proc

  

I wouldn't unmount /var/named/chroot/proc, especially on a live
server. It
should no longer be necessary.

 
  


Creating /opt/qtp-sandbox/var ...
Unexpected named pipe: /var/gdm/.gdmfifo
prw-rw  1 root root 0 Oct 18  2005 /var/gdm/.gdmfifo
Continuing ...

  

I added code that should handle this. I'm guessing that this was
still
v0.1

 
  


Creating /opt/qtp-sandbox/home/vpopmail ...
Creating /opt/qtp-sandbox/ misc directories ...
Sandbox has been built successfully!

  
 
  


Starting to build the binary rpms ...(pizza anyone?)

If you want to view compile messages, you can open another
terminal and:
# tail -f /opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log

qtp-build-rpms 0.1.3
cat: /usr/src/qtp-upgrade: Is a directory
qtp-build-rpms Error - package list not found
Build failed, Exiting.


  

The order of parameters passed from qtp-newmodel to
qtp-build-rpms was
changed at some point. One of these scripts is apparently not up to
date.

You should have:
qtp-newmodel v0.1.10
qtp-whatami v0.1.1
qtp-build-sandbox v0.1.1
qtp-build-rpms v0.1.3

  


here's my run for today ;)

bash-3.00# ./qtp-newmodel
qtp-newmodel v0.1.10 starting Thu Oct 12 21:31:24 EEST 2006
qtp-whatami v0.1.1
DISTRO=CentOS
OSVER=4.4
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 ...
Getting package list ...

qmail Toaster is an integrated distribution.
Packages are preconfigured for the whole distro.
As a result, a partial install might be misconfigured.
Upgrading all packages to their latest version is strongly
recommended.
Now that you've been warned, we will proceed with package
selection ...
..
..
Creating /opt/qtp-sandbox/var ...
Creating /opt/qtp-sandbox/home/vpopmail ...
Creating /opt/qtp-sandbox/ misc directories ...
cp: cannot copy a directory, `/opt/qtp-sandbox', into itself,
`/opt/qtp-sandbox/opt/./qtp-sandbox'
cp: cannot copy a directory, `/opt/qtp-sandbox', into itself,
`/opt/qtp-sandbox/opt/./qtp-sandbox'
Sandbox has been built successfully!

Starting to build the binary rpms ...(pizza anyone?)

If you want to view compile messages, you can open another terminal
and:
# tail -f /opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log

qtp-build-rpms v0.1.3
REMOVED spamassassin-toaster from sandbox (not for real)
Building vpopmail-toaster-5.4.13-1.3.2 ...
qtp-build-rpms - rpmbuild failed for vpopmail-toaster-5.4.13-1.3.2
qtp-build-rpms - see
/opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log
Build failed, Exiting.
bash-3.00#
bash-3.00# tail -f
/opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for gawk... (cached) gawk
checking for gcc... gcc
checking for C compiler default output... configure: error: C
compiler
cannot create executables
error: Bad exit status from /var/tmp/rpm-tmp.32546 (%build)


RPM build errors:
   Bad exit status from /var/tmp/rpm-tmp.32546 (%build)

bash-3.00#


I don't remember if there are some steps to do before running
qtp-newmodel, maybe I'm not doing the right way, i'll try on another
machine, but I have to work and go to school too ..  I'll try the
moment
I'll have free time

-
QmailToast

Re: [qmailtoaster] errors during upgrading qt

[Eric \"Shubes\"]

crispin,

You have two different problems going on here. Downloading all current qtp-*
scripts from qtp.shubes.net (or svn.shubes.net) will fix them. Just be sure
to put them all in the same directory, and cd to that directory before
running ./qtp-newmodel.

Note, this will not be an issue when qt-plus v0.2 is released in a few
weeks. At that time, you will be able to run any qtp-* script from anywhere.

[EMAIL PROTECTED] wrote:
> I downloaded the new scripts placed them on a different path. when I
> executed the newmodel scripts, it first removed the existing sand box but
> did not download the SRPM files since were already there.

That is 'normal' behavior. The script gives you the option of recreating the
sandbox or not. You should recreate the sandbox after downloading the fixed
scripts. Normally (when things are working), you shouldn't need to recreate
the sandbox.

Deleting the sandbox does not delete *.src.rpm files that have already been
downloaded, as there should be no need. If you want to remove them though (I
can't think of why you would want to do this), they're found in
/usr/src/qtp-upgrade/SRPMS.

> 
> Can I remove the sandbox manually?

Certainly. Simply
# rm -rf /opt/qtp-sandbox
or whatever directory you chose to name it. Be *extremely careful* with this
command!

Note,  you can also build the sandbox manually:
# qtp-build-sandbox /opt/qtp-sandbox
If you issue this command and the sandbox still exists, it will remind you
to issue the above command first. ;)

> crispin

-- 
-Eric 'shubes'

-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] errors during upgrading qt

[ldap]

I downloaded the new scripts placed them on a different path. when I
executed the newmodel scripts, it first removed the existing sand box but
did not download the SRPM files since were already there.

Can I remove the sandbox manually?

crispin
>>> The order of parameters passed from qtp-newmodel to qtp-build-rpms was
>>> changed at some point. One of these scripts is apparently not up to
>>> date.
>>>
>>> You should have:
>>> qtp-newmodel v0.1.10
>>> qtp-whatami v0.1.1
>>> qtp-build-sandbox v0.1.1
>>> qtp-build-rpms v0.1.3
>>>
>>> --
>>> -Eric 'shubes'
>>
>> I am still getting the same errors as you can see below. I downloaded
>> ver
>> 1.2 as you instructed.
>>
>> Creating /opt/qtp-sandbox/home/vpopmail ...
>> Creating /opt/qtp-sandbox/ misc directories ...
>> Sandbox has been built successfully!
>>
>> Starting to build the binary rpms ...(pizza anyone?)
>>
>> If you want to view compile messages, you can open another terminal and:
>> # tail -f /opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log
>>
>> qtp-build-rpms 0.1.3
>> cat: /usr/src/qtp-upgrade: Is a directory
>> qtp-build-rpms Error - package list not found
>> Build failed, Exiting.
>> [EMAIL PROTECTED] upgrading]#
>>
>>
>>
>> -
>>  QmailToaster hosted by: VR Hosted 
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
> For me is working ! execute an locate -u then search for duplicate files
> on server, it may be posibile that another qtp-sandbox is in your path
> files
>
>
>
>
> -
>  QmailToaster hosted by: VR Hosted 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>



-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] errors during upgrading qt

[Lucian Cristian]

>> The order of parameters passed from qtp-newmodel to qtp-build-rpms was
>> changed at some point. One of these scripts is apparently not up to
>> date.
>>
>> You should have:
>> qtp-newmodel v0.1.10
>> qtp-whatami v0.1.1
>> qtp-build-sandbox v0.1.1
>> qtp-build-rpms v0.1.3
>>
>> --
>> -Eric 'shubes'
>
> I am still getting the same errors as you can see below. I downloaded ver
> 1.2 as you instructed.
>
> Creating /opt/qtp-sandbox/home/vpopmail ...
> Creating /opt/qtp-sandbox/ misc directories ...
> Sandbox has been built successfully!
>
> Starting to build the binary rpms ...(pizza anyone?)
>
> If you want to view compile messages, you can open another terminal and:
> # tail -f /opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log
>
> qtp-build-rpms 0.1.3
> cat: /usr/src/qtp-upgrade: Is a directory
> qtp-build-rpms Error - package list not found
> Build failed, Exiting.
> [EMAIL PROTECTED] upgrading]#
>
>
>
> -
>  QmailToaster hosted by: VR Hosted 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

For me is working ! execute an locate -u then search for duplicate files
on server, it may be posibile that another qtp-sandbox is in your path
files




-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] errors during upgrading qt

[ldap]

> The order of parameters passed from qtp-newmodel to qtp-build-rpms was
> changed at some point. One of these scripts is apparently not up to date.
>
> You should have:
> qtp-newmodel v0.1.10
> qtp-whatami v0.1.1
> qtp-build-sandbox v0.1.1
> qtp-build-rpms v0.1.3
>
> --
> -Eric 'shubes'

I am still getting the same errors as you can see below. I downloaded ver
1.2 as you instructed.

Creating /opt/qtp-sandbox/home/vpopmail ...
Creating /opt/qtp-sandbox/ misc directories ...
Sandbox has been built successfully!

Starting to build the binary rpms ...(pizza anyone?)

If you want to view compile messages, you can open another terminal and:
# tail -f /opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log

qtp-build-rpms 0.1.3
cat: /usr/src/qtp-upgrade: Is a directory
qtp-build-rpms Error - package list not found
Build failed, Exiting.
[EMAIL PROTECTED] upgrading]#



-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] errors during upgrading qt

[Eric \"Shubes\"]

Lucian Cristian wrote:
> Eric "Shubes" wrote:
>> Lucian Cristian wrote:
>>  
>>> Eric "Shubes" wrote:
>>>
 Forget the new thread. I think I found the problem. It's in
 qtp-build-sandbox (I broke something). I'll get it fixed and tested
 right away.

 Eric "Shubes" wrote:
  
  
> I'm having this same problem now, and am tracking it down. At first
> glance
> it appears to be outside of the qtp- scripts.
>
> I'll start a new thread for this one.
>
> Lucian Cristian wrote:
>   
>> Eric "Shubes" wrote:
>>   
>>> Lucian Cristian wrote:
>>>  
>>>   
 I've looked into the file and it-s saying that is
 v0.1.1 who knows what's happening, i'll remove all 
 qtp-build-sandbox
 files if there are others (I haven't check that yet)
 from the server and download them again.
 
>>> Please download them directly from svn.shubes.net or qtp.shubes.net.
>>> Do not
>>> use the 0.1 qt-plus versions. This should all be ironed out with
>>> the 0.2
>>> release of qt-plus (in a few weeks).
>>>
>>>  
>>>   
 so far this are my results
 after  unmounting /var/named/chroot/proc
 
>>> I wouldn't unmount /var/named/chroot/proc, especially on a live
>>> server. It
>>> should no longer be necessary.
>>>
>>>  
>>>   
 Creating /opt/qtp-sandbox/var ...
 Unexpected named pipe: /var/gdm/.gdmfifo
 prw-rw  1 root root 0 Oct 18  2005 /var/gdm/.gdmfifo
 Continuing ...
 
>>> I added code that should handle this. I'm guessing that this was
>>> still
>>> v0.1
>>>
>>>  
>>>   
 Creating /opt/qtp-sandbox/home/vpopmail ...
 Creating /opt/qtp-sandbox/ misc directories ...
 Sandbox has been built successfully!
 
>>>  
>>>   
 Starting to build the binary rpms ...(pizza anyone?)

 If you want to view compile messages, you can open another
 terminal and:
 # tail -f /opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log

 qtp-build-rpms 0.1.3
 cat: /usr/src/qtp-upgrade: Is a directory
 qtp-build-rpms Error - package list not found
 Build failed, Exiting.

 
>>> The order of parameters passed from qtp-newmodel to
>>> qtp-build-rpms was
>>> changed at some point. One of these scripts is apparently not up to
>>> date.
>>>
>>> You should have:
>>> qtp-newmodel v0.1.10
>>> qtp-whatami v0.1.1
>>> qtp-build-sandbox v0.1.1
>>> qtp-build-rpms v0.1.3
>>>
>>>   
>> here's my run for today ;)
>>
>> bash-3.00# ./qtp-newmodel
>> qtp-newmodel v0.1.10 starting Thu Oct 12 21:31:24 EEST 2006
>> qtp-whatami v0.1.1
>> DISTRO=CentOS
>> OSVER=4.4
>> 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 ...
>> Getting package list ...
>>
>> qmail Toaster is an integrated distribution.
>> Packages are preconfigured for the whole distro.
>> As a result, a partial install might be misconfigured.
>> Upgrading all packages to their latest version is strongly
>> recommended.
>> Now that you've been warned, we will proceed with package
>> selection ...
>> ..
>> ..
>> Creating /opt/qtp-sandbox/var ...
>> Creating /opt/qtp-sandbox/home/vpopmail ...
>> Creating /opt/qtp-sandbox/ misc directories ...
>> cp: cannot copy a directory, `/opt/qtp-sandbox', into itself,
>> `/opt/qtp-sandbox/opt/./qtp-sandbox'
>> cp: cannot copy a directory, `/opt/qtp-sandbox', into itself,
>> `/opt/qtp-sandbox/opt/./qtp-sandbox'
>> Sandbox has been built successfully!
>>
>> Starting to build the binary rpms ...(pizza anyone?)
>>
>> If you want to view compile messages, you can open another terminal
>> and:
>> # tail -f /opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log
>>
>> qtp-build-rpms v0.1.3
>> REMOVED spamassassin-toaster from sandbox (not for real)
>> Building vpopmail-toaster-5.4.13-1.3.2 ...
>> qtp-build-rpms - rpmbuild failed for vpopmail-toaster-5.4.13-1.3.2
>> qtp-build-rpms - see
>> /opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log
>> Build failed, Exiting.
>> bash-3.00#
>> bash-3.00# tail -f
>> /opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-re

Re: [qmailtoaster] errors during upgrading qt

[Lucian Cristian]

Eric "Shubes" wrote:

Lucian Cristian wrote:
  

Eric "Shubes" wrote:


Forget the new thread. I think I found the problem. It's in
qtp-build-sandbox (I broke something). I'll get it fixed and tested
right away.

Eric "Shubes" wrote:
 
  

I'm having this same problem now, and am tracking it down. At first
glance
it appears to be outside of the qtp- scripts.

I'll start a new thread for this one.

Lucian Cristian wrote:
   


Eric "Shubes" wrote:
 
  

Lucian Cristian wrote:
 
   


I've looked into the file and it-s saying that is
v0.1.1 who knows what's happening, i'll remove all  qtp-build-sandbox
files if there are others (I haven't check that yet)
from the server and download them again.
  
  

Please download them directly from svn.shubes.net or qtp.shubes.net.
Do not
use the 0.1 qt-plus versions. This should all be ironed out with
the 0.2
release of qt-plus (in a few weeks).

 
   


so far this are my results
after  unmounting /var/named/chroot/proc
  
  

I wouldn't unmount /var/named/chroot/proc, especially on a live
server. It
should no longer be necessary.

 
   


Creating /opt/qtp-sandbox/var ...
Unexpected named pipe: /var/gdm/.gdmfifo
prw-rw  1 root root 0 Oct 18  2005 /var/gdm/.gdmfifo
Continuing ...
  
  

I added code that should handle this. I'm guessing that this was still
v0.1

 
   


Creating /opt/qtp-sandbox/home/vpopmail ...
Creating /opt/qtp-sandbox/ misc directories ...
Sandbox has been built successfully!
  
  
 
   


Starting to build the binary rpms ...(pizza anyone?)

If you want to view compile messages, you can open another
terminal and:
# tail -f /opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log

qtp-build-rpms 0.1.3
cat: /usr/src/qtp-upgrade: Is a directory
qtp-build-rpms Error - package list not found
Build failed, Exiting.

  
  

The order of parameters passed from qtp-newmodel to qtp-build-rpms was
changed at some point. One of these scripts is apparently not up to
date.

You should have:
qtp-newmodel v0.1.10
qtp-whatami v0.1.1
qtp-build-sandbox v0.1.1
qtp-build-rpms v0.1.3

  


here's my run for today ;)

bash-3.00# ./qtp-newmodel
qtp-newmodel v0.1.10 starting Thu Oct 12 21:31:24 EEST 2006
qtp-whatami v0.1.1
DISTRO=CentOS
OSVER=4.4
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 ...
Getting package list ...

qmail Toaster is an integrated distribution.
Packages are preconfigured for the whole distro.
As a result, a partial install might be misconfigured.
Upgrading all packages to their latest version is strongly recommended.
Now that you've been warned, we will proceed with package selection ...
..
..
Creating /opt/qtp-sandbox/var ...
Creating /opt/qtp-sandbox/home/vpopmail ...
Creating /opt/qtp-sandbox/ misc directories ...
cp: cannot copy a directory, `/opt/qtp-sandbox', into itself,
`/opt/qtp-sandbox/opt/./qtp-sandbox'
cp: cannot copy a directory, `/opt/qtp-sandbox', into itself,
`/opt/qtp-sandbox/opt/./qtp-sandbox'
Sandbox has been built successfully!

Starting to build the binary rpms ...(pizza anyone?)

If you want to view compile messages, you can open another terminal
and:
# tail -f /opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log

qtp-build-rpms v0.1.3
REMOVED spamassassin-toaster from sandbox (not for real)
Building vpopmail-toaster-5.4.13-1.3.2 ...
qtp-build-rpms - rpmbuild failed for vpopmail-toaster-5.4.13-1.3.2
qtp-build-rpms - see
/opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log
Build failed, Exiting.
bash-3.00#
bash-3.00# tail -f
/opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for gawk... (cached) gawk
checking for gcc... gcc
checking for C compiler default output... configure: error: C compiler
cannot create executables
error: Bad exit status from /var/tmp/rpm-tmp.32546 (%build)


RPM build errors:
   Bad exit status from /var/tmp/rpm-tmp.32546 (%build)

bash-3.00#


I don't remember if there are some steps to do before running
qtp-newmodel, maybe I'm not doing the right way, i'll try on another
machine, but I have to work and go to school too ..  I'll try the
moment
I'll have free time

-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail:
[EMAIL PROTECTED]


  
  


  
  

I'm kind of tired, are you think

Re: [qmailtoaster] errors during upgrading qt

[Eric \"Shubes\"]

Lucian Cristian wrote:
> Eric "Shubes" wrote:
>> Forget the new thread. I think I found the problem. It's in
>> qtp-build-sandbox (I broke something). I'll get it fixed and tested
>> right away.
>>
>> Eric "Shubes" wrote:
>>  
>>> I'm having this same problem now, and am tracking it down. At first
>>> glance
>>> it appears to be outside of the qtp- scripts.
>>>
>>> I'll start a new thread for this one.
>>>
>>> Lucian Cristian wrote:
>>>
 Eric "Shubes" wrote:
  
> Lucian Cristian wrote:
>  
>
>> I've looked into the file and it-s saying that is
>> v0.1.1 who knows what's happening, i'll remove all  qtp-build-sandbox
>> files if there are others (I haven't check that yet)
>> from the server and download them again.
>>   
> Please download them directly from svn.shubes.net or qtp.shubes.net.
> Do not
> use the 0.1 qt-plus versions. This should all be ironed out with
> the 0.2
> release of qt-plus (in a few weeks).
>
>  
>
>> so far this are my results
>> after  unmounting /var/named/chroot/proc
>>   
> I wouldn't unmount /var/named/chroot/proc, especially on a live
> server. It
> should no longer be necessary.
>
>  
>
>> Creating /opt/qtp-sandbox/var ...
>> Unexpected named pipe: /var/gdm/.gdmfifo
>> prw-rw  1 root root 0 Oct 18  2005 /var/gdm/.gdmfifo
>> Continuing ...
>>   
> I added code that should handle this. I'm guessing that this was still
> v0.1
>
>  
>
>> Creating /opt/qtp-sandbox/home/vpopmail ...
>> Creating /opt/qtp-sandbox/ misc directories ...
>> Sandbox has been built successfully!
>>   
>  
>
>> Starting to build the binary rpms ...(pizza anyone?)
>>
>> If you want to view compile messages, you can open another
>> terminal and:
>> # tail -f /opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log
>>
>> qtp-build-rpms 0.1.3
>> cat: /usr/src/qtp-upgrade: Is a directory
>> qtp-build-rpms Error - package list not found
>> Build failed, Exiting.
>>
>>   
> The order of parameters passed from qtp-newmodel to qtp-build-rpms was
> changed at some point. One of these scripts is apparently not up to
> date.
>
> You should have:
> qtp-newmodel v0.1.10
> qtp-whatami v0.1.1
> qtp-build-sandbox v0.1.1
> qtp-build-rpms v0.1.3
>
>   
 here's my run for today ;)

 bash-3.00# ./qtp-newmodel
 qtp-newmodel v0.1.10 starting Thu Oct 12 21:31:24 EEST 2006
 qtp-whatami v0.1.1
 DISTRO=CentOS
 OSVER=4.4
 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 ...
 Getting package list ...

 qmail Toaster is an integrated distribution.
 Packages are preconfigured for the whole distro.
 As a result, a partial install might be misconfigured.
 Upgrading all packages to their latest version is strongly recommended.
 Now that you've been warned, we will proceed with package selection ...
 ..
 ..
 Creating /opt/qtp-sandbox/var ...
 Creating /opt/qtp-sandbox/home/vpopmail ...
 Creating /opt/qtp-sandbox/ misc directories ...
 cp: cannot copy a directory, `/opt/qtp-sandbox', into itself,
 `/opt/qtp-sandbox/opt/./qtp-sandbox'
 cp: cannot copy a directory, `/opt/qtp-sandbox', into itself,
 `/opt/qtp-sandbox/opt/./qtp-sandbox'
 Sandbox has been built successfully!

 Starting to build the binary rpms ...(pizza anyone?)

 If you want to view compile messages, you can open another terminal
 and:
 # tail -f /opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log

 qtp-build-rpms v0.1.3
 REMOVED spamassassin-toaster from sandbox (not for real)
 Building vpopmail-toaster-5.4.13-1.3.2 ...
 qtp-build-rpms - rpmbuild failed for vpopmail-toaster-5.4.13-1.3.2
 qtp-build-rpms - see
 /opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log
 Build failed, Exiting.
 bash-3.00#
 bash-3.00# tail -f
 /opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log
 checking build system type... i686-pc-linux-gnu
 checking host system type... i686-pc-linux-gnu
 checking for gawk... (cached) gawk
 checking for gcc... gcc
 checking for C compiler default output... configure: error: C compiler
 cannot create executables
 error: Bad exit status from /var/tmp/rpm-tmp.32546 (%build)


 RPM build errors:
Bad exit status from /var/tmp/rpm-tmp.32546 (%build)

 bash-3.00#


 I don't remember if there are some steps

Re: [qmailtoaster] errors during upgrading qt

[Lucian Cristian]

Eric "Shubes" wrote:

Forget the new thread. I think I found the problem. It's in
qtp-build-sandbox (I broke something). I'll get it fixed and tested right away.

Eric "Shubes" wrote:
  

I'm having this same problem now, and am tracking it down. At first glance
it appears to be outside of the qtp- scripts.

I'll start a new thread for this one.

Lucian Cristian wrote:


Eric "Shubes" wrote:
  

Lucian Cristian wrote:
 


I've looked into the file and it-s saying that is
v0.1.1 who knows what's happening, i'll remove all  qtp-build-sandbox
files if there are others (I haven't check that yet)
from the server and download them again.

  

Please download them directly from svn.shubes.net or qtp.shubes.net.
Do not
use the 0.1 qt-plus versions. This should all be ironed out with the 0.2
release of qt-plus (in a few weeks).

 


so far this are my results
after  unmounting /var/named/chroot/proc

  

I wouldn't unmount /var/named/chroot/proc, especially on a live
server. It
should no longer be necessary.

 


Creating /opt/qtp-sandbox/var ...
Unexpected named pipe: /var/gdm/.gdmfifo
prw-rw  1 root root 0 Oct 18  2005 /var/gdm/.gdmfifo
Continuing ...

  

I added code that should handle this. I'm guessing that this was still
v0.1

 


Creating /opt/qtp-sandbox/home/vpopmail ...
Creating /opt/qtp-sandbox/ misc directories ...
Sandbox has been built successfully!

  
 


Starting to build the binary rpms ...(pizza anyone?)

If you want to view compile messages, you can open another terminal and:
# tail -f /opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log

qtp-build-rpms 0.1.3
cat: /usr/src/qtp-upgrade: Is a directory
qtp-build-rpms Error - package list not found
Build failed, Exiting.


  

The order of parameters passed from qtp-newmodel to qtp-build-rpms was
changed at some point. One of these scripts is apparently not up to date.

You should have:
qtp-newmodel v0.1.10
qtp-whatami v0.1.1
qtp-build-sandbox v0.1.1
qtp-build-rpms v0.1.3

  


here's my run for today ;)

bash-3.00# ./qtp-newmodel
qtp-newmodel v0.1.10 starting Thu Oct 12 21:31:24 EEST 2006
qtp-whatami v0.1.1
DISTRO=CentOS
OSVER=4.4
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 ...
Getting package list ...

qmail Toaster is an integrated distribution.
Packages are preconfigured for the whole distro.
As a result, a partial install might be misconfigured.
Upgrading all packages to their latest version is strongly recommended.
Now that you've been warned, we will proceed with package selection ...
..
..
Creating /opt/qtp-sandbox/var ...
Creating /opt/qtp-sandbox/home/vpopmail ...
Creating /opt/qtp-sandbox/ misc directories ...
cp: cannot copy a directory, `/opt/qtp-sandbox', into itself,
`/opt/qtp-sandbox/opt/./qtp-sandbox'
cp: cannot copy a directory, `/opt/qtp-sandbox', into itself,
`/opt/qtp-sandbox/opt/./qtp-sandbox'
Sandbox has been built successfully!

Starting to build the binary rpms ...(pizza anyone?)

If you want to view compile messages, you can open another terminal and:
# tail -f /opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log

qtp-build-rpms v0.1.3
REMOVED spamassassin-toaster from sandbox (not for real)
Building vpopmail-toaster-5.4.13-1.3.2 ...
qtp-build-rpms - rpmbuild failed for vpopmail-toaster-5.4.13-1.3.2
qtp-build-rpms - see
/opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log
Build failed, Exiting.
bash-3.00#
bash-3.00# tail -f
/opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for gawk... (cached) gawk
checking for gcc... gcc
checking for C compiler default output... configure: error: C compiler
cannot create executables
error: Bad exit status from /var/tmp/rpm-tmp.32546 (%build)


RPM build errors:
   Bad exit status from /var/tmp/rpm-tmp.32546 (%build)

bash-3.00#


I don't remember if there are some steps to do before running
qtp-newmodel, maybe I'm not doing the right way, i'll try on another
machine, but I have to work and go to school too ..  I'll try the moment
I'll have free time

-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


  




  
I'm kind of tired, are you thinking like a quick fix ? should I wait an 
hour to put it to test ? :D


-
QmailToaster hosted by: VR Hosted 
--

Re: [qmailtoaster] errors during upgrading qt

[Eric \"Shubes\"]

Forget the new thread. I think I found the problem. It's in
qtp-build-sandbox (I broke something). I'll get it fixed and tested right away.

Eric "Shubes" wrote:
> I'm having this same problem now, and am tracking it down. At first glance
> it appears to be outside of the qtp- scripts.
> 
> I'll start a new thread for this one.
> 
> Lucian Cristian wrote:
>> Eric "Shubes" wrote:
>>> Lucian Cristian wrote:
>>>  
 I've looked into the file and it-s saying that is
 v0.1.1 who knows what's happening, i'll remove all  qtp-build-sandbox
 files if there are others (I haven't check that yet)
 from the server and download them again.
 
>>> Please download them directly from svn.shubes.net or qtp.shubes.net.
>>> Do not
>>> use the 0.1 qt-plus versions. This should all be ironed out with the 0.2
>>> release of qt-plus (in a few weeks).
>>>
>>>  
 so far this are my results
 after  unmounting /var/named/chroot/proc
 
>>> I wouldn't unmount /var/named/chroot/proc, especially on a live
>>> server. It
>>> should no longer be necessary.
>>>
>>>  
 Creating /opt/qtp-sandbox/var ...
 Unexpected named pipe: /var/gdm/.gdmfifo
 prw-rw  1 root root 0 Oct 18  2005 /var/gdm/.gdmfifo
 Continuing ...
 
>>> I added code that should handle this. I'm guessing that this was still
>>> v0.1
>>>
>>>  
 Creating /opt/qtp-sandbox/home/vpopmail ...
 Creating /opt/qtp-sandbox/ misc directories ...
 Sandbox has been built successfully!
 
>>>  
 Starting to build the binary rpms ...(pizza anyone?)

 If you want to view compile messages, you can open another terminal and:
 # tail -f /opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log

 qtp-build-rpms 0.1.3
 cat: /usr/src/qtp-upgrade: Is a directory
 qtp-build-rpms Error - package list not found
 Build failed, Exiting.

 
>>> The order of parameters passed from qtp-newmodel to qtp-build-rpms was
>>> changed at some point. One of these scripts is apparently not up to date.
>>>
>>> You should have:
>>> qtp-newmodel v0.1.10
>>> qtp-whatami v0.1.1
>>> qtp-build-sandbox v0.1.1
>>> qtp-build-rpms v0.1.3
>>>
>>>   
>> here's my run for today ;)
>>
>> bash-3.00# ./qtp-newmodel
>> qtp-newmodel v0.1.10 starting Thu Oct 12 21:31:24 EEST 2006
>> qtp-whatami v0.1.1
>> DISTRO=CentOS
>> OSVER=4.4
>> 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 ...
>> Getting package list ...
>>
>> qmail Toaster is an integrated distribution.
>> Packages are preconfigured for the whole distro.
>> As a result, a partial install might be misconfigured.
>> Upgrading all packages to their latest version is strongly recommended.
>> Now that you've been warned, we will proceed with package selection ...
>> ..
>> ..
>> Creating /opt/qtp-sandbox/var ...
>> Creating /opt/qtp-sandbox/home/vpopmail ...
>> Creating /opt/qtp-sandbox/ misc directories ...
>> cp: cannot copy a directory, `/opt/qtp-sandbox', into itself,
>> `/opt/qtp-sandbox/opt/./qtp-sandbox'
>> cp: cannot copy a directory, `/opt/qtp-sandbox', into itself,
>> `/opt/qtp-sandbox/opt/./qtp-sandbox'
>> Sandbox has been built successfully!
>>
>> Starting to build the binary rpms ...(pizza anyone?)
>>
>> If you want to view compile messages, you can open another terminal and:
>> # tail -f /opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log
>>
>> qtp-build-rpms v0.1.3
>> REMOVED spamassassin-toaster from sandbox (not for real)
>> Building vpopmail-toaster-5.4.13-1.3.2 ...
>> qtp-build-rpms - rpmbuild failed for vpopmail-toaster-5.4.13-1.3.2
>> qtp-build-rpms - see
>> /opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log
>> Build failed, Exiting.
>> bash-3.00#
>> bash-3.00# tail -f
>> /opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log
>> checking build system type... i686-pc-linux-gnu
>> checking host system type... i686-pc-linux-gnu
>> checking for gawk... (cached) gawk
>> checking for gcc... gcc
>> checking for C compiler default output... configure: error: C compiler
>> cannot create executables
>> error: Bad exit status from /var/tmp/rpm-tmp.32546 (%build)
>>
>>
>> RPM build errors:
>>Bad exit status from /var/tmp/rpm-tmp.32546 (%build)
>>
>> bash-3.00#
>>
>>
>> I don't remember if there are some steps to do before running
>> qtp-newmodel, maybe I'm not doing the right way, i'll try on another
>> machine, but I have to work and go to school too ..  I'll try the moment
>> I'll have free time
>>
>> -
>> QmailToaster hosted by: VR Hosted 
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROT

Re: [qmailtoaster] errors during upgrading qt

[Eric \"Shubes\"]

I'm having this same problem now, and am tracking it down. At first glance
it appears to be outside of the qtp- scripts.

I'll start a new thread for this one.

Lucian Cristian wrote:
> Eric "Shubes" wrote:
>> Lucian Cristian wrote:
>>  
>>> I've looked into the file and it-s saying that is
>>> v0.1.1 who knows what's happening, i'll remove all  qtp-build-sandbox
>>> files if there are others (I haven't check that yet)
>>> from the server and download them again.
>>> 
>>
>> Please download them directly from svn.shubes.net or qtp.shubes.net.
>> Do not
>> use the 0.1 qt-plus versions. This should all be ironed out with the 0.2
>> release of qt-plus (in a few weeks).
>>
>>  
>>> so far this are my results
>>> after  unmounting /var/named/chroot/proc
>>> 
>>
>> I wouldn't unmount /var/named/chroot/proc, especially on a live
>> server. It
>> should no longer be necessary.
>>
>>  
>>> Creating /opt/qtp-sandbox/var ...
>>> Unexpected named pipe: /var/gdm/.gdmfifo
>>> prw-rw  1 root root 0 Oct 18  2005 /var/gdm/.gdmfifo
>>> Continuing ...
>>> 
>>
>> I added code that should handle this. I'm guessing that this was still
>> v0.1
>>
>>  
>>> Creating /opt/qtp-sandbox/home/vpopmail ...
>>> Creating /opt/qtp-sandbox/ misc directories ...
>>> Sandbox has been built successfully!
>>> 
>>
>>  
>>> Starting to build the binary rpms ...(pizza anyone?)
>>>
>>> If you want to view compile messages, you can open another terminal and:
>>> # tail -f /opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log
>>>
>>> qtp-build-rpms 0.1.3
>>> cat: /usr/src/qtp-upgrade: Is a directory
>>> qtp-build-rpms Error - package list not found
>>> Build failed, Exiting.
>>>
>>> 
>> The order of parameters passed from qtp-newmodel to qtp-build-rpms was
>> changed at some point. One of these scripts is apparently not up to date.
>>
>> You should have:
>> qtp-newmodel v0.1.10
>> qtp-whatami v0.1.1
>> qtp-build-sandbox v0.1.1
>> qtp-build-rpms v0.1.3
>>
>>   
> here's my run for today ;)
> 
> bash-3.00# ./qtp-newmodel
> qtp-newmodel v0.1.10 starting Thu Oct 12 21:31:24 EEST 2006
> qtp-whatami v0.1.1
> DISTRO=CentOS
> OSVER=4.4
> 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 ...
> Getting package list ...
> 
> qmail Toaster is an integrated distribution.
> Packages are preconfigured for the whole distro.
> As a result, a partial install might be misconfigured.
> Upgrading all packages to their latest version is strongly recommended.
> Now that you've been warned, we will proceed with package selection ...
> ..
> ..
> Creating /opt/qtp-sandbox/var ...
> Creating /opt/qtp-sandbox/home/vpopmail ...
> Creating /opt/qtp-sandbox/ misc directories ...
> cp: cannot copy a directory, `/opt/qtp-sandbox', into itself,
> `/opt/qtp-sandbox/opt/./qtp-sandbox'
> cp: cannot copy a directory, `/opt/qtp-sandbox', into itself,
> `/opt/qtp-sandbox/opt/./qtp-sandbox'
> Sandbox has been built successfully!
> 
> Starting to build the binary rpms ...(pizza anyone?)
> 
> If you want to view compile messages, you can open another terminal and:
> # tail -f /opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log
> 
> qtp-build-rpms v0.1.3
> REMOVED spamassassin-toaster from sandbox (not for real)
> Building vpopmail-toaster-5.4.13-1.3.2 ...
> qtp-build-rpms - rpmbuild failed for vpopmail-toaster-5.4.13-1.3.2
> qtp-build-rpms - see
> /opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log
> Build failed, Exiting.
> bash-3.00#
> bash-3.00# tail -f
> /opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log
> checking build system type... i686-pc-linux-gnu
> checking host system type... i686-pc-linux-gnu
> checking for gawk... (cached) gawk
> checking for gcc... gcc
> checking for C compiler default output... configure: error: C compiler
> cannot create executables
> error: Bad exit status from /var/tmp/rpm-tmp.32546 (%build)
> 
> 
> RPM build errors:
>Bad exit status from /var/tmp/rpm-tmp.32546 (%build)
> 
> bash-3.00#
> 
> 
> I don't remember if there are some steps to do before running
> qtp-newmodel, maybe I'm not doing the right way, i'll try on another
> machine, but I have to work and go to school too ..  I'll try the moment
> I'll have free time
> 
> -
> QmailToaster hosted by: VR Hosted 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 


-- 
-Eric 'shubes'

-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For 

Re: [qmailtoaster] errors during upgrading qt

[Lucian Cristian]

Eric "Shubes" wrote:

Lucian Cristian wrote:
  

I've looked into the file and it-s saying that is
v0.1.1 who knows what's happening, i'll remove all  qtp-build-sandbox
files if there are others (I haven't check that yet)
from the server and download them again.



Please download them directly from svn.shubes.net or qtp.shubes.net. Do not
use the 0.1 qt-plus versions. This should all be ironed out with the 0.2
release of qt-plus (in a few weeks).

  

so far this are my results
after  unmounting /var/named/chroot/proc



I wouldn't unmount /var/named/chroot/proc, especially on a live server. It
should no longer be necessary.

  

Creating /opt/qtp-sandbox/var ...
Unexpected named pipe: /var/gdm/.gdmfifo
prw-rw  1 root root 0 Oct 18  2005 /var/gdm/.gdmfifo
Continuing ...



I added code that should handle this. I'm guessing that this was still v0.1

  

Creating /opt/qtp-sandbox/home/vpopmail ...
Creating /opt/qtp-sandbox/ misc directories ...
Sandbox has been built successfully!



  

Starting to build the binary rpms ...(pizza anyone?)

If you want to view compile messages, you can open another terminal and:
# tail -f /opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log

qtp-build-rpms 0.1.3
cat: /usr/src/qtp-upgrade: Is a directory
qtp-build-rpms Error - package list not found
Build failed, Exiting.



The order of parameters passed from qtp-newmodel to qtp-build-rpms was
changed at some point. One of these scripts is apparently not up to date.

You should have:
qtp-newmodel v0.1.10
qtp-whatami v0.1.1
qtp-build-sandbox v0.1.1
qtp-build-rpms v0.1.3

  

here's my run for today ;)

bash-3.00# ./qtp-newmodel
qtp-newmodel v0.1.10 starting Thu Oct 12 21:31:24 EEST 2006
qtp-whatami v0.1.1
DISTRO=CentOS
OSVER=4.4
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 ...
Getting package list ...

qmail Toaster is an integrated distribution.
Packages are preconfigured for the whole distro.
As a result, a partial install might be misconfigured.
Upgrading all packages to their latest version is strongly recommended.
Now that you've been warned, we will proceed with package selection ...
..
..
Creating /opt/qtp-sandbox/var ...
Creating /opt/qtp-sandbox/home/vpopmail ...
Creating /opt/qtp-sandbox/ misc directories ...
cp: cannot copy a directory, `/opt/qtp-sandbox', into itself, 
`/opt/qtp-sandbox/opt/./qtp-sandbox'
cp: cannot copy a directory, `/opt/qtp-sandbox', into itself, 
`/opt/qtp-sandbox/opt/./qtp-sandbox'

Sandbox has been built successfully!

Starting to build the binary rpms ...(pizza anyone?)

If you want to view compile messages, you can open another terminal and:
# tail -f /opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log

qtp-build-rpms v0.1.3
REMOVED spamassassin-toaster from sandbox (not for real)
Building vpopmail-toaster-5.4.13-1.3.2 ...
qtp-build-rpms - rpmbuild failed for vpopmail-toaster-5.4.13-1.3.2
qtp-build-rpms - see 
/opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log

Build failed, Exiting.
bash-3.00#
bash-3.00# tail -f /opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for gawk... (cached) gawk
checking for gcc... gcc
checking for C compiler default output... configure: error: C compiler 
cannot create executables

error: Bad exit status from /var/tmp/rpm-tmp.32546 (%build)


RPM build errors:
   Bad exit status from /var/tmp/rpm-tmp.32546 (%build)

bash-3.00#


I don't remember if there are some steps to do before running 
qtp-newmodel, maybe I'm not doing the right way, i'll try on another 
machine, but I have to work and go to school too ..  I'll try the moment 
I'll have free time


-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] errors during upgrading qt

[Eric \"Shubes\"]

Lucian Cristian wrote:
> I've looked into the file and it-s saying that is
> v0.1.1 who knows what's happening, i'll remove all  qtp-build-sandbox
> files if there are others (I haven't check that yet)
> from the server and download them again.

Please download them directly from svn.shubes.net or qtp.shubes.net. Do not
use the 0.1 qt-plus versions. This should all be ironed out with the 0.2
release of qt-plus (in a few weeks).

> so far this are my results
> after  unmounting /var/named/chroot/proc

I wouldn't unmount /var/named/chroot/proc, especially on a live server. It
should no longer be necessary.

> 
> Creating /opt/qtp-sandbox/var ...
> Unexpected named pipe: /var/gdm/.gdmfifo
> prw-rw  1 root root 0 Oct 18  2005 /var/gdm/.gdmfifo
> Continuing ...

I added code that should handle this. I'm guessing that this was still v0.1

> Creating /opt/qtp-sandbox/home/vpopmail ...
> Creating /opt/qtp-sandbox/ misc directories ...
> Sandbox has been built successfully!

> Starting to build the binary rpms ...(pizza anyone?)
> 
> If you want to view compile messages, you can open another terminal and:
> # tail -f /opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log
> 
> qtp-build-rpms 0.1.3
> cat: /usr/src/qtp-upgrade: Is a directory
> qtp-build-rpms Error - package list not found
> Build failed, Exiting.
> 
The order of parameters passed from qtp-newmodel to qtp-build-rpms was
changed at some point. One of these scripts is apparently not up to date.

You should have:
qtp-newmodel v0.1.10
qtp-whatami v0.1.1
qtp-build-sandbox v0.1.1
qtp-build-rpms v0.1.3

-- 
-Eric 'shubes'

-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] errors during upgrading qt

[Lucian Cristian]

Eric "Shubes" wrote:

Erik Espinoza wrote:
  

Try umount /var/named/chroot/proc first and then try building the sanbox.

You have the bind-chroot package installed.

Erik




That is actually (no surprise) a good recommendation to work around the
unfixed script, although I would stop named first.

To be clear about this, beginning with v0.1.1 the qtp-build-sandbox script
handles bind-chroot without a hitch. It no longer tries to copy
/var/named/chroot/proc. There are a couple other fixes in there too.

  
there was a qtp-build-sandbox file in /usr/share/qmailtoaster-plus/ 
directory, now I'm  running version v0.1.1 i'll post an update later


-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] errors during upgrading qt

[Lucian Cristian]

Eric "Shubes" wrote:

Lucian Cristian wrote:
  

Eric "Shubes" wrote:


These errors have all been fixed. Changes were limited to
qtp-build-sandbox.
You can get the latest release (v0.1.1) from qtp.shubes.net or
svn.shubes.net.

Thank you for your patience (and testing!). ;)

  

copyed

qtp-build-sandbox   11-Oct-2006
14:46   14K
and I still got those errors

..
..
clamav-toaster-0.88.4-1.3.3.src.rpm is already downloaded, bypassed

vqadmin-toaster-2.3.4-1.3.2.src.rpm is already downloaded, bypassed
qtp-build-sandbox v0.1 starting Thu Oct 12 01:39:01 EEST 2006



You apparently downloaded the fixed qtp-build-sandbox, but that's not what's
being executed. The fixed version is v0.1.1, and you're still running v0.1.
Check to see where you put the new one, and get rid of the old one. The
scripts should all be in the same directory. The version number is near the
bottom of the script.



  
I've looked into the file and it-s saying that is 


v0.1.1 who knows what's happening, i'll remove all  qtp-build-sandbox files if 
there are others (I haven't check that yet)
from the server and download them again. so far this are my results after  
unmounting /var/named/chroot/proc


Creating /opt/qtp-sandbox/var ...
Unexpected named pipe: /var/gdm/.gdmfifo
prw-rw  1 root root 0 Oct 18  2005 /var/gdm/.gdmfifo
Continuing ...
Creating /opt/qtp-sandbox/home/vpopmail ...
Creating /opt/qtp-sandbox/ misc directories ...
Sandbox has been built successfully!

Starting to build the binary rpms ...(pizza anyone?)

If you want to view compile messages, you can open another terminal and:
# tail -f /opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log

qtp-build-rpms 0.1.3
cat: /usr/src/qtp-upgrade: Is a directory
qtp-build-rpms Error - package list not found
Build failed, Exiting.


-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] errors during upgrading qt

[Eric \"Shubes\"]

Erik Espinoza wrote:
> Try umount /var/named/chroot/proc first and then try building the sanbox.
> 
> You have the bind-chroot package installed.
> 
> Erik
> 

That is actually (no surprise) a good recommendation to work around the
unfixed script, although I would stop named first.

To be clear about this, beginning with v0.1.1 the qtp-build-sandbox script
handles bind-chroot without a hitch. It no longer tries to copy
/var/named/chroot/proc. There are a couple other fixes in there too.

-- 
-Eric 'shubes'

-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] errors during upgrading qt

[Eric \"Shubes\"]

Lucian Cristian wrote:
> Eric "Shubes" wrote:
>> These errors have all been fixed. Changes were limited to
>> qtp-build-sandbox.
>> You can get the latest release (v0.1.1) from qtp.shubes.net or
>> svn.shubes.net.
>>
>> Thank you for your patience (and testing!). ;)
>>
> copyed
> 
> qtp-build-sandbox   11-Oct-2006
> 14:46   14K
> and I still got those errors
> 
> ..
> ..
> clamav-toaster-0.88.4-1.3.3.src.rpm is already downloaded, bypassed
> 
> vqadmin-toaster-2.3.4-1.3.2.src.rpm is already downloaded, bypassed
> qtp-build-sandbox v0.1 starting Thu Oct 12 01:39:01 EEST 2006

You apparently downloaded the fixed qtp-build-sandbox, but that's not what's
being executed. The fixed version is v0.1.1, and you're still running v0.1.
Check to see where you put the new one, and get rid of the old one. The
scripts should all be in the same directory. The version number is near the
bottom of the script.



-- 
-Eric 'shubes'

-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] errors during upgrading qt

[Erik Espinoza]

Try umount /var/named/chroot/proc first and then try building the sanbox.

You have the bind-chroot package installed.

Erik

On 10/11/06, Lucian Cristian <[EMAIL PROTECTED]> wrote:

Eric "Shubes" wrote:
> These errors have all been fixed. Changes were limited to qtp-build-sandbox.
> You can get the latest release (v0.1.1) from qtp.shubes.net or svn.shubes.net.
>
> Thank you for your patience (and testing!). ;)
>
> Lucian Cristian wrote:
>
>> Eric "Shubes" wrote:
>>
>>> Lucian Cristian wrote:
>>>
>>>
 I let the script to run all night (on 2000 mhz and 1 Gb of ram, 60 Gb
 free disk space/14 used) and it have the following output (sandbox is
 copyed, not linked)

 <<
 ...
 Creating /opt/qtp-sandbox/var ...
 Unexpected named pipe: /var/spool/postfix/public/pickup
 prw--w--w-  1 89 89 0 May 18 09:46 /var/spool/postfix/public/pickup
 Continuing ...
 Unexpected named pipe: /var/spool/postfix/public/qmgr
 prw--w--w-  1 89 89 0 May 18 09:46 /var/spool/postfix/public/qmgr
 Continuing ...


>>> This doesn't look kosher for a toaster:
>>> 1) Is postfix installed? I thought it couldn't coexist with qmail. Why
>>> does
>>> /var/spool/postfix exist?
>>> 2) User:group 89:89 not defined? That should normally be vpopmail, but I
>>> suppose it could be any other number.
>>>
>>>
>>>
 Unexpected named pipe: /var/service/qmail-pop3d/supervise/control
 prw---  1 root root 0 Dec  4  2005
 /var/service/qmail-pop3d/supervise/control
 Continuing ...
 Unexpected named pipe: /var/service/qmail-pop3d/supervise/ok
 prw---  1 root root 0 Dec  3  2005
 /var/service/qmail-pop3d/supervise/ok
 Continuing ...
 Unexpected named pipe: /var/service/qmail-pop3d/log/supervise/control
 prw---  1 root root 0 Dec  3  2005
 /var/service/qmail-pop3d/log/supervise/control
 Continuing ...
 Unexpected named pipe: /var/service/qmail-pop3d/log/supervise/ok
 prw---  1 root root 0 Dec  3  2005
 /var/service/qmail-pop3d/log/supervise/ok
 Continuing ...
 Unexpected named pipe: /var/service/qmail-send/supervise/control
 prw---  1 root root 0 Dec  3  2005
 /var/service/qmail-send/supervise/control
 Continuing ...
 Unexpected named pipe: /var/service/qmail-send/supervise/ok
 prw---  1 root root 0 Dec  3  2005
 /var/service/qmail-send/supervise/ok
 Continuing ...
 Unexpected named pipe: /var/service/qmail-send/log/supervise/control
 prw---  1 root root 0 Dec  3  2005
 /var/service/qmail-send/log/supervise/control
 Continuing ...
 Unexpected named pipe: /var/service/qmail-send/log/supervise/ok
 prw---  1 root root 0 Dec  3  2005
 /var/service/qmail-send/log/supervise/ok
 Continuing ...
 Unexpected named pipe: /var/service/qmail-smtpd/supervise/control
 prw---  1 root root 0 Dec  4  2005
 /var/service/qmail-smtpd/supervise/control
 Continuing ...
 Unexpected named pipe: /var/service/qmail-smtpd/supervise/ok
 prw---  1 root root 0 Dec  3  2005
 /var/service/qmail-smtpd/supervise/ok
 Continuing ...
 Unexpected named pipe: /var/service/qmail-smtpd/log/supervise/control
 prw---  1 root root 0 Dec  3  2005
 /var/service/qmail-smtpd/log/supervise/control
 Continuing ...
 Unexpected named pipe: /var/service/qmail-smtpd/log/supervise/ok
 prw---  1 root root 0 Dec  3  2005
 /var/service/qmail-smtpd/log/supervise/ok
 Continuing ...


>>> These are apparently from an older version. They are now in
>>> /var/qmail/supervise/ instead of /var/service/. What toaster version
>>> are you
>>> upgrading from?
>>>
>>> This doesn't hurt anything, as they're not used. I'll update the
>>> script to
>>> create them though (and thus get rid of the messages).
>>>
>>>
>>>
 Unexpected file type for /var/run/pure-ftpd/client-00011531
 ls: /var/run/pure-ftpd/client-00011531: No such file or directory
 Continuing ...


>>> This was apparently (I'm guessing) a transient file from an ftp
>>> session that
>>> disappeared during the run. I'll fix the script to handle the /var/run
>>> directory more appropriately.
>>>
>>>
>>>
 Unexpected named pipe: /var/gdm/.gdmfifo
 prw-rw  1 root root 0 Oct 18  2005 /var/gdm/.gdmfifo
 Continuing ...


>>> I'll fix this one too.
>>>
>>>
>>>
 cp: cannot open `/var/named/chroot/proc/acpi/event' for reading: Device
 or resou
 rce busy
 cp: reading `/var/named/chroot/proc/sys/net/ipv6/route/flush': Operation
 not per
 mitted
 cp: reading `/var/named/chroot/proc/sys/net/ipv4/route/flush': Operation
 not per
 mitted
 cp: reading `/var/named/chroot/proc/sysrq-trigger': Invalid argument


>>> Hmmm, a chroot within a chroot. This is a problem all right. I'm
>>> surprised
>>> to realize that I haven't tested this since I added named-chroot. I'm
>>> getting a boatload of errors at thi

Re: [qmailtoaster] errors during upgrading qt

[Lucian Cristian]

Eric "Shubes" wrote:

These errors have all been fixed. Changes were limited to qtp-build-sandbox.
You can get the latest release (v0.1.1) from qtp.shubes.net or svn.shubes.net.

Thank you for your patience (and testing!). ;)

Lucian Cristian wrote:
  

Eric "Shubes" wrote:


Lucian Cristian wrote:
 
  

I let the script to run all night (on 2000 mhz and 1 Gb of ram, 60 Gb
free disk space/14 used) and it have the following output (sandbox is
copyed, not linked)

<<
...
Creating /opt/qtp-sandbox/var ...
Unexpected named pipe: /var/spool/postfix/public/pickup
prw--w--w-  1 89 89 0 May 18 09:46 /var/spool/postfix/public/pickup
Continuing ...
Unexpected named pipe: /var/spool/postfix/public/qmgr
prw--w--w-  1 89 89 0 May 18 09:46 /var/spool/postfix/public/qmgr
Continuing ...



This doesn't look kosher for a toaster:
1) Is postfix installed? I thought it couldn't coexist with qmail. Why
does
/var/spool/postfix exist?
2) User:group 89:89 not defined? That should normally be vpopmail, but I
suppose it could be any other number.

 
  

Unexpected named pipe: /var/service/qmail-pop3d/supervise/control
prw---  1 root root 0 Dec  4  2005
/var/service/qmail-pop3d/supervise/control
Continuing ...
Unexpected named pipe: /var/service/qmail-pop3d/supervise/ok
prw---  1 root root 0 Dec  3  2005
/var/service/qmail-pop3d/supervise/ok
Continuing ...
Unexpected named pipe: /var/service/qmail-pop3d/log/supervise/control
prw---  1 root root 0 Dec  3  2005
/var/service/qmail-pop3d/log/supervise/control
Continuing ...
Unexpected named pipe: /var/service/qmail-pop3d/log/supervise/ok
prw---  1 root root 0 Dec  3  2005
/var/service/qmail-pop3d/log/supervise/ok
Continuing ...
Unexpected named pipe: /var/service/qmail-send/supervise/control
prw---  1 root root 0 Dec  3  2005
/var/service/qmail-send/supervise/control
Continuing ...
Unexpected named pipe: /var/service/qmail-send/supervise/ok
prw---  1 root root 0 Dec  3  2005
/var/service/qmail-send/supervise/ok
Continuing ...
Unexpected named pipe: /var/service/qmail-send/log/supervise/control
prw---  1 root root 0 Dec  3  2005
/var/service/qmail-send/log/supervise/control
Continuing ...
Unexpected named pipe: /var/service/qmail-send/log/supervise/ok
prw---  1 root root 0 Dec  3  2005
/var/service/qmail-send/log/supervise/ok
Continuing ...
Unexpected named pipe: /var/service/qmail-smtpd/supervise/control
prw---  1 root root 0 Dec  4  2005
/var/service/qmail-smtpd/supervise/control
Continuing ...
Unexpected named pipe: /var/service/qmail-smtpd/supervise/ok
prw---  1 root root 0 Dec  3  2005
/var/service/qmail-smtpd/supervise/ok
Continuing ...
Unexpected named pipe: /var/service/qmail-smtpd/log/supervise/control
prw---  1 root root 0 Dec  3  2005
/var/service/qmail-smtpd/log/supervise/control
Continuing ...
Unexpected named pipe: /var/service/qmail-smtpd/log/supervise/ok
prw---  1 root root 0 Dec  3  2005
/var/service/qmail-smtpd/log/supervise/ok
Continuing ...



These are apparently from an older version. They are now in
/var/qmail/supervise/ instead of /var/service/. What toaster version
are you
upgrading from?

This doesn't hurt anything, as they're not used. I'll update the
script to
create them though (and thus get rid of the messages).

 
  

Unexpected file type for /var/run/pure-ftpd/client-00011531
ls: /var/run/pure-ftpd/client-00011531: No such file or directory
Continuing ...



This was apparently (I'm guessing) a transient file from an ftp
session that
disappeared during the run. I'll fix the script to handle the /var/run
directory more appropriately.

 
  

Unexpected named pipe: /var/gdm/.gdmfifo
prw-rw  1 root root 0 Oct 18  2005 /var/gdm/.gdmfifo
Continuing ...



I'll fix this one too.

 
  

cp: cannot open `/var/named/chroot/proc/acpi/event' for reading: Device
or resou
rce busy
cp: reading `/var/named/chroot/proc/sys/net/ipv6/route/flush': Operation
not per
mitted
cp: reading `/var/named/chroot/proc/sys/net/ipv4/route/flush': Operation
not per
mitted
cp: reading `/var/named/chroot/proc/sysrq-trigger': Invalid argument



Hmmm, a chroot within a chroot. This is a problem all right. I'm
surprised
to realize that I haven't tested this since I added named-chroot. I'm
getting a boatload of errors at this point too. I'm going to fix this
right
now. I'll post to the list when it's fixed and tested, should be later
today.

 
  

( here I pressed CTRL+C )
bash-3.00#




Thanks, Lucian.

  
  

Sometime ago I tested a postfix install and a qmail from original site
install, maybe  that's why I have those files there. qmailtoaster is
almost the last version and is working allright.

-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For a

Re: [qmailtoaster] errors during upgrading qt

[Eric \"Shubes\"]

These errors have all been fixed. Changes were limited to qtp-build-sandbox.
You can get the latest release (v0.1.1) from qtp.shubes.net or svn.shubes.net.

Thank you for your patience (and testing!). ;)

Lucian Cristian wrote:
> Eric "Shubes" wrote:
>> Lucian Cristian wrote:
>>  
>>> I let the script to run all night (on 2000 mhz and 1 Gb of ram, 60 Gb
>>> free disk space/14 used) and it have the following output (sandbox is
>>> copyed, not linked)
>>>
>>> <<
>>> ...
>>> Creating /opt/qtp-sandbox/var ...
>>> Unexpected named pipe: /var/spool/postfix/public/pickup
>>> prw--w--w-  1 89 89 0 May 18 09:46 /var/spool/postfix/public/pickup
>>> Continuing ...
>>> Unexpected named pipe: /var/spool/postfix/public/qmgr
>>> prw--w--w-  1 89 89 0 May 18 09:46 /var/spool/postfix/public/qmgr
>>> Continuing ...
>>> 
>>
>> This doesn't look kosher for a toaster:
>> 1) Is postfix installed? I thought it couldn't coexist with qmail. Why
>> does
>> /var/spool/postfix exist?
>> 2) User:group 89:89 not defined? That should normally be vpopmail, but I
>> suppose it could be any other number.
>>
>>  
>>> Unexpected named pipe: /var/service/qmail-pop3d/supervise/control
>>> prw---  1 root root 0 Dec  4  2005
>>> /var/service/qmail-pop3d/supervise/control
>>> Continuing ...
>>> Unexpected named pipe: /var/service/qmail-pop3d/supervise/ok
>>> prw---  1 root root 0 Dec  3  2005
>>> /var/service/qmail-pop3d/supervise/ok
>>> Continuing ...
>>> Unexpected named pipe: /var/service/qmail-pop3d/log/supervise/control
>>> prw---  1 root root 0 Dec  3  2005
>>> /var/service/qmail-pop3d/log/supervise/control
>>> Continuing ...
>>> Unexpected named pipe: /var/service/qmail-pop3d/log/supervise/ok
>>> prw---  1 root root 0 Dec  3  2005
>>> /var/service/qmail-pop3d/log/supervise/ok
>>> Continuing ...
>>> Unexpected named pipe: /var/service/qmail-send/supervise/control
>>> prw---  1 root root 0 Dec  3  2005
>>> /var/service/qmail-send/supervise/control
>>> Continuing ...
>>> Unexpected named pipe: /var/service/qmail-send/supervise/ok
>>> prw---  1 root root 0 Dec  3  2005
>>> /var/service/qmail-send/supervise/ok
>>> Continuing ...
>>> Unexpected named pipe: /var/service/qmail-send/log/supervise/control
>>> prw---  1 root root 0 Dec  3  2005
>>> /var/service/qmail-send/log/supervise/control
>>> Continuing ...
>>> Unexpected named pipe: /var/service/qmail-send/log/supervise/ok
>>> prw---  1 root root 0 Dec  3  2005
>>> /var/service/qmail-send/log/supervise/ok
>>> Continuing ...
>>> Unexpected named pipe: /var/service/qmail-smtpd/supervise/control
>>> prw---  1 root root 0 Dec  4  2005
>>> /var/service/qmail-smtpd/supervise/control
>>> Continuing ...
>>> Unexpected named pipe: /var/service/qmail-smtpd/supervise/ok
>>> prw---  1 root root 0 Dec  3  2005
>>> /var/service/qmail-smtpd/supervise/ok
>>> Continuing ...
>>> Unexpected named pipe: /var/service/qmail-smtpd/log/supervise/control
>>> prw---  1 root root 0 Dec  3  2005
>>> /var/service/qmail-smtpd/log/supervise/control
>>> Continuing ...
>>> Unexpected named pipe: /var/service/qmail-smtpd/log/supervise/ok
>>> prw---  1 root root 0 Dec  3  2005
>>> /var/service/qmail-smtpd/log/supervise/ok
>>> Continuing ...
>>> 
>>
>> These are apparently from an older version. They are now in
>> /var/qmail/supervise/ instead of /var/service/. What toaster version
>> are you
>> upgrading from?
>>
>> This doesn't hurt anything, as they're not used. I'll update the
>> script to
>> create them though (and thus get rid of the messages).
>>
>>  
>>> Unexpected file type for /var/run/pure-ftpd/client-00011531
>>> ls: /var/run/pure-ftpd/client-00011531: No such file or directory
>>> Continuing ...
>>> 
>>
>> This was apparently (I'm guessing) a transient file from an ftp
>> session that
>> disappeared during the run. I'll fix the script to handle the /var/run
>> directory more appropriately.
>>
>>  
>>> Unexpected named pipe: /var/gdm/.gdmfifo
>>> prw-rw  1 root root 0 Oct 18  2005 /var/gdm/.gdmfifo
>>> Continuing ...
>>> 
>>
>> I'll fix this one too.
>>
>>  
>>> cp: cannot open `/var/named/chroot/proc/acpi/event' for reading: Device
>>> or resou
>>> rce busy
>>> cp: reading `/var/named/chroot/proc/sys/net/ipv6/route/flush': Operation
>>> not per
>>> mitted
>>> cp: reading `/var/named/chroot/proc/sys/net/ipv4/route/flush': Operation
>>> not per
>>> mitted
>>> cp: reading `/var/named/chroot/proc/sysrq-trigger': Invalid argument
>>> 
>>
>> Hmmm, a chroot within a chroot. This is a problem all right. I'm
>> surprised
>> to realize that I haven't tested this since I added named-chroot. I'm
>> getting a boatload of errors at this point too. I'm going to fix this
>> right
>> now. I'll post to the list when it's fixed and tested, should be later
>> today.
>>
>>  
>>> ( here I pressed CTRL+C )
>>> bash-3.00#
>>>
>>> 
>>
>> Thanks, Lucian.
>>
>>   
> Sometime ago I tested a postfix install and a qmail from original site
> install, maybe  that's why I ha

Re: [qmailtoaster] errors during upgrading qt

[Lucian Cristian]

Eric "Shubes" wrote:

Lucian Cristian wrote:
  

Eric "Shubes" wrote:


Lucian Cristian wrote:
 
  

I let the script to run all night (on 2000 mhz and 1 Gb of ram, 60 Gb
free disk space/14 used) and it have the following output (sandbox is
copyed, not linked)

<<
...
Creating /opt/qtp-sandbox/var ...
Unexpected named pipe: /var/spool/postfix/public/pickup
prw--w--w-  1 89 89 0 May 18 09:46 /var/spool/postfix/public/pickup
Continuing ...
Unexpected named pipe: /var/spool/postfix/public/qmgr
prw--w--w-  1 89 89 0 May 18 09:46 /var/spool/postfix/public/qmgr
Continuing ...



This doesn't look kosher for a toaster:
1) Is postfix installed? I thought it couldn't coexist with qmail. Why
does
/var/spool/postfix exist?
2) User:group 89:89 not defined? That should normally be vpopmail, but I
suppose it could be any other number.

 
  

Unexpected named pipe: /var/service/qmail-pop3d/supervise/control
prw---  1 root root 0 Dec  4  2005
/var/service/qmail-pop3d/supervise/control
Continuing ...
Unexpected named pipe: /var/service/qmail-pop3d/supervise/ok
prw---  1 root root 0 Dec  3  2005
/var/service/qmail-pop3d/supervise/ok
Continuing ...
Unexpected named pipe: /var/service/qmail-pop3d/log/supervise/control
prw---  1 root root 0 Dec  3  2005
/var/service/qmail-pop3d/log/supervise/control
Continuing ...
Unexpected named pipe: /var/service/qmail-pop3d/log/supervise/ok
prw---  1 root root 0 Dec  3  2005
/var/service/qmail-pop3d/log/supervise/ok
Continuing ...
Unexpected named pipe: /var/service/qmail-send/supervise/control
prw---  1 root root 0 Dec  3  2005
/var/service/qmail-send/supervise/control
Continuing ...
Unexpected named pipe: /var/service/qmail-send/supervise/ok
prw---  1 root root 0 Dec  3  2005
/var/service/qmail-send/supervise/ok
Continuing ...
Unexpected named pipe: /var/service/qmail-send/log/supervise/control
prw---  1 root root 0 Dec  3  2005
/var/service/qmail-send/log/supervise/control
Continuing ...
Unexpected named pipe: /var/service/qmail-send/log/supervise/ok
prw---  1 root root 0 Dec  3  2005
/var/service/qmail-send/log/supervise/ok
Continuing ...
Unexpected named pipe: /var/service/qmail-smtpd/supervise/control
prw---  1 root root 0 Dec  4  2005
/var/service/qmail-smtpd/supervise/control
Continuing ...
Unexpected named pipe: /var/service/qmail-smtpd/supervise/ok
prw---  1 root root 0 Dec  3  2005
/var/service/qmail-smtpd/supervise/ok
Continuing ...
Unexpected named pipe: /var/service/qmail-smtpd/log/supervise/control
prw---  1 root root 0 Dec  3  2005
/var/service/qmail-smtpd/log/supervise/control
Continuing ...
Unexpected named pipe: /var/service/qmail-smtpd/log/supervise/ok
prw---  1 root root 0 Dec  3  2005
/var/service/qmail-smtpd/log/supervise/ok
Continuing ...



This doesn't hurt anything, as they're not used. I'll update the
script to
create them though (and thus get rid of the messages).

 
  

Unexpected file type for /var/run/pure-ftpd/client-00011531
ls: /var/run/pure-ftpd/client-00011531: No such file or directory
Continuing ...



This was apparently (I'm guessing) a transient file from an ftp
session that
disappeared during the run. I'll fix the script to handle the /var/run
directory more appropriately.

 
  

Unexpected named pipe: /var/gdm/.gdmfifo
prw-rw  1 root root 0 Oct 18  2005 /var/gdm/.gdmfifo
Continuing ...



I'll fix this one too.

 
  

cp: cannot open `/var/named/chroot/proc/acpi/event' for reading: Device
or resou
rce busy
cp: reading `/var/named/chroot/proc/sys/net/ipv6/route/flush': Operation
not per
mitted
cp: reading `/var/named/chroot/proc/sys/net/ipv4/route/flush': Operation
not per
mitted
cp: reading `/var/named/chroot/proc/sysrq-trigger': Invalid argument



Hmmm, a chroot within a chroot. This is a problem all right. I'm
surprised
to realize that I haven't tested this since I added named-chroot. I'm
getting a boatload of errors at this point too. I'm going to fix this
right
now. I'll post to the list when it's fixed and tested, should be later
today.

 
  

( here I pressed CTRL+C )
bash-3.00#




Thanks, Lucian.

  
  

Sometime ago I tested a postfix install and a qmail from original site
install, maybe  that's why I have those files there.



I'd lose them.

  

qmailtoaster is almost the last version and is working allright.



"Almost is good enough for quoits and hand grenades". :)

I ask because I don't want to add checks in the script for /var/service/
pipes if it's not necessary. Do you have /var/qmail/supervise/ files too? If
so, you can lose /var/service/ too. I'd like to know where it came from
though. If it's an older toaster (as I suspect), I'll leave them in the
script. I wonder if they're simply left over from a previous version. What
was the first toaster version on that box? The directories are dated 12/3/05.

P.S. Fixed script final test is running now...
  

this are my qm

Re: [qmailtoaster] errors during upgrading qt

[Eric \"Shubes\"]

Lucian Cristian wrote:
> Eric "Shubes" wrote:
>> Lucian Cristian wrote:
>>  
>>> I let the script to run all night (on 2000 mhz and 1 Gb of ram, 60 Gb
>>> free disk space/14 used) and it have the following output (sandbox is
>>> copyed, not linked)
>>>
>>> <<
>>> ...
>>> Creating /opt/qtp-sandbox/var ...
>>> Unexpected named pipe: /var/spool/postfix/public/pickup
>>> prw--w--w-  1 89 89 0 May 18 09:46 /var/spool/postfix/public/pickup
>>> Continuing ...
>>> Unexpected named pipe: /var/spool/postfix/public/qmgr
>>> prw--w--w-  1 89 89 0 May 18 09:46 /var/spool/postfix/public/qmgr
>>> Continuing ...
>>> 
>>
>> This doesn't look kosher for a toaster:
>> 1) Is postfix installed? I thought it couldn't coexist with qmail. Why
>> does
>> /var/spool/postfix exist?
>> 2) User:group 89:89 not defined? That should normally be vpopmail, but I
>> suppose it could be any other number.
>>
>>  
>>> Unexpected named pipe: /var/service/qmail-pop3d/supervise/control
>>> prw---  1 root root 0 Dec  4  2005
>>> /var/service/qmail-pop3d/supervise/control
>>> Continuing ...
>>> Unexpected named pipe: /var/service/qmail-pop3d/supervise/ok
>>> prw---  1 root root 0 Dec  3  2005
>>> /var/service/qmail-pop3d/supervise/ok
>>> Continuing ...
>>> Unexpected named pipe: /var/service/qmail-pop3d/log/supervise/control
>>> prw---  1 root root 0 Dec  3  2005
>>> /var/service/qmail-pop3d/log/supervise/control
>>> Continuing ...
>>> Unexpected named pipe: /var/service/qmail-pop3d/log/supervise/ok
>>> prw---  1 root root 0 Dec  3  2005
>>> /var/service/qmail-pop3d/log/supervise/ok
>>> Continuing ...
>>> Unexpected named pipe: /var/service/qmail-send/supervise/control
>>> prw---  1 root root 0 Dec  3  2005
>>> /var/service/qmail-send/supervise/control
>>> Continuing ...
>>> Unexpected named pipe: /var/service/qmail-send/supervise/ok
>>> prw---  1 root root 0 Dec  3  2005
>>> /var/service/qmail-send/supervise/ok
>>> Continuing ...
>>> Unexpected named pipe: /var/service/qmail-send/log/supervise/control
>>> prw---  1 root root 0 Dec  3  2005
>>> /var/service/qmail-send/log/supervise/control
>>> Continuing ...
>>> Unexpected named pipe: /var/service/qmail-send/log/supervise/ok
>>> prw---  1 root root 0 Dec  3  2005
>>> /var/service/qmail-send/log/supervise/ok
>>> Continuing ...
>>> Unexpected named pipe: /var/service/qmail-smtpd/supervise/control
>>> prw---  1 root root 0 Dec  4  2005
>>> /var/service/qmail-smtpd/supervise/control
>>> Continuing ...
>>> Unexpected named pipe: /var/service/qmail-smtpd/supervise/ok
>>> prw---  1 root root 0 Dec  3  2005
>>> /var/service/qmail-smtpd/supervise/ok
>>> Continuing ...
>>> Unexpected named pipe: /var/service/qmail-smtpd/log/supervise/control
>>> prw---  1 root root 0 Dec  3  2005
>>> /var/service/qmail-smtpd/log/supervise/control
>>> Continuing ...
>>> Unexpected named pipe: /var/service/qmail-smtpd/log/supervise/ok
>>> prw---  1 root root 0 Dec  3  2005
>>> /var/service/qmail-smtpd/log/supervise/ok
>>> Continuing ...
>>> 
>>
>>
>> This doesn't hurt anything, as they're not used. I'll update the
>> script to
>> create them though (and thus get rid of the messages).
>>
>>  
>>> Unexpected file type for /var/run/pure-ftpd/client-00011531
>>> ls: /var/run/pure-ftpd/client-00011531: No such file or directory
>>> Continuing ...
>>> 
>>
>> This was apparently (I'm guessing) a transient file from an ftp
>> session that
>> disappeared during the run. I'll fix the script to handle the /var/run
>> directory more appropriately.
>>
>>  
>>> Unexpected named pipe: /var/gdm/.gdmfifo
>>> prw-rw  1 root root 0 Oct 18  2005 /var/gdm/.gdmfifo
>>> Continuing ...
>>> 
>>
>> I'll fix this one too.
>>
>>  
>>> cp: cannot open `/var/named/chroot/proc/acpi/event' for reading: Device
>>> or resou
>>> rce busy
>>> cp: reading `/var/named/chroot/proc/sys/net/ipv6/route/flush': Operation
>>> not per
>>> mitted
>>> cp: reading `/var/named/chroot/proc/sys/net/ipv4/route/flush': Operation
>>> not per
>>> mitted
>>> cp: reading `/var/named/chroot/proc/sysrq-trigger': Invalid argument
>>> 
>>
>> Hmmm, a chroot within a chroot. This is a problem all right. I'm
>> surprised
>> to realize that I haven't tested this since I added named-chroot. I'm
>> getting a boatload of errors at this point too. I'm going to fix this
>> right
>> now. I'll post to the list when it's fixed and tested, should be later
>> today.
>>
>>  
>>> ( here I pressed CTRL+C )
>>> bash-3.00#
>>>
>>> 
>>
>> Thanks, Lucian.
>>
>>   
> Sometime ago I tested a postfix install and a qmail from original site
> install, maybe  that's why I have those files there.

I'd lose them.

> qmailtoaster is almost the last version and is working allright.

"Almost is good enough for quoits and hand grenades". :)

I ask because I don't want to add checks in the script for /var/service/
pipes if it's not necessary. Do you have /var/qmail/supervise/ files too? If
so, you can lose /var/service/ too. I'd like to know wh

Re: [qmailtoaster] errors during upgrading qt

[Lucian Cristian]

Eric "Shubes" wrote:

Lucian Cristian wrote:
  

I let the script to run all night (on 2000 mhz and 1 Gb of ram, 60 Gb
free disk space/14 used) and it have the following output (sandbox is
copyed, not linked)

<<
...
Creating /opt/qtp-sandbox/var ...
Unexpected named pipe: /var/spool/postfix/public/pickup
prw--w--w-  1 89 89 0 May 18 09:46 /var/spool/postfix/public/pickup
Continuing ...
Unexpected named pipe: /var/spool/postfix/public/qmgr
prw--w--w-  1 89 89 0 May 18 09:46 /var/spool/postfix/public/qmgr
Continuing ...



This doesn't look kosher for a toaster:
1) Is postfix installed? I thought it couldn't coexist with qmail. Why does
/var/spool/postfix exist?
2) User:group 89:89 not defined? That should normally be vpopmail, but I
suppose it could be any other number.

  

Unexpected named pipe: /var/service/qmail-pop3d/supervise/control
prw---  1 root root 0 Dec  4  2005
/var/service/qmail-pop3d/supervise/control
Continuing ...
Unexpected named pipe: /var/service/qmail-pop3d/supervise/ok
prw---  1 root root 0 Dec  3  2005
/var/service/qmail-pop3d/supervise/ok
Continuing ...
Unexpected named pipe: /var/service/qmail-pop3d/log/supervise/control
prw---  1 root root 0 Dec  3  2005
/var/service/qmail-pop3d/log/supervise/control
Continuing ...
Unexpected named pipe: /var/service/qmail-pop3d/log/supervise/ok
prw---  1 root root 0 Dec  3  2005
/var/service/qmail-pop3d/log/supervise/ok
Continuing ...
Unexpected named pipe: /var/service/qmail-send/supervise/control
prw---  1 root root 0 Dec  3  2005
/var/service/qmail-send/supervise/control
Continuing ...
Unexpected named pipe: /var/service/qmail-send/supervise/ok
prw---  1 root root 0 Dec  3  2005 /var/service/qmail-send/supervise/ok
Continuing ...
Unexpected named pipe: /var/service/qmail-send/log/supervise/control
prw---  1 root root 0 Dec  3  2005
/var/service/qmail-send/log/supervise/control
Continuing ...
Unexpected named pipe: /var/service/qmail-send/log/supervise/ok
prw---  1 root root 0 Dec  3  2005
/var/service/qmail-send/log/supervise/ok
Continuing ...
Unexpected named pipe: /var/service/qmail-smtpd/supervise/control
prw---  1 root root 0 Dec  4  2005
/var/service/qmail-smtpd/supervise/control
Continuing ...
Unexpected named pipe: /var/service/qmail-smtpd/supervise/ok
prw---  1 root root 0 Dec  3  2005
/var/service/qmail-smtpd/supervise/ok
Continuing ...
Unexpected named pipe: /var/service/qmail-smtpd/log/supervise/control
prw---  1 root root 0 Dec  3  2005
/var/service/qmail-smtpd/log/supervise/control
Continuing ...
Unexpected named pipe: /var/service/qmail-smtpd/log/supervise/ok
prw---  1 root root 0 Dec  3  2005
/var/service/qmail-smtpd/log/supervise/ok
Continuing ...



These are apparently from an older version. They are now in
/var/qmail/supervise/ instead of /var/service/. What toaster version are you
upgrading from?

This doesn't hurt anything, as they're not used. I'll update the script to
create them though (and thus get rid of the messages).

  

Unexpected file type for /var/run/pure-ftpd/client-00011531
ls: /var/run/pure-ftpd/client-00011531: No such file or directory
Continuing ...



This was apparently (I'm guessing) a transient file from an ftp session that
disappeared during the run. I'll fix the script to handle the /var/run
directory more appropriately.

  

Unexpected named pipe: /var/gdm/.gdmfifo
prw-rw  1 root root 0 Oct 18  2005 /var/gdm/.gdmfifo
Continuing ...



I'll fix this one too.

  

cp: cannot open `/var/named/chroot/proc/acpi/event' for reading: Device
or resou
rce busy
cp: reading `/var/named/chroot/proc/sys/net/ipv6/route/flush': Operation
not per
mitted
cp: reading `/var/named/chroot/proc/sys/net/ipv4/route/flush': Operation
not per
mitted
cp: reading `/var/named/chroot/proc/sysrq-trigger': Invalid argument



Hmmm, a chroot within a chroot. This is a problem all right. I'm surprised
to realize that I haven't tested this since I added named-chroot. I'm
getting a boatload of errors at this point too. I'm going to fix this right
now. I'll post to the list when it's fixed and tested, should be later today.

  

( here I pressed CTRL+C )
bash-3.00#




Thanks, Lucian.

  
Sometime ago I tested a postfix install and a qmail from original site 
install, maybe  that's why I have those files there. qmailtoaster is 
almost the last version and is working allright.


-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] errors during upgrading qt

[Eric \"Shubes\"]

Lucian Cristian wrote:
> I let the script to run all night (on 2000 mhz and 1 Gb of ram, 60 Gb
> free disk space/14 used) and it have the following output (sandbox is
> copyed, not linked)
> 
> <<
> ...
> Creating /opt/qtp-sandbox/var ...
> Unexpected named pipe: /var/spool/postfix/public/pickup
> prw--w--w-  1 89 89 0 May 18 09:46 /var/spool/postfix/public/pickup
> Continuing ...
> Unexpected named pipe: /var/spool/postfix/public/qmgr
> prw--w--w-  1 89 89 0 May 18 09:46 /var/spool/postfix/public/qmgr
> Continuing ...

This doesn't look kosher for a toaster:
1) Is postfix installed? I thought it couldn't coexist with qmail. Why does
/var/spool/postfix exist?
2) User:group 89:89 not defined? That should normally be vpopmail, but I
suppose it could be any other number.

> Unexpected named pipe: /var/service/qmail-pop3d/supervise/control
> prw---  1 root root 0 Dec  4  2005
> /var/service/qmail-pop3d/supervise/control
> Continuing ...
> Unexpected named pipe: /var/service/qmail-pop3d/supervise/ok
> prw---  1 root root 0 Dec  3  2005
> /var/service/qmail-pop3d/supervise/ok
> Continuing ...
> Unexpected named pipe: /var/service/qmail-pop3d/log/supervise/control
> prw---  1 root root 0 Dec  3  2005
> /var/service/qmail-pop3d/log/supervise/control
> Continuing ...
> Unexpected named pipe: /var/service/qmail-pop3d/log/supervise/ok
> prw---  1 root root 0 Dec  3  2005
> /var/service/qmail-pop3d/log/supervise/ok
> Continuing ...
> Unexpected named pipe: /var/service/qmail-send/supervise/control
> prw---  1 root root 0 Dec  3  2005
> /var/service/qmail-send/supervise/control
> Continuing ...
> Unexpected named pipe: /var/service/qmail-send/supervise/ok
> prw---  1 root root 0 Dec  3  2005 /var/service/qmail-send/supervise/ok
> Continuing ...
> Unexpected named pipe: /var/service/qmail-send/log/supervise/control
> prw---  1 root root 0 Dec  3  2005
> /var/service/qmail-send/log/supervise/control
> Continuing ...
> Unexpected named pipe: /var/service/qmail-send/log/supervise/ok
> prw---  1 root root 0 Dec  3  2005
> /var/service/qmail-send/log/supervise/ok
> Continuing ...
> Unexpected named pipe: /var/service/qmail-smtpd/supervise/control
> prw---  1 root root 0 Dec  4  2005
> /var/service/qmail-smtpd/supervise/control
> Continuing ...
> Unexpected named pipe: /var/service/qmail-smtpd/supervise/ok
> prw---  1 root root 0 Dec  3  2005
> /var/service/qmail-smtpd/supervise/ok
> Continuing ...
> Unexpected named pipe: /var/service/qmail-smtpd/log/supervise/control
> prw---  1 root root 0 Dec  3  2005
> /var/service/qmail-smtpd/log/supervise/control
> Continuing ...
> Unexpected named pipe: /var/service/qmail-smtpd/log/supervise/ok
> prw---  1 root root 0 Dec  3  2005
> /var/service/qmail-smtpd/log/supervise/ok
> Continuing ...

These are apparently from an older version. They are now in
/var/qmail/supervise/ instead of /var/service/. What toaster version are you
upgrading from?

This doesn't hurt anything, as they're not used. I'll update the script to
create them though (and thus get rid of the messages).

> Unexpected file type for /var/run/pure-ftpd/client-00011531
> ls: /var/run/pure-ftpd/client-00011531: No such file or directory
> Continuing ...

This was apparently (I'm guessing) a transient file from an ftp session that
disappeared during the run. I'll fix the script to handle the /var/run
directory more appropriately.

> Unexpected named pipe: /var/gdm/.gdmfifo
> prw-rw  1 root root 0 Oct 18  2005 /var/gdm/.gdmfifo
> Continuing ...

I'll fix this one too.

> cp: cannot open `/var/named/chroot/proc/acpi/event' for reading: Device
> or resou
> rce busy
> cp: reading `/var/named/chroot/proc/sys/net/ipv6/route/flush': Operation
> not per
> mitted
> cp: reading `/var/named/chroot/proc/sys/net/ipv4/route/flush': Operation
> not per
> mitted
> cp: reading `/var/named/chroot/proc/sysrq-trigger': Invalid argument

Hmmm, a chroot within a chroot. This is a problem all right. I'm surprised
to realize that I haven't tested this since I added named-chroot. I'm
getting a boatload of errors at this point too. I'm going to fix this right
now. I'll post to the list when it's fixed and tested, should be later today.

> ( here I pressed CTRL+C )
> bash-3.00#
> 

Thanks, Lucian.

-- 
-Eric 'shubes'

-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] errors during upgrading qt

[Lucian Cristian]

Eric "Shubes" wrote:

Lucian Cristian wrote:
  

I can't get past of  /var/named/chmod directory if BIND is installed
with chroot support




Please provide more details.

  
I let the script to run all night (on 2000 mhz and 1 Gb of ram, 60 Gb 
free disk space/14 used) and it have the following output (sandbox is 
copyed, not linked)


<<
...
Warning: This script does not check for available disk space.
You'll need anywhere from 100M (linked) to 2.4G+ (copied)
 to build the sandbox.
The sandbox may be built in any partition.
A 'linked' sandbox may only be in the / partition
The sandbox will be built at /opt/qtp-sandbox
Shall we continue? (yes, no|skip, quit) [y] / n|s / q : y
Creating Copied sandbox: /opt/qtp-sandbox ... (coffee anyone?)
Creating /opt/qtp-sandbox/backup ...
find: /backup: No such file or directory
Creating /opt/qtp-sandbox/bin ...
Creating /opt/qtp-sandbox/command ...
Creating /opt/qtp-sandbox/etc ...
Creating /opt/qtp-sandbox/lib ...
Creating /opt/qtp-sandbox/service ...
Creating /opt/qtp-sandbox/sbin ...
Creating /opt/qtp-sandbox/usr/bin ...
Creating /opt/qtp-sandbox/usr/etc ...
Creating /opt/qtp-sandbox/usr/include ...
Creating /opt/qtp-sandbox/usr/kerberos ...
Creating /opt/qtp-sandbox/usr/lib ...
Creating /opt/qtp-sandbox/usr/libexec ...
Creating /opt/qtp-sandbox/usr/local ...
Creating /opt/qtp-sandbox/usr/man ...
Creating /opt/qtp-sandbox/usr/sbin ...
Creating /opt/qtp-sandbox/usr/share ...
Creating /opt/qtp-sandbox/usr/src ...
Creating /opt/qtp-sandbox/usr/X11R6 ...
Creating /opt/qtp-sandbox/var ...
Unexpected named pipe: /var/spool/postfix/public/pickup
prw--w--w-  1 89 89 0 May 18 09:46 /var/spool/postfix/public/pickup
Continuing ...
Unexpected named pipe: /var/spool/postfix/public/qmgr
prw--w--w-  1 89 89 0 May 18 09:46 /var/spool/postfix/public/qmgr
Continuing ...
Unexpected named pipe: /var/service/qmail-pop3d/supervise/control
prw---  1 root root 0 Dec  4  2005 
/var/service/qmail-pop3d/supervise/control

Continuing ...
Unexpected named pipe: /var/service/qmail-pop3d/supervise/ok
prw---  1 root root 0 Dec  3  2005 /var/service/qmail-pop3d/supervise/ok
Continuing ...
Unexpected named pipe: /var/service/qmail-pop3d/log/supervise/control
prw---  1 root root 0 Dec  3  2005 
/var/service/qmail-pop3d/log/supervise/control

Continuing ...
Unexpected named pipe: /var/service/qmail-pop3d/log/supervise/ok
prw---  1 root root 0 Dec  3  2005 
/var/service/qmail-pop3d/log/supervise/ok

Continuing ...
Unexpected named pipe: /var/service/qmail-send/supervise/control
prw---  1 root root 0 Dec  3  2005 
/var/service/qmail-send/supervise/control

Continuing ...
Unexpected named pipe: /var/service/qmail-send/supervise/ok
prw---  1 root root 0 Dec  3  2005 /var/service/qmail-send/supervise/ok
Continuing ...
Unexpected named pipe: /var/service/qmail-send/log/supervise/control
prw---  1 root root 0 Dec  3  2005 
/var/service/qmail-send/log/supervise/control

Continuing ...
Unexpected named pipe: /var/service/qmail-send/log/supervise/ok
prw---  1 root root 0 Dec  3  2005 
/var/service/qmail-send/log/supervise/ok

Continuing ...
Unexpected named pipe: /var/service/qmail-smtpd/supervise/control
prw---  1 root root 0 Dec  4  2005 
/var/service/qmail-smtpd/supervise/control

Continuing ...
Unexpected named pipe: /var/service/qmail-smtpd/supervise/ok
prw---  1 root root 0 Dec  3  2005 /var/service/qmail-smtpd/supervise/ok
Continuing ...
Unexpected named pipe: /var/service/qmail-smtpd/log/supervise/control
prw---  1 root root 0 Dec  3  2005 
/var/service/qmail-smtpd/log/supervise/control

Continuing ...
Unexpected named pipe: /var/service/qmail-smtpd/log/supervise/ok
prw---  1 root root 0 Dec  3  2005 
/var/service/qmail-smtpd/log/supervise/ok

Continuing ...
Unexpected file type for /var/run/pure-ftpd/client-00011531
ls: /var/run/pure-ftpd/client-00011531: No such file or directory

Continuing ...
Unexpected named pipe: /var/gdm/.gdmfifo
prw-rw  1 root root 0 Oct 18  2005 /var/gdm/.gdmfifo
Continuing ...
cp: cannot open `/var/named/chroot/proc/acpi/event' for reading: Device 
or resou

rce busy
cp: reading `/var/named/chroot/proc/sys/net/ipv6/route/flush': Operation 
not per

mitted
cp: reading `/var/named/chroot/proc/sys/net/ipv4/route/flush': Operation 
not per

mitted
cp: reading `/var/named/chroot/proc/sysrq-trigger': Invalid argument

( here I pressed CTRL+C )
bash-3.00#

>>

The last line remained there all day until I pressed CTRL+C
Uninstalling named-chroot and rebooting !!! the server solved that 
problem. This machine can't be rebooted so easy, but the day will come :)


-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] errors during upgrading qt

[Eric \"Shubes\"]

Lucian Cristian wrote:
> I can't get past of  /var/named/chmod directory if BIND is installed
> with chroot support
> 

Please provide more details.

-- 
-Eric 'shubes'

-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] errors during upgrading qt

[Lucian Cristian]

[EMAIL PROTECTED] wrote:

I downloaded the upgrade scripts and encoutered the following errors
during upgrade

Continuing ...
Creating /opt/qtp-sandbox/home/vpopmail ...
Creating /opt/qtp-sandbox/ misc directories ...
Sandbox has been built successfully!

Starting to build the binary rpms ...(pizza anyone?)

If you want to view compile messages, you can open another terminal and:
# tail -f /opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log

qtp-build-rpms 0.1.3
cat: /usr/src/qtp-upgrade: Is a directory
qtp-build-rpms Error - package list not found
Build failed, Exiting.
[EMAIL PROTECTED] updates]#

Is there anyone has succeeded to upgrade qt using new-model script?

crispin.


-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

  
I can't get past of  /var/named/chmod directory if BIND is installed 
with chroot support


-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] errors during upgrading qt

[Eric \"Shubes\"]

[EMAIL PROTECTED] wrote:
> I downloaded the upgrade scripts and encoutered the following errors
> during upgrade
> 
> Continuing ...
> Creating /opt/qtp-sandbox/home/vpopmail ...
> Creating /opt/qtp-sandbox/ misc directories ...
> Sandbox has been built successfully!
> 
> Starting to build the binary rpms ...(pizza anyone?)
> 
> If you want to view compile messages, you can open another terminal and:
> # tail -f /opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log
> 
> qtp-build-rpms 0.1.3
> cat: /usr/src/qtp-upgrade: Is a directory
> qtp-build-rpms Error - package list not found
> Build failed, Exiting.
> [EMAIL PROTECTED] updates]#
> 
> Is there anyone has succeeded to upgrade qt using new-model script?
> 
> crispin.
> 
crispin,
I'm looking into it. Should have an answer/fix later today.

-- 
-Eric 'shubes'

-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[qmailtoaster] errors during upgrading qt

[ldap]

I downloaded the upgrade scripts and encoutered the following errors
during upgrade

Continuing ...
Creating /opt/qtp-sandbox/home/vpopmail ...
Creating /opt/qtp-sandbox/ misc directories ...
Sandbox has been built successfully!

Starting to build the binary rpms ...(pizza anyone?)

If you want to view compile messages, you can open another terminal and:
# tail -f /opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log

qtp-build-rpms 0.1.3
cat: /usr/src/qtp-upgrade: Is a directory
qtp-build-rpms Error - package list not found
Build failed, Exiting.
[EMAIL PROTECTED] updates]#

Is there anyone has succeeded to upgrade qt using new-model script?

crispin.


-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[qmailtoaster] Errors in Qmailtoaster..

[Stanley Robins]

rpm -qa | grep toaster [EMAIL PROTECTED] SRPMS]# rpm -qa |grep toastermaildrop-toaster-devel-1.8.1-1.2.10control-panel-toaster-0.5-1.2.8spamassassin-toaster-3.1.0-1.2.11vpopmail-toaster-5.4.10-1.2.10
qmailadmin-toaster-1.2.9-1.2.11ucspi-tcp-toaster-0.88-1.2.9courier-imap-toaster-3.0.8-1.2.9ezmlm-cgi-toaster-0.53.324-1.2.10vqadmin-toaster-2.3.4-1.2.12simscan-toaster-1.1-1.2.6daemontools-toaster-0.76-1.2.9
qmail-pop3d-toaster-1.03-1.2.10ezmlm-toaster-0.53.324-1.2.10isoqlog-toaster-2.1-1.2.9clamav-toaster-0.87.1-1.2.10qmail-toaster-1.03-1.2.10qmailmrtg-toaster-4.2-1.2.8autorespond-toaster-2.0.4-1.2.8
squirrelmail-toaster-1.4.5-1.2.13-- when i do this qmailctl start , i get this error messagemultilog: fatal: unable to lock directory /var/log/qmail/spamd: temporary failurewhen i open localhost/qmailadmin -- i get internal server error,,
What is wrong ??? My OS is Fedora Core 4.. 

RE: [qmailtoaster] Errors in SA

[Riezal Ross]

What's that command again? 'o conf make_install_arg UNINST=1*'? Doesn't
do anything.

[EMAIL PROTECTED] root]# rpm -qa | grep perl | sort
perl-5.8.0-89.10
perl-CGI-2.81-89.10
perl-CPAN-1.61-89.10
perl-DBD-MySQL-2.1021-3
perl-DB_File-1.808-8
perl-DBI-1.32-9
perl-Digest-HMAC-1.01-11.1
perl-Digest-SHA1-2.01-15.1
perl-Filter-1.29-3
perl-HTML-Parser-3.26-17
perl-HTML-Tagset-3.03-28
perl-Net-DNS-0.48-8
perl-Time-HiRes-1.38-3
perl-URI-1.21-7

A force install doesn't work either. So I manually removed the .gz and
it re-downloaded it. The same errors came up:
Checksum for y/sources/authors/id/A/AN/ANDK/CPAN-1.80.tar.gz ok
gzip: y/sources/authors/id/A/AN/ANDK/CPAN-1.80.tar.gz: No such file or
directory
gzip: y/sources/authors/id/A/AN/ANDK/CPAN-1.80.tar.gz: No such file or
directory
/bin/tar: y/sources/authors/id/A/AN/ANDK/CPAN-1.80.tar.gz: Cannot open:
No such file or directory
/bin/tar: Error is not recoverable: exiting now
Using Tar:/bin/tar xvf y/sources/authors/id/A/AN/ANDK/CPAN-1.80.tar.gz:
/bin/tar: y/sources/authors/id/A/AN/ANDK/CPAN-1.80.tar.gz: Cannot open:
No such file or directory
/bin/tar: Error is not recoverable: exiting now
Couldn't untar y/sources/authors/id/A/AN/ANDK/CPAN-1.80.tar.gz

Any other ideas? This is frustrating.

Regards,

Riezal Ross
Network Engineer / Project Manager 

-Original Message-
From: Jake Vickers [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, December 14, 2005 10:42 PM
To: qmailtoaster-list@qmailtoaster.com
Subject: Re: [qmailtoaster] Errors in SA


Riezal Ross wrote:

>First I tried changing local mirrors, it gave the same errors. I tried 
>using mirrors from other countries and it still gave the errors. I 
>suspect that it must've cached the .gz file as I already have it on my 
>machine. So I gave up on that.
>  
>
You may try removing the .gz file as a last resort. I'd try the 
following first:
In the CPAN shell (perl -MCPAN -e shell), do the following:
o conf make_install_arg UNINST=1*
*install Bundle::CPAN

If it asks you to append anything, always say yes.  If it gives you any 
errors, email them to me. We'll get the first part (CPAN) installed 
before we try and add things to it.  You're not running 2 versions of 
perl are you? I've known this to cause problems. Do a 'rpm -qa | grep 
perl | sort' and see if more than 1 version of perl is living on your 
machine.
Also in the perl shell, try 'reload cpan' and see what it yells at you 
about. I'm sure you have them open, but I don't remember which port it 
downloads the modules on - it would be either 21 or 80.  If fulfilling 
the requirements for Bundle::CPAN still doesn't work, you can also try 
forcing it:
force install Bundle::CPAN

*

*

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] Errors in SA

[Jake Vickers]

Riezal Ross wrote:


First I tried changing local mirrors, it gave the same errors. I tried
using mirrors from other countries and it still gave the errors. I
suspect that it must've cached the .gz file as I already have it on my
machine. So I gave up on that.
 

You may try removing the .gz file as a last resort. I'd try the 
following first:

In the CPAN shell (perl -MCPAN -e shell), do the following:
o conf make_install_arg UNINST=1*
*install Bundle::CPAN

If it asks you to append anything, always say yes.  If it gives you any 
errors, email them to me. We'll get the first part (CPAN) installed 
before we try and add things to it.  You're not running 2 versions of 
perl are you? I've known this to cause problems. Do a 'rpm -qa | grep 
perl | sort' and see if more than 1 version of perl is living on your 
machine.
Also in the perl shell, try 'reload cpan' and see what it yells at you 
about. I'm sure you have them open, but I don't remember which port it 
downloads the modules on - it would be either 21 or 80.  If fulfilling 
the requirements for Bundle::CPAN still doesn't work, you can also try 
forcing it:

force install Bundle::CPAN

*

*

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [qmailtoaster] Errors in SA

[Riezal Ross]

First I tried changing local mirrors, it gave the same errors. I tried
using mirrors from other countries and it still gave the errors. I
suspect that it must've cached the .gz file as I already have it on my
machine. So I gave up on that.

Tried the RPM site with all the perl stuff. Downloaded and did a rpm
-Uvh of the rpm I downloaded. It gave me a newer version of perl-CPAN.
After that I got the 'Can't locate CPAN.pm in @INC' again, so I
re-installed the previous version I had using yum.

Failing both of that, I decided to install Net::DNS using the RPM site
you provided. Ran spamassassin -D --lint again and this time it spewed
this:
[25813] dbg: bayes: DB_File module not installed, cannot use bayes
[25813] dbg: config: score set 1 chosen.
[25813] dbg: message:  MIME PARSER START 
[25813] dbg: message: main message type: text/plain
[25813] dbg: message: parsing normal part
[25813] dbg: message: added part, type: text/plain
[25813] dbg: message:  MIME PARSER END 
[25813] dbg: bayes: DB_File module not installed, cannot use bayes
[25813] dbg: dns: is Net::DNS::Resolver available? no
[25813] dbg: dns: is DNS available? 0

So the Net::DNS error wasn't there anymore, but I'm not sure if that got
it fixed or not. Then I thought I might as well install the DB_File
module as well, seeing that spamassassin was complaining about it. rpm
-q perl-DB_File shows perl-DB_File-1.808-8 is installed. Yet, it still
shows 'dbg: bayes: DB_File module not installed, cannot use bayes'

Any ideas?

Regards,

Riezal Ross

-Original Message-
From: Jake Vickers [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, December 13, 2005 9:30 PM
To: qmailtoaster-list@qmailtoaster.com
Subject: Re: [qmailtoaster] Errors in SA


Riezal Ross wrote:

>I actually checked the directory and found that those files do exist in

>root/.spamassassin/y/sources/authors/id/A/AN/ANDK/CPAN-1.80.tar.gz and 
>I am running CPAN from /root/.spamassassin
>
>  
>
You might try installing Bundle::CPAN from this location also; they 
package the perl modules every night into RPM format:
http://www.quantumlinux.com/~kevin/rpmpan/rpm/perl-CPAN-1.76-8.noarch.rp
m
Parent site is http://rpmpan.sourceforge.net/


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] Errors in SA

[Jake Vickers]

Riezal Ross wrote:


I actually checked the directory and found that those files do exist in
root/.spamassassin/y/sources/authors/id/A/AN/ANDK/CPAN-1.80.tar.gz and I
am running CPAN from /root/.spamassassin

 

You might try installing Bundle::CPAN from this location also; they 
package the perl modules every night into RPM format:

http://www.quantumlinux.com/~kevin/rpmpan/rpm/perl-CPAN-1.76-8.noarch.rpm
Parent site is http://rpmpan.sourceforge.net/


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] Errors in SA

[Jake Vickers]

Riezal Ross wrote:


I actually checked the directory and found that those files do exist in
root/.spamassassin/y/sources/authors/id/A/AN/ANDK/CPAN-1.80.tar.gz and I
am running CPAN from /root/.spamassassin

 

That's not where it's trying to pull the file from, though. You may have 
selected a mirror (and it looks like you only selected one) that has 
gone down for some reason.

If you can get into CPAN at all (perl -MCPAN -e shell), then run this:
cpan>o conf init
And that should allow you to reconfigure your perl so you can select 
different mirrors and such. If not, we'll try something else.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [qmailtoaster] Errors in SA

[Riezal Ross]

I actually checked the directory and found that those files do exist in
root/.spamassassin/y/sources/authors/id/A/AN/ANDK/CPAN-1.80.tar.gz and I
am running CPAN from /root/.spamassassin

>Checksum for y/sources/authors/id/A/AN/ANDK/CPAN-1.80.tar.gz ok
>gzip: y/sources/authors/id/A/AN/ANDK/c: No such file or 
>directory
>  
>
Looks like the sources you're trying to get the packages from don't have

the files. Did you try installing the 2 I suggested? I still need to 
know what distro you're using. I had a site bookmarked that had all the 
perl modules built as RPMs Probably on my work-pc, so I'll check 
that in the morning.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [qmailtoaster] Errors in SA

[Riezal Ross]

I tried installing Net::DNS and Bundle::CPAN, both returned the same
sort of errors. As you said, they cant seem to find the files. My distro
is CentOS release 3.5 (Final).

What should I do to get CPAN installing all these necessary modules?

Regards,

Riezal Ross


-Original Message-
From: Jake Vickers [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, December 13, 2005 10:22 AM
To: qmailtoaster-list@qmailtoaster.com
Subject: Re: [qmailtoaster] Errors in SA


Riezal Ross wrote:

>Silly me, I didn't have CPAN install. I did a yum install perl-CPAN and

>it went of. I installed the modules recommended by Nick: 
>Mail::SpamAssassin::Plugin::Pyzor
>  IP::Country::Fast
>  IO::Socket::SSL
>  Archive::Tar
>  IO::Zlib
>
>Some of them worked, some returned errors. Lastly, I installed 
>Bundle::CPAN and it returned the following error:
>
>
>
>Checksum for y/sources/authors/id/A/AN/ANDK/CPAN-1.80.tar.gz ok
>gzip: y/sources/authors/id/A/AN/ANDK/CPAN-1.80.tar.gz: No such file or 
>directory
>  
>
Looks like the sources you're trying to get the packages from don't have

the files. Did you try installing the 2 I suggested? I still need to 
know what distro you're using. I had a site bookmarked that had all the 
perl modules built as RPMs Probably on my work-pc, so I'll check 
that in the morning.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] Errors in SA

[Jake Vickers]

Riezal Ross wrote:


Silly me, I didn't have CPAN install. I did a yum install perl-CPAN and
it went of. I installed the modules recommended by Nick:
Mail::SpamAssassin::Plugin::Pyzor
 IP::Country::Fast
 IO::Socket::SSL
 Archive::Tar
 IO::Zlib

Some of them worked, some returned errors. Lastly, I installed
Bundle::CPAN and it returned the following error:



Checksum for y/sources/authors/id/A/AN/ANDK/CPAN-1.80.tar.gz ok
gzip: y/sources/authors/id/A/AN/ANDK/CPAN-1.80.tar.gz: No such file or
directory
 

Looks like the sources you're trying to get the packages from don't have 
the files. Did you try installing the 2 I suggested? I still need to 
know what distro you're using. I had a site bookmarked that had all the 
perl modules built as RPMs Probably on my work-pc, so I'll check 
that in the morning.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [qmailtoaster] Errors in SA

[Riezal Ross]

Silly me, I didn't have CPAN install. I did a yum install perl-CPAN and
it went of. I installed the modules recommended by Nick:
Mail::SpamAssassin::Plugin::Pyzor
  IP::Country::Fast
  IO::Socket::SSL
  Archive::Tar
  IO::Zlib

Some of them worked, some returned errors. Lastly, I installed
Bundle::CPAN and it returned the following error:



Checksum for y/sources/authors/id/A/AN/ANDK/CPAN-1.80.tar.gz ok
gzip: y/sources/authors/id/A/AN/ANDK/CPAN-1.80.tar.gz: No such file or
directory
gzip: y/sources/authors/id/A/AN/ANDK/CPAN-1.80.tar.gz: No such file or
directory
/bin/tar: y/sources/authors/id/A/AN/ANDK/CPAN-1.80.tar.gz: Cannot open:
No such file or directory
/bin/tar: Error is not recoverable: exiting now
Using Tar:/bin/tar xvf y/sources/authors/id/A/AN/ANDK/CPAN-1.80.tar.gz:
/bin/tar: y/sources/authors/id/A/AN/ANDK/CPAN-1.80.tar.gz: Cannot open:
No such file or directory
/bin/tar: Error is not recoverable: exiting now
Couldn't untar y/sources/authors/id/A/AN/ANDK/CPAN-1.80.tar.gz

Doesn't seem too happy. I haven't tried doing spamassassin -D --lint
yet, coz it doesn't look like Bundle::CPAN installed successfully?

Regards,

Riezal Ross


-Original Message-
From: Jake Vickers [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, December 13, 2005 10:10 AM
To: qmailtoaster-list@qmailtoaster.com
Subject: Re: [qmailtoaster] Errors in SA


Riezal Ross wrote:

>I get this error when using CPAN:
>
>[EMAIL PROTECTED] .spamassassin]# perl -MCPAN -e shell
>Can't locate CPAN.pm in @INC
>
>That file doesn't seem to exist anywhere on my system. Is there any 
>other way to do the upgrade? Or can you point my in the right direction

>to get my CPAN running?
>  
>
Try this:
yum install perl-DBI libdbi

I think one of those packages will solve your problem. Let me know if it

doesn't. And what distro you've got installed.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] Errors in SA

[Jake Vickers]

Riezal Ross wrote:


I get this error when using CPAN:

[EMAIL PROTECTED] .spamassassin]# perl -MCPAN -e shell
Can't locate CPAN.pm in @INC 


That file doesn't seem to exist anywhere on my system. Is there any
other way to do the upgrade? Or can you point my in the right direction
to get my CPAN running?
 


Try this:
yum install perl-DBI libdbi

I think one of those packages will solve your problem. Let me know if it 
doesn't. And what distro you've got installed.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [qmailtoaster] Errors in SA

[Riezal Ross]

I get this error when using CPAN:

[EMAIL PROTECTED] .spamassassin]# perl -MCPAN -e shell
Can't locate CPAN.pm in @INC 

That file doesn't seem to exist anywhere on my system. Is there any
other way to do the upgrade? Or can you point my in the right direction
to get my CPAN running?

Regards,

Riezal Ross



-Original Message-
From: Jake Vickers [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, December 13, 2005 9:29 AM
To: qmailtoaster-list@qmailtoaster.com
Subject: Re: [qmailtoaster] Errors in SA


Riezal Ross wrote:

>
> /[3738] dbg: bayes: DB_File module not installed, cannot use
bayes/
> /[3738] warn: dns: Net::DNS version is 0.31, but need 0.34 at
> /usr/lib/perl5/vendor_perl/5.8.0/Mail/SpamAssassin/Dns.pm line 
> 589./
>
> Cannot use bayes? Also, when I do sa-learn --spam against a mail
> in my ../Maildir/.Spam/new/ directory, it returns this error:
>
> /[EMAIL PROTECTED] new]# sa-learn --spam
> 
> 1133490574.M794156P14002V0803I003D8004.mail.cisasia.com.my
> \,S\=10123/
>
> /dns: Net::DNS version is 0.31, but need 0.34 at
> /usr/lib/perl5/vendor_perl/5.8.0/Mail/SpamAssassin/Dns.pm line
589./
> /Learned tokens from 0 message(s) (1 message(s) examined)/
> /ERROR: the Bayes learn function returned an error, please re-run
> with -D for more information/
>
Can't remember if I posted on this yet or not.  Have you tried 
installing Bundle::CPAN yet in perl?  I remember someone was having 
trouble with this, just not if it was you or not.  I can dig up some RH 
RPMS for these packages if you need them, or are uncomfortable upgrading

CPAN.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] Errors in SA

[Jake Vickers]

Riezal Ross wrote:



/[3738] dbg: bayes: DB_File module not installed, cannot use bayes/
/[3738] warn: dns: Net::DNS version is 0.31, but need 0.34 at
/usr/lib/perl5/vendor_perl/5.8.0/Mail/SpamAssassin/Dns.pm line 589./

Cannot use bayes? Also, when I do sa-learn --spam against a mail
in my ../Maildir/.Spam/new/ directory, it returns this error:

/[EMAIL PROTECTED] new]# sa-learn --spam

1133490574.M794156P14002V0803I003D8004.mail.cisasia.com.my\,S\=10123/

/dns: Net::DNS version is 0.31, but need 0.34 at
/usr/lib/perl5/vendor_perl/5.8.0/Mail/SpamAssassin/Dns.pm line 589./
/Learned tokens from 0 message(s) (1 message(s) examined)/
/ERROR: the Bayes learn function returned an error, please re-run
with -D for more information/

Can't remember if I posted on this yet or not.  Have you tried 
installing Bundle::CPAN yet in perl?  I remember someone was having 
trouble with this, just not if it was you or not.  I can dig up some RH 
RPMS for these packages if you need them, or are uncomfortable upgrading 
CPAN.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [qmailtoaster] Errors in SA

[Riezal Ross]

Title: Message



Anybody has any idea what's wrong with my bayes 
setup? 
Regards, 
Riezal Ross 
 
 -Original Message-From: 
Riezal Ross [mailto:[EMAIL PROTECTED] Sent: Wednesday, 
December 07, 2005 4:49 PMTo: 
qmailtoaster-list@qmailtoaster.comSubject: [qmailtoaster] Errors in 
SA 

  I'm still trying to get a grip on things here. I've 
  just re-installed the new spamassassin-toaster and it looks to be booting up 
  fine with no issues. When I run spamassassin -D --lint, it spews a whole lot 
  of messages. There is one part that I'm concerned about:
  [3738] dbg: bayes: DB_File module not installed, 
  cannot use bayes [3738] dbg: config: 
  score set 1 chosen. [3738] dbg: 
  message:  MIME PARSER START  [3738] dbg: message: main message type: text/plain 
  [3738] dbg: message: parsing normal 
  part [3738] dbg: message: added 
  part, type: text/plain [3738] dbg: 
  message:  MIME PARSER END  [3738] dbg: bayes: DB_File module not installed, cannot use 
  bayes [3738] warn: dns: Net::DNS 
  version is 0.31, but need 0.34 at 
  /usr/lib/perl5/vendor_perl/5.8.0/Mail/SpamAssassin/Dns.pm line 
  589.
  Cannot use bayes? Also, when I do sa-learn --spam 
  against a mail in my ../Maildir/.Spam/new/ directory, it returns this 
  error:
  [EMAIL PROTECTED] new]# sa-learn --spam 
  1133490574.M794156P14002V0803I003D8004.mail.cisasia.com.my\,S\=10123 
  dns: Net::DNS version is 0.31, but need 0.34 at 
  /usr/lib/perl5/vendor_perl/5.8.0/Mail/SpamAssassin/Dns.pm line 589. 
  Learned tokens from 0 message(s) (1 message(s) 
  examined) ERROR: the Bayes learn 
  function returned an error, please re-run with -D for more 
  information 
  Clearly both of them don't like the dns: Net::DNS version. I 
  am not sure what the above means, but could someone tell me what I'm doing 
  wrong? Or at least point me in the right direction? Thanks in 
  advanced.
  Regards, 
  Riezal Ross 

Re: [qmailtoaster] Errors in SA

[Jake Vickers]

Riezal Ross wrote:

I'm still trying to get a grip on things here. I've just re-installed 
the new spamassassin-toaster and it looks to be booting up fine with 
no issues. When I run spamassassin -D --lint, it spews a whole lot of 
messages. There is one part that I'm concerned about:


/[3738] dbg: bayes: DB_File module not installed, cannot use bayes/
/[3738] dbg: config: score set 1 chosen./
/[3738] dbg: message:  MIME PARSER START /
/[3738] dbg: message: main message type: text/plain/
/[3738] dbg: message: parsing normal part/
/[3738] dbg: message: added part, type: text/plain/
/[3738] dbg: message:  MIME PARSER END /
/[3738] dbg: bayes: DB_File module not installed, cannot use bayes/
/[3738] warn: dns: Net::DNS version is 0.31, but need 0.34 at 
/usr/lib/perl5/vendor_perl/5.8.0/Mail/SpamAssassin/Dns.pm line 589./


Cannot use bayes? Also, when I do sa-learn --spam against a mail in my 
../Maildir/.Spam/new/ directory, it returns this error:


/[EMAIL PROTECTED] new]# sa-learn --spam 
1133490574.M794156P14002V0803I003D8004.mail.cisasia.com.my\,S\=10123/ 

/dns: Net::DNS version is 0.31, but need 0.34 at 
/usr/lib/perl5/vendor_perl/5.8.0/Mail/SpamAssassin/Dns.pm line 589./

/Learned tokens from 0 message(s) (1 message(s) examined)/
/ERROR: the Bayes learn function returned an error, please re-run with 
-D for more information/


Clearly both of them don't like the/ dns: Net::DNS version./ I am not 
sure what the above means, but could someone tell me what I'm doing 
wrong? Or at least point me in the right direction? Thanks in advanced.


Net::DNS is a perl module.  Do 'perl -MCPAN -e shell' and then 'install 
Bundle::CPAN' while in there. That will at least load the "default" 
packages for you. Net::DNS is included with the CPAN Bundle.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[qmailtoaster] Errors in SA

[Riezal Ross]

Title: Errors in SA 






I'm still trying to get a grip on things here. I've just re-installed the new spamassassin-toaster and it looks to be booting up fine with no issues. When I run spamassassin -D --lint, it spews a whole lot of messages. There is one part that I'm concerned about:

[3738] dbg: bayes: DB_File module not installed, cannot use bayes

[3738] dbg: config: score set 1 chosen.

[3738] dbg: message:  MIME PARSER START 

[3738] dbg: message: main message type: text/plain

[3738] dbg: message: parsing normal part

[3738] dbg: message: added part, type: text/plain

[3738] dbg: message:  MIME PARSER END 

[3738] dbg: bayes: DB_File module not installed, cannot use bayes

[3738] warn: dns: Net::DNS version is 0.31, but need 0.34 at /usr/lib/perl5/vendor_perl/5.8.0/Mail/SpamAssassin/Dns.pm line 589.

Cannot use bayes? Also, when I do sa-learn --spam against a mail in my ../Maildir/.Spam/new/ directory, it returns this error:

[EMAIL PROTECTED] new]# sa-learn --spam 1133490574.M794156P14002V0803I003D8004.mail.cisasia.com.my\,S\=10123

dns: Net::DNS version is 0.31, but need 0.34 at /usr/lib/perl5/vendor_perl/5.8.0/Mail/SpamAssassin/Dns.pm line 589.

Learned tokens from 0 message(s) (1 message(s) examined)

ERROR: the Bayes learn function returned an error, please re-run with -D for more information


Clearly both of them don't like the dns: Net::DNS version. I am not sure what the above means, but could someone tell me what I'm doing wrong? Or at least point me in the right direction? Thanks in advanced.


Regards,


Riezal Ross