Raymond Toy | 7 Jan 2012 19:05
Picon

Update trac mercurial to 0.11.0.8 or later?

Can we update trac mercurial to 0.11.0.8 or later?  I'm getting the
error messages as mentioned in http://trac.edgewall.org/ticket/8897.

I don't see anything bad happening, but the log file fills up pretty
quickly with the error messages.

I tried to update it myself using the trac admin interface to plugins,
but it complains that it's already installed.

Ray
Erik Huelsmann | 8 Jan 2012 11:12
Picon
Gravatar

Re: Update trac mercurial to 0.11.0.8 or later?

Hi Raymond,

The errors are probably due to the fact that our older version was
installed in python's default search path. I've just upgraded the
mercurial plugin to 0.11.10 (latest for Trac 0.11).

After restarting Apache, I didn't see any new errors pop up in the
logs when browsing the repository through Trac.

Hope that fixes it and completes your request!

Bye,

Erik.

On Sat, Jan 7, 2012 at 7:05 PM, Raymond Toy <toy.raymond <at> gmail.com> wrote:
> Can we update trac mercurial to 0.11.0.8 or later?  I'm getting the
> error messages as mentioned in http://trac.edgewall.org/ticket/8897.
>
> I don't see anything bad happening, but the log file fills up pretty
> quickly with the error messages.
>
> I tried to update it myself using the trac admin interface to plugins,
> but it complains that it's already installed.
>
> Ray
>
>
> _______________________________________________
> clo-devel mailing list
(Continue reading)

Raymond Toy | 8 Jan 2012 18:42
Picon

Re: Update trac mercurial to 0.11.0.8 or later?

On 1/8/12 2:12 AM, Erik Huelsmann wrote:
> Hi Raymond,
>
> The errors are probably due to the fact that our older version was
> installed in python's default search path. I've just upgraded the
> mercurial plugin to 0.11.10 (latest for Trac 0.11).
>
> After restarting Apache, I didn't see any new errors pop up in the
> logs when browsing the repository through Trac.
>
> Hope that fixes it and completes your request!

Thanks for the update.  I haven't checked, but the bug report says it's
fixed, and I believe it.

Thanks,

Ray

Gmane