| ../irclogs/#mantishelp.2010-07-21.log | ||
| --- scribe started --- | 00:00 | |
| alemayo | Hi @all! I am just registering a new plugin that dawit made .... | 07:09 |
|---|---|---|
| alemayo | http://git.mantisforge.org/w/LDAPAutocomplete.git | 07:12 |
| alemayo | were is paul ?? | 08:11 |
| alemayo | pushing to git.mantisforge.org does not work for us :( | 08:11 |
| alemayo | can anybody reach port 22 at git.mantisforge.org ??? | 08:11 |
| kirillka | alemayo: hi. move projects to github.com | 09:34 |
| alemayo | kirillka: how ? | 09:39 |
| alemayo | git.mantisforge.org will be discontinued ? | 09:39 |
| kirillka | alemayo: register own on site. register project on site. You give url for pushing | 09:40 |
| kirillka | alemayo: yes. | 09:40 |
| kirillka | alemayo: next in local project write git remote add gh <url for pushing> | 09:40 |
| kirillka | alemayo: git push gh master | 09:40 |
| alemayo | and then register it as a mirror on git.mantisforge ? | 09:43 |
| kirillka | alemayo: for future all plugins and mirror of mantisbt will be on github. git.mantisforge.org die. | 09:44 |
| kirillka | alemayo: don't forget read http://help.github.com/ | 09:44 |
| alemayo | how do you plan to collect the plugins ?? is there already a wiki page or something ? | 09:47 |
| alemayo | to add it to ? | 09:47 |
| alemayo | on github nobody would find it | 09:47 |
| kirillka | alemayo: I think all unite to organization | 09:50 |
| jack_spratt | Hi, I'm about to install mantis, but ill need to move it to another server later. Will this be possible/easy? just copy database? | 11:42 |
| nuclear_eclipse | jack_spratt: just copy the database and files to the new machine, and update the config_inc.php with the new database information, and other chances you need to make for sending mail, urls, etc | 11:44 |
| jack_spratt | nuclear_eclipse: have you done this successfully before? | 11:45 |
| nuclear_eclipse | yes | 11:46 |
| nuclear_eclipse | just make sure you keep backups just in case :) | 11:46 |
| kirillka | nuclear_eclipse: mo | 12:11 |
| jack_spratt | nuclear_eclipse: thanks very much | 12:32 |
| nuclear_eclipse | hi kirillka | 12:51 |
| kirillka | nuclear_eclipse: I right answer for alemayo? | 12:51 |
| nuclear_eclipse | well, I don't think mantisforge is going away :P | 12:53 |
| kirillka | not mantisforge.org, I talk about git.mantisforge.org | 12:54 |
| nuclear_eclipse | but it is very frustrating that paul keeps having issues with maintaining it... | 12:54 |
| nuclear_eclipse | kirillka: nothing has been decided for sure yet.. =\ | 12:54 |
| kirillka | bad.. I talk alemayo not correct information :( | 12:55 |
| nuclear_eclipse | no worries | 12:55 |
| jack_spratt | I need to remove some of the default fields, like reproducability and severity, what is the best way to do this? via plugin? | 13:22 |
| nuclear_eclipse | jack_spratt: if you're using version 1.2.x, there are some configuration options that you can modify that select what fields are visible on the various pages | 13:23 |
| jack_spratt | nuclear_eclipse: I am, so that is in config_inc.php? | 13:24 |
| nuclear_eclipse | you can copy the values from config_defaults_inc.php into your config_inc.php | 13:25 |
| nuclear_eclipse | look for $g_bug_report_page_fields | 13:25 |
| nuclear_eclipse | the rest are below that | 13:25 |
| jack_spratt | nuclear_eclipse: thanks! thats great | 13:27 |
| nuclear_eclipse | you're welcome | 13:27 |
| Shakra | Does anyone know if there are any problems with changing status on a bug in a custom workflow? | 17:03 |
| Shakra | In my custom workflow, I have several "resolved" statuses. If I try to change status of a bug to any of them, it always changes the bug to only to the $g_bug_resolved_status_threshold. It won't let me change to any of the other ones in 1.2.1. | 17:07 |
| nuclear_eclipse | Shakra: I believe that's a bug that dhx_m is in the middle of trying to resolve... | 17:10 |
| Shakra | Ouch. I just noticed that it sent an email that said that it was put in a completely different status - neither $g_bug_resolved_status_threshold nor the status I had picked when I changed status. | 17:13 |
| Shakra | Are there any workarounds for now? | 17:15 |
| nuclear_eclipse | I'm not sure, I haven't seen the issue myself, sorry | 17:16 |
| Shakra | OK...thanks for responding anyway :) | 17:17 |
| nuclear_eclipse | you're welcome | 17:18 |
| Shakra | BTW...the patch you had given me for your Source Integration auto-resolving issues even when it wasn't supposed to...works. | 17:18 |
| nuclear_eclipse | awesome | 17:22 |
| nuclear_eclipse | I've got that sitting on my to-do list :P | 17:22 |
| * paulr pokes dhx_m and nuclear_eclipse | 18:21 | |
| nuclear_eclipse | hi paulr | 18:21 |
| paulr | seen dhx? | 18:21 |
| nuclear_eclipse | paulr: fix mantisforge | 18:21 |
| paulr | hmm? | 18:21 |
| nuclear_eclipse | jreese@dyson ~ ยป ssh git.mantisforge.org | 18:22 |
| nuclear_eclipse | ssh: connect to host git.mantisforge.org port 22: Connection refused | 18:22 |
| nuclear_eclipse | seriously, this is why we're wanting to move away from self-hosted solutions; it's way too easy for things to go down without anyone around to fix it | 18:22 |
| paulr | root@mantisforge:/# crontab -l | 18:22 |
| paulr | # m h dom mon dow command | 18:22 |
| paulr | */1 * * * * /home/repo/repomgr/fixupcheck.sh | 18:22 |
| paulr | @reboot /root/sshd.sh | 18:22 |
| foobot | paulr: Error: "reboot" is not a valid command. | 18:22 |
| paulr | it's supposed to run on reboot ;/ | 18:23 |
| nuclear_eclipse | why don't you just create a proper init.d script? | 18:23 |
| nuclear_eclipse | it's a lot better and more reliable than a crontab with @reboot | 18:24 |
| paulr | i'd kinda figured that would work... | 18:24 |
| paulr | nuclear_eclipse: you any good with java? :P | 19:42 |
| nuclear_eclipse | you keep asking me this... | 19:44 |
| nuclear_eclipse | what is it this time? | 19:44 |
| * daryn is good with java...preferably Sumatra dark roast... | 19:47 | |
| paulr | nuclear_eclipse: i'm still stuck on the same question :P | 19:48 |
| paulr | heh | 19:48 |
| nuclear_eclipse | paulr: I don't even remember what the question was | 19:49 |
| dhx_m | @Shakra (not here, but for the purpose of people listening in): that should be fixed in the latest git checkout (1.3.x branch) with my new bug_update.php | 22:03 |
| foobot | dhx_m: Error: "Shakra" is not a valid command. | 22:03 |
Generated by irclog2html.py