RE: HELP: getting an "error flushing read input" after updating s ome packets on debian

"Patzelt, Holger" <[email protected]>
Newsgroups gmane.comp.bug-tracking.gnats.general
Message-ID <[email protected]>
hi,

it's not the "debian gnats" we are using (sinc it is v4 as you mentioned)
we have (should I say "had"?) a running v3 gnats db with customers used to
it,
 so this is why we are still stuck with it.

No, it must be something with the gnatsweb vs. new(er) perl.

--
Holger D. Patzelt
Condat AG, Alt-Moabit 91d, 10559 Berlin, Germany
Tel: +49.30.39 49 - 11 93 | Fax: +49.30.39 49 222 11 93
http://www.condat.de | mailto:[email protected]
--
At the point you depend on it,
you get to know your real strength

>-----Original Message-----
>From: Chad Walstrom [mailto:[email protected]]
>Sent: Tuesday, November 23, 2004 7:04 PM
>To: Patzelt, Holger
>Cc: [email protected]
>Subject: Re: HELP: getting an "error flushing read input" 
>after updating
>some packets on debian
>
>
>Holger Patzelt wrote:
>> After I installed some new packets (and updated some others
>> automatically) on my debian woody (testing) I get an "error flushing
>> read input" when trying to change the responsible using gnatsweb 2
>> (and gnats 3. corresp.)
>
>Sounds like a gnatsweb version mismatch.  The gnats and gnats-user
>packages on woody are essentially gnats 4.0, or very close to it.  You
>should definitely NOT be using gnatsweb v2.x  You should most 
>definitely
>be using gnatsweb v4.00 or greater.
>
>    http://ftp.gnu.org/pub/gnu/gnatsweb/
>
>-- 
>Chad Walstrom <[email protected]>           http://www.wookimus.net/
>           assert(expired(knowledge)); /* core dump */
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.