Gnus development mailing list
 help / color / mirror / Atom feed
From: Harry Putnam <reader@newsguy.com>
Subject: Re: Update to CVS breaks for me
Date: Fri, 08 Mar 2002 17:48:50 -0800	[thread overview]
Message-ID: <m14rjqseuk.fsf@reader.newsguy.com> (raw)
In-Reply-To: <87y9h3f1p7.fsf@delphi.lan-ks.de> (Jochen Hein's message of "Fri, 08 Mar 2002 17:45:24 +0100")

Jochen Hein <jochen@jochen.org> writes:

> But why did it break, and why couldn't I find any hint with
> gnus-verbose set to 9?  For now it is fixed for me, but the error
> message has *not* helped in finding the problem - which I consider a
> bug.

You didn't say if regenerating the nov files did any good.

Like this: M-x generate-nov-data-bases-1 <RET> /path/to/mail.misc-2002

If you don't have long filenames enabled that will be
~/Mail/mail/misc-2002

Other wise:
~/Mail/mail.misc-2002

If it asks you to create a group.  Something is wrong.  Find that
group on your file system and give its full name at the prompt.

You could also delete or rename .overview in that group first.

Looking at your output somemore.. I don't ever see output like that:
Fetching headers for nnml+private:mail.misc-2002...

I never see anything about fetching headers on nnml groups in
*Messages* on startup or any other time.  Only on agentized newsgoups.

You didn't some how get that nnml server under the agent did you?
Depending on your version, you might be able to tell by looking in
server buffer (^) and see if you see (agent) next to it.



  parent reply	other threads:[~2002-03-09  1:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87zo1l1qgk.fsf@delphi.lan-ks.de>
2002-03-06 18:57 ` Karl Kleinpaste
2002-03-06 18:57 ` Karl Kleinpaste
     [not found]   ` <87wuwplboq.fsf@delphi.lan-ks.de>
2002-03-07  5:05     ` Harry Putnam
     [not found]       ` <87y9h3f1p7.fsf@delphi.lan-ks.de>
2002-03-09  1:48         ` Harry Putnam [this message]
2002-03-09  1:48         ` Harry Putnam
2002-03-07  5:05     ` Harry Putnam

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m14rjqseuk.fsf@reader.newsguy.com \
    --to=reader@newsguy.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).