Re: [Trac] TracError: The Trac Environment needs to be upgraded.

2011-10-19 Thread Grzegorz Sobanski
* Martin Landa  [2011-10-19 21:23]:
> as root (same when creating trac environment). Anyway it's very
> strange that I am asked to upgrade immediately after installing Trac
> instance.

In my experience in 95% situations it means that apache cannot read
access trac.ini. Error is the same. Check permission very carefully.


greets
silk

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com.
To unsubscribe from this group, send email to 
trac-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en.



Re: [Trac] TracError: The Trac Environment needs to be upgraded.

2011-10-19 Thread Martin Landa
2011/10/19 Matthew Caron :
> On 10/19/2011 02:41 PM, Martin Landa wrote:
>>
>> Hi,
>> """
>> Trac Error
>>
>> TracError: The Trac Environment needs to be upgraded.
>>
>> Run "trac-admin /opt/trac/qgama upgrade"
>> """
>>
>> OK, strange, anyway when running `upgrade` command nothing happen.
>
> What user are you running trac-admin as?

as root (same when creating trac environment). Anyway it's very
strange that I am asked to upgrade immediately after installing Trac
instance.

Martin

-- 
Martin Landa  * http://geo.fsv.cvut.cz/~landa

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com.
To unsubscribe from this group, send email to 
trac-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en.



Re: [Trac] TracError: The Trac Environment needs to be upgraded.

2011-10-19 Thread Matthew Caron

On 10/19/2011 02:41 PM, Martin Landa wrote:

Hi,
"""
Trac Error

TracError: The Trac Environment needs to be upgraded.

Run "trac-admin /opt/trac/qgama upgrade"
"""

OK, strange, anyway when running `upgrade` command nothing happen.


What user are you running trac-admin as?

--
Matthew Caron
Build Engineer
Sixnet | www.sixnet.com
O +1 518 877 5173 Ext. 138
F +1 518 602 9209
matt.ca...@sixnet.com

--
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com.
To unsubscribe from this group, send email to 
trac-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en.



[Trac] TracError: The Trac Environment needs to be upgraded.

2011-10-19 Thread Martin Landa
Hi,

I have problem with creating a new Trac instance on my server, sample
workflow

export TRAC=qgama
trac-admin /opt/trac/$TRAC initenv
chgrp www-data /opt/trac/$TRAC -R
chmod g+w /opt/trac/$TRAC -R

cat /etc/apache2/sites-enabled/003-trac


   SetHandler mod_python
   PythonInterpreter main_interpreter
   PythonHandler trac.web.modpython_frontend
   PythonOption TracEnv /opt/trac/qgama
   PythonOption TracUriRoot /trac/qgama


/etc/init.d/apache2 restart

When I open Trac instance in my web browser I get

"""
Trac Error

TracError: The Trac Environment needs to be upgraded.

Run "trac-admin /opt/trac/qgama upgrade"
"""

OK, strange, anyway when running `upgrade` command nothing happen.

Database is up to date, no upgrade necessary.

Debian GNU/Linux stable with Trac 0.12.3.dev.

Any ideas what is wrong? Thanks in advance, Martin

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com.
To unsubscribe from this group, send email to 
trac-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en.



RE: [Trac] What is the difference between svn and svnfs (and direct-svnfs)?

2011-10-19 Thread Cooke, Mark
> -Original Message-
> From: trac-users@googlegroups.com On Behalf Of Grzegorz Sobanski
> Sent: 19 October 2011 11:44
> To: trac-users@googlegroups.com
> Subject: Re: [Trac] What is the difference between svn and 
> svnfs (and direct-svnfs)?
> 
> * Cooke, Mark  [2011-10-19 10:41]:
> > > These two are synonyms. It's what you should normally use.
> > > 
> > I was wondering why we had two synonyms, I assumed 
> something like 'svn' would use e.g. server based access (svn: 
> or http:) whilst svnfs would use direct (file:) access (which 
> seemed like it would be dangerous).
> > 
> > Does this require the post-commit changeset hook?
> 
> Well, it does not require it. You can enable synchronizing on every
> request, but I would recommend against it. Solution with the hook
> is much more effective.
>  
> > > >  * direct-svnfs
> > > 
> > > This one bypasses the cache, so you don't need to resync 
> Trac to the
> > > repository, and changesets are picked up automatically. 
> But it's also
> > > much, much slower.
> > > 
> > ..so this is the 0.11 method of checking the repository on 
> every access (no hook required)?
> 
> No.
> 0.11 was caching everything too, but it checked on every request if
> there is something new in the repository to be cached.
> direct-svnfs does not cache nothing, it always goes to the repository
> if it needs some info about it.
> 
> 
> -- 
> greets
> silk
> 
Thanks for the clarification (from a David Eddings fan).

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com.
To unsubscribe from this group, send email to 
trac-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en.



Re: [Trac] What is the difference between svn and svnfs (and direct-svnfs)?

2011-10-19 Thread Grzegorz Sobanski
* Cooke, Mark  [2011-10-19 10:41]:
> > These two are synonyms. It's what you should normally use.
> > 
> I was wondering why we had two synonyms, I assumed something like 'svn' would 
> use e.g. server based access (svn: or http:) whilst svnfs would use direct 
> (file:) access (which seemed like it would be dangerous).
> 
> Does this require the post-commit changeset hook?

Well, it does not require it. You can enable synchronizing on every
request, but I would recommend against it. Solution with the hook
is much more effective.
 
> > >  * direct-svnfs
> > 
> > This one bypasses the cache, so you don't need to resync Trac to the
> > repository, and changesets are picked up automatically. But it's also
> > much, much slower.
> > 
> ..so this is the 0.11 method of checking the repository on every access (no 
> hook required)?

No.
0.11 was caching everything too, but it checked on every request if
there is something new in the repository to be cached.
direct-svnfs does not cache nothing, it always goes to the repository
if it needs some info about it.


-- 
greets
silk

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com.
To unsubscribe from this group, send email to 
trac-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en.



RE: [Trac] What is the difference between svn and svnfs (and direct-svnfs)?

2011-10-19 Thread Cooke, Mark
> -Original Message-
> From: trac-users@googlegroups.com 
> [mailto:trac-users@googlegroups.com] On Behalf Of Remy Blank
> Sent: 18 October 2011 20:55
> To: trac-users@googlegroups.com
> Subject: Re: [Trac] What is the difference between svn and 
> svnfs (and direct-svnfs)?
> 
> Cooke, Mark wrote:
> >  * svn
> >  * svnfs
> 
> These two are synonyms. It's what you should normally use.
> 
I was wondering why we had two synonyms, I assumed something like 'svn' would 
use e.g. server based access (svn: or http:) whilst svnfs would use direct 
(file:) access (which seemed like it would be dangerous).

Does this require the post-commit changeset hook?

> >  * direct-svnfs
> 
> This one bypasses the cache, so you don't need to resync Trac to the
> repository, and changesets are picked up automatically. But it's also
> much, much slower.
> 
...so this is the 0.11 method of checking the repository on every access (no 
hook required)?

Many thanks,

~ mark c

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com.
To unsubscribe from this group, send email to 
trac-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en.