[Trac] Using a svn repository subdirectory path (or managing mult projects in 1 repo)
My main question is about how to get trac to only look at a subdirectory of a repository rather than the whole thing. That is, we have a repo with top-level dirs for "common", "proj1" and "proj2". I would like to create a trac instance for "proj1" that limits the timeline and source browsing to only files within the svn proj1 dir. I see the repository_dir gets set to the root of the repo (/home/svn/repos/sw in our case) and setting it to something else causes trac to fail. I was wondering if there was some "filter" method of accomplishing this. The overall environment is that we would like to have separate ticket, milestone, timeline, browse, etc areas for each project as well as having one for "all" which handles tracking "common" and has links to the others and can show all source changes. Thanks in advance for any ideas, Chris --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Trac corrupting the SVN repository it points too?
aaron smith wrote: > I'm having a weird issue with SVN and Trac.. Here's whats going on.. > > I had to move a repo from one machine to the machine I've got Trac on.. > > --So I dumped the repo from the other machine. > --Loaded the repos into the new repo. > --trac-admin initenv ... > --pointed the repo to my new repo. > --seems like something I'm doing when I access Trac is causing SVN to > error out. I get these errors. > > svn: PROPFIND request failed on '/repos/rubyamf' > svn: Could not open the requested SVN filesystem > > > I've done some testing with re-creating the SVN repo / resyncing Trac. > and I've found that until I actually tell trac to use the repo, the > SVN is fine. But as soon as Trac is looking at that repository - it > seems like something happens when browsing trac that is kiling the > repository.. > > any ideas? It sounds to me like an apache config issue I had awhile back when trying to add vhosts to a server that also hosted svn. I would investigate your apache svn set up. I am fairly certain this is not trac's fault as I have trac referencing my svn repository via a readonly NFS mount right now in a test environment. Check your apache logs and config and make sure all your paths are right in terms of svn commands as well. Best, Chris --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Does not know how to use Webadmin
balaji wrote: > Hi There. > > I have installed the trac latest from trunk and did include the > [components] webadmin.*=enabled line in the trac.ini. Can anyone help > me with finding how to use WebAdmin module? > > Thanks in advance, > Balaji > > You have to be logged in as a user with TRAC_ADMIN rights for it to show up. trac-admin /path/to/tracEnv permission add balaji TRAC_ADMIN Best, Chris --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Process: sending tickets to test
Dana V. Baldwin wrote: > I'm wondering if anyone can help improve my process with TRAC. > > I run an MMOG and use TRAC to manage tickets for features, tasks and > bugs. I currently have several projects but as they are all for one team > I keep them all in the same TRAC environment so I can track owners tasks > across multiple projects, separating them with milestones. > > Currently when a ticket is complete, it needs to be tested in a release > build. I'm currently managing this by changing the user to test. This > has the benefit of keeping all of my test tickets together but is a > burden to accountability for the original owner. > > Is there a better process for flagging tickets that are ready to be tested? > A good alternative here is to use the ticket-workflow section of trac.ini to define a new state "done" or "needstesting". You can then make it so devels can not resolve tickets, only set them to "done", then you (or someone w/ proper prerms) can query everything in this state and change them to closed/resolved with a resolution of "tested" (you can easily create custom resolutions in trac). This is what I am doing for our trac (still in the process of testing/research), but keep in mind I am using 0.11 and I am not sure of the status of some of these features in 0.10.x. Best, Chris --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] PrivateTickets for 0.11
We have been working on moving to trac and decided to go with 0.11 due to the customizable workflow engine and extra permissions. Unfortunately I can not figure out how to make a submit-only user that can also see the ticket they submitted (but no other tickets that they are not associated with). We have set it up so these users have TICKET_CREATE access and nothing else which allows them to login, get an error about insufficient permissions (since they can not view the default wiki page), click new ticket, submit a ticket, and then get another insufficient permissions error. The ticket does get submitted but we imagine the error will be confusing and would like the user to be able to see their own tickets. It seems like the PrivateTickets plugin is exactly what we need but is not available for 0.11. Is there anything I can do to get the functionality we desire? Best, Chris --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: PrivateTickets for 0.11
Noah Kantrowitz wrote: > Due to lack of tuits, this may not happen for a few weeks after the > upcoming context-refactoring merge. > Two questions: 1. What do you mean by "lack of tuits"? 2. Could you give me some links/info about context-refactoring? Will it be easy to upgrade from current 0.11 to a post-context-refactoring version? --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: http://trac-hacks dead?
Rainer Sokoll wrote: > On Tue, Nov 06, 2007 at 03:48:06PM +0100, Emmanuel Blot wrote: > >>> using a distributed version control (like git, mercurial, dards) >>> instead of svn would at least make mirroring the plugins easy :) >>> >> Using SVN 1.4 on trac-hacks.org (and on t.e.o. BTW) would be a good >> start: svnmirror could be used. >> SVN 1.4+ has svnsync available which is also an option. It can be set up to run as a commit hook and push out/sync changesets to a list of mirror repositories or just be scheduled for periodic sync. Chris --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: http://trac-hacks dead?
Richard Lyman wrote: > On 11/6/07, Noah Kantrowitz <[EMAIL PROTECTED]> wrote: > >> How about we just wait the 2 hours for an admin to notice and kick >> apache in the head? >> >> I think this is being seriously over-thought. If people need the code >> for plugins, it should all be available on PyPI as a "mirror" (assuming >> the author was wise enough to push copies there). >> > > > Over thought? Today makes 2 out of the 3 times I've tried to > 'show-off' trac hacks and it's been down. All three have been to > separate groups where I was advocating the use of Trac. Extensibility > through plugins are a life-line. We need a solution that doesn't keep > putting kinks in that line. > > All I care about are the plugins themselves and especially the > directions on installing and setting up each plugin. > > What the owner of trac-hacks is doing for the community is fantastic - > we just need to have a good solution in place to help support the > existing effort. > Agreed, the plugins on trac-hacks are super important to the usefulness of trac for many people, no doubt. A well-known/linked mirror or even better an easily changeable DNS record would be ideal so that plugins can always be downloaded (or the downloads can be fixed quickly) regardless of the status of the primary trac-hacks server. On the other hand, I understand that trac-hacks has undergone some changes recently (moved to a new machine I believe?) and therefore understand how this downtime can happen and am grateful for those maintaining the service. Best, Chris --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: http://trac-hacks dead?
Alec Thomas wrote: > On 11/6/07, Richard Lyman <[EMAIL PROTECTED]> wrote: > >> Over thought? Today makes 2 out of the 3 times I've tried to >> 'show-off' trac hacks and it's been down. All three have been to [stuff deleted] First of all, thanks very much for getting t-h back up in October and the further work on moving it to the new server and working with apache. >> existing effort. >> > > Is there something that Noah's read-only mirror of TH doesn't provide A prominent link from trac.edgewall.org, a url like mirror.trac-hacks.org, or the ability to easily be pointed to as "www.trac-hacks.org" when the main server goes down. Best, Chris --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: wysiwyg editor (potential installation problem resolution/tip)
rupert thurner wrote: > hi, > > an excellent wysiwyg editor is available at > http://trac-hacks.org/wiki/TracWysiwygPlugin, > thanks to jun66j5! > For those seeing the js and css but not seeing the button to actually go into wysiwyg mode, I believe the problem may be that the plugin is not fully enabled. To fully enable it, you not only have to put the bit in trac.ini as described, but you must also restart the webserver under some configurations (such as mod_python). Hope this helps someone, Chris --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
