unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stephen Berman <Stephen.Berman@gmx.net>
To: emacs-devel@gnu.org
Cc: emacs-pretest-bug@gnu.org, ding@gnus.org
Subject: Re: 23.0.60; File corruption when Gnus reads .overview
Date: Fri, 28 Mar 2008 23:00:27 +0100	[thread overview]
Message-ID: <87k5jm5x1g.fsf@escher.local.home> (raw)
In-Reply-To: <v91w5vopgc.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Thu, 27 Mar 2008 21:57:07 +0100")

On Thu, 27 Mar 2008 21:57:07 +0100 Reiner Steib <reinersteib+gmane@imap.cc> wrote:

> On Fri, Mar 14 2008, Stephen Berman wrote:
>
>> With my current build (GNU Emacs 23.0.60.1 (i686-pc-linux-gnu, GTK+
>> Version 2.12.0) of 2008-03-13 on escher), the file corruption has
>> disappeared, but Gnus still has a problem with the .overview file: when
>> I open the gmane.emacs.help group, all my marks are gone except the one
>> corresponding to the entry in the .overview file that occurs earlier
>> than the first entry containing the problematic non-ascii characters.
>> In other words, it appears that Gnus is not processing the .overview
>> file after it reads the problematic non-ascii characters.  I would be
>> grateful if a Gnus hacker could look into this, as I cannot usefully
>> read gmane.emacs.help with Gnus from the current trunk.
>
> It's the agent cache overview, right?  I don't use the agent, so I'm
> not familiar with it, but IIRC it's no problem to delete the corrupt
> overview file.  Does this help?

This does not help: after deleting the .overview file from
News/agent/nntp/news.gmane.org/gmane/emacs/help (but retaining the
corresponding .agentview file), all marked (ticked) articles, as well as
all seen but unread articles, are missing from the summary buffer.
However, the good news is that bug has apparently been fixed in the mean
time: I updated from the trunk today and after opening gmane.emacs.help
with Gnus all the marks were intact, and remained so after closing and
reopening.  This is with the previous 14 MB .overview file reinstated.
(I was sent an email on March 19 from the testbed Emacs bugtracker
saying that Stefan Monnier had closed the bug, but it didn't give
details and I cannot tell from the change logs which change contains the
fix (I was away when the email was sent and wasn't able to update until
today).)

Steve Berman




      parent reply	other threads:[~2008-03-28 22:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-07 10:54 23.0.60; File corruption when Gnus reads .overview Stephen Berman
2008-03-14  9:14 ` Stephen Berman
2008-03-27 20:57   ` Reiner Steib
2008-03-28  1:09     ` Leo
2008-03-28  9:10       ` Tassilo Horn
2008-03-28 18:18         ` Reiner Steib
2008-03-28 21:18           ` Tassilo Horn
2008-03-28 22:00     ` Stephen Berman [this message]

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=87k5jm5x1g.fsf@escher.local.home \
    --to=stephen.berman@gmx.net \
    --cc=ding@gnus.org \
    --cc=emacs-devel@gnu.org \
    --cc=emacs-pretest-bug@gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).