Re: [Trac] Issues bringing up Trac 1.0 after upgrade from version 0.12

Thanks for the quick replies Ryan and Steffen. I went ahead with the requested changes (upgrading 2 plugins and removing the GitPlugin). When upgrading (trac-admin /var/lib/trac/project upgrade), I still get the following error which now only appears to fail on (DatabaseError: no such table:

Re: [Trac] Issues bringing up Trac 1.0 after upgrade from version 0.12

On Wed, Jan 16, 2013 at 1:45 PM, Auto User automation.cl...@gmail.comwrote: Thanks for the quick replies Ryan and Steffen. I went ahead with the requested changes (upgrading 2 plugins and removing the GitPlugin). When upgrading (trac-admin /var/lib/trac/project upgrade), I still get the

[Trac] enable uwsgi alarm system failed

I want to enable uwsgi alarm system through the wiki: http://uwsgi-docs.readthedocs.org/en/latest/AlarmSubsystem.html The reason is that I need to be alarmed when the uwsgi server log the listen queue full But I can't get the email after the alarm log happen. Attached the production.ini

[Trac] Re: Upgrade 0.12 to 1.0 fails with UndefinedError: pretty_dateinfo not defined

On Monday, November 5, 2012 1:55:08 PM UTC-6, Tim Thornton wrote: Hi, I've had 0.12 running fine under Windows using tracd. I've just tried upgrading to 1.0. When I restart Trac and go to a project, after logging in I get the following error: *Trac detected an internal error:*

[Trac] unsupported local exception

I'm using OSX Snow Leopard Server (yes, I know). I have installed trac many times on linux boxes, this is my first attempt on osx. I've tried WSGI and FastCGI access now, but getting a locale error. Here's the most recent one with FastCGI from apache log: [Wed Jan 16 11:03:50 2013] [notice]

[Trac] Help to setup trac on Apache+mod_fcgid+Windows

Hola a todos, Traté de configurar trac con mod_fcgid sin éxito. Siempre consiguiendo error *(OS 109) La tubería se ha terminado. : Mod_fcgid: get error superposición resultado Final prematuro de las cabeceras de script: trac.fcgid* Le agradecería si alguien me ayuda con los pasos a seguir

RE: [Trac] Apache Bloodhound 0.3 release (incubating)

Joe Dreimann wrote: If any of you would like to find out more about our MultiProduct approach, please see our Wiki here: https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0003 Due massive lack of time I've read it but now, and IMO it looks good. Although I'm a big fan of first having

[Trac] Re: enable uwsgi alarm system failed

On Wednesday, January 16, 2013 5:31:27 AM UTC-8, kennyeric wrote: I want to enable uwsgi alarm system through the wiki: http://uwsgi-docs.readthedocs.org/en/latest/AlarmSubsystem.html The reason is that I need to be alarmed when the uwsgi server log the listen queue full But I can't get

[Trac] Re: Intermittent errors with BrowserModule

Hello, Any additional suggestions? :( What I've tried so far: * Using the workaround documented here: http://trac.edgewall.org/wiki/TracSubversion#instance-dict-restricted-mode * I was using the same svn repository for both trac environments, but now I've changed to two different ones * I

Re: [Trac] Password reset not updating htpasswd file

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 15.01.2013 23:52, Samuel Degrande wrote: On 01/15/2013 08:23 PM, Steffen Hoffmann wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 15.01.2013 18:17, Falcon EndorphinE wrote: Hello, when I try to get the password using Forgot your

[Trac] Trac 0.12.3 released

Hello everyone, Our first maintenance release for the year is Trac 0.12.5, for our long term maintenance release line 0.12.x. 1.0.1 will follow in the next days, as well as 1.1.1. But in the meantime, back to 0.12.5 in more details... Trac 0.12.5 Released We're happy to

[Trac] Trac 0.12.5 released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 (resent signed and with fixed Subject... sorry for the 0.12.3 bogus one) Hello everyone, Our first maintenance release for the year is Trac 0.12.5, for our long term maintenance release line 0.12.x. 1.0.1 will follow in the next days, as well as