[Trac] Short-term Trac consulting gig: move a Trac to a new machine
I apologize in advance if this is an inappropriate use of this list. We have a multi-Trac 0.12.x install here, and need to migrate one of them to a different machine (both Ubuntu though). We have some customizations (including a customized trac-git plugin and other things) that make it a little non-trivial. If anyone here has expertise in this area and would be interested in a short-term consulting gig to do this migration, please let me know OFF-LIST. Thanks! -- . . . . . . . . . . . . . . . . . . . . . . Gary Oberbrunner ga...@genarts.com VP Engineering Tel: 617-492-2888 GenArts, Inc. www.genarts.com -- You received this message because you are subscribed to the Google Groups Trac Users group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-users+unsubscr...@googlegroups.com. To post to this group, send email to trac-users@googlegroups.com. Visit this group at http://groups.google.com/group/trac-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Trac] Trac and Git: ready for prime time?
On 10/15/2010 8:28 AM, Matthew Caron wrote: On 10/14/2010 05:27 PM, Gary Oberbrunner wrote: Our repo has around 7k files and around 17k commits total, so it's not huge. But the trac source browser takes upwards of 30-60 seconds just to display the top-level source dir! We actually dodged this problem because we needed git multirepository support, so we changed the post-commit hook to insert links in the ticket on commit to the relevant repository in gitweb. We don't actually use the git source browser. Hmm. So what about the timeline? And diffs? Or do you just use Trac as a ticketing system? -- . . . . . . . . . . . . . . . . . . . . . . . . . Gary Oberbrunnerga...@genarts.com GenArts, Inc. Tel: 617-492-2888 955 Mass. Ave Fax: 617-492-2852 Cambridge, MA 02139 USA www.genarts.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-us...@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] Trac and Git: ready for prime time?
We have a Trac instance that's been serving our svn repo for many years and we've been very happy with it. We've just converted to git, and we're using the Trac Git plug-in (http://trac-hacks.org/wiki/GitPlugin) with Trac 0.12 and it works; but everything's gotten a lot slower, and we're not sure Trac and the git model really get along very well yet. Our repo has around 7k files and around 17k commits total, so it's not huge. But the trac source browser takes upwards of 30-60 seconds just to display the top-level source dir! Most of that is related to filling in the metadata columns for each file (date, last rev, etc.) The timeline is slow too, because it also makes a *lot* of queries to git. We've made some simplifications, and things are OK now performance-wise, but it seems like there's still a lot to do. Here's a few of the things that bug us right now: there's some mismatch between Trac's svn-like model of the world and git's; in the source browser, for instance, Trac asks for the youngest rev in the repo, but in git that could be on *any* branch -- so Browse Source sometimes takes you to master, and sometimes it takes you to some other branch. Tags don't show up in the timeline because the git plugin doesn't yet implement ITimelineEventProvider (we have a version of that in-house that works OK now). Previous/next change links are pretty senseless because they cross branches too (this is http://trac.edgewall.org/ticket/1492). I'm wondering who else is using Trac with git repos? Are others working on fixing these same issues? It might make sense to work together or at least share experiences. Is it appropriate to post git-related bugs or suggestions to Trac anywhere, or should they all be considered GitPlugin issues? For comparison, how's the Mercurial side coming? Are people running non-trivial hg repos in Trac? Do they face similar model-mismatch issues? How's the performance? -- Gary Oberbrunner -- You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-us...@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] Wiki markup in ticket titles?
Does anyone have a trac plug-in to allow wiki markup (specifically rXYZW) in ticket titles? We often have tickets like Merge rXYZ into other branch and those aren't clickable, at least in v0.12. I'd even be OK with the wiki markup only getting interpreted in the ticket view (as opposed to the timeline view). Thanks! -- . . . . . . . . . . . . . . . . . . . . . . . . . Gary Oberbrunnerga...@genarts.com GenArts, Inc. Tel: 617-492-2888 955 Mass. Ave Fax: 617-492-2852 Cambridge, MA 02139 USA www.genarts.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-us...@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] New plugins: a true Test Case Manager
On 8/18/2010 10:05 AM, Roberto Longobardi wrote: Hi Olemis, I have introduced the Test Plans feature in the plugin http://trac-hacks.org/wiki/TestManagerForTracPlugin. We tried to install this here but it appears to be incompatible with Trac 0.12. Are you planning to update it to 0.12? -- Gary -- You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-us...@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] Migrating from svn to hg or git with trac: will changeset wiki links break?
On 5/13/2010 2:31 PM, Noah Kantrowitz wrote: You could make a plugin that handles r\d+ syntax and force it to load before trac.versioncontrol. That plugin could then handle looking up rev-sha mappings in a table somewhere (depending on how fancy you wanted to get). Thanks for the pointer! I have this implemented now but I don't think it's actually handling the links. How do I force it to load before trac.versioncontrol? We're running 0.12.1dev-r9968 on Ubuntu. -- Gary -- You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-us...@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] Migrating from svn to hg or git with trac: will changeset wiki links break?
- Original Message - We're considering moving from svn to hg or git (who isn't?), Me! At least I have no worries with svn at the moment. Would you mind elaborating on what is so bad with svn / so good with hg/git? Wow, where to start. :-) Faster/easier branching, merging, sensible tagging, speed, distributed development, rename support, speed, local commits (disconnected workflow), every repo is a backup, speed, disk space savings, ... Google around if you've been living under a source-control rock. :-) -- -- Gary Oberbrunner -- You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-us...@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] Migrating from svn to hg or git with trac: will changeset wiki links break?
We're considering moving from svn to hg or git (who isn't?), and I'm worried about all the trac wiki links that point to rev numbers. I have a few questions: * If we switch to a dvcs, what does trac use after the r or in the [123] to refer to a changeset? Shortened SHA-1? * If I switch my repo from svn - hg or svn - git, is there any way for trac to update all the rXYZ links (in tickets, wiki pages, milestones, etc.) to point to the new changesets? Has anyone done this successfully? Have any pointers? Thanks, -- -- Gary Oberbrunner -- You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-us...@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] Re: Trac in trouble.
Noah Kantrowitz wrote: Well work that idea out in more detail. How do you share things, and how do you not share things. Things like plugins probably have to be global just as an implementation detail, but what about other stuff. User preferences should be shared between projects? Etc etc. What about UI, how do you handle submitting a new ticket. Start writing up use cases from other multi-project systems, and showing how to implement them (what options to set) in this model. OK, will do. -- Gary --~--~-~--~~~---~--~~ 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 in trouble.
Noah Kantrowitz wrote: ... So, in summary, #5 is the only real issue on this list and that has been on our roadmap forever. Everything else is just a failure to either read the documentation or to find the right plugin. Well, to be fair I think #3, if interpreted as subproject support, has been outstanding for quite some time (See http://trac.edgewall.org/wiki/TracMultipleProjects/SingleEnvironment, http://trac.edgewall.org/wiki/GenericTrac, http://trac.edgewall.org/ticket/130 etc.) But maybe that's not Jani's meaning? -- Gary Oberbrunner --~--~-~--~~~---~--~~ 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 in trouble.
Noah Kantrowitz wrote: I have also explained many times on this list why we have put off multiple project support (including subprojects), but just for kicks: People are very quick to ask for multiple project support, citing tools like GForge or Redmine that can do it so it must be easy. This fails to take a very important part of the Trac philosophy into mind; we go as far as humanly possible to not enforce any project management philosophies on the end user. The fundamental problem with mutli-project support is that if you ask 10 people what they want from it, you get back 10 different critical feature lists. This leaves us in a quandary. Constructing a single design that allows all of those styles is incredibly tricky and not something that can be done overnight. If someone has suggested such an overarching design, I have yet to see it. The simple solution to this for right now is to leave multiple project handling in the domain of plugins and scripts for right now. This means each plugin can experiment design-wise without impacting the users of another plugin. Over time I suspect we will see a small number of these plugins become the de-facto standard, and then at that point it is much easier to talk about integrating the few winning designs into Trac core. So, in short, if you think mutli-project support is easy and know how it should be done, go prove me wrong. Really, I won't be offended. Make something that everyone acknowledges is The Right Way To Do It and we can move forward, but without that we have bigger fish to fry. Interesting. I didn't realize it was so controversial! It seems to me that implementing http://trac.edgewall.org/ticket/1048, which is basically my suggestion from http://lists.edgewall.com/archive/trac/2005-May/002932.html, and the leading suggestion from #130 as well, would be easy and would satisfy at least some of these requirements, without precluding other different multi-project models -- so IMHO it escapes your quandary about needing one overall architecture that satisfies all comers. Also doing this in a plug-in is quite difficult. I guess I just don't see the downside to adding a Project table and related fields. (And btw this is exactly how Redmine does it; see http://forge.typo3.org/repositories/entry/team-forge/redmine/db/schema.rb). Quoting from that email: ... a good way to do this would be to continue to use a single sqlite database, but add a Projects table, and a 'project' field to tickets, versions, milestones, and anything else that's per-project. The default project (project id 0) could be the null project for compatibility, then anyone not using this feature would see no change. The Projects table could specify repository subdirs for each project; in our case they'd all be the same (top-level). Then just tweak a bunch of sql queries to use the proper Project where needed. Later on ticket model changes could allow tickets to be part of multiple projects if desired and so on -- that part is easily handled by a plugin. -- . . . . . . . . . . . . . . . . . . . . . . . . . Gary Oberbrunner[EMAIL PROTECTED] GenArts, Inc. Tel: 617-492-2888 955 Mass. Ave Fax: 617-492-2852 Cambridge, MA 02139 USA www.genarts.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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Trac in trouble.
Noah Kantrowitz wrote: And, as many people have noted in this thread, redmine is generally quite inflexible. There is always a downside to everything, adding more code is a higher maintenance burden if nothing else. I do agree that I think that model is a step in the right direction for single-environment mutli-project, but it isn't the full picture (yet). OK, how can I help get trac to the full picture? I'm willing to invest some time, because otherwise we will have to switch away from Trac and that itself will cost me some time. -- Gary --~--~-~--~~~---~--~~ 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] Ticket query replacing report module
Hi folks; I'm running 0.11 (or nearly), and would like to write a new report. I know that the report module's getting phased out in favor of TracQuery language. I read http://trac.edgewall.org/wiki/TracQuery but two major things I don't see are how to select output columns nor how to select grouping nor sorting. I made some queries myself and I see those are done by col=col=, group=xxx, and order=xxx respectively. Perhaps those should be documented in TracQuery on t.e.o? And one more question: is it possible to select multi-level sorting like in SQL: order by foo,bar? I tried order=foo|bar and order=fooorder=bar but neither seemed to work for me. thanks again for a great tool! -- Gary --~--~-~--~~~---~--~~ 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: CSS styling to adjust appearance of lists in wiki?
Scott Bussinger wrote:
I came up with a way to accomplish the same effect a different way and
it works the same in both Firefox and IE7:
.wikipage p { margin-bottom:0px; }
.wikipage ul, ol { margin-top:0px; }
This removes the margin below paragraphs and above lists.
+1. This is very nice, and doesn't seem to mess up other formatting.
-- Gary
--~--~-~--~~~---~--~~
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: Link check-in comments to a Ticket
David Chiew wrote: Hi All, When entering comments using SubVersion, I’d like to be able to type in eg. #123 and for this to link to a ticket number. This should work fine. The other direction (find all wiki pages/tickets/svnlogs referencing a given ticket) is harder. I can see that Trac does show #123 as a hyperlink in the timeline, but the most important part which I can’t get to work is: - View ticket details - See a list of relevant changesets I think you want to look at trac-post-commit-hook in contrib. Won't help with your existing data but it will add reverse links for future commits. -- Gary Oberbrunner --~--~-~--~~~---~--~~ 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: Single Project/env - segregated tickets
[EMAIL PROTECTED] wrote: I would like to use a single project but have tickets grouped into logical projects. For example, when I go into view tickets, I would like to be to view tickets for logical project 1, logical project 2, etc. I would like to use a single physical project so that my authentication/authorization requires only one setup and single sign on for users. See http://trac.edgewall.org/wiki/TracMultipleProjects/SingleEnvironment, http://trac.edgewall.org/wiki/GenericTrac, http://trac.edgewall.org/ticket/130, and so on. -- Gary Oberbrunner --~--~-~--~~~---~--~~ 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: Milestone or Component Hierarchy?
[EMAIL PROTECTED] wrote: If we want to implement this hierarchy into the Trac code ourself, would this be a huge task? This discussion might give you some context and/or ideas: http://trac.edgewall.org/wiki/TracMultipleProjects/SingleEnvironment http://lists.edgewall.com/archive/trac/2005-May/002932.html http://trac.edgewall.org/wiki/TracMultipleProjects/ByProductAndSearch I think the basic answer, providing a new project table and links to it from tickets, milestones and wiki, would be pretty simple. But others may disagree. -- . . . . . . . . . . . . . . . . . . . . . . . . . Gary Oberbrunner[EMAIL PROTECTED] GenArts, Inc. Tel: 617-492-2888 955 Mass. Ave Fax: 617-492-2852 Cambridge, MA 02139 USA www.genarts.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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: anyone using agilo plugins?
Noah Kantrowitz wrote: I've just started testing these plugins for my team, so far I like what I see. Given they don't seem to know Trac isn't an acronym, I would avoid them. I don't think English is their native language. (I assume you're referring to the periodic use of TRAC or trac rather than consistently Trac). But I don't know anything about them either. Does seem odd that Trac isn't more prominent on their site though, since their product is a plug-in for Trac. -- Gary Oberbrunner --~--~-~--~~~---~--~~ 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: Mutiple-Branches vs Mutliple Projects...
[EMAIL PROTECTED] wrote: I have a trac 'related' question, although it is primarily a Subversion/philosophy question. I am on a project that has 2 very distinct parts. An embedded device, and a sister application that runs entirely on PC. From trac, I will run them as separate milestones with separate components. The question is really what is the best strategy for maintaining this in the repo. I EVENTUALLY want some sort of continuous build/unittest framework (say, bitten) but one step at a time. The PC app is on language x while the embedded stuff is in language Y, so whatever I do will require separate set-ups etc. I have suggested in the past a Trac architecture for this: * a new table, project, looking like this: id integer PRIMARY KEY, nametext, description text * make tickets, milestones, and wiki entries (and maybe components?) have a project id, so for instance you could have project A with milestone v1.0 and project B with milestone v1.0 but they are distinct milestones. * the default project ID, 0, means no project, i.e. current behavior. * update various pages and sql queries to allow project selection, i.e. where project_id = selected_project_id or sometimes where project_id = selected_project_id or project_id = 0 to also show the default (non-project-specific) items. * add a new page for project maintenance (create, update, delete) (Or do it via trac-admin) There was also a proposal in http://trac.edgewall.org/wiki/TracMultipleProjects/ByProductAndSearch which is much more complex but notes that it would be nice to have repository paths per project. I don't think most people seem to value this organizational structure though; I haven't ever gotten any interest in implementing it. -- Gary Oberbrunner --~--~-~--~~~---~--~~ 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
Tyrone Hed wrote: ... File /usr/local/lib/python2.5/site-packages/trac/web/main.py, line 456, in send_project_index req.hdf = HDFWrapper(loadpaths) File /usr/local/lib/python2.5/site-packages/trac/web/clearsilver.py, line 135, in __init__ raise TracError, ClearSilver not installed (%s) % e TracError: ClearSilver not installed (No module named neo_cgi) Can't you just modify /usr/local/lib/python2.5/site-packages/trac/web/clearsilver.py to print sys.path just before it tries to import it (somewhere before line 135) and see where it's looking for neo_cgi? Or just add str(sys.path) to the trac error line? Looks like it's trying to be helpful here. -- Gary --~--~-~--~~~---~--~~ 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
Tyrone Hed wrote: Gary, I attempted to do what you suggested but, apparently, I'm not up on the syntax of a Python script. I vi-edited the file and when I tried to run it got this: try: ^ IndentationError: unindent does not match any outer indentation level /apps/trac-0.10.4: Yes, python is sensitive to whitespace. You should not have touched the above line. Try this: except ImportError, e: raise TracError, ClearSilver not installed (%s; sys.path is %s) % (e, str(sys.path)) That last line is ALL ONE LINE starting with raise and ending with )). Ignore the email line wrapping. In other words, just edit the raise line til it looks like mine above. Keep any initial whitespace the same. Then restart the server and try it. It'll print where it's looking for the neo_cgi module, then you can take the next step which is to find out where it really is and why it's not found where python is looking. -- Gary --~--~-~--~~~---~--~~ 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
Tyrone Hed wrote: So by saying I need the setuptools you're saying 0.11 is going to be basically another version buffet like the previous versions. Another nightmare, in other words? nope. (Setuptools, a.k.a. easy_install, is like apt-get for python. It makes everything simple. But it's the baseline you have to have to make things simple.) -- Gary --~--~-~--~~~---~--~~ 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
Tyrone Hed wrote: Noah, Can you answer my last question please. This link you sent me: curl http://peak.telecommunity.com/dist/ez_setup.py | python curl http://trac.edgewall.org/changeset/latest/trunk?old_path=/filename=trunkformat=zip trac_src.zip easy_install trac_src.zip Does that execute on one line? Is curl a command? The is that intentional or an artifact of the install. It's three lines: curl http/... ez_setup.py | python curl http://trac... trac_src.zip easy_install trac_src.zip -- Gary --~--~-~--~~~---~--~~ 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
Tyrone Hed wrote: curl is not found on my system sorry, you're hosed. Yes, you could probably try wget, but you're in way over your head here. Whoever it was that said you need a pro hosting provider or a different tool (remember, trac is at 0.11! Not even close to 1.0 yet!) for your job was on the right track. Even if we get you up running today, how are you going to maintain trac? You need a lot more Unix (AIX) knowledge before diving into a project like this. -- Gary --~--~-~--~~~---~--~~ 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: Which Version of trac is This Fix In ?
Jeremy Mordkoff wrote: Back to the original (hypothetical) problem. I determine that the bug that my customer just reported is fixed in changeset 1234. How do I determine what version to give him that has this fix? It may be fixed in the trunk. It may be fixed in a branch. It may have been merged. How do I determine this? This is the wrong mailing list to be discussing this; it's for Trac, not Subversion. (Still, what you want to do is hard in Subversion. Read the red book to learn more.) -- Gary --~--~-~--~~~---~--~~ 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: Help with simple wiki macro: can a macro return more wiki markup (with macros)?
Christian Boos wrote: Hello, Gary Oberbrunner wrote: I'd like to write a new-style (v0.11, expand_macro) plug-in to return all the open and closed tickets for a given milestone: [[MilestoneInfo(Foo_2.1, Foo_2.0)]] (the second arg is the version to use when submitting a new ticket, see below) I'd like it to do exactly what this wiki markup does: = Foo 2.1: '''Open tickets:''' [[TicketQuery(milestone=Foo_2.1status!=closed)]] '''Closed tickets:''' [[TicketQuery(milestone=Foo_2.1status=closed)]] You can submit a [http://www/trac/newticket?milestone=Foo_2.1component=Fooversion=Foo_2.0 new ticket] here. = Can I just have my macro expand the above wiki text after appropriate string substitution, or do I need to do the ticket queries myself using sql, and build up the resulting HTML? (I hope not) In other words, what should expand_macro return? Wiki markup, or HTML? HTML, or rather a Markup string. This is what wiki_to_html () returns, so you could just build the wiki markup text above, call wiki_to_html() on it and return that. Just for the archives: I found a way to do this without using the deprecated wiki_to_html method: # Convert Wiki markup to HTML, new style out = StringIO() Formatter(formatter.context).format(text, out) return Markup(out.getvalue()) Perhaps the Formatter object could have a new wiki_to_html() method that would just do the above code? Seems like a common need, and it was easy the old way. -- Gary --~--~-~--~~~---~--~~ 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: TracMetrixPlugin Released
Deen Sethanandha wrote:
Hi All,
I finished the first public release of the TracMetrixPlugin
(http://trac-hacks.org/wiki/TracMetrixPlugin). I hope that it will be
useful for the community. Please give it a try if you are running or
plan to use Trac 0.11.
The plugin provides number of statistics and metrics by analyzing
the Trac database.
https://projects.cecs.pdx.edu/~bhuricha/SCOPE2/index.cgi/pdashboard
There are much more to improve on this plugin and I will take your
comments seriously.
Hi Deen; I just tried Trac Metrix Plugin and after installing the prereqs and
enabling it and doing the trac-admin upgrade, I had a few problems before I
got it working. The first was that matplotlib needs os.environ['HOME'] =
'/tmp' (it needs its HOME to be writable; it defaults to /var/www which is not
writable). I added that in model.py and mdashboard.py just before importing
matplotlib.
Then I rebuilt the egg and installed it, and then I could see the Dashboard
in my nav bar. But when I clicked it, I got this error (after waiting a
little while):
How to Reproduce
While doing a GET operation on `/pdashboard`, Trac issued an internal error.
Just click on the Dashboard link and wait a while.
Request parameters:
{{{
{'imagename': None}
}}}
System Information
|| '''Trac''' || `0.11dev-r5923` ||
|| '''Python''' || `2.4.3 (#1, Jun 13 2006, 11:46:08) ` [[br]] `[GCC 4.1.1
20060525 (Red Hat 4.1.1-1)]` ||
|| '''setuptools''' || `0.6c5` ||
|| '''SQLite''' || `3.3.3` ||
|| '''pysqlite''' || `1.1.7` ||
|| '''Genshi''' || `0.5dev-r715` ||
|| '''Pygments''' || `0.6` ||
|| '''Subversion''' || `1.3.2 (r19776)` ||
Python Traceback
{{{
Traceback (most recent call last):
File
/usr/lib/python2.4/site-packages/Trac-0.11dev_r5923-py2.4.egg/trac/web/main.py,
line 406, in dispatch_request
dispatcher.dispatch(req)
File
/usr/lib/python2.4/site-packages/Trac-0.11dev_r5923-py2.4.egg/trac/web/main.py,
line 216, in dispatch
resp = chosen_handler.process_request(req)
File build/bdist.linux-i686/egg/tracmetrixplugin/web_ui.py, line 119, in
process_request
File build/bdist.linux-i686/egg/tracmetrixplugin/web_ui.py, line 192, in
_render_view
File build/bdist.linux-i686/egg/tracmetrixplugin/model.py, line 423, in
get_daily_backlog_history
ValueError: list.remove(x): x not in list
}}}
I tried protecting that line with a try/except/pass (only for ValueError) and
now it gets past that, but then it failed with this error: RuntimeError: Could
not open file /usr/share/trac/genarts/cache/tracmetrixplugin/dailybacklog.png.
Here's the traceback:
Python Traceback
{{{
Traceback (most recent call last):
File
/usr/lib/python2.4/site-packages/Trac-0.11dev_r5923-py2.4.egg/trac/web/main.py,
line 406, in dispatch_request
dispatcher.dispatch(req)
File
/usr/lib/python2.4/site-packages/Trac-0.11dev_r5923-py2.4.egg/trac/web/main.py,
line 216, in dispatch
resp = chosen_handler.process_request(req)
File build/bdist.linux-i686/egg/tracmetrixplugin/web_ui.py, line 119, in
process_request
File build/bdist.linux-i686/egg/tracmetrixplugin/web_ui.py, line 193, in
_render_view
File build/bdist.linux-i686/egg/tracmetrixplugin/model.py, line 488, in
get_daily_backlog_chart
File
/usr/lib/python2.4/site-packages/matplotlib-0.90.1-py2.4-linux-i686.egg/matplotlib/figure.py,
line 759, in savefig
self.canvas.print_figure(*args, **kwargs)
File
/usr/lib/python2.4/site-packages/matplotlib-0.90.1-py2.4-linux-i686.egg/matplotlib/backends/backend_agg.py,
line 478, in print_figure
self.renderer._renderer.write_png(str(filename))
RuntimeError: Could not open file
/usr/share/trac/genarts/cache/tracmetrixplugin/dailybacklog.png
}}}
I changed the permissions on that dir to 777 manually, and now it works! So I
think whoever's creating that dir just needs to do a chmod on it after the
mkdir.
Hope that's helpful, and thanks for a really nice plug-in!
--
Gary
--~--~-~--~~~---~--~~
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] bug: Edit Milestone defaults to moving all open tickets to milestone None
If you edit a milestone, the checkbox to Retarget associated open tickets to milestone: defaults to checked, and the target milestone is None. If you don't notice that and just change the milestone text or date or whatever, all of a sudden all your tickets for that milestone are gone (moved to None). And there's no easy way to get them back except one by one. This is in 0.11dev-r5923 (trunk as of a couple of weeks ago). Seem like a bug to anyone else? (Of course batch modify tickets would help here... but I still think moving them by default is dangerous.) I'll file a ticket, but just wanted to let folks know... -- Gary Oberbrunner --~--~-~--~~~---~--~~ 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] format included wiki text as html?
Hi; I'm writing a sort of wiki-Include plugin for 0.11. I have my expand_macro(self, formatter, name, args) function implemented, and it wants to take some wiki-formatted text and return it from the macro. I understand macros have to return HTML, right? (Not sure how nested macros work in that situation, but anyway...) what do I call to process a string of wiki text into html? I tried formatter.format(text) but that didn't work. I'd like to do this without any deprecated methods (e.g. wiki_to_html?) too. thanks, -- Gary --~--~-~--~~~---~--~~ 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: Preliminary port of Tags to 0.11
Alec Thomas wrote:
Hello,
I've made a start at porting Tags to 0.11. It's pretty much feature
equivalent to the 0.10 version as it stands.
To try it out:
easy_install http://trac-hacks.org/svn/tagsplugin/trunk/
It requires Genshi trunk, so it'll probably pull that down as well.
Works for me against current Trac trunk, r5903. Please test and
respond with any issues.
Hi Alec -- thanks very much for this! I just updated to the trac trunk and
installed tags as above. Basic things work out of the box.
I got an error with the following tags URL:
http://www/trac/tags/foobar
NameError: global name 'escape' is not defined
I fixed that by importing 'escape' from trac.util.html in web_ui.py.
But then I get another error later on while processing the same URL:
AttributeError: 'NoneType' object has no attribute 'perm'
This is deep in the formatter code. Apparently at tractags/macros.py line
215, there's this code:
htitle = wiki_to_oneliner(title, self.env)
which ends up calling back like this:
...Trac-0.11dev_r5912-py2.4.egg/trac/wiki/formatter.py:1052
...Trac-0.11dev_r5912-py2.4.egg/trac/wiki/formatter.py: 881 (format)
... then into python's SRE module, and then back out:
...Trac-0.11dev_r5912-py2.4.egg/trac/wiki/formatter.py: 735 (replace)
...Trac-0.11dev_r5912-py2.4.egg/trac/wiki/formatter.py:728 (handle_match)
...Trac-0.11dev_r5912-py2.4.egg/trac/wiki/api.py: 309 (wikipagename_link)
...Trac-0.11dev_r5912-py2.4.egg/trac/wiki/api.py:345 (format_link)
and that last function wants a Request object from the formatter, which it
turns out is None:
req = formatter.context.req
context = Context(self.env, req)('wiki', id=page, version=version)
if 'WIKI_VIEW' not in req.perm(context):
So I fixed that by passing the req object into wiki_to_oneliner in both places
in macros.py. Then I'd get the same error when I explicitly call
[[ListTagged('foo')]] in a wiki page:
Error: Macro ListTagged('releaseprocedure') failed
'NoneType' object has no attribute 'perm'
so I just looked around and passed the req object into a few more places. Now
everything seems to be working for me! I'm extremely happy to be able to run
0.11 now!!!
Patch attached. I'll submit it to trac-hacks as well.
-- Gary Oberbrunner
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---
Index: tractags/api.py
===
--- tractags/api.py (revision 2566)
+++ tractags/api.py (working copy)
@@ -108,7 +108,7 @@
Remove all tags from a name in a tagspace.
self.remove_tags(req, name, self.get_name_tags(name))
-def name_details(self, name):
+def name_details(self, req, name):
Return a tuple of (href, htmllink, title). eg.
(/ticket/1, a href=/ticket/1#1/a, Broken links)
raise NotImplementedError
@@ -174,10 +174,10 @@
cursor.execute('DELETE FROM tags WHERE tagspace=%s AND name=%s',
(self.tagspace, name))
db.commit()
-def name_details(self, name):
+def name_details(self, req, name):
from trac.wiki.formatter import wiki_to_oneliner
return (getattr(self.env.href, self.tagspace),
-wiki_to_oneliner('[%s:%s %s]' % (self.tagspace, name, name),
self.env), '')
+wiki_to_oneliner('[%s:%s %s]' % (self.tagspace, name, name),
self.env, req=req), '')
class TagspaceProxy:
A convenience for performing operations on a specific tagspace,
@@ -356,10 +356,10 @@
return result
-def name_details(self, tagspace, name):
+def name_details(self, tagspace, req, name):
Return a tuple of (href, htmllink, title). eg.
(/ticket/1, a href=/ticket/1#1/a, Broken links)
-return self._get_tagsystem(tagspace).name_details(name)
+return self._get_tagsystem(tagspace).name_details(req, name)
# ITaggingSystemProvider methods
def get_tagspaces_provided(self):
Index: tractags/web_ui.py
===
--- tractags/web_ui.py (revision 2566)
+++ tractags/web_ui.py (working copy)
@@ -6,7 +6,7 @@
from trac.web.chrome import ITemplateProvider, INavigationContributor,
add_stylesheet
from trac.web.api import ITemplateStreamFilter
from trac.wiki.api import IWikiPageManipulator
-from trac.util.html import Markup
+from trac.util.html import Markup, escape
from trac.util.compat import set
from trac.wiki.web_ui import WikiModule
from trac.wiki.formatter import wiki_to_oneliner
Index: tractags/ticket.py
[Trac] Re: Should I use 0.11 in production now?
ryan wrote: Should I use 0.10.4 and go through the process of installing and tuning plug-ins, or should I just install some version of 0.11 and be prepared to continually upgrade my codebase towards a stable version of 0.11? I'd be interested to hear the opinions of trac veterans on this issue. My goal is to pick the path which minimizes the amount of upgrading work I'll have to do until I finally arrive at a stable 0.11 in production. I think it mostly depends on what existing plug-ins you use. Some very popular ones like TracTags are not ported to 0.11 yet, so you have to stick with 0.10 if you want to use them. See www.trac-hacks.org for the status of all the plug-ins. Migrating a plug-in to 0.11 is not a matter of tuning since large parts of the API changed (ClearSilver - Genshi plus other changes). -- Gary --~--~-~--~~~---~--~~ 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: Any idea about trac 0.11
Christian Boos wrote: Anton wrote: Hi, I only wanted to know about the release date of trac 0.11: All the major items are now in place. ... Hi folks -- we are eagerly awaiting this! We'd already be running it from the trunk, except for plugins; any news on TracTags, BatchModify, or RevTree? (We can't live without tags; we think it should be built in. Best plugin ever.) -- Gary --~--~-~--~~~---~--~~ 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: Help installing Trac on Pair.com account
jimsnaps wrote: I'm having the same issue. Does anyone have any insight into how to fix/workaround this issue? On Apr 4, 6:58 pm, Casey [EMAIL PROTECTED] wrote: I'm in need of installing Trac on Pair Networks, i've contacted support about this and they assured me that the install would be fine. Yet when I run it, I get this error. Question: even if you get Trac running (presumably via cgiwrap so the permissions come out OK?) at Pair, how are you going to connect it to a subersion repository? I didn't think you could serve subversion repos from a shared Pair server due to them not allowing long-running daemons and killing processes with more than 16MB of RAM and so on... -- or maybe you can now? Or maybe you have a dedicated server there? -- Gary --~--~-~--~~~---~--~~ 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: Problems after upgrade to HEAD
Sarah George wrote: I've been working on the same thing: Getting trac 0.11 usable. Two of your problems might be solved by knowing there seems to be a new setting in trac.ini called base_url... try making sure that's set. What should this be set to in 0.11? Complete URL including protocol host? In our case that would not work, since our trac is accessible via two different hostnames; trac-generated URLs have to preserve the correct one. I tried just the part after the host, like /trac, but still had some problems... -- Gary --~--~-~--~~~---~--~~ 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: Possible to use plain text instead of wikiformatting?
Christian Boos wrote: Gary Oberbrunner wrote: Christian Boos wrote: A middle term would be to simply respect newlines, as we already do for changeset messages. That would avoid most of the issues. I wanted to do that for 0.11 anyway, but wondered about what the default should be. Like we have now, or escape newlines enabled by default? I'd like escape-newlines to be on. What about a compromise: respect newlines after 50 chars? I.e. short lines stay short; long lines wrap. Creole respects source line breaks too. Just to clarify: I was talking about respecting newlines in the context of ticket description and comments only, not in general. In regular Wiki pages, I prefer to keep the ability to break down a paragraph in multiple lines, as this gives clearer diffs. Agreed, me too. -- Gary --~--~-~--~~~---~--~~ 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: Possible to use plain text instead of wikiformatting?
Christian Boos wrote: A middle term would be to simply respect newlines, as we already do for changeset messages. That would avoid most of the issues. I wanted to do that for 0.11 anyway, but wondered about what the default should be. Like we have now, or escape newlines enabled by default? I'd like escape-newlines to be on. What about a compromise: respect newlines after 50 chars? I.e. short lines stay short; long lines wrap. Creole respects source line breaks too. -- Gary --~--~-~--~~~---~--~~ 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] Backup before updating to trunk?
Hi; I'm currently using trac SVN r3790 (from Sept. 25). At that point it was working well, and we were in crunch mode so I didn't want to touch it. I'd now like to update to the latest trunk to get the latest good stuff and be prepared for the upcoming wonderfulness (blame, workflow, etc.). My question is, since trac is in daily use (3 developers), how can I make 100% sure I can go back to my existing version if my upgrade goes bad? I know I should start with this: trac-admin /path/to/trac/projenv hotcopy ~/trac-backup. But what about the Python modules in my python site-packages, the stuff in /path/to/trac (i.e. one level above my projenv), and is there anything else I might need to put back? I'm using SQLite and svn backend, btw. (I'm partly worried that some plugins might stop working; webadmin, tractags, graphviz? But mostly I just want to make sure trac doesn't completely break.) Thanks, -- Gary --~--~-~--~~~---~--~~ 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: Announce new version of email2trac (version 0.8.2)
Bas van der Vlies wrote: - Fixed an error in Ticket Update. When ticket does not exists, proceed as if it is a new ticket I may be interested in this plugin, but I don't see in the documentation how emails are mapped to existing tickets, and what fields in the email are used to update the ticket (change status, take, etc.). There must be certain conventions used, yes? -- Gary Oberbrunner --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[Trac] Re: Announce new version of email2trac (version 0.8.2)
Bas van der Vlies wrote: Yes there is a convention. When i ticket is inserted it gets a tickets id, eg #4 This number is inserted in the description field of ticket. This is the same as the subject line for emails (notifications). If you hit reply and update_ticket is set and #4 is not removed from the subject line it will try to update the ticket. Thanks, I see. It must have a regex matching the subject against something like '\b#[0-9]+\b'. That makes sense. And then how does it actually update the ticket (change status, etc.)? Is that done by similar special regexes in the body, kind of like how the trac post-commit hook works? thanks! -- Gary --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[Trac] PageTemplates question
I see the nice new PageTemplates stuff (r3881, #962). I'm wondering if it would be hard to extend this to milestone templates? Perhaps milestones could look for PageTemplates/Milestone and use that for their default content? Or alternatively, MilestoneTemplates/* like PageTemplates now? (With selector at the bottom of the Roadmap page next to Add New Milestone) Is anyone other than me interested? If so I'll file an enhancement. -- Gary Oberbrunner --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
