Sandro Santilli

comment: error: unable to fetch timestamp -- WARNING: Untested Trac version (1.4)

2

I cannot comment on a ticket with Trac version 1.4, this is what happens: ``` WARNING: Untested Trac version (1.4) error: unable to fetch timestamp ```

something ilke `cm download-ticket-attachement ticket_id`, ideally with the ability to request "last-attachment" or a number of last attachments...

Right now "cm search" also returns closed ticket, but it's usually useful to only search in the open ones, or generally pass all the possible search options (category,status etc.)

Invalid 'Milestone' with empty expected

6

Error message on "cm new": {{{ Found the following errors: - Invalid 'Milestone': expected: - Invalid 'Priority': expected: blocker, critical, high, medium, low }}} The 'Milestone' part is suspicious

python setup.py install refuses to override an existing installation

3

I'm not sure if this is expected behavior but everytime I try to install an update version of cartman the installation fails unless I manually remove an installed file: ```...

Allow for context in "cm comment" data input

2

I've setup a script to integrate cartman with Mutt: http://strk.keybit.net/blog/2015/11/11/trac-from-mutt/ Doing so, I'm missing the context while commenting on a ticket. Ideally, I'd have the full context in the editor,...

Same than with "cm new" (dealt with in #14), here's the full list of requests generated by a "cm comment" command: ``` Getting /login Getting / Getting /ticket/3366 Posting /ticket/3366...

Rather than calling `/login` for every invocation of the command, it would be useful to store the cookies in a session.

Mention that virtualbox is required to run `vagrant up`

1

Was cought by missing it (apt-get install virtualbox)

Bogus `Listening on port 0` message, provide useful info

1

I'm willing to find a random available port for my postgrest service, so I run: ``` PGRST_SERVER_PORT=0 postgrest postgrest.conf ``` It works fine, except then I'm left alone in figuring...