We should be able to patch and upgrade our roundup software when needed, to
apply needed local changes (cf issue1084 & issue1090) and to manage those
changes with darcs and perhaps feed them upstream. Currently we use the debian
roundup package which is quite old and editable only by root (David). I propose to

1. install the same roundup version (1.2.x) in /usr/local/src/
2. have David change /usr/bin/roundup-mailgw to /usr/local/bin in
/etc/darcs_bugs_procmailrc. Or better, give me write access on that file so that
I can switch when I'm ready and revert if needed. I think that's all we'd need
to do. 

After that I'd be able to apply the fixes we need, and later look into upgrading
to current roundup.

I must admit that I'd be considerably more comfortable continuing to
run the debian package.  If you want to change this, you'll have to
tell me what to change in considerably greater detail than you mention
in this bug.  I know, for instance, that I'll need to change the
apache configuration somehow (or put a symlink somewhere that apache
can find it?).

David

An apache change might be needed, or it may be simply picking up roundup from
the path in which case uninstalling the system package would be enough. That I
can figure out.

I think you can do what I propose here, which lets me or someone else you
nominate improve our bug tracker; or stick with debian's roundup, which doesn't.
An in-between option is for you to apply the most needed patches in-place to the
system roundup, but why bother doing that.

At a minimum, this would then require adding /usr/local/bin to the path.

But you still haven't suggested any change that you want me to make.

David

I sure did. But I also was asking for your support before spending  
more time on this.

If you are willing, I suggest you give me write access to /etc/ 
darcs_bugs_procmailrc. You pointed out that apache config may also  
need a change, so I'll find out about that and come back to you. After  
you grant permissions, I don't have access to /usr/local so would  
install the software in my home directory and test from there.

Or, you can do more of it yourself and I'll do the legwork to walk you  
through it. Or we can do nothing.

It seems to me apache is running roundup via mod_python, importing
"roundup.cgi.apache. So the second thing I'd need you to do is give me write
access to /etc/apache2/sites-enabled/001-bugs , where I would add 

 PythonPath "[localrounduppath]+sys.path"

and it should start using the localroundup. I think that covers the mail
gateway, the web interface, and there's nothing else.

Didn't I already do this?

David - you did, thanks. I didn't notice your action. I'll explore this further.

I'm ready to try this, by enabling the PythonPath directive at the top of 
/etc/apache2/sites-enabled/001-bugs but I need to restart apache, possibly more 
than once. If I could get access to do that, it would be best, otherwise I need 
someone else who can do that while we are on irc, so I can resolve any issues. I 
think David or Mark Stosberg are the two who could do that.

Apache restarted.  Thanks!

Simon: is there anything you need here?

With Eric's help, bugs.darcs.net now runs the roundup software from / 
usr/local/src, editable by staff. Currently this is 1.2.1, the same  
version as before.

We hit trouble when we tried upgrading to 1.4.6, so have set up a test  
server where I'll troubleshoot new roundup/tracker code  
(bugstest.darcs.net). I hope to publish our roundup code (and tracker  
config, ideally, but it may be too sensitive) as darcs repos soon to  
facilitate collaboration.

So this is resolved. Thanks!

For the record, we discussed this again on #darcs today, and the darcs bug tracker 
is now running the roundup 1.4.4 which comes with our upgraded debian lenny 
system. Latest roundup is 1.4.8 with a bunch of fixes but nothing that we deemed 
critical.

Hi Simon, please update this if this bug if this is not actually resolved.  Thanks!