Have compiled the SRPM and your patch appears to solve the problem.

Thanks


Godfrey



[EMAIL PROTECTED] wrote:

> OK, you have made the big time:
>
> Version 3.3.22 - Sun Aug 20 11:24:02 PDT 2000
>  The 'read from parallel port' code caused status@
>   to be ignored.  Just a tad aggressive on this,  I was.
>  (Reported by: Godfrey <[EMAIL PROTECTED]>)
>
> > From [EMAIL PROTECTED] Sat Aug 19 21:28:22 2000
> > Date: Sun, 20 Aug 2000 15:34:56 +1200
> > From: Godfrey <[EMAIL PROTECTED]>
> > To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
> > Subject: LPRng: status@ no longer works?
> >
> > I have upgraded to
> >
> > LPRng 3.6.24
> >
> > and I get the following error which I did not get with 3.6.22
> >
>
> All by yourself on this one... :-)
>
> Patrick
>
> -----------------------------------------------------------------------------
> If you need help, send email to [EMAIL PROTECTED] (or lprng-requests
> or lprng-digest-requests) with the word 'help' in the body.  For the impatient,
> to subscribe to a list with name LIST,  send mail to [EMAIL PROTECTED]
> with:                           | example:
> subscribe LIST <mailaddr>       |  subscribe lprng-digest [EMAIL PROTECTED]
> unsubscribe LIST <mailaddr>     |  unsubscribe lprng [EMAIL PROTECTED]
>
> If you have major problems,  send email to [EMAIL PROTECTED] with the word
> LPRNGLIST in the SUBJECT line.
> -----------------------------------------------------------------------------


-----------------------------------------------------------------------------
If you need help, send email to [EMAIL PROTECTED] (or lprng-requests
or lprng-digest-requests) with the word 'help' in the body.  For the impatient,
to subscribe to a list with name LIST,  send mail to [EMAIL PROTECTED]
with:                           | example:
subscribe LIST <mailaddr>       |  subscribe lprng-digest [EMAIL PROTECTED]
unsubscribe LIST <mailaddr>     |  unsubscribe lprng [EMAIL PROTECTED]

If you have major problems,  send email to [EMAIL PROTECTED] with the word
LPRNGLIST in the SUBJECT line.
-----------------------------------------------------------------------------

Reply via email to