| [00:27:22] |
* |
pminnieur has joined #trac |
| [00:48:20] |
* |
cmlenz has quit IRC |
| [01:02:26] |
* |
jrydberg has joined #trac |
| [01:06:53] |
* |
cmlenz has joined #trac |
| [01:16:16] |
* |
imajes has joined #trac |
| [01:18:08] |
* |
imajes has quit IRC |
| [01:19:04] |
* |
imajes has joined #trac |
| [01:25:44] |
* |
phoenixz has quit IRC |
| [01:40:13] |
* |
_idostyle has joined #trac |
| [01:55:46] |
* |
cookin_ has joined #trac |
| [01:56:28] |
* |
idostyle has quit IRC |
| [01:56:33] |
* |
_idostyle is now known as idostyle |
| [01:57:49] |
* |
hpnadig has quit IRC |
| [02:02:28] |
* |
MasterC has joined #trac |
| [02:13:06] |
* |
jrydberg has quit IRC |
| [02:24:15] |
* |
Synapse is now known as TownCrier[rbot] |
| [02:24:29] |
* |
TownCrier[rbot] is now known as Synapse |
| [02:26:29] |
<The_Tick> |
so I have trac installed in a users home directory, without root access, I'm wondering how to add a user so they can click the little login button thinger |
| [02:29:51] |
* |
converter has quit IRC |
| [02:33:45] |
<ranq_> |
depends on the http authentication method |
| [02:35:32] |
<The_Tick> |
assume I don't know wtf I'm doing :) |
| [02:37:03] |
<The_Tick> |
I'm trying to find just a page on how to do it and can't find much, read some of the readme but I could have missed it |
| [02:39:03] |
<The_Tick> |
I mean, I get trac-admin permission stuff |
| [02:39:16] |
<The_Tick> |
just not sure how to approach the setting password stuff |
| [02:40:32] |
* |
tuxipuxi has joined #trac |
| [02:42:32] |
<The_Tick> |
oh I think I know how |
| [02:42:34] |
<The_Tick> |
cheers |
| [02:50:06] |
<ptman> |
when is 0.9.7 going to be released? |
| [02:50:26] |
<ptman> |
It's been sitting there all ready for probably a month now |
| [03:00:11] |
<tuxipuxi> |
cmlenz: i somehow remember that permission groups may not have uppercase letters in their name, correct? |
| [03:00:45] |
<cmlenz> |
yeah, because uppercase means action |
| [03:00:52] |
<cmlenz> |
and yeah, that's a gross hack |
| [03:01:30] |
<cmlenz> |
ptman: there probably won't be a 0.9.7 release |
| [03:01:34] |
<tuxipuxi> |
ah right.. forgot to file the bug report against WebAdmin which allows uppercase groups :) |
| [03:01:50] |
<cmlenz> |
ptman: the milestone's just a placeholder if you need to make a security fix release |
| [03:01:54] |
<cmlenz> |
s/you/we |
| [03:03:33] |
<cmlenz> |
tuxipuxi: good point :-P |
| [03:13:09] |
<ptman> |
ah |
| [03:19:40] |
<pminnieur> |
if i want to "move" my trac to another server, i only have to copy the sqlite.db and init the project on the other server, same settings, and just copy in the db-file? |
| [03:21:20] |
<ptman> |
copy the whole directory which hosts the environment |
| [03:21:48] |
<ptman> |
there are wiki pages and attachments and whatnot that aren't in the database |
| [03:22:11] |
<pminnieur> |
ah, okay. then i just have to edit the trac.ini if the path etc changed. |
| [03:22:25] |
<ptman> |
that ought not to be a great hassle |
| [03:22:36] |
<tuxipuxi> |
and probably convert your database if the sqlite versions are different |
| [03:22:57] |
<pminnieur> |
okay, thank you for your help. |
| [03:23:03] |
<ptman> |
tuxipuxi: isn't sqlite3 pretty compatible between versions |
| [03:23:25] |
<tuxipuxi> |
sqlite3 is afaik, but sqlite2 and 3 isn't ;) |
| [03:25:16] |
<ptman> |
tuxipuxi: but trac doesn't use sqlite2, does it? |
| [03:26:31] |
<tuxipuxi> |
ptman: "If you have PySQLite 2.x installed, Trac will now try to open your SQLite database using the SQLite 3.x file format. The database formats used by SQLite 2.8.x and SQLite 3.x are incompatible. If you get an error like “file is encrypted or is not a database” after upgrading, then you must convert your database file." that's the case for one of my servers |
| [03:26:51] |
<ptman> |
oh |
| [03:26:56] |
<ptman> |
not nice at all |
| [03:59:29] |
* |
moolight has quit IRC |
| [04:14:55] |
* |
dcab has joined #trac |
| [04:18:47] |
<dcab> |
hi |
| [04:19:03] |
<dcab> |
I new in apache |
| [04:19:23] |
<dcab> |
I want to configure virtual server |
| [04:20:20] |
<dcab> |
actually, virtualhost |
| [04:20:47] |
<dcab> |
and it should work with 8080 port |
| [04:21:23] |
<dcab> |
can anyone post working virtualhost section from httpd.conf? |
| [04:22:14] |
<dcab> |
I want urls to be like http://trac.localhost:8080 |
| [04:39:07] |
<ptman> |
you might try #apache |
| [04:39:31] |
<dcab> |
ptman: thanks, they already helped me |
| [05:09:15] |
* |
dcab has quit IRC |
| [05:16:22] |
* |
firli has joined #trac |
| [05:17:31] |
<firli> |
hi, could anyone point me to the (unfinished) script for migrating a sqlite3-database to a postgresql-database? |
| [05:23:43] |
* |
firli has quit IRC |
| [05:26:52] |
* |
firli has joined #trac |
| [05:29:51] |
<firli> |
sorry, the network firewall here is confusing :p |
| [05:30:21] |
<firli> |
so anyone know anything about the sqlite3 -> postgresql migration script? |
| [05:30:52] |
<firli> |
it's mentioned in a ticket: http://trac.edgewall.org/ticket/2441 |
| [05:36:31] |
* |
imajes has quit IRC |
| [05:41:04] |
* |
stretch has quit IRC |
| [05:49:44] |
* |
flosch has joined #trac |
| [05:55:34] |
* |
agile has quit IRC |
| [05:56:22] |
* |
hpnadig has joined #trac |
| [06:00:26] |
<firli> |
nvm, someone was so kind to reply on the wiki :) |
| [06:00:31] |
* |
firli has quit IRC |
| [06:31:53] |
* |
agile has joined #trac |
| [06:43:33] |
* |
jave has quit IRC |
| [06:45:14] |
* |
coderanger_ has joined #trac |
| [06:46:51] |
* |
imajes has joined #trac |
| [07:08:09] |
* |
dmax has quit IRC |
| [07:08:33] |
* |
milk-it has joined #trac |
| [07:10:05] |
* |
dmax has joined #trac |
| [07:18:08] |
* |
vanderkerkoff has joined #trac |
| [07:18:11] |
* |
dmax has quit IRC |
| [07:18:17] |
* |
danbeck has joined #trac |
| [07:21:47] |
* |
dmax has joined #trac |
| [07:22:28] |
* |
hpnadig has quit IRC |
| [07:27:01] |
<vanderkerkoff> |
I want to put a drop down of users in the add ticket section so people adding a job to trac can select them from the list of users, and hten have that select statement show their username, but pass their email address to trac |
| [07:27:05] |
<vanderkerkoff> |
has anyone done this? |
| [07:29:35] |
<coderanger_> |
vanderkerkoff: Its already done |
| [07:29:52] |
<coderanger_> |
http://trac.edgewall.org/wiki/TracIni#ticket |
| [07:29:58] |
<coderanger_> |
restrict_owner = True |
| [07:37:44] |
* |
klasstek has joined #trac |
| [07:41:26] |
* |
boorad has quit IRC |
| [07:51:32] |
* |
shawn_work has joined #trac |
| [07:51:39] |
* |
Ryan has joined #trac |
| [07:51:50] |
<shawn_work> |
Can one use the SQL page to do malicious SQL actions? |
| [07:52:01] |
<shawn_work> |
ie the 'Edit Report' stuff |
| [07:52:10] |
* |
Ryan has quit IRC |
| [07:52:22] |
<cmlenz> |
sure |
| [07:52:25] |
<shawn_work> |
eep |
| [07:52:37] |
<cmlenz> |
so please keep that page protected |
| [07:52:51] |
<shawn_work> |
fair enough I will |
| [07:53:41] |
<coderanger_> |
It should be noted that you would need to have privs to modify/add reports |
| [07:54:17] |
<shawn_work> |
cmlenz: do we know when #869 is going into 0.11dev? there's a lot of interest @ work since we would like to use that custom workflow/ticketflow stuff |
| [07:54:29] |
<shawn_work> |
coderanger: true, i haven't configured the fine tuned security yet |
| [07:54:52] |
<coderanger_> |
http://trac.edgewall.org/wiki/TracPermissions#Reports |
| [07:54:58] |
<coderanger_> |
Those are the relevant perms |
| [07:54:59] |
<cmlenz> |
shawn_work: can't say yet |
| [07:55:10] |
<coderanger_> |
Real Soon Now (TM) ;-) |
| [07:55:47] |
<shawn_work> |
coderanger: yum |
| [07:55:56] |
<cmlenz> |
"There's an 80% chance it will be before Vista is released" |
| [07:56:09] |
<shawn_work> |
:-) |
| [07:56:47] |
<shawn_work> |
for now I have 0.10dev built in RHEL4 with various plugins from trackhacks and stuff, im glad it works with python 2.3, since our IT wouldn't let me use Fedora :/ |
| [07:57:05] |
<shawn_work> |
so once 0.11dev gets into the 90% bug fix range i'll upgrade to it |
| [07:57:53] |
<coderanger_> |
Check back in about a year |
| [07:58:20] |
<shawn_work> |
thats fine, we'll fine tune our process until 0.11 |
| [07:58:43] |
<shawn_work> |
0.10 is shaping up nice however |
| [07:59:30] |
<coderanger_> |
I think Jonas should start talks with 3D Realms. We should get Duke Nukem to be the Trac mascot :) |
| [08:00:39] |
<shawn_work> |
there's some functionality I'd like to get into 0.11 if it doesn't exist, like pull down combobox for 'assigning' a bug to someone |
| [08:01:23] |
<coderanger_> |
Once the workflow stuff is in, basically everything possibly related to the ticket system can be pluginified |
| [08:03:38] |
* |
flosch has quit IRC |
| [08:03:39] |
<vanderkerkoff> |
do I need to restart anything once I"ve edited the trac.ini files if I want the changes to happen gents? |
| [08:03:56] |
<vanderkerkoff> |
codreanger, thanks for the link |
| [08:04:26] |
<coderanger_> |
vanderkerkoff: Shouldn't have to, but it usually doesn't hurt |
| [08:06:09] |
* |
gromgull has joined #trac |
| [08:07:42] |
<gromgull> |
hi - is there a known way to delete ticket comments? |
| [08:08:00] |
<shawn_work> |
there is a plugin to do it |
| [08:08:05] |
<gromgull> |
we've been getting a fair amount of spam there lately, i.e.: http://gnowsis.opendfki.de/ticket/219 |
| [08:08:26] |
<gromgull> |
http://trac-hacks.org/wiki/TicketDeletePlugin? |
| [08:08:26] |
<exarkun> |
delete from ticket_changes where author = 'spammer_name'; |
| [08:08:40] |
<coderanger_> |
gromgull: Use the TicketDelete plugin |
| [08:08:52] |
<gromgull> |
right - thanks |
| [08:08:54] |
<coderanger_> |
Also will handle property reversion |
| [08:08:55] |
<exarkun> |
`ticket_change', rather. |
| [08:12:27] |
* |
boorad has joined #trac |
| [08:17:21] |
* |
shawn_work abuses the WikiGoodiesPlugin |
| [08:29:34] |
* |
chandlerc has quit IRC |
| [08:30:30] |
* |
gromgull has left #trac |
| [08:31:46] |
* |
PasChampionDuMon has joined #trac |
| [08:41:53] |
* |
hunter has joined #trac |
| [08:42:12] |
* |
ralreegorganon has quit IRC |
| [08:48:04] |
* |
vanderkerkoff has quit IRC |
| [08:49:06] |
* |
Riccc has quit IRC |
| [09:01:16] |
<mitsuhiko> |
alect: install tracantispam on python-trac.swapoff |
| [09:01:24] |
<mitsuhiko> |
otherwise jira might win :( |
| [09:03:27] |
* |
flosch has joined #trac |
| [09:10:03] |
<cmlenz> |
tbh, I suspect jira may be more appropriate for a project as large as python |
| [09:10:26] |
<cmlenz> |
the issue tracker in trac is intentionally simple |
| [09:21:01] |
* |
pminnieur has quit IRC |
| [09:28:49] |
* |
chandlerc has joined #trac |
| [09:28:58] |
<coderanger_> |
They may prefer being able to hack on it though |
| [09:29:17] |
<coderanger_> |
And it is likely that most Python devs are better at python than Java |
| [09:30:36] |
<cmlenz> |
plus jira is a commercial product |
| [09:34:35] |
* |
hunter has quit IRC |
| [09:48:31] |
* |
phoenixz has joined #trac |
| [09:49:53] |
* |
sven_oostenbrink has joined #trac |
| [09:49:56] |
* |
phoenixz has left #trac |
| [09:50:02] |
* |
phoenixz has joined #trac |
| [09:50:03] |
<pacopablo> |
morning vatos |
| [09:50:09] |
* |
sven_oostenbrink has quit IRC |
| [09:50:18] |
<coderanger_> |
alo |
| [10:06:14] |
* |
hunter has joined #trac |
| [10:14:55] |
* |
chandlerc has quit IRC |
| [10:22:18] |
* |
chandlerc has joined #trac |
| [10:45:16] |
* |
ErikRose has joined #trac |
| [10:51:05] |
<ErikRose> |
Has anybody had luck making Apache serve Trac RSS as text/xml? I'm running Trac as a FastCGI, and all I get is pretty uninformative Invalid Argument tracebacks--nothing in the logs. |
| [10:57:43] |
* |
cmlenz has quit IRC |
| [10:59:30] |
* |
erg has joined #trac |
| [11:01:03] |
<erg> |
anyone know of a clean way (better than manually editing trac.ini) to handle a custom ticket field (select) that's large (~130 entries) and dynamic (changes ~weekly)? |
| [11:01:22] |
<pacopablo> |
python |
| [11:01:48] |
<pacopablo> |
http://embassy.asylumware.com/projects/trac/wiki/snippets/MassConfigChanges |
| [11:01:53] |
<pacopablo> |
something along those lines |
| [11:02:04] |
<erg> |
I've currently got the data for this field in a wiki page, which I'm right now transforming via a couple of regexen |
| [11:02:09] |
<erg> |
hmm, let me take a look at that |
| [11:02:53] |
* |
ged has joined #trac |
| [11:06:22] |
<erg> |
that's pretty f'in sweet |
| [11:07:39] |
<ErikRose> |
You know you can have a "site-wide" trac.ini from which stuff is inherited, right? |
| [11:08:02] |
<pacopablo> |
me? yes |
| [11:08:07] |
<ErikRose> |
erg, mostly |
| [11:08:10] |
<erg> |
yeah, but my problem is that I have to update the trac.ini over and over |
| [11:08:16] |
<erg> |
site-wide isn't going to help with that |
| [11:08:23] |
<pacopablo> |
though my installtio does predate the site-wide config |
| [11:08:47] |
<ErikRose> |
Ah. |
| [11:09:22] |
<erg> |
pacopablo: the basic gameplan for that script snippet is to update many ini files simultaneously? |
| [11:09:33] |
<ErikRose> |
Sure looks like it. |
| [11:09:38] |
<erg> |
obviously it's about 1 line from doing multiple changes to one ini |
| [11:09:50] |
<pacopablo> |
erg: right |
| [11:10:00] |
* |
erg doesn't have much python mojo |
| [11:10:06] |
<erg> |
just wanted to be sure I was reading it right |
| [11:10:14] |
<pacopablo> |
the main thing is that if you changes are scriptable, then updating the trac.ini is scriptable too |
| [11:10:27] |
<pacopablo> |
if you don't want to do multiples, just drop the for loop |
| [11:10:29] |
<erg> |
yeah, I get that... that's beautiful |
| [11:10:49] |
<pacopablo> |
and specify the environment instead of listdir |
| [11:10:49] |
<erg> |
using trac's own Environment module |
| [11:10:56] |
<ErikRose> |
I'm a little puzzled. How is editing and running a script easier than editing a trac.ini? |
| [11:11:22] |
<erg> |
I script scraping the data from a wiki page and transforming it into a trac.ini line |
| [11:11:33] |
<ErikRose> |
Ohhhhh. |
| [11:11:34] |
<erg> |
that's easier than manual regex application any day |
| [11:12:08] |
<ErikRose> |
Just make sure you do validation. :-) |
| [11:12:21] |
<erg> |
:)... good point |
| [11:14:21] |
<erg> |
hmmm... the trac.env Environment ... what does the constructor expect? string path to ini file? |
| [11:14:45] |
<pacopablo> |
path to trac environment |
| [11:15:04] |
<erg> |
ahhh... that makes more sense (and it works, too!) |
| [11:17:17] |
<erg> |
where can I find documentation about the Environment module? |
| [11:17:27] |
* |
boorad has quit IRC |
| [11:17:50] |
<ErikRose> |
In the Trac source, in trac/env.py |
| [11:18:08] |
<ErikRose> |
All those """multi-line strings""" are full of documentation. |
| [11:18:30] |
<pacopablo> |
http://trac.edgewall.org/browser/trunk/trac/env.py#L53 |
| [11:18:31] |
* |
boorad has joined #trac |
| [11:18:44] |
<erg> |
isn't there a pydoc or some such? I mean, to extract the multi-line strings into a concise class, method description |
| [11:19:07] |
<erg> |
sorry, I probably should be asking that in #python :) |
| [11:19:12] |
<exarkun> |
`pydoc trac.env' |
| [11:19:18] |
<pacopablo> |
yes, pydoc does exist |
| [11:19:30] |
<erg> |
hahah... should've tried first and asked second |
| [11:25:56] |
<erg> |
it looks like the Environment constructor accepts the path to the environment, but the WikiSystem constructor chokes (on wiki = WikiSystem('/path/to/env') ) |
| [11:26:17] |
<erg> |
but the doc says to feed both of them a 'trac.core.Component' |
| [11:26:27] |
<pacopablo> |
yeah, cus you need an environment before you can create a WikiSystem |
| [11:26:34] |
<pacopablo> |
so it should be: |
| [11:26:44] |
<pacopablo> |
env = Environment('/path/to/env') |
| [11:26:51] |
<pacopablo> |
wiki = WikiSystem(env) |
| [11:27:17] |
<erg> |
yet again... makes sense (and works!) |
| [11:27:44] |
* |
cmlenz has joined #trac |
| [11:32:26] |
<erg> |
are collections accessible via array indices? ie., env = Environment('/path/to/trac'); wiki = WikiSystem(env); docs = wiki.get_pages('docs'); how to access each page? |
| [11:32:39] |
<erg> |
er, each page object |
| [11:33:36] |
<pacopablo> |
I believe that you have to specify the path to the given page |
| [11:33:55] |
<pacopablo> |
usually I use the WikiPage() object |
| [11:34:15] |
<erg> |
in the get_pages call you specify the path? |
| [11:34:41] |
<pacopablo> |
well, path relative to wiki |
| [11:35:10] |
<pacopablo> |
so if a page were: http://mydom.com/wiki/bob, then 'bob' would be what to pass |
| [11:35:16] |
<erg> |
but if you wanted to get several pages, and step through them or some such? |
| [11:35:39] |
<pacopablo> |
get_pages will give you: bob, bob/one, bob/two, etc |
| [11:35:45] |
<erg> |
I have docs, docs/dev, docs/misc |
| [11:35:46] |
<pacopablo> |
provided bob/one and bob/two exist |
| [11:35:48] |
<erg> |
perfect |
| [11:36:04] |
<erg> |
but the collection that get_pages returns... how to access one element? |
| [11:36:19] |
<pacopablo> |
it returns an iterator, which is basically a list |
| [11:36:40] |
<pacopablo> |
so you can say: doc = [page for page in wiki.get_pages('docs')] |
| [11:36:57] |
<pacopablo> |
that will give you a list of pages that you can then look through |
| [11:37:31] |
<pacopablo> |
alternatively, if you don't need the list object to manipulate, you can just have wiki.get_pages('docs') be you loop condition |
| [11:39:49] |
* |
cookin_ is now known as jrydberg |
| [11:41:34] |
<erg> |
the for loop would look like: for page in wiki.get_pages('path'): |
| [11:41:36] |
<erg> |
right? |
| [11:41:57] |
<pacopablo> |
yeah |
| [11:49:53] |
<erg> |
hmm.. how do you access the contents of the page via a WikiPage object? |
| [11:49:58] |
<erg> |
the pydoc is sparse |
| [11:50:23] |
<pacopablo> |
p = WikiPage('page').text |
| [11:51:42] |
<pacopablo> |
er, WikiPage(env, 'page') |
| [11:51:47] |
<pacopablo> |
.text of course |
| [11:52:18] |
<erg> |
what do I need to import to get WikiPage? |
| [11:52:25] |
<erg> |
from trac.wiki import ??? |
| [11:52:33] |
<pacopablo> |
from trac.wiki.model import WikiPage |
| [11:52:37] |
<erg> |
mmmm |
| [12:17:15] |
* |
flosch has quit IRC |
| [12:19:06] |
* |
boorad has quit IRC |
| [12:19:56] |
* |
boorad has joined #trac |
| [12:32:15] |
* |
agile has quit IRC |
| [12:32:57] |
* |
agile has joined #trac |
| [12:48:41] |
* |
Jack9 has joined #trac |
| [12:49:07] |
<Jack9> |
What could be the reasons I dont have the option to delete a version or wiki entry in my Trac+SVN? |
| [12:49:47] |
<Jack9> |
am I not authenticating against SVN? |
| [12:49:58] |
<Jack9> |
can you not delete the first version of a page? |
| [13:04:16] |
* |
matt_good has joined #trac |
| [13:17:57] |
<pacopablo> |
Jack9: you don't have WIKI_DELETE permissions ? |
| [13:19:39] |
<Jack9> |
sure nuff |
| [13:20:03] |
<Jack9> |
how is trac notified when you commit to svn? |
| [13:20:13] |
<pacopablo> |
by default it isn't |
| [13:20:31] |
<Jack9> |
what's the popular methodology for that |
| [13:20:37] |
<pacopablo> |
you can use the post commit hook in the contrib directory if you want to modiify tickets on svn commit |
| [13:26:32] |
<Jack9> |
can you link to an online resource for the svn source? I installed w/ yum and I dunno where the contrib ended up |
| [13:26:52] |
<Jack9> |
i found a python script that I think will serve as post-commit, but I just want to double check |
| [13:27:21] |
<pacopablo> |
check /usr/share/doc/trac-x.x.x/ |
| [13:27:25] |
<pacopablo> |
might be in there |
| [13:27:38] |
<pacopablo> |
otherwise simply go to the broswer on the main trac site |
| [13:28:01] |
<pacopablo> |
it'll be in the tags subdirectory under whatever release of trac you installed |
| [13:29:26] |
<Jack9> |
ya that's what I put in as post-commit |
| [13:29:49] |
<Jack9> |
no need to hup anything? |
| [13:30:04] |
<pacopablo> |
no. |
| [13:30:24] |
<pacopablo> |
but you have to make sure it's executable, etc. |
| [13:30:43] |
<pacopablo> |
I'm assuming that you're familiar with installing hooks for subversion |
| [13:31:02] |
<Jack9> |
i'm not |
| [13:32:17] |
<pacopablo> |
first you need to create a shell script that is called post-commit and make it executable |
| [13:32:31] |
<pacopablo> |
then you put it in the hooks dir of your repos |
| [13:32:58] |
<pacopablo> |
in the trac-commit-hook script there is an example of what the post-commit hook should look like |
| [13:33:04] |
<Jack9> |
yes |
| [13:33:22] |
<pacopablo> |
then simply adjust the parameters as necessary and then you're done |
| [13:34:47] |
<Jack9> |
I dont understand, the post-commit file in contrib, that isn't enough to drop in the subversion hook dir |
| [13:34:51] |
<Jack9> |
? |
| [13:35:06] |
<pacopablo> |
no |
| [13:35:16] |
<Jack9> |
probably shouldnt be named post-commit |
| [13:35:26] |
<pacopablo> |
it's named trac-post-commit |
| [13:35:41] |
<Jack9> |
sure enough |
| [13:35:57] |
* |
coderanger_ has quit IRC |
| [13:36:12] |
<pacopablo> |
so now create a post-commit script |
| [13:36:21] |
* |
lightcap has quit IRC |
| [13:36:27] |
<pacopablo> |
based off the example in the trac-post-commit hook |
| [13:36:42] |
<pacopablo> |
basically it's a simple bash script to call the trac-post-commit hook |
| [13:36:44] |
* |
lightcap has joined #trac |
| [13:37:10] |
<pacopablo> |
that passes the proper args to the trac-post-commit script |
| [13:37:19] |
* |
lightcap has quit IRC |
| [13:38:12] |
<Jack9> |
got it |
| [13:38:28] |
<erg> |
it looks like WikiPage.text stores the text with whatever line endings the client provided -- ie., if you edit a page from a windows client, page.text has "\r\n" instead of just "\n" |
| [13:38:51] |
<pacopablo> |
erg: understanable |
| [13:39:09] |
<erg> |
is there any arguments to text.split() that will just split agnostic of line termination? |
| [13:39:34] |
<erg> |
s/is/are/ |
| [13:43:21] |
* |
lightcap has joined #trac |
| [13:49:38] |
* |
hunter has quit IRC |
| [13:53:59] |
<coderanger> |
erg: splitlines? |
| [13:55:43] |
<erg> |
yeah, that does |
| [13:55:44] |
<erg> |
it |
| [13:55:55] |
<erg> |
.... I guess it's time to learn more python |
| [13:57:54] |
* |
danbeck has quit IRC |
| [14:00:55] |
* |
lightcap has quit IRC |
| [14:09:31] |
* |
otavio has joined #trac |
| [14:09:42] |
<otavio> |
cmlenz: Check it: http://www.wiggy.net/#20060804trac-cia |
| [14:09:59] |
<otavio> |
cmlenz: dunno if wiggy already reported it as a ticket |
| [14:10:47] |
<matt_good> |
otavio: someone did report a ticket about adding an extension for notification plugins, noting CIA support as a goal |
| [14:13:12] |
<otavio> |
matt_good: there is already have a ready patch |
| [14:13:23] |
<otavio> |
matt_good: you might do a look and apply if well done |
| [14:15:05] |
<erg> |
is there a .uniq method (or equivalent) for arrays? |
| [14:15:36] |
<exarkun> |
no |
| [14:15:49] |
<exarkun> |
also, #python is a good channel for general python questions |
| [14:16:11] |
<otavio> |
matt_good: he also implemented a testing support for tickets. You might check both patches |
| [14:16:18] |
<erg> |
I'm not running an identd (windows), and I get 'You need to be identified to join that channel' |
| [14:16:39] |
<exarkun> |
That message regards Freenode identification, not ident. :) |
| [14:16:43] |
<exarkun> |
/msg nickserv help |
| [14:18:49] |
<coderanger> |
otavio: That kind of thing shouldn't be int Trac itself, it belongs in a plugin |
| [14:19:50] |
* |
erg is now known as raphael |
| [14:20:15] |
<otavio> |
coderanger: the testing? or cia? |
| [14:20:19] |
<coderanger> |
Both |
| [14:20:46] |
* |
raphael is now known as tomorrow |
| [14:21:05] |
<coderanger> |
There are too many notification systems and ticket testing systems to possibly try doing it in a monolithic fashion |
| [14:23:17] |
<coderanger> |
testing stuff would require the workflow branch at least, but notification plugins can already use the TicketChangeListener interface |
| [14:37:10] |
* |
tenshiKur0 has joined #trac |
| [14:38:13] |
<Jack9> |
how can I keep trac from being unable to see the repository when I commit changes? |
| [14:38:44] |
<Jack9> |
er wrong chan |
| [14:39:52] |
* |
tenshiKur0 has quit IRC |
| [14:41:50] |
* |
matt_good has quit IRC |
| [14:48:53] |
<coderanger> |
Not sure what other chan you would ask that in ... |
| [14:56:49] |
* |
bnovc has quit IRC |
| [15:02:49] |
* |
ErikRose has quit IRC |
| [15:13:20] |
<coderanger> |
alect: STRT |
| [15:15:31] |
<otavio> |
coderanger: makes sense |
| [15:16:16] |
* |
agile has quit IRC |
| [15:19:48] |
* |
jrydberg has quit IRC |
| [15:31:19] |
* |
cmlenz has quit IRC |
| [15:38:16] |
<tomorrow> |
anyone using the WikiTemplates plugin? |
| [15:38:34] |
<tomorrow> |
or know anything about it? |
| [15:39:14] |
<pacopablo> |
s0undt3ch does |
| [15:42:04] |
<tomorrow> |
s0undt3ch: you around? |
| [15:42:50] |
<tomorrow> |
well, another question: anyone know if there's a limit on the length of arguments passed to macros? |
| [15:45:09] |
<pacopablo> |
shouldn't be |
| [15:45:18] |
<pacopablo> |
unless the macro itself imposes one |
| [15:46:56] |
<tomorrow> |
I want to get a templating system going inside of trac (take advantage of the history features, centralize documentation, etc), but the macro and plugin seem a little too lightweight |
| [15:47:20] |
* |
PasChampionDuMon is now known as Riccc |
| [15:47:21] |
<tomorrow> |
I'd have to pass pretty large strings into the macro, and it would be pretty ugly in the calling page |
| [15:47:29] |
* |
Riccc is now known as Rica |
| [15:47:50] |
* |
klasstek has quit IRC |
| [15:47:52] |
<tomorrow> |
pacopablo: do you know if you can split a macro invocation across multiple lines? |
| [15:48:01] |
<pacopablo> |
yes |
| [15:48:15] |
<pacopablo> |
well, I think so |
| [15:48:26] |
* |
grim has joined #trac |
| [15:48:27] |
<pacopablo> |
actually not sure I've ever tried |
| [15:48:28] |
<tomorrow> |
[[T(TemplateName| |
| [15:48:34] |
<tomorrow> |
Argument1| |
| [15:48:35] |
<grim> |
wheres the best place to send patches? |
| [15:48:41] |
<tomorrow> |
Argument2| (etc) |
| [15:48:58] |
<tomorrow> |
I'll just try it (what a novel idea!) |
| [15:50:38] |
* |
Jack9 has quit IRC |
| [15:51:50] |
<pacopablo> |
grim: create a ticket and attach it to the ticket |
| [15:51:54] |
<tomorrow> |
on 0.9.6 multi-line macro invocations do NOT work |
| [15:52:07] |
<pacopablo> |
there is your answer! :) |
| [15:52:10] |
<coderanger> |
tomorrow: use the {{{#!foo }}} form |
| [15:52:30] |
<tomorrow> |
{{{ #!macro_name }}} ? |
| [15:52:38] |
<coderanger> |
{{{\n#!macroname\nlines_of_text\n}}} |
| [15:53:11] |
<tomorrow> |
and lines_of_text will be passed as an argument to macroname? |
| [15:53:14] |
<coderanger> |
yep |
| [15:53:20] |
<tomorrow> |
no need for parens? |
| [15:53:24] |
<coderanger> |
no |
| [15:53:32] |
<tomorrow> |
one argument per line? |
| [15:53:47] |
<coderanger> |
The text is passed to the macro exactly as you enter it |
| [15:54:13] |
<coderanger> |
Just as one long (possibly multi-line) string |
| [15:54:37] |
<tomorrow> |
is there any way to pass specific args into the macro, as well as (possibly long) strings? |
| [15:55:13] |
<coderanger> |
Most string define the first line of text to be args (comma sep) |
| [15:55:18] |
<coderanger> |
er, most macros |
| [15:55:22] |
<grim> |
pacopablo: done ;) |
| [15:55:33] |
<coderanger> |
Even in the one-line form the string is pased unaltered |
| [15:55:41] |
<tomorrow> |
anywhere I can read more about the {{{ #!macroname }}} invocation format? |
| [15:55:5 |
