Team Chat Logs

February 17, 2010

2010 1
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
<< <   > >>

[00:18:14.786527]<otaku42>moin
[00:49:46.200751]<gozerbot>trac: Changeset [9199]: WikiProcessors: fix a potential problem with processor arguments. At the ... - <http://trac.edgewall.org/changeset/9199>
[01:19:46.630607]<gozerbot>trac: Changeset [9200]: WikiProcessors: `span` can be called as a wiki processor and the parameter ... - <http://trac.edgewall.org/changeset/9200>
[01:49:47.041687]<gozerbot>trac: Ticket #8204 (Unify wiki processors and macros) closed - <http://trac.edgewall.org/ticket/8204#comment:10>
[02:19:47.979706]<gozerbot>trac: Changeset [9201]: TracBrowser: fix a link which was not MultiRepos compatible and remove a ... - <http://trac.edgewall.org/changeset/9201>
[02:34:20.972587]<piko>Hello all, I search for some tracking environment and wiki system to document work of small team. I know track as software used for raising bug report/acquiring changes ... and wiki system. This all is nice interface between devs and other world, but I need also to log some things (like 12.12. 2010 14:34 new version released for testing). Could trac do also this?
[02:35:53.578599]<piko>Several other tasks like ([date] machine xx installed) would be nice to use
[02:38:42.988035]<hylje>piko: use the Trac API to make whatever event services you have talk to Trac
[02:43:54.460830]<hylje>web services should make the easiest way to communicate with specific running trac instances if you want that
[02:44:17.072975]<hylje>you could also bypass trac altogether and inject your new events to the database
[02:44:50.260297]<hylje>though in that case you also bypass whatever processes set up to trac to control and process row inserts and updates
[02:49:46.832314]<gozerbot>trac: MultiRepos edited - <http://trac.edgewall.org/wiki/MultiRepos?version=3> || 0.12/TracBrowser edited - <http://trac.edgewall.org/wiki/0.12/TracBrowser?version=5> || MultipleRepositorySupport edited - <http://trac.edgewall.org/wiki/MultipleRepositorySupport?version=38>
[02:51:21.213058]<piko>hylje, you mean to implement it? I search more for some existing implementation/plugin ...
[02:53:43.851541]<hylje>search through trachacks for plugins
[02:57:06.502437]<piko>what is trachacks?
[02:58:15.007379]<hylje>http://trac-hacks.org/ (it's also in the topic)
[03:19:52.178010]<gozerbot>trac: 0.12/TracRepositoryAdmin edited - <http://trac.edgewall.org/wiki/0.12/TracRepositoryAdmin?version=10>
[05:18:47.190348]<gozerbot>trac: PyCon edited - <http://trac.edgewall.org/wiki/PyCon?version=9>
[06:18:48.255287]<gozerbot>trac: Ticket #7384 (Unordered list with empty items does not display correctly on FireFox3) closed - <http://trac.edgewall.org/ticket/7384#comment:7> || Ticket #66 (New file contents are shown twice) closed - <http://trac.edgewall.org/ticket/66#comment:4> || TracSprint edited - <http://trac.edgewall.org/wiki/TracSprint?version=27>
[06:48:47.038516]<gozerbot>trac: Ticket #9000 (Add "← Previous TicketBack to QueryNext Ticket → " to bottom of ticket) closed - <http://trac.edgewall.org/ticket/9000#comment:1> || TracSprint edited - <http://trac.edgewall.org/wiki/TracSprint?version=28> || AdvancedSearch edited - <http://trac.edgewall.org/wiki/AdvancedSearch?version=21>
[06:56:57.906789]<Rada>#9000!!!!
[07:01:39.576269]<kirean>Who buys the cake?
[07:02:41.185246]<retracile>Have we hit 9000 commits yet?
[07:02:55.906579]<hylje>soon it is over nine thousand
[07:03:01.938684]<misc>no, 9000 bugs :)
[07:03:02.151759]<hylje>we have to crush the scouter
[07:03:04.519856]<retracile>oh, yeah, we're past 9200
[07:03:25.805189]<retracile>At least we're staying ahead of the bugs ;)
[07:12:03.439365]<gamla_kossan>hi people! um, I'm a bit lost - I'm running trac 0.10 (from epel) on centos 5.4, got mod_python installed, set up my trac.conf, made a vhost, did the trac-admin /srv/trav/barometer initenv, but...............
[07:12:25.035571]<gamla_kossan>when I point my browser towards my tracbox, all I get is the httpd file listing
[07:12:39.610332]<gamla_kossan>(I set the DocumentRoot to /srv/trac/barometer)
[07:12:57.147391]<gamla_kossan>anyone got an idea of what I'm missing?
[07:13:45.650561]<kirean>gamla_kossan: pastebin your apache configs
[07:14:32.209655]<gamla_kossan>kirean: http://fpaste.org/wLsk/
[07:15:09.032769]<gamla_kossan>(this is just the vhost, the rest of the httpd is a standard centos 5.4 (if that tells you anything))
[07:18:18.688462]<gamla_kossan>kirean: I'm guessing the 'Location' bits are funny?
[07:19:04.242256]<gamla_kossan>kirean: well, I tried this just now - http://fpaste.org/dzpp/ but still no dice :/
[07:19:05.665188]<retracile>gamla_kossan: document root shouldn't point into the trac environment on disk
[07:19:21.703746]<gamla_kossan>retracile: oh
[07:19:27.328430]<gamla_kossan>retracile: where should it point?
[07:19:29.854786]<retracile>you don't serve the files directly, which is what you're doing with that.
[07:19:33.794044]<gamla_kossan>right
[07:19:41.533972]<retracile>You need to have mod_python handle it...
[07:20:13.804966]<gamla_kossan>oh, so I should just comment out DocumentRoot then?
[07:20:44.763983]<retracile>gamla_kossan: there should be an example mod_python config somewhere on trac.edgewall.org. If I get a chance later I'll lend a hand, but I'm kinda busy at the moment
[07:20:58.495949]<gamla_kossan>retracile: thanks, I'll look at that!
[07:21:03.983049]<gamla_kossan>(again :)
[07:21:13.462199]<gamla_kossan>(very new to mod_python.. :)
[07:22:17.342774]<retracile>TRAC_ENV should be set to the directory you used for the initenv
[07:22:26.926029]<gamla_kossan>ah
[07:23:38.556578]<retracile>gamla_kossan: The Location should be the part of the URL for where you want to access the trac instance, so maybe '/trac' or /barometer/trac, or /trac/barometer or /barometer ... whatever makes sense to you
[07:24:01.051000]<retracile>I don't _think_ you need the LocationMatch entry you have in that config
[07:24:18.456666]<gamla_kossan>ah ok. it was there by default :)
[07:24:49.259282]<retracile>gamla_kossan: well, keep in mind that I have been known to make mistakes... ;)
[07:24:56.641878]<gamla_kossan>hehe
[07:27:04.232903]<retracile>gamla_kossan: update your paste with your new config, and let me know what you've tried
[07:27:18.294938]<retracile>(I'm waiting on subversion, so you have a minute of my time. ;) )
[07:27:52.342096]<gamla_kossan>hehe
[07:29:23.973851]<gamla_kossan>http://fpaste.org/ZoCt/
[07:30:15.581575]<retracile>gamla_kossan: ok, if you go to your.hostname://var/www/cgi-bin/trac.cgi do you see Trac?
[07:30:57.639185]<retracile>*sigh* Where's my brain? Make that: http://your.hostname/var/www/cgi-bin/trac.cgi
[07:31:23.895058]*retracile mutters something derogatory about subversion's speed
[07:31:24.797149]<gamla_kossan>:) yay
[07:31:36.634413]<gamla_kossan>hold on, got a perm error
[07:31:45.925016]<retracile>gamla_kossan: Ok, I would suggest changing the Location to something more reasonable...
[07:33:29.221742]<gamla_kossan>um, reasonable? care to elaborate?
[07:33:55.937549]<retracile>maybe '/trac' or /barometer/trac, or /trac/barometer or /barometer
[07:34:36.136647]<retracile>That way you'd go to http://your.hostname/trac or http://your.hostname/barometer or something
[07:34:36.380205]<gamla_kossan>hm, but changing the location..
[07:34:46.743432]<retracile>That's not the location on disk....
[07:36:18.900303]<gamla_kossan>retracile: thanks!
[07:36:26.836308]<gamla_kossan>retracile: now it looks like it should!
[07:36:38.293671]<retracile>you'll probably want to setup authentication next.
[07:37:08.809325]<gamla_kossan>yeah :)
[07:48:47.819610]<gozerbot>trac: Ticket #9008 (: in password for HTTP Auth always fails) closed - <http://trac.edgewall.org/ticket/9008#comment:2>
[08:18:10.836581]<agussman>Is trac search case-sensitive?
[08:18:48.183475]<gozerbot>trac: Ticket #8751 (refactor transaction handling) closed - <http://trac.edgewall.org/ticket/8751#comment:62> || TracMercurial edited - <http://trac.edgewall.org/wiki/TracMercurial?version=68> || TracStandalone edited - <http://trac.edgewall.org/wiki/TracStandalone?version=76>
[09:18:48.126660]<gozerbot>trac: Ticket #7512 (report 8 (active tickets, mine first) sorts owner wrong) reopened - <http://trac.edgewall.org/ticket/7512#comment:10> || Ticket #9062 (IOError: (13, 'Permission denied')) created - <http://trac.edgewall.org/ticket/9062>
[09:48:48.139858]<gozerbot>trac: Ticket #9062 (IOError: (13, 'Permission denied')) closed - <http://trac.edgewall.org/ticket/9062#comment:2>
[10:18:48.771738]<gozerbot>trac: SeaChange/WhatDevelopersWant edited - <http://trac.edgewall.org/wiki/SeaChange/WhatDevelopersWant?version=3>
[11:18:49.588292]<gozerbot>trac: Ticket #8046 (Sort browser entries by author) reopened - <http://trac.edgewall.org/ticket/8046#comment:7>
[11:21:45.196198]<Av>hi guys :) I'm trying to find a particular functionality, can someone help me? What I want is this: http://trac-hacks.org/wiki/PrivateTicketsPlugin but I want to be able to change it per-ticket. Eg, some tickets only the people mentioned can see. Other tickets, people in the same group as those mentioned can see. And finally, ones everyone can see.
[11:21:49.726054]<Av>is that possible?
[12:04:40.436611]<cmc>Av: I'm not aware of a plugin that does that, but you can probably code one similar to PrivateTicketsPlugin by looking at its source
[12:32:47.111554]<mydog2>hey... in trac.. is there a way to set it up so users have to register/login in order to make changes/add files to a project..
[12:33:15.490355]<mydog2>and is there a way to have separate areas/folders for different files.. docs.. source.. help.. that kind of thing..
[12:36:36.281122]<cmc>I think TICKET_MODIFY and FILE_VIEW are the only permissions related to that
[12:36:53.812853]<cmc>I don't believe you can make an alternative directory structure
[12:38:29.688858]<mydog2>cmc - was that to my question?
[12:38:40.258937]<cmc>yes
[12:39:20.929220]<mydog2>so how can i register as a new user..
[12:39:33.290373]<mydog2>i just see the login
[12:41:41.085641]<cmc>Adding authentication: http://trac.edgewall.org/wiki/TracCgi#AddingAuthentication
[12:42:23.121811]<cmc>http://trac-hacks.org/wiki/AccountManagerPlugin if you want people to sign up
[12:43:32.304119]<mydog2>and you said i can't store files in different folders/heirarchies?
[12:43:42.150499]<cmc>not that I'm aware of
[12:46:59.700037]<mydog2>so all files are in a single location??
[12:47:08.321223]<mydog2>ouch...
[12:50:17.504396]<cmc>attachments are stored in /attachements/ticket#
[12:50:54.964097]<cmc>you can't alter that location, as far as I am aware
[12:51:56.501689]<cmc>there is a hierarchy, you just can't change it. Does that make sense?
[12:53:42.616198]<rblank>retracile: Not driving yet? :)
[13:13:42.172555]<Av>cmc: thanks :)
[13:14:21.848673]<cmc>:)
[13:21:21.440841]<Av>never written a plugin before. this should be interesting
[13:23:28.556383]<cmc>I made a patch against trac core which allows for multi-selects; maybe you can use that for users
[13:24:14.884400]<cmc>http://trac-hacks.org/wiki/MultiSelectCustomFieldsPatch
[13:25:34.962258]<Av>almost. It's only have 3 users in there: Private|Group|Public
[13:26:19.784591]<Av>and then, I need to check: If private, and current user = (Owner|Reporter|in CC), then show.
[13:26:34.077503]<Av>and then somehow do somehting more complex for Group
[13:27:28.403843]<cmc>:) Yeah, I'd suggest looking at trac-hacks for something that pays attention to permissions/groups and review that
[13:27:41.474231]<cmc>source is self documenting, right? :-P
[13:31:34.250935]<Av>hah! yes :P
[13:31:43.826022]<Av>http://trac-hacks.org/wiki/VirtualTicketPermissionsPlugin
[13:31:45.645011]<Av>that's close
[13:31:51.118502]<Av>except it's global, not per-ticket
[13:31:54.019980]<jhammel>cmc: that said, there sure is a lot of documentation written ;)
[13:31:59.158457]<Av>maybe that's the easiest thing to hack
[13:34:19.435658]<cmc>jhammel: true
[13:34:29.169994]<cmc>Av: http://trac.edgewall.org/wiki/TracDev might be helpful
[13:34:55.706684]<Av>thanks :)
[13:36:37.314303]<cmc>wow yeah a lot has been added since last I looked there
[14:16:24.274748]<groogs>anyone know an easy way to find tickets that were ever reopened (but eg, the ticket may be closed now)? just doing some analytics
[14:17:14.929757]<cmc>look in ticket_change for field='status' and newvalue='open'
[14:17:31.106885]<cmc>you probably want oldvalue='closed', too
[14:42:39.051374]<groogs>cmc: thanks
[14:43:36.393106]<cmc>np
[14:48:39.809077]<retracile>groogs: it'll vary based on your configured workflow, but in some of the workflows a reopen action will have a newvalue="reopened" instad of "open".
[14:49:08.136540]<groogs>retracile: yeah, i did for mine
[14:50:33.505584]<retracile>groogs: did you upgrade from 0.10?
[14:50:47.113613]<groogs>i haven't totally decided if 'reopened' belongs in my workflow or not (its effectively equal to 'new', just coming from a different path) .. but its handy for tracking tickets that are regressions, as well as doing this analysis now
[14:51:02.077168]<groogs>retracile: hm, i THINK this was always .11, but I could be wrong
[14:51:22.748894]<groogs>its a customized workflow anyways, with 'testing' and a couple other statuses
[14:51:42.620741]<retracile>groogs: ok. Well, there are two "default" workflows in 0.11, if it's an upgrade, it's one thing, and if it's a new 0.11 install, it's something more sane.
[14:51:50.413764]<retracile>Ah, ok
[14:52:15.075747]<groogs>yeah, the .10 workflow was a bit weird. i do like the new one in new .11 installs
[14:52:23.533408]<retracile>heh :)
[14:53:05.143947]<groogs>actually one thing i haven't figured in mine is with my 'testing' status, how to handle owner
[14:53:54.275766]<groogs>generally it goes new > confirmed > testing > closed ... when it goes to testing, it gets reassigned to someone else (usually a special 'QA' user)
[14:54:37.682799]<groogs>but if it goes testing > reopened, whoever opens has to specifically look back to find the original owner. it would be nice to have seperate 'owner' and 'tester' fields or something..
[14:55:02.057567]<groogs>love to hear how other people handle it, or suggestions on it...
[15:00:15.066739]<cmc>groogs, we keep the owner the same throughout that whole process, but I think there's a plugin for what you were describing
[15:00:16.388035]<cmc>one moment
[15:00:47.006977]<cmc>http://trac-hacks.org/wiki/AdvancedTicketWorkflowPlugin
[15:00:59.133115]<cmc>set_owner_to_previous, I think?
[15:01:11.857957]<groogs>oh.. yeah, i saw that before, forgot about it though, thanks
[15:01:36.967460]<cmc>retracile wrote it, so he'd know if it suits you better
[15:01:47.404737]<groogs>i do like the idea of keeping the owner the developer the whole time
[15:53:10.286416]<mitsuhiko>pacopablo: yay. trac sprints at pycon
[15:53:18.423895]<mitsuhiko>now i feel even worse for not attending
[15:56:15.014192]*retracile wonders if he signed up for those yet.... wanders off to check
[15:57:18.645357]<retracile>oh good, my name's already on the list :)
[16:01:38.371450]<retracile>hmm... I wonder if IBM's storage unit is using Trac.
[16:04:02.857993]<jhammel>retracile: what makes you say that?
[16:04:35.883021]<retracile>jhammel: look at the PyCon page for the Trac sprint, and two names listed there at the bottom.
[16:05:08.775384]<retracile>(under 'participants')
[17:25:07.863014]<paissad>hi all, is it possible to get the translation of trac in some other langages ? ..
[17:25:15.858299]<paissad>here is my version 0.11.1
[17:27:25.359745]<paissad>is it available if i upgrade to 0.11.6 ?
[17:30:54.383483]<doki_pen>pacopablo: yo, I have an accountmanager question
[17:33:24.501213]<retracile>paissad: start here: http://trac.edgewall.org/wiki/TracL10N
[17:36:27.431206]<paissad>retracile, do you use Debian/Ubuntu .... i guess it's this package you mean
[17:36:28.003993]<paissad>http://pastebin.com/f41442b63
[17:40:51.481735]<retracile>paissad: I generally use Fedora, and I really haven't done anything with translation stuff myself.
[17:41:07.007196]<paissad>ok^^
[17:55:44.415436]<|rt|>I'm about to setup Trac for a client who's running windows and have a question about the bitnami package....does anyone know how easy these packages are to upgrade as newer versions come out?
[17:58:12.124217]<retracile>|rt|: Had never heard of bitnami... interesting project. But that also implies I have no knowledge applicable to answering your question....
[17:58:53.688510]<|rt|>that's ok....i found out about bitnami from the trac wiki
[17:59:21.714026]<retracile>heh :)
[18:00:24.959100]<|rt|>seems like a perfect solution for my client....I won't have to spend the time getting all the bits installed and setup right and they are small enough where sqllite was the db backend I was planning on using anyhow b/c mysql would be overkill
[18:00:55.496679]<|rt|>but I'm concerned about upgrading and maintainability
[18:02:19.234274]<|rt|>the tricky thing is going to be migrating their data out of CVSNT and into subversion.....looks like the CVSNT fork is a bit of a bastard child so cvs2svn may not work
[18:51:34.238228]<retracile>|rt|: that source control migration sounds like it could be painful :(
[18:52:41.920664]<retracile>|rt|: you might ping people in #revctrl about it though. I don't know how many people are still hanging out in there, but at one time there was a lot of source control knowledge concentrated there.
[19:24:52.881162]<|rt|>retracile: thanks for the tip
[19:55:06.999498]<|rt|>what's the best way to get trac to deal with multiple projects? The wiki seems to go 100 different directions when trying to figure this out
[19:56:41.835737]<retracile>|rt|: that's because there isn't one right solution. You can do one environment per project, you can do trac-forge, you can combine them into one source repository and trac instance divided by 'component' or the like. Depends on how many and how large your multiple projects are.
[19:57:39.761452]<|rt|>yeah I was looking at the component option....looking for simple...it's for a small company that only has a few developers working on a dozen or so software projects
[20:00:17.470621]<retracile>|rt|: how is their source control structured?
[20:00:31.698569]<retracile>ie. do they have a dozen repositories, or one?
[20:01:12.530715]<|rt|>retracile: right now they are using CVSNT which keeps each project in it's own repo...I think CVSNT's terminology for it is module
[20:01:28.643967]<|rt|>I was planning on bringing them all into one SVN repo though
[20:10:01.831036]<retracile>|rt| Ok, my inclination in that case would be to put them all in one Trac environment and map a 'component' to a top-level directory in subversion coresponding to each of those modules.
[20:10:45.529621]<|rt|>yeah sounds like a good plan....I don't think any of their software projects are large enough to need bug tracking at a component level
[20:11:02.743263]<|rt|>so one level of tickets per project should suffice
[20:11:03.397103]<retracile>That'll be simpler than some of the other approaches. If they decide later to split those apart, it'll take some effort.
[20:12:31.689208]<|rt|>thanks for your help retracile
[20:13:40.852883]<retracile>|rt| np
[21:37:15.053649]<doki_pen>goodnight.