I've been working a similar problem--updating Trac tickets from a Perl
script. I'm going through the HTTP interface using Perl's LWP library for
the HTTP requests and form parsing. It's been relatively painless, but I
did run into a couple of complications (neither of which may be applicable
I think that you are also going to need cookies. My first attempt at
authentication just included the HTTP Basic Authentication and that was
not enough. Trac didn't recognize the authentication unless it was
coupled with a session. Hitting the login page with the Basic
Authentication and
I'm not sure if this is a bug, or just a design consequence. I'm trying
to document some perl code and I'm running into a formatting problem. I
would like to set it up as definition lists, but the perl package syntax
is messing things up. An indented line containing something like
See the
Thanks, Christian.
I missed that ticket.
Alex Buccino
Christian Boos [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
01/28/2006 06:40 AM
Please respond to trac
To: trac@lists.edgewall.com
cc:
Subject:Re: [Trac] Double colon processing in TracWiki
First off, let me say that I love Trac. It's been a huge help to my
development group. However, I'm not sure I would want to make the
argument of Trac over Roundup. I've been a big fan of Roundup since way
back, and I would love to see it get the kind of momentum that you mention
Trac
As I said, I'm a big fan of Roundup's concept of the nosy list. Basically
it's a list of email addresses to be notified about changes to a ticket.
Whenever a user makes any change to a ticket, they are automatically added
to the nosy list. Essentially, if you express a stake in a ticket, you
