Gnus development mailing list
 help / color / mirror / Atom feed
From: Tassilo Horn <tassilo@member.fsf.org>
To: ding@gnus.org
Subject: Archive group broken since very recently
Date: Wed, 15 Sep 2010 18:04:10 +0200	[thread overview]
Message-ID: <201009151804.11061.tassilo@member.fsf.org> (raw)

Hi all,

I use the gnus version that comes with emacs 24 from bzr.  Since my last
update, my archive group is broken.  The definition is as follows:

--8<---------------cut here---------------start------------->8---
(setq gnus-update-message-archive-method t
      gnus-message-archive-method
      `(nnml "archive"
             (nnml-inhibit-expiry t)
             (nnml-get-new-mail   nil)
             (nnml-directory      ,(expand-file-name "archive" gnus-
directory))
             (nnml-active-file    ,(expand-file-name
				    "active"
				    (expand-file-name "archive" gnus-
directory)))))
--8<---------------cut here---------------end--------------->8---

When posting to some group, it seems the message is correctly saved.  At
least that's in *Messages*:

--8<---------------cut here---------------start------------->8---
Wrote /home/horn/.gnus.d/News/archive/sent-postings/762
20100915T175512.137> Opening nnml server on archive+nnml+archive:sent-
postings...
20100915T175512.137> Opening nnml server on archive+nnml+archive:sent-
postings...done
Sending...done
--8<---------------cut here---------------end--------------->8---

But I cannot enter the archive group (nnml+archive:sent-postings)
anymore.  RET RET on it gives:

--8<---------------cut here---------------start------------->8---
20100915T180005.759> Retrieving newsgroup: nnml+archive:sent-postings...
20100915T180006.431> Fetching headers for nnml+archive:sent-postings...
20100915T180006.433> nnml: Receiving headers... 2%
20100915T180006.434> nnml: Receiving headers... 5%
20100915T180006.435> nnml: Receiving headers... 7%
20100915T180006.436> nnml: Receiving headers... 10%
20100915T180006.438> nnml: Receiving headers... 13%
20100915T180006.439> nnml: Receiving headers... 15%
20100915T180006.440> nnml: Receiving headers... 18%
20100915T180006.441> nnml: Receiving headers... 21%
20100915T180006.443> nnml: Receiving headers... 23%
20100915T180006.444> nnml: Receiving headers... 26%
20100915T180006.445> nnml: Receiving headers... 28%
20100915T180006.446> nnml: Receiving headers... 31%
20100915T180006.447> nnml: Receiving headers... 34%
20100915T180006.449> nnml: Receiving headers... 36%
20100915T180006.450> nnml: Receiving headers... 39%
20100915T180006.451> nnml: Receiving headers... 42%
20100915T180006.452> nnml: Receiving headers... 44%
20100915T180006.453> nnml: Receiving headers... 47%
20100915T180006.454> nnml: Receiving headers... 49%
20100915T180006.456> nnml: Receiving headers... 52%
20100915T180006.457> nnml: Receiving headers... 55%
20100915T180006.458> nnml: Receiving headers... 57%
20100915T180006.459> nnml: Receiving headers... 60%
20100915T180006.460> nnml: Receiving headers... 63%
20100915T180006.464> nnml: Receiving headers... 65%
20100915T180006.465> nnml: Receiving headers... 68%
20100915T180006.466> nnml: Receiving headers... 70%
20100915T180006.468> nnml: Receiving headers... 73%
20100915T180006.469> nnml: Receiving headers... 76%
20100915T180006.470> nnml: Receiving headers... 78%
20100915T180006.472> nnml: Receiving headers... 81%
20100915T180006.473> nnml: Receiving headers... 84%
20100915T180006.474> nnml: Receiving headers... 86%
20100915T180006.475> nnml: Receiving headers... 89%
20100915T180006.476> nnml: Receiving headers... 91%
20100915T180006.477> nnml: Receiving headers... 94%
20100915T180006.478> nnml: Receiving headers... 97%
20100915T180006.479> nnml: Receiving headers... 99%
20100915T180006.480> nnml: Receiving headers...done
20100915T180006.481> Fetching headers for nnml+archive:sent-
postings...done
20100915T180006.489> Scoring...
20100915T180006.490> Scoring...done
20100915T180006.491> No articles in the group
20100915T180006.493> No more unread newsgroups
20100915T180006.494> No unread news
--8<---------------cut here---------------end--------------->8---

And to make things even more strange, there are now several archive
servers in the server buffer!

--8<---------------cut here---------------start------------->8---
     {nnml:archive} (opened)
     {nnml:archive} (opened)
     {nnml:archive+nnml+archive:sent-postings} (opened)
     {nntp:Uni} (opened) (agent)
     {nntp:Gmane} (opened) (agent)
     {nntp:Eclipse} (opened) (agent)
--8<---------------cut here---------------end--------------->8---

The former two contain my sent-postings group, but hitting RET on that
group takes me back to *Group* with the same entries in *Messages* plus
the line

  gnus-browse-read-group: Couldn't enter nnml+archive:sent-postings

The server {nnml:archive+nnml+archive:sent-postings} is empty.

Any ideas?

Bye,
Tassilo



             reply	other threads:[~2010-09-15 16:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-15 16:04 Tassilo Horn [this message]
2010-09-16  1:21 ` Katsumi Yamaoka
2010-09-16 10:26   ` Tassilo Horn
2010-09-16 18:00     ` Lars Magne Ingebrigtsen
2010-09-16 19:03       ` Tassilo Horn
2010-09-17  1:25         ` Lars Magne Ingebrigtsen
2010-09-17  8:09           ` Tassilo Horn
2010-09-17 15:51             ` Lars Magne Ingebrigtsen
2010-09-17 18:40               ` Tassilo Horn
2010-09-17 19:13                 ` Lars Magne Ingebrigtsen
2010-09-17 19:17                   ` Tassilo Horn
2010-09-17 19:24                     ` Lars Magne Ingebrigtsen
2010-09-17 21:57                       ` Tassilo Horn
2010-09-18 17:16                         ` Lars Magne Ingebrigtsen
2010-09-19  8:24                           ` Tassilo Horn

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=201009151804.11061.tassilo@member.fsf.org \
    --to=tassilo@member.fsf.org \
    --cc=ding@gnus.org \
    /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).