[Trac] Re: post-commit-hook and NoSuchChangeSet error
Emmanuel Blot wrote: I'm not using a pre-commit hook, and I wouldn't want to use one that rejected all commits without a ticket attached (svn mkdir in particular)! That's just not appropriate in our case. I'm not sure the post commit script can be used w/o the pre commit script: if you've removed the pre-condition checks on purpose, it's not surprising the post commit hook fails in some conditions. No, it's fine to just have the trac-post-commit-hook script enabled. OTOH, one must be sure that the version of the Trac hook corresponds to the version of Trac modules that get used by the script (either the Trac installed in site-libs or located by the PYTHONPATH set in the script) and that version must be the same (or at least compatible. API and database_version wise) with the version actually used. -- 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@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] ??: [Trac] Installing Trac using FastCGI in a shared hosting environment
- ?-
??: Eric Anderson [EMAIL PROTECTED]
: Trac Users trac-users@googlegroups.com
??: 28.06.07 5:55
: [Trac] Installing Trac using FastCGI in a shared hosting environment
Not sure if this is the right place to post a installation question so
please tell me where to post if this is the wrong place.
I am trying to install the latest stable version of Trac on my shared
hosting environment (Site5 to be specific). My basic steps were:
1. Download Trac
2. Run the install with the --prefix option to install in a directory
I can manage
3. Download ClearSilver
4. Install with the --prefix option to install where I desire
5. Create a Trac environment for my project
Now at this point I can run tracd and I have a working installation of
Trac. But I would like to make trac use Apache/FastCGI instead of
tracd but at least I know it is basically working. I'm attempting
plain CGI first before I throw in FastCGI to the mix.
To get tracd working all I had to do was update my PYTHONPATH to
include the libraries installed for trac and update my LD_LIBRARY_PATH
to include the ClearSilver libraries. So my assumption is the CGI
needs the same environment variables set so it can find the necessary
libraries. So I my next steps are:
1. Symlink the directories my webserver looks loads to the htdocs and
cgi-bin directory in trac. That way the resources and scripts are
available.
2. Create a .htaccess file that looks like the following so that
trac.cgi is always run unless a resource requested exists:
###
AddHandler fastcgi-script .fcgi
AddHandler cgi-script .cgi
Options +FollowSymLinks +ExecCGI
RewriteEngine On
RewriteCond %{REQUEST_FILENAME} !-f
RewriteRule ^(.*)$ cgi-bin/trac.cgi [QSA,L]
###
The .htaccess file was mostly borrowed from the way rails redirects to
it's dispatch file. This may be overkill and I may just need to
redirect a request for / to cgi-bin/trac.cgi.
3. Added the following to start of trac.cgi so the environment
variables are set right:
##
import os
os.environ['LD_LIBRARY_PATH'] = /home/pix/lib/clearsilver/lib
os.environ['PYTHONPATH'] = /home/pix/apps/trac/lib/python2.4/site-
packages:/home/pix/lib/clearsilver/lib:/usr/lib/python2.3/site-
--~--~-~--~~~---~--~~
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: Installing Trac using FastCGI in a shared hosting environment
On Jun 28, 11:55 am, Eric Anderson [EMAIL PROTECTED] wrote: Not sure if this is the right place to post a installation question so please tell me where to post if this is the wrong place. I am trying to install the latest stable version of Trac on my shared hosting environment (Site5 to be specific). My basic steps were: 1. Download Trac 2. Run the install with the --prefix option to install in a directory I can manage 3. Download ClearSilver 4. Install with the --prefix option to install where I desire 5. Create a Trac environment for my project ... 3. Added the following to start of trac.cgi so the environment variables are set right: ## import os os.environ['LD_LIBRARY_PATH'] = /home/pix/lib/clearsilver/lib os.environ['PYTHONPATH'] = /home/pix/apps/trac/lib/python2.4/site- packages:/home/pix/lib/clearsilver/lib:/usr/lib/python2.3/site- packages Don't set PYTHONPATH like that as it is too late by then. Instead use: import sys sys.path.insert(0, /home/pix/lib/clearsilver/lib) That you are inserting site-packages directories for two different Python versions looks very bad. Graham --~--~-~--~~~---~--~~ 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: Installing Trac using FastCGI in a shared hosting environment
On Jun 28, 6:56 am, Graham Dumpleton [EMAIL PROTECTED] wrote: Don't set PYTHONPATH like that as it is too late by then. Instead use: import sys sys.path.insert(0, /home/pix/lib/clearsilver/lib) That you are inserting site-packages directories for two different Python versions looks very bad. I thought that was odd also but that is the path the trac install put it under. Anyway thanks to your help I now have it running under CGI. Now my next task is FastCGI. --~--~-~--~~~---~--~~ 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] Clearing Sample Data
When setting up a new trac environment it comes with a bunch of sample data. It seems to be 4 milestones and the Trac manual. Is there anyway I can get it to not do this? Right now I am manually deleting each wiki page but that is time consuming. I am hoping to setup a trac environment for each project I work on and really don't want to do this on every project. I can live with the milestones but the wiki is a pain. --~--~-~--~~~---~--~~ 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: Clearing Sample Data
On 28/06/07, Eric Anderson [EMAIL PROTECTED] wrote: When setting up a new trac environment it comes with a bunch of sample data. It seems to be 4 milestones and the Trac manual. Is there anyway I can get it to not do this? Right now I am manually deleting each wiki page but that is time consuming. I am hoping to setup a trac environment for each project I work on and really don't want to do this on every project. I can live with the milestones but the wiki is a pain. If you're using 0.11dev then make sure you've given yourself TRAC_ADMIN and you can then edit milestones etc from the built-in web admin. If you're on 0.10x, then you can manage milestones from within the trac-admin command line utility. http://trac.edgewall.org/wiki/TracAdmin Regards Stephen --~--~-~--~~~---~--~~ 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: Integration of Trac and Bugzilla
Two easier options: 1) check out the bugzilla plugin for Trac 2) migrate from bugzilla to trac with the bugzilla2trac.py script HTH -Chrs On 6/27/07, cobwebsmasher [EMAIL PROTECTED] wrote: Hello. I am interested in connecting an instance of Trac and an instance of Bugzilla together. Currently I have both systems authenticating against the same LDAP repository (Microsoft Active Directory in this case), and want to take advantage of the better UI and ease of use features of Trac while not snatching everything out from under the engineering team by just migrating the bugs from Bugzilla and saying, Here you go - enjoy your new system. For this situation, I was wondering if anyone has done anything like adding a button to the View Ticket form that would post the Trac Ticket information to another system (like a Bugzilla). Short of just forcing the engineering team to start using Trac, an option we are considering is adding some functionality that would link the Trac ticket and it's corresponding Bugzilla item. The quick and dirty way would be to post comments to the Trac and Bugzilla ticket with links to each others' system, with a snippet web-form to do the job (i.e. a form that says enter the Trac ticket # and the Bugzilla ticket # you want to link), with this feature being automated by a Forward this ticket to Bugzilla feature that would generate a new bugzilla item - get the # out of the database and make the appropriate connections. I could probably get some mileage out of rewording this problem/issue, but my guess is that anyone that has had similar aspirations might have a sense of what I'm trying to do and hopefully some success that they would be willing to share? Heck, even making Bugzilla look like Trac from a style perspective would be a welcome solution --- I've seen this on one website before, but I can't find it to save my life again. Thanks, Vincent Food fight? Enjoy some healthy debate in the Yahoo! Answers Food Drink QA. --~--~-~--~~~---~--~~ 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: Clearing Sample Data
On Thursday 28 June 2007, Eric Anderson wrote: When setting up a new trac environment it comes with a bunch of sample data. It seems to be 4 milestones and the Trac manual. Is there anyway I can get it to not do this? Right now I am manually deleting each wiki page but that is time consuming. I am hoping to setup a trac environment for each project I work on and really don't want to do this on every project. I can live with the milestones but the wiki is a pain. The wiki pages provide the help text for the system; it is not recommended that you remove those. The sample milestones and components can be removed by a script around trac-admin. (Not saying that's ideal, just that that's what can be done at the moment.) Eli --~--~-~--~~~---~--~~ 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: Clearing Sample Data
On Jun 28, 10:44 am, Eli Carter [EMAIL PROTECTED] wrote: The wiki pages provide the help text for the system; it is not recommended that you remove those. If I want help I'll go to the main website. I'll keep key pages in there (page index, recent changes, wiki formatting) but most of that stuff is just annoying and in the way. The sample milestones and components can be removed by a script around trac-admin. (Not saying that's ideal, just that that's what can be done at the moment.) I think wiki pages can also be managed via trac-admin so perhaps I just need to craft a script that uses trac-admin convert the default environment to my preferred default environment. Thanks for the advice, Eric --~--~-~--~~~---~--~~ 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: Clearing Sample Data
* Eric Anderson [EMAIL PROTECTED] [2007-06-28 14:58]: I can get it to not do this? Right now I am manually deleting each wiki page but that is time consuming. I am hoping to setup a trac environment for each project I work on and really don't want to do this on every project. I can live with the milestones but the wiki is a pain. Look into share/trac/wiki-default in /usr or /usr/local or where you have trac installed. Files from there are imported to every project on creation, you can modify, remove, add them to your liking. -- Grzegorz Silk Sobańskisilk (at) boktor.net Error messages from an old Apple C compiler: http://boktor.net Call me paranoid but finding '/*' inside this comment makes me suspicious --~--~-~--~~~---~--~~ 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] Clearing Sample Data
Eric Anderson eman1000-at-gmail.com |TracMailingList| wrote: On Jun 28, 10:44 am, Eli Carter [EMAIL PROTECTED] wrote: The wiki pages provide the help text for the system; it is not recommended that you remove those. If I want help I'll go to the main website. I'll keep key pages in there (page index, recent changes, wiki formatting) but most of that stuff is just annoying and in the way. I agree with you on this one. The wiki contains lots of stuff that is of no interest to the trac *user*, as distinct from the trac admin. All the stuff on how to install, upgrade, import tickets, etc. is confusing for a user who just wants to report bugs. For what it's worth, what I did for this was heavily modify the first (top level) page of the wiki. It has links to things like wiki formatting, but does not contain links to the installation and admin pages. That hides those pages from normal users. The pages are still there, but they aren't visible. (In my installation I have a single link for admin off the top page, that gets me to those admin pages (locally, without having to go to the trac web site), but of course you don't have to have that if you don't want.) When I create a new project I just paste in my replacement top page, and all those extra pages are hidden from users. By the way, I think this issue is related to the thread Improving Trac's LookFee (sic) from a few days ago (25-Jun-2007). Most users want to do only two things -- report a bug (90%) and search for a bug (10%). I admit I made up those statistics, but I'll bet the 90% is an underestimate. Simplifying the wiki helps a little. However, the functionality in Trac is there, and I don't think that improving look and feel is a priority at this time -- the existing look and feel is acceptable. I would like to see the wiki structure changed so that there was essentially a users manual, and a admin manual. That would make it easier to provide users with just the help that they need. 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: possible flush of stderr causing post-commit script to fail with no output
Christopher Taylor wrote: Hello all, I'm running trac 0.10.3, apache 2.2.4, mod_python 3.2.8, timingandestimationplugin-0.3.8, TracBurndown-01.08.10, subversion 1.4.3 I'm using the trac-post commit hook from the timing and estimation plugin. When commiting to svn I got the error: Warning: 'post-commit' hook failed with error output: $ notice the empty line that's printed. I could live with an empty warning, but this causes the the post-commit changes to be backed out I tired running the script manually (on the server) after a commit and I got the error: Warning: 'post-commit' hook failed with error output: first run of update_burndown_data - insert needed $ After a little search it appears there was (what amounts to) an unconditional print to stderr in the burndown plugin (line 291/294), but I commented that out. I can now run the script manually on the server and everythign works fine, but I still get the warning (and the post-commit script then fails) when I commit and let svn run the post-commit script. based on the output it looks like there's an uncessary flush to stderr... I tried looking for it but I wasn't able to find it has anyone else had any experiences like this on the post-commit hooks for svn with trac? Respectfully, Christopher Taylor I am experiencing this problem too, running roughly the same versions (apache 2.2.3, subversion 1.4.2). I see that Chris reported the bug bug: http://www.trac-hacks.org/ticket/1590 -- -Eric 'shubes' --~--~-~--~~~---~--~~ 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] Blog? Bulletin Board?
Hi - I'm new here and was wondering how to setup the blog to be similar to these discussions, where you can view the topics of threads over time - similar to a bulletin or message board. Thank you. --~--~-~--~~~---~--~~ 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: swig bindings
Thank you for the link. I have tried it and when I do from svn import core I get: ImportError: /usr/local/lib/libsvn_ra_dav-1.so.0: undefined symbol: xmlCreatePushParserCtxt (On my other server with exactly the same environment where trac works flawlessly, if I run that command, I get 'svn' cannot be found but my svn-python bindings and trac work without any issues -- this confuses me even more). Further, when I run# cat /proc/7663/maps | grep .so | cut -d/ -f2- | sort -u I get the output that does not seem to match anything that is required. lib/ld-2.3.4.so lib/libdl-2.3.4.so lib/libtermcap.so.2.0.8 lib/libutil-2.3.4.so lib/tls/libc-2.3.4.so lib/tls/libm-2.3.4.so lib/tls/libpthread-2.3.4.so lib/tls/librt-2.3.4.so usr/lib/libpython2.3.so.1.0 usr/lib/libreadline.so.4.3 usr/lib/python2.3/lib-dynload/readline.so But my PYTHONPATH has '/usr/local/lib/svn-python' and that contains files generated by building swig 1.3.25, followed by buiding the svn, followed by 'make swig-py' which has created that folder. Robert On Jun 28, 1:42 am, Rony Cesana [EMAIL PROTECTED] wrote: I understand your frustration, as I was having the same problem... I'm not sure whether you've already tried this [1]: it did help me a lot, especially comparing the libraries lists... Rony [1]http://trac.edgewall.org/wiki/TracSubversion#unsupported-vcs Rob13 ha scritto: I am running to pretty much dead end. It is extremely frustrating It seems that swig binding issue is one of the leading installation issues with trac and yet there is only a scattered documentation on this. I am trying to post to swig, svn and python newsgroups but not expecting to get much help there. Robert --~--~-~--~~~---~--~~ 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] trac-hacks down
Hi, if somone from track-hacks.org is subscribed to the list: trac-hacks throws a 500. Rainer --~--~-~--~~~---~--~~ 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] Trac ticket resolved as dropdown box
Hi Is there away to change the resolve as drop down items names and add to the dropdown box the items are fixed, invalid , wontfix,duplicate, worksforme Thanks, Brian mailto:[EMAIL PROTECTED] --~--~-~--~~~---~--~~ 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 ticket resolved as dropdown box
On Thursday 28 June 2007, Brian McCann wrote: Hi Is there away to change the resolve as drop down items names and add to the dropdown box the items are fixed, invalid , wontfix,duplicate, worksforme In 0.11dev, through webadmin or trac-admin. In 0.10.*, you'd have to do SQL on the database. Eli --~--~-~--~~~---~--~~ 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] Gmail for SMTP?
Hi guys, I've never setup an SMTP server, so I figured I'd have Trac use Gmail's SMTP service. However my notifications seem to not be going through. Would someone be willing to take a look at my configuration file and see if you notice my problem? (Note: for smtp_user, I've tried it with with and without the @gmail.com suffix.) Thanks, Christian [notification] always_notify_owner = false always_notify_reporter = false always_notify_updater = true mime_encoding = base64 smtp_always_bcc = smtp_always_cc = [EMAIL PROTECTED] smtp_default_domain = smtp_enabled = true smtp_from = [EMAIL PROTECTED] smtp_password = MY.PROJECT'S.GMAIL.PASSWORD smtp_port = 465 smtp_replyto = [EMAIL PROTECTED] smtp_server = smtp.gmail.com smtp_subject_prefix = __default__ smtp_user = MY.PROJECT.EMAIL.ADDRESS use_public_cc = false use_short_addr = false use_tls = true --~--~-~--~~~---~--~~ 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: Gmail for SMTP?
More detail: (1) I *can* basically connect to smtp.gmail.com port 465. For example: [EMAIL PROTECTED]:~/trac/ivp/log$ telnet smtp.gmail.com 465 Trying 209.85.133.111... Connected to gmail-smtp.l.google.com. Escape character is '^]'. (2) I'm running tracd from the command-line, with myself (cjc) as the user. So (1) above presumably isn't using a different set of permissions than my tracd process has. (3) My symptom is that when I have smtp_enabled = true, submitting a ticked blocks the web browser. That is, after I hit the Submit Ticket button, my browser takes an indefinitely long period of time to go to the ticket submitted page. Ticket submission works just fine when I have smtp_enabled = false. Any help greatly appreciated. - Christian On Jun 28, 4:05 pm, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi guys, I've never setup an SMTP server, so I figured I'd have Trac use Gmail's SMTP service. However my notifications seem to not be going through. Would someone be willing to take a look at my configuration file and see if you notice my problem? (Note: for smtp_user, I've tried it with with and without the @gmail.com suffix.) Thanks, Christian [notification] always_notify_owner = false always_notify_reporter = false always_notify_updater = true mime_encoding = base64 smtp_always_bcc = smtp_always_cc = [EMAIL PROTECTED] smtp_default_domain = smtp_enabled = true smtp_from = [EMAIL PROTECTED] smtp_password = MY.PROJECT'S.GMAIL.PASSWORD smtp_port = 465 smtp_replyto = [EMAIL PROTECTED] smtp_server = smtp.gmail.com smtp_subject_prefix = __default__ smtp_user = MY.PROJECT.EMAIL.ADDRESS use_public_cc = false use_short_addr = false use_tls = true --~--~-~--~~~---~--~~ 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: Gmail for SMTP?
Remove the following line: smtp_port = 465 or use it with the regular SMTP port (25). Trac connects to the SMTP port, then kicks off a TLS connection. Do not append the domain for smtp_user. On 6/28/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: More detail: --~--~-~--~~~---~--~~ 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: Blog? Bulletin Board?
Sarah Rae wrote: Hi - I'm new here and was wondering how to setup the blog to be similar to these discussions, where you can view the topics of threads over time - similar to a bulletin or message board. http://www.dsource.org/projects/tracforums see it in action: http://www.dsource.org/projects/tango/forums BA --~--~-~--~~~---~--~~ 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: Integration of Trac and Bugzilla
Thanks, I've used the bugzilla2trac.py script, and it does an excellent job of moving bugs from bugzilla to Trac, but unfortunately the eng. team doesn't want to use Trac for all bugs just yet, just some, so bringing everything over into a system that wouldn't be in sync isn't quite so useful. Bugzilla plugin. Hmmm, Looking at it, it does seem interesting, although in this case, I don't want to lose the Trac ticket functionality as much as I want to integrate both. Any other ideas? I will definitely propose the bugzilla plugin to my group, though. Thanks for that thought. Vincent Christopher Taylor [EMAIL PROTECTED] wrote: Two easier options: 1) check out the bugzilla plugin for Trac 2) migrate from bugzilla to trac with the bugzilla2trac.py script HTH -Chrs On 6/27/07, cobwebsmasher wrote: Hello. I am interested in connecting an instance of Trac and an instance of Bugzilla together. Currently I have both systems authenticating against the same LDAP repository (Microsoft Active Directory in this case), and want to take advantage of the better UI and ease of use features of Trac while not snatching everything out from under the engineering team by just migrating the bugs from Bugzilla and saying, Here you go - enjoy your new system. For this situation, I was wondering if anyone has done anything like adding a button to the View Ticket form that would post the Trac Ticket information to another system (like a Bugzilla). Short of just forcing the engineering team to start using Trac, an option we are considering is adding some functionality that would link the Trac ticket and it's corresponding Bugzilla item. The quick and dirty way would be to post comments to the Trac and Bugzilla ticket with links to each others' system, with a snippet web-form to do the job (i.e. a form that says enter the Trac ticket # and the Bugzilla ticket # you want to link), with this feature being automated by a Forward this ticket to Bugzilla feature that would generate a new bugzilla item - get the # out of the database and make the appropriate connections. I could probably get some mileage out of rewording this problem/issue, but my guess is that anyone that has had similar aspirations might have a sense of what I'm trying to do and hopefully some success that they would be willing to share? Heck, even making Bugzilla look like Trac from a style perspective would be a welcome solution --- I've seen this on one website before, but I can't find it to save my life again. Thanks, Vincent Food fight? Enjoy some healthy debate in the Yahoo! Answers Food Drink QA. - Boardwalk for $500? In 2007? Ha! Play Monopoly Here and Now (it's updated for today's economy) at Yahoo! Games. --~--~-~--~~~---~--~~ 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] Drop down list for LDAP users and email
I am currently using LDAP authentication (Microsoft Active Directory) against Trac. Works wonderfully, although I admit it was a headache at first, so if anyone needs config files against Apache 2.x, feel free to ping me. :) I have 2 questions. 1. Email Notification to users. How do I get Trac to know what the email address is for the users in the LDAP directory? For login purposes, we are using the sAMAccount, which resolves to names like frank and jamie, whereas the email address is typically [EMAIL PROTECTED], [EMAIL PROTECTED] I am working on an instance of Trac for another client that seems to do auto-email to folks even when you only login as frank and jamie, but the admin has no idea how or why it is capable of doing this. Any ideas? 2. Drop down list for assign to: and cc: --- In Bugzilla, you have a drop down list for users when you want to assign tickets and or cc them. This is considered a good thing so that folks don't typo the heck out of their assignment/cc lists. Anyone know if there's a hack or plugin that would replicate that functionality? Ideally it would be able to do an LDAP lookup, but I would be happy with having a manual or database driven list as well if need be. Thanks, Vincent - Yahoo! oneSearch: Finally, mobile search that gives answers, not web links. --~--~-~--~~~---~--~~ 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: Drop down list for LDAP users and email
cobwebsmasher wrote: I am currently using LDAP authentication (Microsoft Active Directory) against Trac. Works wonderfully, although I admit it was a headache at first, so if anyone needs config files against Apache 2.x, feel free to ping me. :) I have 2 questions. 0. Please don't hit reply when starting a new thread. It breaks standards-compliant MUAs. 1. Email Notification to users. How do I get Trac to know what the email address is for the users in the LDAP directory? For login purposes, we are using the sAMAccount, which resolves to names like frank and jamie, whereas the email address is typically [EMAIL PROTECTED], [EMAIL PROTECTED] I am working on an instance of Trac for another client that seems to do auto-email to folks even when you only login as frank and jamie, but the admin has no idea how or why it is capable of doing this. Any ideas? 1. Look at smtp_default_domain in trac.ini 2. Drop down list for assign to: and cc: --- In Bugzilla, you have a drop down list for users when you want to assign tickets and or cc them. This is considered a good thing so that folks don't typo the heck out of their assignment/cc lists. Anyone know if there's a hack or plugin that would replicate that functionality? Ideally it would be able to do an LDAP lookup, but I would be happy with having a manual or database driven list as well if need be. 2. restrict_owner in trac.ini --Noah signature.asc Description: OpenPGP digital signature
[Trac] HTDigest, mod_proxy_rewrite, and infinite loops on login
I seem to be on a posting roll today. Apologies for the spike in traffic.
Last question for the week. :)
I am maintaining an instance of Trac that is hosted on textdrive nee' Joyent.
These guys don't allow access to the main Apache conf file, so I have to do any
jiggy cuteness with Apache by using directory specific .htaccess files.
Because of the lockdown on Apache, rather than using mod_python through Apache,
I am forced to use tracd on a specific port.
So I have tracd running on a specific port , utilizing a specific digest
file.
In an .htaccess file under /tracweb, I have mod_rewrite rules proxying any
requests to /tracweb to the tracd instance running at port .
Everything works hunky dory until it comes time to authenticate. If I attempt
to authenticate directly to the tracd instance at port , everything works
perfectly. However, if I attempt to authenticate by clicking LOGIN from
/tracweb, it accepts my credentials and then proceeds to go into an infinite
loop when attempting to login.
The error I see in my logs is:
[Thu Jun 28 15:03:44 2007] [error] [client 84.42.203.214] Digest: invalid nonce
3f29a221bf8dc7164e2ab27fd922fd34 received - length is not 52
Below is my .htaccess file (w/names changed to protect the innocent)
===
AuthUserFile /{blah}/trac.digest.passwd
AuthGroupFile /{blah}/groups.htgroups
AuthType Digest
AuthDigestProvider file
AuthName {foo}
require group all
RewriteEngine On
RewriteRule ^trac_common/(.*) http://127.0.0.1:9006/trac_common/$1 [P]
RewriteRule ^trac/?(.*) http://127.0.0.1:9006/$1 [P]
RewriteRule ^project1(.*) http://127.0.0.1:9006/project1$1 [P]
RewriteRule ^project2(.*) http://127.0.0.1:9006/project2$1 [P]
RewriteRule ^project3(.*) http://127.0.0.1:9006/project3$1 [P]
RewriteRule ^project4(.*) http://127.0.0.1:9006/project4$1 [P]
This also assumes that there is an instance of tracd running under the
following:
/usr/local/bin/python /usr/local/bin/tracd -d -p 9006 --auth
*,{blah}/trac.digest.passwd, {foo} -e {homedir of Trac}
I don't think I've forgotten anything. Any ideas?
Vincent
-
Food fight? Enjoy some healthy debate
in the Yahoo! Answers Food Drink QA.
--~--~-~--~~~---~--~~
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: Integration of Trac and Bugzilla
I guess that depends on how you operate. if you have one big project, try having several smaller components moved over to Trac if you have several smaller projects, try hosting only a subset of them in Trac. HTH! -Chris On 6/28/07, cobwebsmasher [EMAIL PROTECTED] wrote: Thanks, I've used the bugzilla2trac.py script, and it does an excellent job of moving bugs from bugzilla to Trac, but unfortunately the eng. team doesn't want to use Trac for all bugs just yet, just some, so bringing everything over into a system that wouldn't be in sync isn't quite so useful. Bugzilla plugin. Hmmm, Looking at it, it does seem interesting, although in this case, I don't want to lose the Trac ticket functionality as much as I want to integrate both. Any other ideas? I will definitely propose the bugzilla plugin to my group, though. Thanks for that thought. Vincent Christopher Taylor [EMAIL PROTECTED] wrote: Two easier options: 1) check out the bugzilla plugin for Trac 2) migrate from bugzilla to trac with the bugzilla2trac.py script HTH -Chrs On 6/27/07, cobwebsmasher wrote: Hello. I am interested in connecting an instance of Trac and an instance of Bugzilla together. Currently I have both systems authenticating against the same LDAP repository (Microsoft Active Directory in this case), and want to take advantage of the better UI and ease of use features of Trac while not snatching everything out from under the engineering team by just migrating the bugs from Bugzilla and saying, Here you go - enjoy your new system. For this situation, I was wondering if anyone has done anything like adding a button to the View Ticket form that would post the Trac Ticket information to another system (like a Bugzilla). Short of just forcing the engineering team to start using Trac, an option we are considering is adding some functionality that would link the Trac ticket and it's corresponding Bugzilla item. The quick and dirty way would be to post comments to the Trac and Bugzilla ticket with links to each others' system, with a snippet web-form to do the job (i.e. a form that says enter the Trac ticket # and the Bugzilla ticket # you want to link), with this feature being automated by a Forward this ticket to Bugzilla feature that would generate a new bugzilla item - get the # out of the database and make the appropriate connections. I could probably get some mileage out of rewording this problem/issue, but my guess is that anyone that has had similar aspirations might have a sense of what I'm trying to do and hopefully some success that they would be willing to share? Heck, even making Bugzilla look like Trac from a style perspective would be a welcome solution --- I've seen this on one website before, but I can't find it to save my life again. Thanks, Vincent Food fight? Enjoy some healthy debate in the Yahoo! Answers Food Drink QA. Boardwalk for $500? In 2007? Ha! Play Monopoly Here and Now (it's updated for today's economy) at Yahoo! Games --~--~-~--~~~---~--~~ 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] Can Trac render README files in browser?
Hi, I have been thinking (always dangerous) and was wondering is there a way to render README files? I was thinking of a configuration option like: [browser] header=README.HEADER footer=README.FOOTER The browser would then show the contents of the configured header or footer if the file existed in the directory being browsed. Probably would just be rendered as text. Can this be done? Does the plugin neede to be written? :) Cheers, Roo. --~--~-~--~~~---~--~~ 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: Can Trac render README files in browser?
On 6/28/07, Roo [EMAIL PROTECTED] wrote: I have been thinking (always dangerous) and was wondering is there a way to render README files? http://trac.edgewall.org/ticket/3098 - Aaron --~--~-~--~~~---~--~~ 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: Can Trac render README files in browser?
On 29/06/07, Aaron D. Marasco [EMAIL PROTECTED] wrote: http://trac.edgewall.org/ticket/3098 Thanks for that Aaron, I didn't find anything on track hacks, probably should have thought to look in Trac's trac ;) Cheers, Roo --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
