[Trac] Re: how to set the permission and ownership of trac in linux?

On Apr 9, 11:51 am, "Emmanuel Blot" <manu.b...@...> wrote:
> > I add this line 'umask022' at the top of my post-commit script:
> > /srv/svn/repositories/snapshot/hooks/post-commit
>
> > And after I commit a ticket, the /tmp/trac.log still own by a user and
> > the permission is not 777
>
> That's the expected behaviour, isn't it?umask022 gives '644'
> permissions, that is rw-r--r-
> (manumaskif you have any doubt)
>
> What is the user that executes the 'SVN' process ?
> Add something like:
>
> id > /tmp/svn-ower.log
>
> at the top of your commit script, commit a new revision, and look at
> the content of this new file.
>
> Cheers,

Manu,

Thanks for your help. I have tried you suggestion like this, but I
still get the same problem:
Can you please tell me if you have any other idea?

umask 022

[Trac] trac not responding - error tracing how to

Hi,

I'm running trac 10.04 on Suse 10 OSS. I had two projects running just 
fine but since a few days I can't access the trac app anymore (accessing 
via browser, only receiving timeout message).

I can run the trac-admin but when I want to list e.g. the wiki pages for 
one project trac-admin hangs also (without any error message). Any clues 
on how to trace the error?

--~--~---------~--~----~------------~-------~--~----~
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@...
To unsubscribe from this group, send email to trac-users-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---

[Trac] Consultant wanted to enhance trac burndown plugin

Hello

We use trac to manage the software development at our company.

There are a few things which we'd like to change to make the burndown
plugin work more like the SCRUM development process.  I'm looking to
contract someone for the work.

The changes are modest and build on the existing plugin so I think
this is a relatively simple development project.

Please contact me if you are interested in this work.

kind regards,

Oliver George
--
Community Project Manager
Openads Ltd
+44 20 7299 7497
oliver.george@...

--~--~---------~--~----~------------~-------~--~----~
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@...
To unsubscribe from this group, send email to trac-users-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---

[Trac] Hi Friends

[Trac] Re: Hi Friends

This is great in theory; unfortunately, this mailing list happens to
be smarter than that.  Each of those sites have been reported to
Google's AdSense department as well as AdSpam.  No guarantees that
immediate action will be taken, but at least it's on the books.

It's best to thoroughly ignore these sites.

--

-- 
Samuel A. Falvo II

--~--~---------~--~----~------------~-------~--~----~
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@...
To unsubscribe from this group, send email to trac-users-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---

[Trac] Support for WBS and PBS

Hi,

Is there any Trac hack/module for creating and maintaining WBS (Work
Breakdown Structure) and/or PBS (Product Breakdown Structure)?

To give you a picture of how I see things: I see the current handling
of components in Trac as a (very) simple PBS-tool. I see WBS as as the
base of all project planning and management. I see tickets as a way of
capturing things to be done that weren't originally planned. Having
said that I don't believe in over-detailed planning. I believe a in
sound planning *and* daily capturing of new (lesser) requirements and
issues to deal with.

To begin with I'm interested in being able to:

1. Replace the current handling of components with a more fully
fledged PBS support.
2. Set properties of PBS nodes. Eg: "owner", "platform".
3. Create and maintain heirarchical WBS structures of arbitrary depth.
4. Set properties of WBS nodes. Eg: "owner", "estimated time to
completion", "priority level"
5. Assign WBS nodes as belonging to a given PBS-node/component.
6. A given WBS should be able to be marked as belonging to a given Milestone.
7. Have multiple WBS:s in a given Trac-project.

In addition I would of course like to:

1. Derive computed "estimate time to completion" for higher level WBS
nodes, using different cost estimation models, preferably via some
plug-in mechanism.
2. Use a WBS as a base for time reporting.

Maybe I have to write it myself!  What is is the most important
documentation to read before  starting to hack Trac?

/Paul

--~--~---------~--~----~------------~-------~--~----~
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@...
To unsubscribe from this group, send email to trac-users-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---

[Trac] Looking for Trac expert to help setting up Trac on host running CentOS, Apache, SVN

Hi,

I'm working on a development team that wants to try out Trac -- is
there anyone who can help us get it set up quickly?  Could be a paid
project if necessary.  Should be pretty simple and straightforward for
anyone who's done it before -- we just didn't want to spend a ton of
hours getting the right hooks set up with SVN, Apache, db backend,
etc.

We're running CentOS, SVN, Apache, we'd prefer MySQL but could use
SQLite or PostgreSQL if needbe...

Email me for more details!

Thanks,
Mike

--~--~---------~--~----~------------~-------~--~----~
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@...
To unsubscribe from this group, send email to trac-users-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---

[Trac] Older revisions not visible in Trac after repository reorganisation

It has been decided that the projects in our group's Subversion
repository should be moved from the top level into folders for each
user, so /project1 -> /user1/project1. I adjusted repository_dir
accordingly in my trac.ini and performed a trac-admin resync. Trac can
see the project but not any revisions prior to the reorganisation.
Help? I'm using Trac 0.10.3.

Hamish

--~--~---------~--~----~------------~-------~--~----~
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@...
To unsubscribe from this group, send email to trac-users-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---

[Trac] Re: Older revisions not visible in Trac after repository reorganisation

Hello,

Hamish Lawson wrote:
> It has been decided that the projects in our group's Subversion
> repository should be moved from the top level into folders for each
> user, so /project1 -> /user1/project1. I adjusted repository_dir
> accordingly in my trac.ini and performed a trac-admin resync. Trac can
> see the project but not any revisions prior to the reorganisation.
> Help? I'm using Trac 0.10.3.
>   

That can't be done if you use a scoped repository.

Current alternatives are:
 - setup another trac using the /project1 scope, access it using 
InterTrac links (e.g. legacy:source:/README.txt)
 - use a non-scoped repository and define an authz policy that allows 
you to browse only the /project1/user1 and /project1 paths (see the 
FineGrainedPermissions page in the Trac wiki)

-- Christian

--~--~---------~--~----~------------~-------~--~----~
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@...
To unsubscribe from this group, send email to trac-users-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---

[Trac] Problem restore backup

Hi,

I have backupped a trac with "hotcopy" and restored it on another
server. But in localhost/trac I got for that trac this error:

project-name: Error
()

on log files no error are reported.

Both servers use sqlite. Probably I have not restored db (db/trac.db)
on sqlite. How can I restore it on sqlite (not found in sqlite-doc)?
or is it unuseful? otherwise I have not idea of this error...

Thanks,
Giulio

--~--~---------~--~----~------------~-------~--~----~
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@...
To unsubscribe from this group, send email to trac-users-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---