[Trac] Re: Plugins not showing up.
Trac egg is located at: /home/arv/pyenv/python2.7/lib/python2.7/site-packages/Trac-0.12.2- py2.7.egg/trac/__init__.pyc Here's my sys.path: --> print(sys.path) ['', '/home/arv/pyenv/python2.7/bin', '/home/arv/pyenv/python2.7/lib/ python2.7/site-packages/setuptools-0.6c11-py2.7.egg', '/home/arv/pyenv/ python2.7/lib/python2.7/site-packages/pip-1.0-py2.7.egg', '/home/arv/ pyenv/python2.7/lib/python2.7/site-packages/Babel-0.9.5-py2.7.egg', '/ home/arv/pyenv/python2.7/lib/python2.7/site-packages/Trac-0.12.2- py2.7.egg', '/home/arv/pyenv/python2.7/lib/python2.7/site-packages/ Genshi-0.6-py2.7.egg', '/home/arv/pyenv/python2.7/lib/python2.7/site- packages/South-0.7.3-py2.7.egg', '/home/arv/pyenv/python2.7/lib/ python2.7', '/home/arv/pyenv/python2.7/lib/python2.7/plat-linux2', '/ home/arv/pyenv/python2.7/lib/python2.7/lib-tk', '/home/arv/pyenv/ python2.7/lib/python2.7/lib-old', '/home/arv/pyenv/python2.7/lib/ python2.7/lib-dynload', '/usr/lib/python2.7', '/usr/lib/python2.7/plat- linux2', '/usr/lib/python2.7/lib-tk', '/home/arv/pyenv/python2.7/lib/ python2.7/site-packages', '/home/arv/pyenv/python2.7/lib/python2.7/ site-packages/PIL', '/usr/local/lib/python2.7/dist-packages/ virtualenv-1.6-py2.7.egg', '/usr/local/lib/python2.7/site-packages', '/ usr/local/lib/python2.7/dist-packages', '/usr/lib/python2.7/dist- packages', '/home/arv/pyenv/python2.7/lib/python2.7/site-packages/ IPython/Extensions', u'/home/arv/.ipython'] On May 4, 3:06 pm, Jason Miller wrote: > Oh and, where was your Trac egg located? > > On Wed, May 4, 2011 at 12:47 PM, Jason Miller > wrote: > > can you tell us what your sys.path says? > > > python > > > import sys > > print sys.path > > > Thanks! > > > On Wed, May 4, 2011 at 9:47 AM, Alejandro V. > > wrote: > >> Here are mine: > >>> cat easy-install.pth: > >> import sys; sys.__plen = len(sys.path) > >> ./setuptools-0.6c11-py2.7.egg > >> ./pip-1.0-py2.7.egg > >> ./Babel-0.9.5-py2.7.egg > >> ./Trac-0.12.2-py2.7.egg > >> ./Genshi-0.6-py2.7.egg > >> import sys; new=sys.path[sys.__plen:]; del sys.path[sys.__plen:]; > >> p=getattr(sys,'__egginsert',0); sys.path[p:p]=new; sys.__egginsert = p > >> +len(new) > > >>> cat setuptools.pth : > >> ./setuptools-0.6c11-py2.7.egg > > >> On May 4, 11:01 am, Jason Miller wrote: > >>> In the same place where you moved your eggs to, can you concatenate > >>> your easy-install.pth file for us? > >>> eg, mine reads: > > >>> (for your information so you know what I am running on) > >>> #> lsb_release -a > >>> No LSB modules are available. > >>> Distributor ID: Ubuntu > >>> Description: Ubuntu 10.10 > >>> Release: 10.10 > >>> Codename: maverick > > >>> #> cd /usr/local/lib/python2.6/dist-packages > >>> #> cat easy-install.pth > >>> import sys; sys.__plen = len(sys.path) > >>> ./Trac-0.12.3dev_r10683-py2.6.egg > >>> /usr/local/lib/python2.6/dist-packages > >>> ./Bitten-0.6.1dev_r990-py2.6.egg > >>> ./TracAnnouncer-0.11.1-py2.6.egg > >>> ./TracDoxygen-0.11.0.2-py2.6.egg > >>> import sys; new=sys.path[sys.__plen:]; del sys.path[sys.__plen:]; > >>> p=getattr(sys,'__egginsert',0); sys.path[p:p]=new; sys.__egginsert = > >>> p+len(new) > > >>> It might not hurt to concatenate your setuptools.pth as well (also in > >>> the same location): > > >>> #> cat setuptools.pth > >>> /usr/lib/python2.6/dist-packages > > >>> This information will help us continue troubleshooting > > >>> Thanks, > >>> Jason > > >>> On Wed, May 4, 2011 at 8:24 AM, Alejandro V. > > >>> wrote: > >>> > Hm, locating the trac egg pointed out that none of the other plugin > >>> > eggs were in the same folder, but even after moving they still do not > >>> > appear in the admin panel, or anywhere else. > > >>> > On May 3, 7:50 pm, Jason Miller wrote: > >>> >> I believe with Ubuntu the eggs are stored in: > > >>> >> /usr/local/lib/python2.6/dist-packages > >>> >> or > >>> >> /usr/lib/python2.6/dist-packages > >>> >> (not site-packages with normal python ./setup.py install) > > >>> >> If in doubt you could always try running python directly (just type > >>> >> python at your shell prompt) and enter in the command: > > >>> >> import > >>> >> print myplugin.__file__ > > >>> >> TracAnnouncer for example on my machine in a svn developers non- > >>> >> installed state: > > >>> >> import announcerplugin > >>> >> print announcerplugin.__file__ > >>> >> returns: > >>> >> /home/milljm/dev/DEV-Trac/downloads/announcer/0.11/announcerplugin/ > >>> >> __init__.pyc > > >>> >> Once you have the "exact" location, you can start messing with > >>> >> permissions and the like (if that is indeed the issue). However, if > >>> >> python errors out with un-able to find said module (plugin), then you > >>> >> have a different issue... > >>> >> The module is just not installed correctly as of yet. Or at the very > >>> >> least, in a location python does not know about. > > >>> >> You do seem to have trac installed correctly though, so I would start > >>> >> a python shell and do the following: > > >>> >> import trac
Re: [Trac] Re: Plugins not showing up.
Oh and, where was your Trac egg located? On Wed, May 4, 2011 at 12:47 PM, Jason Miller wrote: > can you tell us what your sys.path says? > > python > > import sys > print sys.path > > Thanks! > > On Wed, May 4, 2011 at 9:47 AM, Alejandro V. > wrote: >> Here are mine: >>> cat easy-install.pth: >> import sys; sys.__plen = len(sys.path) >> ./setuptools-0.6c11-py2.7.egg >> ./pip-1.0-py2.7.egg >> ./Babel-0.9.5-py2.7.egg >> ./Trac-0.12.2-py2.7.egg >> ./Genshi-0.6-py2.7.egg >> import sys; new=sys.path[sys.__plen:]; del sys.path[sys.__plen:]; >> p=getattr(sys,'__egginsert',0); sys.path[p:p]=new; sys.__egginsert = p >> +len(new) >> >> >>> cat setuptools.pth : >> ./setuptools-0.6c11-py2.7.egg >> >> >> On May 4, 11:01 am, Jason Miller wrote: >>> In the same place where you moved your eggs to, can you concatenate >>> your easy-install.pth file for us? >>> eg, mine reads: >>> >>> (for your information so you know what I am running on) >>> #> lsb_release -a >>> No LSB modules are available. >>> Distributor ID: Ubuntu >>> Description: Ubuntu 10.10 >>> Release: 10.10 >>> Codename: maverick >>> >>> #> cd /usr/local/lib/python2.6/dist-packages >>> #> cat easy-install.pth >>> import sys; sys.__plen = len(sys.path) >>> ./Trac-0.12.3dev_r10683-py2.6.egg >>> /usr/local/lib/python2.6/dist-packages >>> ./Bitten-0.6.1dev_r990-py2.6.egg >>> ./TracAnnouncer-0.11.1-py2.6.egg >>> ./TracDoxygen-0.11.0.2-py2.6.egg >>> import sys; new=sys.path[sys.__plen:]; del sys.path[sys.__plen:]; >>> p=getattr(sys,'__egginsert',0); sys.path[p:p]=new; sys.__egginsert = >>> p+len(new) >>> >>> It might not hurt to concatenate your setuptools.pth as well (also in >>> the same location): >>> >>> #> cat setuptools.pth >>> /usr/lib/python2.6/dist-packages >>> >>> This information will help us continue troubleshooting >>> >>> Thanks, >>> Jason >>> >>> On Wed, May 4, 2011 at 8:24 AM, Alejandro V. >>> >>> wrote: >>> > Hm, locating the trac egg pointed out that none of the other plugin >>> > eggs were in the same folder, but even after moving they still do not >>> > appear in the admin panel, or anywhere else. >>> >>> > On May 3, 7:50 pm, Jason Miller wrote: >>> >> I believe with Ubuntu the eggs are stored in: >>> >>> >> /usr/local/lib/python2.6/dist-packages >>> >> or >>> >> /usr/lib/python2.6/dist-packages >>> >> (not site-packages with normal python ./setup.py install) >>> >>> >> If in doubt you could always try running python directly (just type >>> >> python at your shell prompt) and enter in the command: >>> >>> >> import >>> >> print myplugin.__file__ >>> >>> >> TracAnnouncer for example on my machine in a svn developers non- >>> >> installed state: >>> >>> >> import announcerplugin >>> >> print announcerplugin.__file__ >>> >> returns: >>> >> /home/milljm/dev/DEV-Trac/downloads/announcer/0.11/announcerplugin/ >>> >> __init__.pyc >>> >>> >> Once you have the "exact" location, you can start messing with >>> >> permissions and the like (if that is indeed the issue). However, if >>> >> python errors out with un-able to find said module (plugin), then you >>> >> have a different issue... >>> >> The module is just not installed correctly as of yet. Or at the very >>> >> least, in a location python does not know about. >>> >>> >> You do seem to have trac installed correctly though, so I would start >>> >> a python shell and do the following: >>> >>> >> import trac >>> >> print.trac.__file__ >>> >>> >> and see where the Trac egg is. In most if not all cases, the plugin >>> >> eggs should be located in the same spot. >>> >>> >> Looking forward to your results! >>> >> Jason >>> >>> >> On May 3, 12:03 pm, "Alejandro V." >>> >> wrote: >>> >>> >> > Oh ok, the url is only /about in my case, but yes I do not see any >>> >> > plugins, but it also doesn't look like my plugins_dir is set for >>> >> > whatever reason. >>> >> > Setting it doesn't seem to do anything either though. >>> >>> >> > On May 3, 1:57 pm, "Jeff Watson" wrote: >>> >>> >> > > Sorry, just login to the website (I presume you can since you >>> >> > > indicate you >>> >> > > can get in the admin panel to see the plug-ins, so in general the >>> >> > > site is >>> >> > > alive) and click on the "About Trac" link. That should have been >>> >> > > localhost:/trac//about (so in >>> >> > > my case >>> >> > > it'shttp://localhost:8080/trac/risks/about)-Hidequoted text - >>> >>> >> > - Show quoted text - >>> >>> > -- >>> > You received this message because you are subscribed to the Google Groups >>> > "Trac Users" group. >>> > To post to this group, send email to trac-users@googlegroups.com. >>> > To unsubscribe from this group, send email to >>> > trac-users+unsubscr...@googlegroups.com. >>> > For more options, visit this group >>> > athttp://groups.google.com/group/trac-users?hl=en. >> >> -- >> 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 fro
Re: [Trac] Re: Plugins not showing up.
can you tell us what your sys.path says? python import sys print sys.path Thanks! On Wed, May 4, 2011 at 9:47 AM, Alejandro V. wrote: > Here are mine: >> cat easy-install.pth: > import sys; sys.__plen = len(sys.path) > ./setuptools-0.6c11-py2.7.egg > ./pip-1.0-py2.7.egg > ./Babel-0.9.5-py2.7.egg > ./Trac-0.12.2-py2.7.egg > ./Genshi-0.6-py2.7.egg > import sys; new=sys.path[sys.__plen:]; del sys.path[sys.__plen:]; > p=getattr(sys,'__egginsert',0); sys.path[p:p]=new; sys.__egginsert = p > +len(new) > > >> cat setuptools.pth : > ./setuptools-0.6c11-py2.7.egg > > > On May 4, 11:01 am, Jason Miller wrote: >> In the same place where you moved your eggs to, can you concatenate >> your easy-install.pth file for us? >> eg, mine reads: >> >> (for your information so you know what I am running on) >> #> lsb_release -a >> No LSB modules are available. >> Distributor ID: Ubuntu >> Description: Ubuntu 10.10 >> Release: 10.10 >> Codename: maverick >> >> #> cd /usr/local/lib/python2.6/dist-packages >> #> cat easy-install.pth >> import sys; sys.__plen = len(sys.path) >> ./Trac-0.12.3dev_r10683-py2.6.egg >> /usr/local/lib/python2.6/dist-packages >> ./Bitten-0.6.1dev_r990-py2.6.egg >> ./TracAnnouncer-0.11.1-py2.6.egg >> ./TracDoxygen-0.11.0.2-py2.6.egg >> import sys; new=sys.path[sys.__plen:]; del sys.path[sys.__plen:]; >> p=getattr(sys,'__egginsert',0); sys.path[p:p]=new; sys.__egginsert = >> p+len(new) >> >> It might not hurt to concatenate your setuptools.pth as well (also in >> the same location): >> >> #> cat setuptools.pth >> /usr/lib/python2.6/dist-packages >> >> This information will help us continue troubleshooting >> >> Thanks, >> Jason >> >> On Wed, May 4, 2011 at 8:24 AM, Alejandro V. >> >> wrote: >> > Hm, locating the trac egg pointed out that none of the other plugin >> > eggs were in the same folder, but even after moving they still do not >> > appear in the admin panel, or anywhere else. >> >> > On May 3, 7:50 pm, Jason Miller wrote: >> >> I believe with Ubuntu the eggs are stored in: >> >> >> /usr/local/lib/python2.6/dist-packages >> >> or >> >> /usr/lib/python2.6/dist-packages >> >> (not site-packages with normal python ./setup.py install) >> >> >> If in doubt you could always try running python directly (just type >> >> python at your shell prompt) and enter in the command: >> >> >> import >> >> print myplugin.__file__ >> >> >> TracAnnouncer for example on my machine in a svn developers non- >> >> installed state: >> >> >> import announcerplugin >> >> print announcerplugin.__file__ >> >> returns: >> >> /home/milljm/dev/DEV-Trac/downloads/announcer/0.11/announcerplugin/ >> >> __init__.pyc >> >> >> Once you have the "exact" location, you can start messing with >> >> permissions and the like (if that is indeed the issue). However, if >> >> python errors out with un-able to find said module (plugin), then you >> >> have a different issue... >> >> The module is just not installed correctly as of yet. Or at the very >> >> least, in a location python does not know about. >> >> >> You do seem to have trac installed correctly though, so I would start >> >> a python shell and do the following: >> >> >> import trac >> >> print.trac.__file__ >> >> >> and see where the Trac egg is. In most if not all cases, the plugin >> >> eggs should be located in the same spot. >> >> >> Looking forward to your results! >> >> Jason >> >> >> On May 3, 12:03 pm, "Alejandro V." >> >> wrote: >> >> >> > Oh ok, the url is only /about in my case, but yes I do not see any >> >> > plugins, but it also doesn't look like my plugins_dir is set for >> >> > whatever reason. >> >> > Setting it doesn't seem to do anything either though. >> >> >> > On May 3, 1:57 pm, "Jeff Watson" wrote: >> >> >> > > Sorry, just login to the website (I presume you can since you >> >> > > indicate you >> >> > > can get in the admin panel to see the plug-ins, so in general the >> >> > > site is >> >> > > alive) and click on the "About Trac" link. That should have been >> >> > > localhost:/trac//about (so in >> >> > > my case >> >> > > it'shttp://localhost:8080/trac/risks/about)-Hidequoted text - >> >> >> > - Show quoted text - >> >> > -- >> > You received this message because you are subscribed to the Google Groups >> > "Trac Users" group. >> > To post to this group, send email to trac-users@googlegroups.com. >> > To unsubscribe from this group, send email to >> > trac-users+unsubscr...@googlegroups.com. >> > For more options, visit this group >> > athttp://groups.google.com/group/trac-users?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "Trac Users" group. > To post to this group, send email to trac-users@googlegroups.com. > To unsubscribe from this group, send email to > trac-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/trac-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Tra
[Trac] Is there anyway that I can extend the attached file size for more than 262144 bytes?
Hello everyone I attached a wireshark file to the new ticket (bug.trac) and get error as "Maximum attachment size: 262144 bytes" Is there any way that I can extend the size? Thanks Pink -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to trac-users@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
Re: [Trac] Is there anyway that I can extend the attached file size for more than 262144 bytes?
On 05/04/2011 01:54 PM, Tina Phan wrote: Hello everyone I attached a wireshark file to the new ticket (bug.trac) and get error as "Maximum attachment size: 262144 bytes" Is there any way that I can extend the size? [attachment] max_size = 2 in trac.ini -- Matthew Caron Build Engineer Sixnet | www.sixnet.com O +1 518 877 5173 Ext. 138 F +1 518 602 9209 matt.ca...@sixnet.com -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to trac-users@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
[Trac] Re: Plugins not showing up.
Here are mine: > cat easy-install.pth: import sys; sys.__plen = len(sys.path) ./setuptools-0.6c11-py2.7.egg ./pip-1.0-py2.7.egg ./Babel-0.9.5-py2.7.egg ./Trac-0.12.2-py2.7.egg ./Genshi-0.6-py2.7.egg import sys; new=sys.path[sys.__plen:]; del sys.path[sys.__plen:]; p=getattr(sys,'__egginsert',0); sys.path[p:p]=new; sys.__egginsert = p +len(new) > cat setuptools.pth : ./setuptools-0.6c11-py2.7.egg On May 4, 11:01 am, Jason Miller wrote: > In the same place where you moved your eggs to, can you concatenate > your easy-install.pth file for us? > eg, mine reads: > > (for your information so you know what I am running on) > #> lsb_release -a > No LSB modules are available. > Distributor ID: Ubuntu > Description: Ubuntu 10.10 > Release: 10.10 > Codename: maverick > > #> cd /usr/local/lib/python2.6/dist-packages > #> cat easy-install.pth > import sys; sys.__plen = len(sys.path) > ./Trac-0.12.3dev_r10683-py2.6.egg > /usr/local/lib/python2.6/dist-packages > ./Bitten-0.6.1dev_r990-py2.6.egg > ./TracAnnouncer-0.11.1-py2.6.egg > ./TracDoxygen-0.11.0.2-py2.6.egg > import sys; new=sys.path[sys.__plen:]; del sys.path[sys.__plen:]; > p=getattr(sys,'__egginsert',0); sys.path[p:p]=new; sys.__egginsert = > p+len(new) > > It might not hurt to concatenate your setuptools.pth as well (also in > the same location): > > #> cat setuptools.pth > /usr/lib/python2.6/dist-packages > > This information will help us continue troubleshooting > > Thanks, > Jason > > On Wed, May 4, 2011 at 8:24 AM, Alejandro V. > > wrote: > > Hm, locating the trac egg pointed out that none of the other plugin > > eggs were in the same folder, but even after moving they still do not > > appear in the admin panel, or anywhere else. > > > On May 3, 7:50 pm, Jason Miller wrote: > >> I believe with Ubuntu the eggs are stored in: > > >> /usr/local/lib/python2.6/dist-packages > >> or > >> /usr/lib/python2.6/dist-packages > >> (not site-packages with normal python ./setup.py install) > > >> If in doubt you could always try running python directly (just type > >> python at your shell prompt) and enter in the command: > > >> import > >> print myplugin.__file__ > > >> TracAnnouncer for example on my machine in a svn developers non- > >> installed state: > > >> import announcerplugin > >> print announcerplugin.__file__ > >> returns: > >> /home/milljm/dev/DEV-Trac/downloads/announcer/0.11/announcerplugin/ > >> __init__.pyc > > >> Once you have the "exact" location, you can start messing with > >> permissions and the like (if that is indeed the issue). However, if > >> python errors out with un-able to find said module (plugin), then you > >> have a different issue... > >> The module is just not installed correctly as of yet. Or at the very > >> least, in a location python does not know about. > > >> You do seem to have trac installed correctly though, so I would start > >> a python shell and do the following: > > >> import trac > >> print.trac.__file__ > > >> and see where the Trac egg is. In most if not all cases, the plugin > >> eggs should be located in the same spot. > > >> Looking forward to your results! > >> Jason > > >> On May 3, 12:03 pm, "Alejandro V." > >> wrote: > > >> > Oh ok, the url is only /about in my case, but yes I do not see any > >> > plugins, but it also doesn't look like my plugins_dir is set for > >> > whatever reason. > >> > Setting it doesn't seem to do anything either though. > > >> > On May 3, 1:57 pm, "Jeff Watson" wrote: > > >> > > Sorry, just login to the website (I presume you can since you indicate > >> > > you > >> > > can get in the admin panel to see the plug-ins, so in general the site > >> > > is > >> > > alive) and click on the "About Trac" link. That should have been > >> > > localhost:/trac//about (so in > >> > > my case > >> > > it'shttp://localhost:8080/trac/risks/about)-Hidequoted text - > > >> > - Show quoted text - > > > -- > > You received this message because you are subscribed to the Google Groups > > "Trac Users" group. > > To post to this group, send email to trac-users@googlegroups.com. > > To unsubscribe from this group, send email to > > trac-users+unsubscr...@googlegroups.com. > > For more options, visit this group > > athttp://groups.google.com/group/trac-users?hl=en. -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to trac-users@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
Re: [Trac] There is Babel, but I don't see “language”
Ahh got it, I was performing an install from a subversion checkout is where I got confused. I was following these instructions: http://babel.edgewall.org/wiki/SubversionCheckout On Wed, May 4, 2011 at 7:46 AM, Christian Boos wrote: > On 5/4/2011 3:22 PM, Jason Miller wrote: >> >> Well, installing Babel through easy_install will get you Babel of >> course. However, the easy_install method does not download, compile >> and parse the unicode character dictionaries into the Babel parser. > > easy_install'ing Babel is all what is needed. It will fetch a pre-built > package from the places listed in http://babel.edgewall.org/wiki/Download. > > >> Babel in all its glory is just an interpreter plugin for Trac. > > Not a plugin, just an optional dependency. > >> But it >> still needs those language dictionaries CLDR: http://cldr.unicode.org >> >> Thankfully, its a very easy process to parse those dictionaries into >> Babel. As Babel has so graciously provided a simple script which does >> all the parse/conversion for you :) >> >> (./scripts/import_cldr.py) >> >> After reading the Babel wiki instructions, it appears that you must >> re-compile Babel every time you download a new CLDR update. > > True, but you don't necessarily need the latest CLDR, using the already > bundled one should be enough (I'm not sure which version was used for Babel > 0.9.6, but for Babel 0.9.5 it was CLDR 1.6.1). > > -- Christian > >> Which is >> also why I included instructions on re-installing Babel. But, I think >> the one part you missed was obtaining the CLDR data. easy_install will >> not give you the ability to run that needed import_cldr.py script >> (someone correct me if I am wrong). >> >> Hope that helps! >> >> Jason >> >> On Wed, May 4, 2011 at 1:55 AM, Ista Pouss wrote: >>> >>> For Babel I've done nothing of that. I've done "easy_install Babel". >>> >>> Is it not so easy ? >>> >>> >>> 2011/5/4 Jason Miller Not knowing what you have done to compile Babel, I will provide a set of instruction I just performed to allow multi-lingual support to my 'already running' Trac environment: Stop Apache mkdir ~/dev cd ~/dev svn co http://svn.edgewall.org/repos/babel/branches/stable/0.9.x babel svn co http://svn.edgewall.org/repos/genshi/branches/stable/0.6.x genshi svn co http://svn.edgewall.org/repos/trac/branches/0.12-stable trac curl -O http://unicode.org/Public/cldr/1.7.2/core.zip unzip core.zip cd babel python ./setup.py egg_info python ./scripts/import_cldr.py ~/dev/common sudo python ./setup.py install cd ../genshi sudo python ./setup.py install cd ../trac sudo python ./setup.py install At this point Trac is setup with multi lingual support. You already have a working Trac environment, so lets just simply update it: sudo su - trac-admin /path/to/your/trac upgrade trac-admin /path/to/your/trac wiki upgrade Start Apache... log in, check out prefrences, and you should now have a "Language" tab. Enjoy! Hope this helps! Jason On Tue, May 3, 2011 at 1:20 AM, istaous wrote: > > I've installed on a Debian system Trac 0.12 (thanks > > > http://superuser.com/questions/277674/easy-install-install-trac-0-11-but-i-want-0-12 > ) and know I want to get the localization (for French). > > So I've installed Babel, but that doesn't work. I've uninstalled and > re-installed Trac, but that doesn't work: I don't see "Language" in > the preference panel. > > I do the same thing on a mandriva system, and that works like a charm. > > What's happend? How can I resolve that? > > Thanks. > > -- > You received this message because you are subscribed to the Google Groups > "Trac Users" group. > To post to this group, send email to trac-users@googlegroups.com. > To unsubscribe from this group, send email to > trac-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/trac-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to trac-users@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
Re: [Trac] Re: Plugins not showing up.
In the same place where you moved your eggs to, can you concatenate your easy-install.pth file for us? eg, mine reads: (for your information so you know what I am running on) #> lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 10.10 Release:10.10 Codename: maverick #> cd /usr/local/lib/python2.6/dist-packages #> cat easy-install.pth import sys; sys.__plen = len(sys.path) ./Trac-0.12.3dev_r10683-py2.6.egg /usr/local/lib/python2.6/dist-packages ./Bitten-0.6.1dev_r990-py2.6.egg ./TracAnnouncer-0.11.1-py2.6.egg ./TracDoxygen-0.11.0.2-py2.6.egg import sys; new=sys.path[sys.__plen:]; del sys.path[sys.__plen:]; p=getattr(sys,'__egginsert',0); sys.path[p:p]=new; sys.__egginsert = p+len(new) It might not hurt to concatenate your setuptools.pth as well (also in the same location): #> cat setuptools.pth /usr/lib/python2.6/dist-packages This information will help us continue troubleshooting Thanks, Jason On Wed, May 4, 2011 at 8:24 AM, Alejandro V. wrote: > Hm, locating the trac egg pointed out that none of the other plugin > eggs were in the same folder, but even after moving they still do not > appear in the admin panel, or anywhere else. > > On May 3, 7:50 pm, Jason Miller wrote: >> I believe with Ubuntu the eggs are stored in: >> >> /usr/local/lib/python2.6/dist-packages >> or >> /usr/lib/python2.6/dist-packages >> (not site-packages with normal python ./setup.py install) >> >> If in doubt you could always try running python directly (just type >> python at your shell prompt) and enter in the command: >> >> import >> print myplugin.__file__ >> >> TracAnnouncer for example on my machine in a svn developers non- >> installed state: >> >> import announcerplugin >> print announcerplugin.__file__ >> returns: >> /home/milljm/dev/DEV-Trac/downloads/announcer/0.11/announcerplugin/ >> __init__.pyc >> >> Once you have the "exact" location, you can start messing with >> permissions and the like (if that is indeed the issue). However, if >> python errors out with un-able to find said module (plugin), then you >> have a different issue... >> The module is just not installed correctly as of yet. Or at the very >> least, in a location python does not know about. >> >> You do seem to have trac installed correctly though, so I would start >> a python shell and do the following: >> >> import trac >> print.trac.__file__ >> >> and see where the Trac egg is. In most if not all cases, the plugin >> eggs should be located in the same spot. >> >> Looking forward to your results! >> Jason >> >> On May 3, 12:03 pm, "Alejandro V." >> wrote: >> >> > Oh ok, the url is only /about in my case, but yes I do not see any >> > plugins, but it also doesn't look like my plugins_dir is set for >> > whatever reason. >> > Setting it doesn't seem to do anything either though. >> >> > On May 3, 1:57 pm, "Jeff Watson" wrote: >> >> > > Sorry, just login to the website (I presume you can since you indicate >> > > you >> > > can get in the admin panel to see the plug-ins, so in general the site is >> > > alive) and click on the "About Trac" link. That should have been >> > > localhost:/trac//about (so in my >> > > case >> > > it'shttp://localhost:8080/trac/risks/about)-Hide quoted text - >> >> > - Show quoted text - > > -- > You received this message because you are subscribed to the Google Groups > "Trac Users" group. > To post to this group, send email to trac-users@googlegroups.com. > To unsubscribe from this group, send email to > trac-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/trac-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to trac-users@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
[Trac] FlexibleReportNotificationPlugIn not working properly
Hi trac Team, I have a requirement where I need email notification like below I need email notifications to only be sent for three specific events, The events would be when a new ticket is opened, when a ticket is assigned to a new owner, and when the status of a ticket changes (example, new to assigned, open to closed, closed to reopened). In these cases, an email to the reporter and assignee would be helpful. I tried to install FlexibleReportNotificationPlugIn and made changes in trac.ini file but it is again sending mails for everything.I have also added the fix for 0.12, I followed this link http://trac-hacks.org/wiki/FlexibleReporterNotificationPlugin, can you please prvide me some solution for this, I badly need this. Thanks in advance, Venkat. -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to trac-users@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
[Trac] Re: Plugins not showing up.
Hm, locating the trac egg pointed out that none of the other plugin eggs were in the same folder, but even after moving they still do not appear in the admin panel, or anywhere else. On May 3, 7:50 pm, Jason Miller wrote: > I believe with Ubuntu the eggs are stored in: > > /usr/local/lib/python2.6/dist-packages > or > /usr/lib/python2.6/dist-packages > (not site-packages with normal python ./setup.py install) > > If in doubt you could always try running python directly (just type > python at your shell prompt) and enter in the command: > > import > print myplugin.__file__ > > TracAnnouncer for example on my machine in a svn developers non- > installed state: > > import announcerplugin > print announcerplugin.__file__ > returns: > /home/milljm/dev/DEV-Trac/downloads/announcer/0.11/announcerplugin/ > __init__.pyc > > Once you have the "exact" location, you can start messing with > permissions and the like (if that is indeed the issue). However, if > python errors out with un-able to find said module (plugin), then you > have a different issue... > The module is just not installed correctly as of yet. Or at the very > least, in a location python does not know about. > > You do seem to have trac installed correctly though, so I would start > a python shell and do the following: > > import trac > print.trac.__file__ > > and see where the Trac egg is. In most if not all cases, the plugin > eggs should be located in the same spot. > > Looking forward to your results! > Jason > > On May 3, 12:03 pm, "Alejandro V." > wrote: > > > Oh ok, the url is only /about in my case, but yes I do not see any > > plugins, but it also doesn't look like my plugins_dir is set for > > whatever reason. > > Setting it doesn't seem to do anything either though. > > > On May 3, 1:57 pm, "Jeff Watson" wrote: > > > > Sorry, just login to the website (I presume you can since you indicate you > > > can get in the admin panel to see the plug-ins, so in general the site is > > > alive) and click on the "About Trac" link. That should have been > > > localhost:/trac//about (so in my > > > case > > > it'shttp://localhost:8080/trac/risks/about)-Hide quoted text - > > > - Show quoted text - -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to trac-users@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
Re: [Trac] There is Babel, but I don't see “language”
On 5/4/2011 3:22 PM, Jason Miller wrote: Well, installing Babel through easy_install will get you Babel of course. However, the easy_install method does not download, compile and parse the unicode character dictionaries into the Babel parser. easy_install'ing Babel is all what is needed. It will fetch a pre-built package from the places listed in http://babel.edgewall.org/wiki/Download. Babel in all its glory is just an interpreter plugin for Trac. Not a plugin, just an optional dependency. But it still needs those language dictionaries CLDR: http://cldr.unicode.org Thankfully, its a very easy process to parse those dictionaries into Babel. As Babel has so graciously provided a simple script which does all the parse/conversion for you :) (./scripts/import_cldr.py) After reading the Babel wiki instructions, it appears that you must re-compile Babel every time you download a new CLDR update. True, but you don't necessarily need the latest CLDR, using the already bundled one should be enough (I'm not sure which version was used for Babel 0.9.6, but for Babel 0.9.5 it was CLDR 1.6.1). -- Christian Which is also why I included instructions on re-installing Babel. But, I think the one part you missed was obtaining the CLDR data. easy_install will not give you the ability to run that needed import_cldr.py script (someone correct me if I am wrong). Hope that helps! Jason On Wed, May 4, 2011 at 1:55 AM, Ista Pouss wrote: For Babel I've done nothing of that. I've done "easy_install Babel". Is it not so easy ? 2011/5/4 Jason Miller Not knowing what you have done to compile Babel, I will provide a set of instruction I just performed to allow multi-lingual support to my 'already running' Trac environment: Stop Apache mkdir ~/dev cd ~/dev svn co http://svn.edgewall.org/repos/babel/branches/stable/0.9.x babel svn co http://svn.edgewall.org/repos/genshi/branches/stable/0.6.x genshi svn co http://svn.edgewall.org/repos/trac/branches/0.12-stable trac curl -O http://unicode.org/Public/cldr/1.7.2/core.zip unzip core.zip cd babel python ./setup.py egg_info python ./scripts/import_cldr.py ~/dev/common sudo python ./setup.py install cd ../genshi sudo python ./setup.py install cd ../trac sudo python ./setup.py install At this point Trac is setup with multi lingual support. You already have a working Trac environment, so lets just simply update it: sudo su - trac-admin /path/to/your/trac upgrade trac-admin /path/to/your/trac wiki upgrade Start Apache... log in, check out prefrences, and you should now have a "Language" tab. Enjoy! Hope this helps! Jason On Tue, May 3, 2011 at 1:20 AM, istaous wrote: I've installed on a Debian system Trac 0.12 (thanks http://superuser.com/questions/277674/easy-install-install-trac-0-11-but-i-want-0-12 ) and know I want to get the localization (for French). So I've installed Babel, but that doesn't work. I've uninstalled and re-installed Trac, but that doesn't work: I don't see "Language" in the preference panel. I do the same thing on a mandriva system, and that works like a charm. What's happend? How can I resolve that? Thanks. -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to trac-users@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
Re: [Trac] There is Babel, but I don't see “language”
Well, installing Babel through easy_install will get you Babel of course. However, the easy_install method does not download, compile and parse the unicode character dictionaries into the Babel parser. Babel in all its glory is just an interpreter plugin for Trac. But it still needs those language dictionaries CLDR: http://cldr.unicode.org Thankfully, its a very easy process to parse those dictionaries into Babel. As Babel has so graciously provided a simple script which does all the parse/conversion for you :) (./scripts/import_cldr.py) After reading the Babel wiki instructions, it appears that you must re-compile Babel every time you download a new CLDR update. Which is also why I included instructions on re-installing Babel. But, I think the one part you missed was obtaining the CLDR data. easy_install will not give you the ability to run that needed import_cldr.py script (someone correct me if I am wrong). Hope that helps! Jason On Wed, May 4, 2011 at 1:55 AM, Ista Pouss wrote: > For Babel I've done nothing of that. I've done "easy_install Babel". > > Is it not so easy ? > > > 2011/5/4 Jason Miller >> >> Not knowing what you have done to compile Babel, I will provide a set >> of instruction I just performed to allow multi-lingual support to my >> 'already running' Trac environment: >> >> Stop Apache >> >> mkdir ~/dev >> cd ~/dev >> svn co http://svn.edgewall.org/repos/babel/branches/stable/0.9.x babel >> svn co http://svn.edgewall.org/repos/genshi/branches/stable/0.6.x genshi >> svn co http://svn.edgewall.org/repos/trac/branches/0.12-stable trac >> curl -O http://unicode.org/Public/cldr/1.7.2/core.zip >> unzip core.zip >> cd babel >> python ./setup.py egg_info >> python ./scripts/import_cldr.py ~/dev/common >> sudo python ./setup.py install >> cd ../genshi >> sudo python ./setup.py install >> cd ../trac >> sudo python ./setup.py install >> >> At this point Trac is setup with multi lingual support. You already >> have a working Trac environment, so lets just simply update it: >> >> sudo su - >> trac-admin /path/to/your/trac upgrade >> trac-admin /path/to/your/trac wiki upgrade >> >> Start Apache... log in, check out prefrences, and you should now have >> a "Language" tab. Enjoy! >> >> Hope this helps! >> Jason >> >> On Tue, May 3, 2011 at 1:20 AM, istaous wrote: >> > >> > I've installed on a Debian system Trac 0.12 (thanks >> > >> > http://superuser.com/questions/277674/easy-install-install-trac-0-11-but-i-want-0-12 >> > ) and know I want to get the localization (for French). >> > >> > So I've installed Babel, but that doesn't work. I've uninstalled and >> > re-installed Trac, but that doesn't work: I don't see "Language" in >> > the preference panel. >> > >> > I do the same thing on a mandriva system, and that works like a charm. >> > >> > What's happend? How can I resolve that? >> > >> > Thanks. >> > >> > -- >> > You received this message because you are subscribed to the Google >> > Groups "Trac Users" group. >> > To post to this group, send email to trac-users@googlegroups.com. >> > To unsubscribe from this group, send email to >> > trac-users+unsubscr...@googlegroups.com. >> > For more options, visit this group at >> > http://groups.google.com/group/trac-users?hl=en. >> > >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Trac Users" group. >> To post to this group, send email to trac-users@googlegroups.com. >> To unsubscribe from this group, send email to >> trac-users+unsubscr...@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/trac-users?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups > "Trac Users" group. > To post to this group, send email to trac-users@googlegroups.com. > To unsubscribe from this group, send email to > trac-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/trac-users?hl=en. > -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to trac-users@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
Re: [Trac] There is Babel, but I don't see “language”
For Babel I've done nothing of that. I've done "easy_install Babel". Is it not so easy ? 2011/5/4 Jason Miller > Not knowing what you have done to compile Babel, I will provide a set > of instruction I just performed to allow multi-lingual support to my > 'already running' Trac environment: > > Stop Apache > > mkdir ~/dev > cd ~/dev > svn co http://svn.edgewall.org/repos/babel/branches/stable/0.9.x babel > svn co http://svn.edgewall.org/repos/genshi/branches/stable/0.6.x genshi > svn co http://svn.edgewall.org/repos/trac/branches/0.12-stable trac > curl -O http://unicode.org/Public/cldr/1.7.2/core.zip > unzip core.zip > cd babel > python ./setup.py egg_info > python ./scripts/import_cldr.py ~/dev/common > sudo python ./setup.py install > cd ../genshi > sudo python ./setup.py install > cd ../trac > sudo python ./setup.py install > > At this point Trac is setup with multi lingual support. You already > have a working Trac environment, so lets just simply update it: > > sudo su - > trac-admin /path/to/your/trac upgrade > trac-admin /path/to/your/trac wiki upgrade > > Start Apache... log in, check out prefrences, and you should now have > a "Language" tab. Enjoy! > > Hope this helps! > Jason > > On Tue, May 3, 2011 at 1:20 AM, istaous wrote: > > > > I've installed on a Debian system Trac 0.12 (thanks > > > http://superuser.com/questions/277674/easy-install-install-trac-0-11-but-i-want-0-12 > > ) and know I want to get the localization (for French). > > > > So I've installed Babel, but that doesn't work. I've uninstalled and > > re-installed Trac, but that doesn't work: I don't see "Language" in > > the preference panel. > > > > I do the same thing on a mandriva system, and that works like a charm. > > > > What's happend? How can I resolve that? > > > > Thanks. > > > > -- > > You received this message because you are subscribed to the Google Groups > "Trac Users" group. > > To post to this group, send email to trac-users@googlegroups.com. > > To unsubscribe from this group, send email to > trac-users+unsubscr...@googlegroups.com. > > For more options, visit this group at > http://groups.google.com/group/trac-users?hl=en. > > > > -- > You received this message because you are subscribed to the Google Groups > "Trac Users" group. > To post to this group, send email to trac-users@googlegroups.com. > To unsubscribe from this group, send email to > trac-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/trac-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to trac-users@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
