Re: 5.8.3 (CVS version) NNTP primary server stops updating unread number

[Steinar Bang <sb@metis.no>]

>>>>> Steinar Bang <sb@metis.no>:

>>>>> Steinar Bang <sb@metis.no>:
>>>>> Steinar Bang <sb@metis.no>:
>>> My problem, is that a normal
>>> 	g
>>> in the *Group* buffer no longer updates the unread number on the NNTP
>>> groups on the primary server (I only have this one NNTP server).
>>> After the get command I see the text "nntp read: 15k" for a while in
>>> the minibuffer, until it moves on to the secondary servers (nnml and
>>> an nnimap server).

>>> I can update the NNTP groups individually with
>>> 	M-g
>>> but that is impractical in the long run.

>> Actually it updates the NNTP groups on 
>> 	g
>> (ie. it increases the article count), but a
>> 	M-g
>> shows even more articles.

>> To be fair I've only actually observed this in a single NNTP group.

> This rang a bell, and looking in the ~/.newsrc.eld file, I have found
> that I have both an "nntp+news.eunet.no:no.alt.motorsykler", and a
> "no.alt.motorsykler".

> Now the questions are:
>  1. how did the first group appear?
>  2. can I merge them, or do I need to delete them both, and
>     resubscribe?

The nntp+news.eunet.no group was on level 6 and has probably been
there for ages, through many versions of Gnus and pgnus and now Gnus
again. 

Why it suddenly started to make problems is anyone's guess.

In any case I killed the nntp+news.eunet.no:no.alt.motorsykler group,
using 
	S k
saved ~/.newsrc.eld, and this seems to have cured the problem.