| ../irclogs/#mantishelp.2010-07-05.log | ||
| --- scribe started --- | 00:00 | |
| ToffeePops | Hi, we recently updated to mantis 1.2... I noticed where we used to be able to send reminders to any user, now we can only send them to developers. | 03:56 |
|---|---|---|
| ToffeePops | I.e the list of people to send reminders to is only developers and higher. | 03:57 |
| ToffeePops | Has it been tightened up how you can send reminders to? | 03:57 |
| ToffeePops | s/how/who/ | 03:57 |
| ToffeePops | Or is this a new bit of config that I need to tweak? | 03:58 |
| LinuxLearner64 | Hi, 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? | 05:50 |
| vinvin | hi | 08:13 |
| vinvin | anyone reads the forum sometimes or is it a dead place? | 08:13 |
| vinvin | anyone tried to use captcha on a non-windows OS? | 08:17 |
| nuclear_eclipse | ToffeePops: it should be a configurable threshold IIRC | 14:22 |
| nuclear_eclipse | vinvin: I'm able to use captcha on my linux host | 14:22 |
| nuclear_eclipse | vinvin: I had to set the following values in my config_inc.php: | 14:23 |
| nuclear_eclipse | $g_system_font_folder = '/usr/share/fonts/truetype/ttf-dejavu/'; | 14:23 |
| nuclear_eclipse | $g_font_per_captcha = 'DejaVu.ttf'; | 14:23 |
| arslanali | mantis is down http://www.mantisbt.org/wiki/doku.php/mantisbt:instantmantis_faq?s=smtp | 14:38 |
| arslanali | Database connection failed. Error received from database was #1040: Too many connections. | 14:38 |
| arslanali | my emails are not working with mantis | 14:38 |
| arslanali | can anyone help me in emails using mantis | 14:40 |
| vinvin | nuclear_eclipse: thanks for the answer. That's what I did, but it has no effect on the signup page | 16:27 |
| vinvin | nuclear_eclipse: do you have debian? What package did you install for GD? | 16:31 |
| vinvin | ok nevermind... I did not find the right package | 16:40 |
| skayser | greetings | 17:30 |
| skayser | something wrong with mantisbt.org? | 17:30 |
| skayser | connection times out here | 17:30 |
| nuclear_eclipse | skayser: yeah, I'm looking into it | 17:31 |
| nuclear_eclipse | pushing a hard reboot, should be back up in a few minutes | 17:32 |
| skayser | thanks! | 17:32 |
| nuclear_eclipse | np | 17:32 |
| paulr | nuclear_eclipse: moo | 18:52 |
| nuclear_eclipse | hi paulr | 18:56 |
| paulr | dhx/myself had a good play at weekend | 18:57 |
| paulr | you cna't do sunday's can you ? | 18:58 |
| nuclear_eclipse | depends on what's going on | 18:59 |
| paulr | well, we came up with a script to build the integrity data @ weekend | 19:00 |
| paulr | however started having a debate about how far back to go | 19:00 |
| paulr | nuclear_eclipse: wow, the problem with git is if people dont use sensible heads :P | 19:08 |
| paulr | 3 hours wasted ;/ | 19:09 |
| nuclear_eclipse | paulr: I'm not even sure what you're talking about atm... =\ | 19:13 |
| paulr | i'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 :) | 19:22 |
| paulr | my question: should I ignore the main git ? answer: yes/maybe | 19:23 |
| nuclear_eclipse | ah | 19:23 |
| paulr | anyway | 19:25 |
| paulr | <paulr> well, we came up with a script to build the integrity data @ weekend | 19:25 |
| paulr | <paulr> however started having a debate about how far back to go | 19:25 |
| paulr | any thoughts? | 19:25 |
| nuclear_eclipse | what integrity data? | 19:26 |
| nuclear_eclipse | I'm completely lost | 19:26 |
| paulr | for check.php | 19:26 |
| nuclear_eclipse | ah | 19:28 |
| nuclear_eclipse | that | 19:28 |
| paulr | if we are looking for old files | 19:38 |
| paulr | we probably really need to go back to day 0 | 19:38 |
| nuclear_eclipse | perhaps | 19:40 |
| nuclear_eclipse | or we could just have some way of saying "if it doesn't match, it must be customized or old" | 19:40 |
| paulr | well, could be nice to detect customised vs old | 19:43 |
| nuclear_eclipse | true | 19:47 |
| nuclear_eclipse | but is it really worthwhile do know "all" old revisions of files? | 19:47 |
| ToffeePops | nuclear_eclipse: thanks for the answer some hours ago, will take a look | 19:48 |
| paulr | not sure | 19:49 |
| nuclear_eclipse | ToffeePops: yw | 19:49 |
| paulr | it's useful in the sense that if we say we store all old releases | 19:49 |
| paulr | i.e. tags | 19:50 |
| paulr | it's probably not that much more to store commits | 19:50 |
| paulr | I think I summed it up to dhx with | 19:50 |
| paulr | it's a file that lives in tarball that sf.net host for free | 19:50 |
| ToffeePops | nuclear_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'... | 20:02 |
| ToffeePops | There 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? | 20:03 |
| paulr | i'm also wondering if you can get from a file blob to a commit blob | 20:03 |
| paulr | ToffeePops: there's probably a config value | 20:03 |
| KevBurnsJr | what is the default administrator password for mantisbt? | 20:04 |
| ToffeePops | paulr: might that be in a config file rather than a setting found via the interface? | 20:04 |
| paulr | KevBurnsJr: root/admin | 20:05 |
| paulr | ToffeePops: probably | 20:05 |
| KevBurnsJr | root, thankx | 20:05 |
| ToffeePops | any idea where to start looking? I do admin via the interface but not familiar with the on-disk config files... | 20:06 |
| ToffeePops | paulr: | 20:07 |
| paulr | nope | 20:07 |
| paulr | config_defaults_inc.php | 20:07 |
| paulr | it's a nice long read :) | 20:07 |
| ToffeePops | Yeah I have seen that one ;-) | 20:08 |
| ToffeePops | paulr: 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. | 20:09 |
| ToffeePops | Any way to change that? | 20:10 |
| ToffeePops | We 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. | 20:11 |
| ToffeePops | What concerns me more is that all the old values seem to have disappeared :( | 20:12 |
| nuclear_eclipse | ToffeePops: there's a separate field for product build that's no longer displayed by default | 20:15 |
| nuclear_eclipse | you can edit $g_view_page_columns iirc to add that back in | 20:15 |
| ToffeePops | nuclear_eclipse: awesome! | 20:16 |
| nuclear_eclipse | also: $g_reminder_receive_threshold = DEVELOPER; | 20:16 |
| nuclear_eclipse | $g_bug_view_page_fields and similar | 20:16 |
| ToffeePops | fantastic | 20:16 |
| ToffeePops | nuclear_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? | 20:19 |
| paulr | yes | 20:19 |
| paulr | nuclear_eclipse: need to have a discussion/plan at some point about whether we think github is a good/bad idea | 20:20 |
| paulr | probably when dhx is around | 20:20 |
| nuclear_eclipse | ToffeePops: you need to copy it to your config_inc.php and edit it there | 20:20 |
| nuclear_eclipse | paulr: we've had mulitple discussions about it already; you're the only one on the team who has expressed any dislike for it | 20:21 |
| paulr | well, dhx seemed to be going off it at weekend | 20:21 |
| nuclear_eclipse | we had multiple discussions abotu it before I ever even sent the email to the dev list | 20:21 |
| nuclear_eclipse | dhx 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 list | 20:22 |
| paulr | <dhx_m> I'd prefer to see us host the infrastructure ourselves | 20:23 |
| ToffeePops | nuclear_eclipse: should that be config_inc.php or config_defaults_inc.php? | 20:23 |
| paulr | <dhx_m> but it'd be a lot of work to setup a distributed system | 20:24 |
| giallu | paulr, what's the issue with github? | 20:24 |
| nuclear_eclipse | ToffeePops: config_inc.php -- you shouldn't be making changes directly in config_defaults_inc.php because it will get overwritten on updates | 20:25 |
| ToffeePops | cheers | 20:25 |
| nuclear_eclipse | giallu: he just doesn't like github | 20:25 |
| paulr | it's more about the case of why | 20:25 |
| giallu | I mean, don't use it... git is decentralized | 20:25 |
| giallu | ;) | 20:25 |
| paulr | i've already said | 20:25 |
| paulr | I dont mind us using github | 20:25 |
| giallu | why is always a good question | 20:25 |
| paulr | if we point bug tracker at git.mantisbt.org as gitweb interface is nicer | 20:25 |
| paulr | which led me to wondering what point of is | 20:26 |
| giallu | but I think John explained properly the advantages in his mail | 20:26 |
| nuclear_eclipse | paulr: 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... | 20:27 |
| paulr | then in which case I'd rather not move | 20:27 |
| nuclear_eclipse | it doesn't make sense, and would be negating most of the benefits of using github as our primary collaboration point | 20:27 |
| nuclear_eclipse | giallu: summary: paulr doesn't want to move to github because he doesn't like the way it looks and prefers gitweb instead | 20:28 |
| paulr | well, more a case of | 20:28 |
| paulr | if we aren't gonna use the comments/issue functionality of github | 20:28 |
| paulr | and it's just going to be a central repro | 20:28 |
| paulr | to commit to | 20:28 |
| paulr | it seems kinda silly to change what aint broken | 20:29 |
| nuclear_eclipse | but it won't be *just* a central repo | 20:29 |
| nuclear_eclipse | the point is that we can use the collab features of github | 20:29 |
| nuclear_eclipse | their issue tracker is pitiful | 20:29 |
| nuclear_eclipse | ntm of course we have our own | 20:29 |
| paulr | collab features being? | 20:29 |
| nuclear_eclipse | github makes it super trivial to fork, track, and pull-request between community users | 20:29 |
| giallu | tbh, I think not having to worry about administration is enough of a reason to move... | 20:30 |
| paulr | how much admin do we have atm? | 20:30 |
| paulr | or more how much time | 20:30 |
| nuclear_eclipse | if 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 interface | 20:30 |
| paulr | those should really go as patches into our bugtracker though... | 20:31 |
| nuclear_eclipse | well they can be | 20:31 |
| giallu | and 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 whatever | 20:31 |
| nuclear_eclipse | what's to say the person didn't also file a bug report? | 20:31 |
| paulr | giallu: 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 links | 20:32 |
| paulr | if we move | 20:32 |
| nuclear_eclipse | paulr: if you add bot to add bugnotes I will kill you | 20:32 |
| nuclear_eclipse | the whole point of adding proper source control integration to mantis as a plugin was to *remove* all those bugnotes announcing commits | 20:33 |
| paulr | actually, i'd probably edit the source control integration to allow multiple urls to repo | 20:34 |
| paulr | or something ;p | 20:34 |
| nuclear_eclipse | you really are insane | 20:34 |
| nuclear_eclipse | is it really that big of a deal to view commits on github instead of gitweb? they all show the same information | 20:35 |
| paulr | they dont show the same information | 20:35 |
| nuclear_eclipse | tell me one thing that gitweb shows that github doesnt | 20:35 |
| paulr | you can diff between any two versions of the tree | 20:36 |
| paulr | so I can generate a diff of last 4 commits in one go for example | 20:37 |
| nuclear_eclipse | a) how often do you honestly do that, and b) github can do that too, it's just not on the same page | 20:37 |
| paulr | a) quite often - tend to use that to review what's been commited | 20:37 |
| paulr | so once a week | 20:37 |
| paulr | b) how? | 20:38 |
| paulr | we have a lot of flexibility atm on what we can do | 20:39 |
| paulr | we lose some of that if we move everything to github | 20:39 |
| paulr | when we could keep the flexibility and allow github to mirror us | 20:39 |
| paulr | people can then fork, send a patch to bugtracker | 20:39 |
| paulr | dhx said something about not liking github's fixed-width viewer | 20:40 |
| paulr | but i dunno what that was about specifically | 20:40 |
| ToffeePops | nuclear_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 adding | 20:40 |
| nuclear_eclipse | if 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 features | 20:40 |
| paulr | I'll be mirroring on mantisforge anyway | 20:40 |
| paulr | will probably set up github to mirror mantisforge | 20:40 |
| paulr | repo's | 20:40 |
| paulr | to act as a nice easy backup | 20:41 |
| nuclear_eclipse | but paulr that's exactly my point, why would we use github as just a mirror? that doesn't make sense to me | 20:41 |
| nuclear_eclipse | if we make it the primary repo, it encourages people to use it; if it's just a mirror, it's almost useless | 20:42 |
| paulr | right for example | 20:42 |
| nuclear_eclipse | you'll have it mirrored on mantisforge just like you always have... so I don't understand why you're so upset with this... | 20:42 |
| paulr | at the moment I run some automated rules on formatting etc (e.g. spaces for tabs) | 20:43 |
| paulr | it would be nice to be able to consider to run that as a post-commit hook | 20:43 |
| nuclear_eclipse | but it would be insane to run that as a post-commit hook | 20:43 |
| paulr | nod | 20:43 |
| nuclear_eclipse | that doesn't make sense | 20:43 |
| paulr | it's kinda an example though | 20:43 |
| paulr | it would probably less insane to add that as pre-commit or whatever hook | 20:44 |
| paulr | then to let someone commit | 20:44 |
| paulr | then revert the commit saying 'fix the code formatitng' | 20:44 |
| paulr | then recommit | 20:44 |
| paulr | or something equally silly | 20:44 |
| nuclear_eclipse | perhaps, 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? | 20:44 |
| paulr | I think what i'm saying is having moved away from sf.net with svn | 20:44 |
| paulr | to git hosted by ourselves | 20:44 |
| ToffeePops | nuclear_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)". | 20:45 |
| paulr | to fix the fact that sf.net was starting to be rubbish | 20:45 |
| ToffeePops | But 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". | 20:45 |
| ToffeePops | So I guess I need to add it via the config_inc.php like you suggested.... or is the 'build' column no longer valid? | 20:45 |
| paulr | I'm not sure why we bothering to move | 20:45 |
| paulr | people can fork repo atm | 20:45 |
| paulr | we don't want commenting on code/commits | 20:45 |
| paulr | nor the issue tracker | 20:45 |
| paulr | so that's knocking out the social-coding features | 20:46 |
| nuclear_eclipse | paulr: a) because they can't fork from our primary mirror (mantisforge isn't obvious), and b) mantisforge has a very complex setup | 20:46 |
| paulr | that would be the point to move in first place | 20:46 |
| paulr | b) mantisforge has a very complex setup --> re that | 20:46 |
| nuclear_eclipse | why would we not want comments on code/commits?? | 20:46 |
| paulr | that I believe will be easier if I update it as the guy's now writtein a 'jailsetup' script | 20:46 |
| paulr | nuclear_eclipse: as we want feedback to go to our bugtracker... | 20:47 |
| nuclear_eclipse | paulr: mantisforge is still complex because it requires a lot more setup steps than github, and doesn't have any obvious workflow | 20:47 |
| paulr | dare I ask what workflow github has? | 20:47 |
| paulr | I mean, for the most part, git's a command line app :) | 20:48 |
| nuclear_eclipse | well, once you have an account, it's a single click to fork a repo | 20:48 |
| nuclear_eclipse | with mantisforge, there's a very involved process to setting up a repo/fork | 20:48 |
| paulr | isn't it just add a ssh key? | 20: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) | 20:49 |
| paulr | is that still the case in the latest code at http://repo.or.cz/ ? | 20:49 |
| nuclear_eclipse | and it's still not obvious that you can do any of that | 20:49 |
| nuclear_eclipse | lastly, mantisforge still lacks the rest of the collaboration features that github has | 20:50 |
| nuclear_eclipse | ie, you can't easily see what's changed between forks, and there's no way to automate pull requests, or integrate patches from forks | 20:50 |
| nuclear_eclipse | and the new version from repo.or.cz is even more confusing and complicated to fork from | 20:51 |
| paulr | really? | 20:53 |
| * paulr hasn't looked | 20:53 | |
| nuclear_eclipse | it adds more silly fields, but still requires you to setup an admin password, and then go back through and add yourself to it after creation | 20:53 |
| nuclear_eclipse | it's a stupid way of doing things, IMO | 20:53 |
| nuclear_eclipse | and unrelated, they have a crappy anti-spam measure: | 20:54 |
| nuclear_eclipse | Anti-captcha - please | 20:54 |
| nuclear_eclipse | enter name of our nearest star | 20:54 |
| nuclear_eclipse | I don't know what the nearest star is, and ytf is that preventing me from forking your repository? | 20:54 |
| paulr | LOL | 20:55 |
| paulr | so workflow is still same? | 20:55 |
| nuclear_eclipse | basically yes | 20:55 |
| nuclear_eclipse | anyways, 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 everything | 20:57 |
| nuclear_eclipse | dinner time for me | 21:01 |
| paulr | can you have a chat to dhx/myself first? | 21:02 |
| nuclear_eclipse | I'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 work | 21:03 |
| nuclear_eclipse | daryn and victor both like github and want to move to it, and giallu is at least in passive agreement | 21:04 |
| paulr | besides | 21:05 |
| paulr | we need to plan when to move if we do move | 21:05 |
| paulr | otherwise you'll have mantisforge emailing out errors that the git repo is broken | 21:06 |
| nuclear_eclipse | well, you could always turn off that notifier now, knowing that we'll be moving soon ;) | 21:06 |
| paulr | anyway, as I said about 3-4 weeks ago now | 21:09 |
| paulr | during end of july/august, plan to fix up mantisforge more | 21:10 |
| paulr | and finish automating stuff | 21:10 |
| paulr | hence dhx/myself looking at scripts to generate integrity files last 2 weeks | 21:10 |
| ToffeePops | Hmmm, 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 :( | 21:11 |
| ToffeePops | Do we somehow have to add it to 'all available columns'? | 21:12 |
| ToffeePops | Ah, found it by looking at the php - $g_enable_product_build = ON; :-) | 21:14 |
| ToffeePops | Now we just have to get mantis to display the padlock icon (private issues) in the list view.... | 21:17 |
Generated by irclog2html.py