Some commit today broke my Gnus

Some commit today broke my Gnus

[Tassilo Horn]

Hi all,

since I've updated my git checkout some minutes ago until commit
647c17891849c561534af42b619e9679259ba2b3, I get a very strange warning
on startup.

  Warning: Warning - invalid active: 

And, after that happens, my *scratch* buffer has been modified to this:

--8<---------------cut here---------------start------------->8---
\;\; This buffer is for notes you don\'t want to save, and for Lisp evaluation.
\;\; If you want to create a file, visit that file with C-x C-f,
\;\; then enter the text in that file\'s own buffer.
--8<---------------cut here---------------end--------------->8---

What's going on?

I tried restarting emacs/gnus with `debug-on-error', but nothing errors.
Hm, after Gnus has started, I seem not to be able to get new news using
`g' anymore.  When I try, I get

  gnus-active-to-gnus-format: Buffer is read-only: #<buffer *Group*>

but no error (at least I don't enter the debugger...).

Bye,
Tassilo
-- 
Sent from my Emacs

Re: Some commit today broke my Gnus

[Tassilo Horn]

Tassilo Horn <tassilo@member.fsf.org> writes:

Hi!

> since I've updated my git checkout some minutes ago until commit
> 647c17891849c561534af42b619e9679259ba2b3, I get a very strange warning
> on startup.
>
>   Warning: Warning - invalid active: 
>
> And, after that happens, my *scratch* buffer has been modified to this:
>
> \;\; This buffer is for notes you don\'t want to save, and for Lisp evaluation.
> \;\; If you want to create a file, visit that file with C-x C-f,
> \;\; then enter the text in that file\'s own buffer.
>
> What's going on?

The commit

--8<---------------cut here---------------start------------->8---
commit 26be1f2820f24c95bc97369e86c6f0bd9b389cea
Author: Adam Sjøgren <asjo@koldfront.dk>
Date:   Thu Feb 3 11:49:30 2011 -0800

    * gnus-start.el (gnus-get-unread-articles): Fix the call to methods
    that have no groups.
--8<---------------cut here---------------end--------------->8---

fixes the issue for me again.

Bye,
Tassilo
-- 
Sent from my Emacs

Re: Some commit today broke my Gnus

[Lars Ingebrigtsen]

Tassilo Horn <tassilo@member.fsf.org> writes:

> since I've updated my git checkout some minutes ago until commit
> 647c17891849c561534af42b619e9679259ba2b3, I get a very strange warning
> on startup.
>
>   Warning: Warning - invalid active: 

This message was stuck in a Gmane queue until now.

I assume this problem has gone away by now?

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

Re: Some commit today broke my Gnus

[Tassilo Horn]

Lars Ingebrigtsen <larsi@gnus.org> writes:

Hi Lars,

>>   Warning: Warning - invalid active: 
>
> This message was stuck in a Gmane queue until now.
>
> I assume this problem has gone away by now?

Yes, it's gone.

Bye,
Tassilo
-- 
Sent from my Emacs