From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: Re: Crash on startup with recent gnus-agent.el patch
Date: Tue, 30 May 2006 17:34:38 +0900 [thread overview]
Message-ID: <b4m4pz73o81.fsf@jpl.org> (raw)
In-Reply-To: <87veroj5pj.fsf@latte.josefsson.org>
>>>>> In <87veroj5pj.fsf@latte.josefsson.org> Simon Josefsson wrote:
> These changes:
> 2006-05-30 Katsumi Yamaoka <yamaoka@jpl.org>
> * gnus-agent.el (directory-files-and-attributes): Move forward.
> 2006-05-29 Kevin Greiner <kevin.greiner@compsol.cc>
> * gnus-agent.el (Added gnus-agent-flush*) to purge agent info.
> (gnus-agent-read-agentview): Fixed handling of end-of-file error.
> (gnus-agent-read-local): All symbols allocated in my-obarray
> (gnus-agent-set-local): Skip invalid entries (min and/or max is nil).
> (gnus-agent-regenerate-group): Check numeric names to see if they are
> messages or groups.
> (gnus-agent-total-fetched-for): Ignore 'dummy.group' (there should be a
> better way of do this...)
> appear to cause problems for me when I start Gnus, I get the backtrace
> below. If I revert to 7.57 of gnus-agent.el, it works.
> Debugger entered--Lisp error: (file-error "Opening directory" "no such file or directory" "/home/jas/News/agent/nntp/news.gmane.org/gmane.ietf.techspec")
The gmane.ietf.techspec group was created recently, wasn't it?
I got a similar error and reported it in this list[1] a moment
ago together with a way to reproduce that error. A workaround I
tried is to remove an entry of the group in question from the
~/.newsrc.eld file.
[1] <b4mhd383r9g.fsf@jpl.org>
next prev parent reply other threads:[~2006-05-30 8:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-30 8:07 Simon Josefsson
2006-05-30 8:34 ` Katsumi Yamaoka [this message]
2006-05-30 9:01 ` Simon Josefsson
2006-05-30 12:37 ` gdt
2006-05-30 23:29 ` Katsumi Yamaoka
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=b4m4pz73o81.fsf@jpl.org \
--to=yamaoka@jpl.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).