Monday, 2010-07-05

*** Quits: micahg (~micah@ubuntu/member/micahg) (Ping timeout: 245 seconds)00:19
*** Joins: kirillka (~Miranda@global01.vester.ru)00:45
*** Joins: LinuxLearner64 (~foo@ingena.lnk.telstra.net)01:48
LinuxLearner64Hi, is it possible to trigger actions in mantis after X time? eg someone logs an issue, and if nobody updates it within 30 minutes an email is generated?01:49
*** Joins: Cupertino (~Cupez@unaffiliated/cupertino)02:33
*** Joins: giallu (~giallu@fedora/giallu)03:07
*** Quits: siebrand (~beis@62.237.32.162) ()03:08
*** Quits: LinuxLearner64 (~foo@ingena.lnk.telstra.net) ()03:11
*** Joins: siebrand (~beis@conference/akademy/x-vtbmzxdjemnqjjbp)03:42
*** Quits: siebrand (~beis@conference/akademy/x-vtbmzxdjemnqjjbp) (Read error: Connection reset by peer)04:02
*** Joins: siebrand_alt (~beis@conference/akademy/x-ocuxmnoxkdzowfgg)04:03
*** Joins: Rixie (~Rixie@0x4dd7390e.adsl.cybercity.dk)04:05
*** Quits: siebrand_alt (~beis@conference/akademy/x-ocuxmnoxkdzowfgg) (Read error: No route to host)04:05
*** Joins: siebrand (~beis@conference/akademy/x-spahergqwhesmmac)04:06
*** Joins: vinvin (~vinvin@ANice-251-1-43-117.w86-206.abo.wanadoo.fr)04:12
vinvinhi04:12
vinvinanyone reads the forum sometimes or is it a dead place?04:13
vinvinanyone tried to use captcha on a non-windows OS?04:17
*** Quits: siebrand (~beis@conference/akademy/x-spahergqwhesmmac) (Ping timeout: 245 seconds)04:18
*** Joins: rolfkleef (~rolf@cc1080790-a.hdb1.ov.home.nl)04:30
*** Joins: micahg (~micah@ubuntu/member/micahg)05:08
*** Joins: siebrand (~beis@conference/akademy/x-yxpwiwgveevmolrt)06:55
*** Joins: moto-moi (~hylke@cara.xs4all.nl)09:56
nuclear_eclipseToffeePops: it should be a configurable threshold IIRC10:22
nuclear_eclipsevinvin: I'm able to use captcha on my linux host10:22
nuclear_eclipsevinvin: I had to set the following values in my config_inc.php:10:23
nuclear_eclipse$g_system_font_folder   = '/usr/share/fonts/truetype/ttf-dejavu/';                                            10:23
nuclear_eclipse$g_font_per_captcha = 'DejaVu.ttf';10:23
*** Joins: arslanali (~chatzilla@202.59.74.74)10:37
arslanalimantis is down http://www.mantisbt.org/wiki/doku.php/mantisbt:instantmantis_faq?s=smtp10:38
arslanaliDatabase connection failed. Error received from database was #1040: Too many connections.10:38
arslanalimy emails are not working with mantis10:38
arslanalican anyone help me in emails using mantis10:40
*** Quits: Cupertino (~Cupez@unaffiliated/cupertino) (Quit: I give up...)10:55
*** Quits: giallu (~giallu@fedora/giallu) (Ping timeout: 240 seconds)11:08
*** Joins: fanno (~b3g@193.3.95.240)11:14
*** Quits: arslanali (~chatzilla@202.59.74.74) (Remote host closed the connection)11:34
*** Parts: Rixie (~Rixie@0x4dd7390e.adsl.cybercity.dk)11:36
*** Quits: kirillka (~Miranda@global01.vester.ru) (Quit: kirillka)12:08
vinvinnuclear_eclipse: thanks for the answer. That's what I did, but it has no effect on the signup page12:26
vinvinnuclear_eclipse: do you have debian? What package did you install for GD?12:31
*** Quits: siebrand (~beis@conference/akademy/x-yxpwiwgveevmolrt) ()12:37
vinvinok nevermind... I did not find the right package12:40
*** Parts: vinvin (~vinvin@ANice-251-1-43-117.w86-206.abo.wanadoo.fr)12:52
*** Joins: skayser (~ska@vserver01.sebastiankayser.de)13:30
skaysergreetings13:30
skaysersomething wrong with mantisbt.org?13:30
skayserconnection times out here13:30
nuclear_eclipseskayser: yeah, I'm looking into it13:30
nuclear_eclipsepushing a hard reboot, should be back up in a few minutes13:32
skayserthanks!13:32
nuclear_eclipsenp13:32
*** Joins: paulr (~paul@cpc1-enfi9-0-0-cust389.hari.cable.virginmedia.com)14:51
paulrnuclear_eclipse: moo14:52
nuclear_eclipsehi paulr 14:56
paulrdhx/myself had a good play at weekend14:57
paulryou cna't do sunday's can you ?14:57
nuclear_eclipsedepends on what's going on14:59
paulrwell, we came up with a script to build the integrity data @ weekend14:59
paulrhowever started having a debate about how far back to go15:00
*** Joins: siebrand (~beis@62.237.32.162)15:04
paulrnuclear_eclipse: wow, the problem with git is if people dont use sensible heads :P15:07
paulr3 hours wasted ;/15:09
nuclear_eclipsepaulr: I'm not even sure what you're talking about atm... =\15:13
paulri've spent 3 hours working out why something doesn't work in a projects trunk to find out they've been doing development in a github fork and haven't merged it for ages :)15:22
paulrmy question: should I ignore the main git ? answer: yes/maybe15:23
nuclear_eclipseah15:23
paulranyway15:24
paulr<paulr> well, we came up with a script to build the integrity data @ weekend15:25
paulr<paulr> however started having a debate about how far back to go15:25
paulrany thoughts?15:25
nuclear_eclipsewhat integrity data?15:26
nuclear_eclipseI'm completely lost15:26
paulrfor check.php15:26
nuclear_eclipseah15:28
nuclear_eclipsethat15:28
paulrif we are looking for old files15:38
paulrwe probably really need to go back to day 015:38
nuclear_eclipseperhaps15:40
nuclear_eclipseor we could just have some way of saying "if it doesn't match, it must be customized or old"15:40
paulrwell, could be nice to detect customised vs old15:43
nuclear_eclipsetrue15:47
nuclear_eclipsebut is it really worthwhile do know "all" old revisions of files?15:47
ToffeePopsnuclear_eclipse: thanks for the answer some hours ago, will take a look15:48
paulrnot sure15:48
nuclear_eclipseToffeePops: yw15:49
paulrit's useful in the sense that if we say we store all old releases15:49
paulri.e. tags15:49
paulrit's probably not that much more to store commits15:50
paulrI think I summed it up to dhx with15:50
paulrit's a file that lives in tarball that sf.net host for free15:50
ToffeePopsnuclear_eclipse: Hi a few hours ago I raised the question re. th fact that we can only send reminders to developers and higher and you thought 'it should be a configurable threshold IIRC'...16:02
ToffeePopsThere is a threshold but it controls who can send reminders, not the people they can be sent to. I.e it's the latter that is the problem - is there a setting I've missed, I cannot see how to allow reminders to be sent to anyone?16:02
paulri'm also wondering if you can get from a file blob to a commit blob16:02
paulrToffeePops: there's probably a config value16:03
*** Joins: KevBurnsJr (KevBurnsJr@c-69-181-187-21.hsd1.ca.comcast.net)16:04
KevBurnsJrwhat is the default administrator password for mantisbt?16:04
ToffeePopspaulr: might that be in a config file rather than a setting found via the interface?16:04
paulrKevBurnsJr: root/admin16:04
paulrToffeePops: probably16:04
KevBurnsJrroot, thankx16:05
*** Quits: mellen (~thansen@x1-6-00-22-02-00-0c-40.k253.webspeed.dk) (Ping timeout: 265 seconds)16:05
ToffeePopsany idea where to start looking? I do admin via the interface but not familiar with the on-disk config files...16:06
ToffeePopspaulr:16:06
paulrnope16:07
paulrconfig_defaults_inc.php16:07
paulrit's a nice long read :)16:07
ToffeePopsYeah I have seen that one ;-)16:07
ToffeePopspaulr: Another thing that I and several of our users are missing - we used to put our product build IDs (old, current or future builds) in the field "Product Version" but that has now turned into an uneditable combo box.16:09
ToffeePopsAny way to change that?16:09
*** Joins: mellen (~thansen@x1-6-00-22-02-00-0c-40.k253.webspeed.dk)16:10
ToffeePopsWe have 100's of builds so I can't see that we can add them all to a combo list (if that is the only solution)... so maybe we need to add a custom field.16:11
*** Joins: giallu (~giallu@fedora/giallu)16:12
ToffeePopsWhat concerns me more is that all the old values seem to have disappeared :(16:12
nuclear_eclipseToffeePops: there's a separate field for product build that's no longer displayed by default16:15
nuclear_eclipseyou can edit $g_view_page_columns iirc to add that back in16:15
ToffeePopsnuclear_eclipse: awesome!16:15
nuclear_eclipsealso: $g_reminder_receive_threshold = DEVELOPER;16:16
nuclear_eclipse$g_bug_view_page_fields and similar16:16
ToffeePopsfantastic16:16
ToffeePopsnuclear_eclipse: $g_view_page_columns - can that be tweaked via the 'manage columns' page in the interface, or will I need to edit config_defaults_inc.php?16:18
paulryes16:19
paulrnuclear_eclipse: need to have a discussion/plan at some point about whether we think github is a good/bad idea16:20
paulrprobably when dhx is around16:20
nuclear_eclipseToffeePops: you need to copy it to your config_inc.php and edit it there16:20
nuclear_eclipsepaulr: we've had mulitple discussions about it already; you're the only one on the team who has expressed any dislike for it16:21
paulrwell, dhx seemed to be going off it at weekend16:21
nuclear_eclipsewe had multiple discussions abotu it before I ever even sent the email to the dev list16:21
nuclear_eclipsedhx and daryn were both in agreement with me before I sent the email, and then both Victor and Giallu agreed with it on the mailing list16:22
paulr<dhx_m> I'd prefer to see us host the infrastructure ourselves16:23
ToffeePopsnuclear_eclipse: should that be config_inc.php or config_defaults_inc.php?16:23
paulr<dhx_m> but it'd be a lot of work to setup a distributed system16:23
giallupaulr, what's the issue with github?16:24
nuclear_eclipseToffeePops: config_inc.php -- you shouldn't be making changes directly in config_defaults_inc.php because it will get overwritten on updates16:24
ToffeePopscheers16:25
nuclear_eclipsegiallu: he just doesn't like github16:25
paulrit's more about the case of why16:25
gialluI mean, don't use it... git is decentralized16:25
giallu;)16:25
paulri've already said16:25
paulrI dont mind us using github16:25
gialluwhy is always a good question16:25
paulrif we point bug tracker at git.mantisbt.org as gitweb interface is nicer16:25
paulrwhich led me to wondering what point of is16:26
giallubut I think John explained properly the advantages in his mail16:26
nuclear_eclipsepaulr: like I've said before, it would be stupid and insane to have github be our primary repo, yet point our tracker at some random gitweb mirror instead...16:26
paulrthen in which case I'd rather not move16:27
nuclear_eclipseit doesn't make sense, and would be negating most of the benefits of using github as our primary collaboration point16:27
nuclear_eclipsegiallu: summary: paulr doesn't want to move to github because he doesn't like the way it looks and prefers gitweb instead16:27
paulrwell, more a case of16:28
paulrif we aren't gonna use the comments/issue functionality of github16:28
paulrand it's just going to be a central repro16:28
paulrto commit to16:28
paulrit seems kinda silly to change what aint broken16:28
nuclear_eclipsebut it won't be *just* a central repo16:28
nuclear_eclipsethe point is that we can use the collab features of github16:29
nuclear_eclipsetheir issue tracker is pitiful16:29
nuclear_eclipsentm of course we have our own16:29
paulrcollab features being?16:29
nuclear_eclipsegithub makes it super trivial to fork, track, and pull-request between community users16:29
giallutbh, I think not having to worry about administration is enough of a reason to move...16:30
paulrhow much admin do we have atm?16:30
paulror more how much time16:30
nuclear_eclipseif someone forks on github, commits a fix, and then does a pull-request, that pull-request can be sent to our developer discussion list, and either pull/push like normal, or we can integrate the bugfix directly through github's web interface16:30
paulrthose should really go as patches into our bugtracker though...16:31
nuclear_eclipsewell they can be16:31
gialluand again, I don't see how we need to argue about this more. If you don't like github, don't use it and keep the code on mantisforge or whatever16:31
nuclear_eclipsewhat's to say the person didn't also file a bug report?16:31
paulrgiallu: I plan to, will probably set up a bot to add a bugnote to closed issue reports linking to the mantisforge.org commit so I can click on gitweb links16:32
paulrif we move16:32
nuclear_eclipsepaulr: if you add bot to add bugnotes I will kill you16:32
nuclear_eclipsethe whole point of adding proper source control integration to mantis as a plugin was to *remove* all those bugnotes announcing commits16:33
paulractually, i'd probably edit the source control integration to allow multiple urls to repo16:34
paulror something ;p16:34
nuclear_eclipseyou really are insane16:34
nuclear_eclipseis it really that big of a deal to view commits on github instead of gitweb? they all show the same information16:35
paulrthey dont show the same information16:35
nuclear_eclipsetell me one thing that gitweb shows that github doesnt16:35
paulryou can diff between any two versions of the tree16:36
paulrso I can generate a diff of last 4 commits in one go for example16:37
nuclear_eclipsea) how often do you honestly do that, and b) github can do that too, it's just not on the same page16:37
paulra) quite often - tend to use that to review what's been commited16:37
paulrso once a week16:37
paulrb) how?16:37
paulrwe have a lot of flexibility atm on what we can do16:38
paulrwe lose some of that if we move everything to github16:39
paulrwhen we could keep the flexibility and allow github to mirror us16:39
paulrpeople can then fork, send a patch to bugtracker16:39
paulrdhx said something about not liking github's fixed-width viewer16:39
paulrbut i dunno what that was about specifically16:40
ToffeePopsnuclear_eclipse: sorry to bother you with all these simple requests ;-) I found $g_view_issues_page_columns and the comment above (maybe outdated) suggests one of the standard column names is "build (for product build)".But I tried adding16:40
nuclear_eclipseif that's all you want, why's it such a problem to continue mirroring on mantisforge?  that would let you view things, but still encourage everyone to use github's features16:40
paulrI'll be mirroring on mantisforge anyway16:40
paulrwill probably set up github to mirror mantisforge16:40
paulrrepo's16:40
paulrto act as a nice easy backup16:40
nuclear_eclipsebut paulr that's exactly my point, why would we use github as just a mirror? that doesn't make sense to me16:41
nuclear_eclipseif we make it the primary repo, it encourages people to use it; if it's just a mirror, it's almost useless16:42
paulrright for example16:42
nuclear_eclipseyou'll have it mirrored on mantisforge just like you always have... so I don't understand why you're so upset with this...16:42
paulrat the moment I run some automated rules on formatting etc (e.g. spaces for tabs)16:42
paulrit would be nice to be able to consider to run that as a post-commit hook16:43
nuclear_eclipsebut it would be insane to run that as a post-commit hook16:43
paulrnod16:43
nuclear_eclipsethat doesn't make sense16:43
paulrit's kinda an example though16:43
paulrit would probably less insane to add that as pre-commit or whatever hook16:43
paulrthen to let someone commit16:43
paulrthen revert the commit saying 'fix the code formatitng'16:44
paulrthen recommit16:44
paulror something equally silly16:44
nuclear_eclipseperhaps, but why do we really care in the first place?  if someone can't get the formatting right, why are we giving them push access to our repository?16:44
paulrI think what i'm saying is having moved away from sf.net with svn16:44
*** Joins: bigbluehat (~byoung@adsl-71-143-157.gsp.bellsouth.net)16:44
paulrto git hosted by ourselves16:44
ToffeePopsnuclear_eclipse: sorry to bother you with all these simple requests ;-) I found $g_view_issues_page_columns and the comment above (maybe outdated) suggests one of the standard column names is "build (for product build)".16:44
paulrto fix the fact that sf.net was starting to be rubbish16:45
ToffeePopsBut I tried adding "build" to the 'view issues columns' section of the 'Manage columns' screen but I get app error 2601 Field "view_issues" contains invalid field "build".16:45
ToffeePopsSo I guess I need to add it via the config_inc.php like you suggested.... or is the 'build' column no longer valid?16:45
paulrI'm not sure why we bothering to move16:45
paulrpeople can fork repo atm16:45
paulrwe don't want commenting on code/commits16:45
paulrnor the issue tracker16:45
paulrso that's knocking out the social-coding features16:46
nuclear_eclipsepaulr: a) because they can't fork from our primary mirror (mantisforge isn't obvious), and b) mantisforge has a very complex setup16:46
paulrthat would be the point to move in first place16:46
paulrb) mantisforge has a very complex setup --> re that16:46
*** Quits: fanno (~b3g@193.3.95.240) (Read error: Connection reset by peer)16:46
nuclear_eclipsewhy would we not want comments on code/commits??16:46
paulrthat I believe will be easier if I update it as the guy's now writtein a 'jailsetup' script16:46
paulrnuclear_eclipse: as we want feedback to go to our bugtracker...16:47
nuclear_eclipsepaulr: mantisforge is still complex because it requires a lot more setup steps than github, and doesn't have any obvious workflow16:47
paulrdare I ask what workflow github has?16:47
paulrI mean, for the most part, git's a command line app :)16:47
nuclear_eclipsewell, once you have an account, it's a single click to fork a repo16:48
nuclear_eclipsewith mantisforge, there's a very involved process to setting up a repo/fork16:48
paulrisn't it just add a ssh key?16:48
nuclear_eclipse(first you fork and need to specify an admin password, then you have to edit the fork to add your account with push access, assuming you've already set up your account properly)16:49
paulris that still the case in the latest code at http://repo.or.cz/ ?16:49
nuclear_eclipseand it's still not obvious that you can do any of that16:49
nuclear_eclipselastly, mantisforge still lacks the rest of the collaboration features that github has16:50
nuclear_eclipseie, you can't easily see what's changed between forks, and there's no way to automate pull requests, or integrate patches from forks16:50
nuclear_eclipseand the new version from repo.or.cz is even more confusing and complicated to fork from16:51
paulrreally?16:53
* paulr hasn't looked16:53
nuclear_eclipseit adds more silly fields, but still requires you to setup an admin password, and then go back through and add yourself to it after creation16:53
nuclear_eclipseit's a stupid way of doing things, IMO16:53
nuclear_eclipseand unrelated, they have a crappy anti-spam measure:16:54
nuclear_eclipseAnti-captcha - please16:54
nuclear_eclipseenter name of our nearest star16:54
nuclear_eclipseI don't know what the nearest star is, and ytf is that preventing me from forking your repository?16:54
paulrLOL16:54
paulrso workflow is still same?16:54
nuclear_eclipsebasically yes16:55
nuclear_eclipseanyways, I'm planning to make the move to Github official within the next few days after I finish updating and testing my SourceGithub plugin -- please continue mirroring the repo on git.mantisforge.org, but I will be having git.mantisbt.org redirect to the github repo, and changing the mantisbt.org tracker to point to the github repo for everything16:57
nuclear_eclipsedinner time for me17:01
paulrcan you have a chat to dhx/myself first?17:02
nuclear_eclipseI'm not sure what needs to chatted about... dhx agrees with moving to github afaik because he's not satisfied with any way of hosting it ourself that won't require a huge amount of sysadmin work17:03
nuclear_eclipsedaryn and victor both like github and want to move to it, and giallu is at least in passive agreement17:04
paulrbesides17:05
paulrwe need to plan when to move if we do move17:05
paulrotherwise you'll have mantisforge emailing out errors that the git repo is broken17:05
nuclear_eclipsewell, you could always turn off that notifier now, knowing that we'll be moving soon ;)17:06
paulranyway, as I said about 3-4 weeks ago now17:09
paulrduring end of july/august, plan to fix up mantisforge more17:10
paulrand finish automating stuff17:10
paulrhence dhx/myself looking at scripts to generate integrity files last 2 weeks17:10
ToffeePopsHmmm, updated $g_view_issues_page_columns in config_inc.php to include 'build' (which is still in our 'mantis_bug_table', cool), but it does not appear :(17:11
ToffeePopsDo we somehow have to add it to 'all available columns'?17:12
ToffeePopsAh, found it by looking at the php - $g_enable_product_build = ON;   :-)17:14
ToffeePopsNow we just have to get mantis to display the padlock icon (private issues) in the list view....17:16
*** Joins: fanno (~Morten@90.184.93.233)17:31
*** Quits: moto-moi (~hylke@cara.xs4all.nl) (Quit: Ex-Chat)18:01
*** Quits: rolfkleef (~rolf@cc1080790-a.hdb1.ov.home.nl) (Ping timeout: 240 seconds)18:50
*** Quits: paulr (~paul@cpc1-enfi9-0-0-cust389.hari.cable.virginmedia.com) ()19:04
*** Quits: giallu (~giallu@fedora/giallu) (Ping timeout: 260 seconds)19:29
*** Quits: scribe9343423 (~scribe934@static.96.23.63.178.clients.your-server.de) (Remote host closed the connection)19:59
*** Joins: scribe9343423 (~scribe934@static.96.23.63.178.clients.your-server.de)20:00
*** Quits: ToffeePops (~chatzilla@202.20.3.13) (Read error: Connection reset by peer)20:51
*** Joins: LinuxNewb66 (8b826042@gateway/web/freenode/ip.139.130.96.66)20:54
LinuxNewb66Hi, is it possible to use something like time based triggers in Mantis? eg, if a reported issue isn't assigned to someone within 60 minutes an email is generated?20:55
*** Quits: bigbluehat (~byoung@adsl-71-143-157.gsp.bellsouth.net) (Quit: bigbluehat)21:10
*** Quits: fanno (~Morten@90.184.93.233) (Read error: Connection reset by peer)22:10
*** Joins: |HaruAFK| (~haruka@p54ACF31B.dip.t-dialin.net)22:27
*** Quits: |Otter| (~haruka@p54ACCF0A.dip.t-dialin.net) (Ping timeout: 265 seconds)22:31

Generated by irclog2html.py 2.9.2 by Marius Gedminas - find it at mg.pov.lt!