>From the property journal of issue1284:

  2009-01-06 00:29:32 twb set nosy: kowey, simon, twb, thorkilnaur, dmitry.kurochkin
                              messages: + msg6995
  2009-01-11 10:40:11 twb set assignedto: twb ->
                              nosy: kowey, simon, twb, thorkilnaur, dmitry.kurochkin
  2009-01-11 10:51:50 twb set topic: + ProbablyEasy
                              nosy: + jaredj
  2009-01-11 11:17:24 twb set nosy: kowey, simon, twb, thorkilnaur, jaredj, dmitry.kurochkin
                              messages: + msg7034

These properties were changed by simple bodyless messages like
"[assignedto=]".  *I'm* not setting nosy, and repeatedly setting nosy
to the same thing bloats out the property journal and makes it hard to
read.

I guess what's happening is that someone added a hook to set nosy when
a ticket is changed by email, to make sure that when a ticket is first
created, the core team are in the nosy list.  But I guess it's
accidentally being called EVERY time an issue is changed via email.

Thank you. As I understand this, you wish for Roundup to leave out the messages 
that state that the nosy list has been set when it, in fact, hasn't changed. In 
the example you quote, "nosy: kowey, simon, twb, thorkilnaur, dmitry.kurochkin" 
for "2009-01-11 10:40:11" and "nosy: kowey, simon, twb, thorkilnaur, jaredj, 
dmitry.kurochkin" for "2009-01-11 11:17:24" should not be included in the history.

It is not clear to me whether this is a problem in Roundup or the way the darcs 
tracker is configured or possibly both. I have looked at the Roundup documentation 
(http://roundup.sourceforge.net/doc-1.0/) and the repository at 
http://darcs.net/darcsbugtracker (which I believe contains the darcs tracker 
configuration) without coming closer to an answer to this question. My best guess 
is that Roundup is careless, in some cases, and not properly detecting that a 
wholesale replacement of the nosy list for an issue is not actually changing 
anything.

Is anyone able to shed some light on this question?

Thanks and best regarads
Thorkil

Hi Simon,

Is this something you could shed light on?

Thanks!

Sounds like we need to ask somebody on the roundup mailing list.

Note that this also happens with the web interface too, and it doesn't affect
the Python instance of Roundup (eg. http://bugs.python.org/issue1602 ), so it's
either something to do with our version of roundup or more probably, our setup.

Hurrah, one more roundup issue fixed.

This was due to a our nosy_keyword_reaction detector (plugin) systematically
updating nosy.  I've pushed some patches so that it only updates nosy when nosy
actually changes, following the model of the nosyreaction detector.  

I'm also in the middle of checking out the roundup SVN depot in case they'd like
a patch.