Team Chat Logs

January 26, 2010

2010 0
Mo Tu We Th Fr Sa Su
        1 2 3
4 5 6 7 8 9 10
11 12 13 14 15 16 17
18 19 20 21 22 23 24
25 26 27 28 29 30 31
<< <   > >>

[00:01:11.930953]<otaku42>moin
[02:10:43.442818]<PlasmaHH>hi, it looks that trac somehow keeps a cache of things like log messages from the svn repo... how can I reset that cache?
[02:17:07.083413]<kirean>PlasmaHH: not sure that it's a cache thing, but you may need to sync Trac with svn if you hacked any svn log messages
[02:17:45.501082]<PlasmaHH>kirean: how to do that manually?
[02:17:54.328852]<kirean>http://trac.edgewall.org/wiki/TracFaq#RevisionLog
[02:18:03.815869]<kirean>PlasmaHH: ^^
[02:18:32.306034]<PlasmaHH>thanks a lot
[07:34:23.444359]<cboos>osimons: got a minute?
[07:35:02.445725]<cboos>I'd like to renegotiate http://trac.edgewall.org/ticket/5968#comment:6 ;-)
[07:36:00.405719]<cboos>e.g. [trachacks:ThatPlugin] displaying as trachacks:ThatPlugin, instead of ThatPlugin
[07:37:10.423585]<cboos>your reasoning was that trachacks: prefix should be shown always, like we do for [http://...], but I think that Inter* prefixes are more like realm prefixes and that we should hide them when in [] brackets.
[07:37:55.656072]<cboos>After all, one can always write a plain " trachacks:ThatPlugin " string when one wants to see the Inter* prefix.
[07:39:22.067962]<cboos>With the current r6417 / r7239 behavior, we have no way of hiding the prefix (except from the heavy handed [trachacks:ThatPlugin ThatPlugin]).
[07:40:12.067707]<cboos>So I'd like to revert this, especially that the hack I suggested to you in http://trac.edgewall.org/ticket/5968#comment:8 now gets in the way of reusing _make_link ...
[08:15:07.688172]<cboos>osimons: in case you find some time -> http://trac.edgewall.org/ticket/5968#comment:11
[10:40:04.249219]<puzzel>hello, i want to add a "Documentation" section in the Wiki with an hierarchical structure. how do i define such a structure?
[10:45:24.414084]<kisielk>just make a wiki name with slashes in it
[10:45:39.680447]<kisielk>[wiki:Documentation], [wiki:Documentation/Foo], [wiki:Documentation/Bar]
[10:45:42.358799]<kisielk>etc
[10:47:24.546517]<puzzel>great! thank you kisielk.
[10:47:32.624866]<kisielk>np
[11:01:14.351081]<bsund>How much work is involved to migrate from mantis to trac?
[11:10:06.227281]<puzzel>bsund: i never did it but there is a migration script available: http://trac.edgewall.org/wiki/TracImport#Mantis
[12:16:53.680015]<dikim33>Hi, can you help me to figure out the weird behavior on the new ticket which is created by the svn check-in hook? (note, the ticket was not created by the trac web interface but by the svn commit hook script).
[12:18:09.692729]<dikim33>When a ticket admin tries to update the ticket with some comments, the description is updated even though the description was not even touched.
[12:19:43.217767]<dikim33>But the preview of ticket to see if there is any diff but nothing shows and "description modified" message can be seen.
[12:21:34.902015]<dikim33>http://pastebin.ca/1767009
[12:22:03.202333]<dikim33>This is the part of svn hook script to generate the trac ticket.
[12:22:56.983791]<dikim33>FYI, adding a comment to the ticket as a normal user is just fine because it seems that the user does not have the privilege to change the description of the ticket.
[12:24:09.756704]<scfe>dikim33: Check the database. I guess there is something going on with conversion of '\n' to '\r\n'.
[12:27:27.568834]<dikim33>Yes, scfe thanks for your input. That's the most suspicious thing that I have had but I have no idea how to create a ticket just like creating a ticket via the trac web interface.
[12:27:29.259206]<dikim33>http://pastebin.ca/1767017
[12:27:53.099218]<dikim33>This is the sqlite db contents right after updating the ticket.
[12:31:23.009661]<scfe>You won't see it on the sqlite command line. You need to go with Python and do a repr() on the values.
[12:32:13.715536]<scfe>You can try to do my_description.replace('\n', '\r\n') in your commit hook.
[12:35:28.252528]<dikim33>ok, scfe thanks.
[12:39:44.543285]<dikim33>scfe: your answer fixed my problem. Thank you very much.
[12:40:37.195864]<scfe>dikim33: Glad to hear that it worked for you.
[12:40:41.797224]<scfe>However it is not a real fix imho
[12:41:17.629468]<scfe>for example the replacement is not smart enough. If your svn hook has '\r\n' ever, the result will be '\r\r\n'.
[12:41:20.094685]<dikim33>scfe: I agree. anything in your mind for the real fix?
[12:41:38.629006]<dikim33>Oh, right.
[12:41:48.825468]<scfe>Also I'm not sure what happens if you have a Unix or Mac machine in the web interface - do they send just '\n' or '\r\n' as well?
[12:42:23.029671]<scfe>I see two paths fixing this:
[12:42:23.459890]<dikim33>Looks like that it is '\r\n'.
[12:43:26.444829]<scfe>1. Fix trac itself - IMHO changing from '\r\n' should result in a 'description modified'. Or at least the ticket model should check when the ticket is created that '\r\n' is always used.
[12:43:52.209171]<scfe>however this will require some work (mostly convincing rblank+cboos I guess)
[12:44:08.288787]<scfe>2. Use a regex in your svn hook.
[12:44:51.496870]<dikim33>I was thinking the second solution.
[12:45:11.986688]<scfe>e.g. re.sub('[^\r]\n', '\r\n')
[12:45:35.525448]<scfe>dikim33: That's what I feared (I hoped actually that someone would fix this issue for me :-)
[12:46:20.177120]<dikim33>scfe: thanks. your answer was really helpful.
[12:46:45.209130]<scfe>dikim33: You're welcome.
[20:26:41.103526]<rw__>anyone here using email2trac to update tickets?
[20:28:25.488462]<rw__>email2trac is adding new tickets no problem, but when I try and format a subject to update an existing ticket...it doesn't show up on the ticket (and doesn't create another ticket either... the void claims my updates)
[21:46:35.202334]<rw__>nm error in my email2trac config
[23:53:14.532189]<dubey>hi
[23:53:31.581097]<dubey>i need help to config trac notification