It's probably a good idea to do this soon rather than later.

The roundup script used to be run on my staging repo.  Now it needs to be run on
darcs.net as well.

I've update the post-hook.  I'll need to see this actually working before I
close this bug.

On a hunch, I have fired up CPAN and done install MIME::Lite
Let's see if this changes anything.

Phooey! That didn't help either (issue1300).
Now I've tried changing bugs@darcs.net to bugs@lists.osuosl.org

Some minor good news on this:

1. It seems the script has been running since my last update (I must
have forgotten to disable it), only the To address was unset.  The
contents of the message body seem correct.

2. After fixing the forcearray problem in update_roundup.pl [which broke
the script when you only push one patch] and setting the outgoing email
address to 'bugs@lists.osuosl.org', I was able to run the update script
manually on darcs.net and resolve a bug.

3. The bad news... it still appears that for *some* reason, pushing a
patch did not cause a bug to be resolved. :-(

I'm a bit confused about this.  Anyway, I've now moved the line from the
posthook line in _darcs/prefs/defaults

  apply --posthook nice -19 ./build-darcs-dot-net-darcs; perl
contrib/update_roundup.pl

to the build-darcs-dot-net-darcs script.

That should not make a difference, but it seems tidier anyway.

I'm going to continue to monitor this.  Maybe everything is actually in
order.  The update_roundup.pl script has now been *disabled* from my
staging repo.  It will be running exclusively on darcs.net for now. 
Fingers crossed.

Hooray, this seems to be fixed at last.  This means you should now
expect bugs to be resolved the instant somebody pushes the relevant
patch.  Our infrastructure slowly catches up with the commit-bit model
change.