From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: upgrade 5.9.0 -> Oort 0.04 CVS ==> Kaboing!
Date: Sun, 09 Dec 2001 13:12:18 +0100 [thread overview]
Message-ID: <iluelm4wq1p.fsf@dhcp128.extundo.com> (raw)
In-Reply-To: <81d71og0v7.fsf@zion.bpnetworks.com> (Ami Fischman's message of "Sun, 09 Dec 2001 02:10:36 -0800")
Ami Fischman <usenet@fischman.org> writes:
> Specifically, it was as if gnus completely forgot about the marks in my mail
> and news groups (everything was unmarked). I tried rebuilding the nov files
> (I'm using nnml, but since I had the same prob with nntp groups, I doubt
> that the problem lay there), and that didn't help. ended up resorting to
> manually marking what I wanted and expiring/catching up on the rest. Is
> this a known behaviour? Does it serve me right for upgrading to a CVS
> version? (I am mostly interested in updated support for nnwarchive and other
> interesting backends).
This isn't a known behaviour, to me at least.
Oort Gnus introduced ".marks" files for nnml which move the
information stored in .newsrc.eld into a file within each group.
But nntp groups doesn't grok it, so if you have this problem in both
nnml and nntp something else is causing it. Could you make a M-x
gnus-bug RET report so we can see what your config is? Do you have a
backup of your files, and can reproduce this behaviour? What does `G
E' say for a group which lost all its marks, in 5.9.0, and in Oort
after starting it the first time, and in Oort after trying to enter
the group?
next prev parent reply other threads:[~2001-12-09 12:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-09 10:10 Ami Fischman
2001-12-09 12:12 ` Simon Josefsson [this message]
2001-12-09 20:03 ` Ami Fischman
2001-12-09 20:13 ` Ami Fischman
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=iluelm4wq1p.fsf@dhcp128.extundo.com \
--to=jas@extundo.com \
--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).