| *** Joins: nuclear_eclipse (~jreese@leetcode.net) | 01:11 | |
| *** Joins: davidinc (~davidinc@213.55.100.134) | 01:18 | |
| *** Joins: nuclear_eclipse (~jreese@leetcode.net) | 01:35 | |
| *** Quits: davidinc (~davidinc@213.55.100.134) (Quit: #mantishelp) | 01:43 | |
| *** Joins: davidinc (~davidinc@213.55.100.134) | 01:44 | |
| *** Quits: roentgen (~arthur@miranda/user/roentgen) (Remote host closed the connection) | 01:52 | |
| *** Joins: giallu (~giallu@88-149-142-233.dynamic.ngi.it) | 02:37 | |
| *** Quits: giallu (~giallu@88-149-142-233.dynamic.ngi.it) (Changing host) | 02:37 | |
| *** Joins: giallu (~giallu@fedora/giallu) | 02:37 | |
| *** Quits: siebrand (~beis@sm.xs4all.nl) () | 02:55 | |
| *** Quits: rolfkleef (~rolf@urtica.xs4all.nl) (Read error: Connection reset by peer) | 03:29 | |
| *** Joins: rolfkleef (~rolf@urtica.xs4all.nl) | 03:29 | |
| *** Quits: rolfkleef (~rolf@urtica.xs4all.nl) (Ping timeout: 252 seconds) | 03:35 | |
| *** Joins: Cupertino (~Cupez@unaffiliated/cupertino) | 03:35 | |
| *** Quits: tavasti (~tavasti@ov1.tavasti.fi) (Quit: tavasti) | 03:41 | |
| *** Joins: tavasti (~tavasti@ov1.tavasti.fi) | 03:44 | |
| *** Joins: Rixie (~Rixie@0x4dd7390e.adsl.cybercity.dk) | 03:49 | |
| *** Joins: Al_Chapone (~chatzilla@85-168-204-15.rev.numericable.fr) | 04:38 | |
| *** Joins: moto-moi (~hylke@2001:888:13e4:0:21f:e2ff:fe0c:ce28) | 06:13 | |
| *** Joins: istvanb (d917e473@gateway/web/freenode/ip.217.23.228.115) | 06:18 | |
| istvanb | hi! | 06:18 |
|---|---|---|
| istvanb | Is it possible to archive the mantis mysql database by copy the \mysql\data folder to a safe location? | 06:19 |
| istvanb | I know its not preferred, I would use the mysqldump command, but for other reasons I need to know this | 06:19 |
| *** Quits: Al_Chapone (~chatzilla@85-168-204-15.rev.numericable.fr) (Ping timeout: 240 seconds) | 06:43 | |
| istvanb | dhx1 | 06:48 |
| istvanb | nuclear_eclipse | 06:48 |
| istvanb | any guess? | 06:48 |
| dhx1 | istvanb: it's not recommended by any means, but I think it's possible | 06:50 |
| dhx1 | istvanb: you may encounter issues if you move the data folder to a different server or to a different version of MySQL | 06:50 |
| istvanb | yeah... our IT is a bunch of whining girls | 06:50 |
| dhx1 | Google it to find out | 06:50 |
| istvanb | they dont want to run a script | 06:50 |
| dhx1 | it is *MUCH* easier to dump the database in an .sql file and import it | 06:50 |
| dhx1 | there is even a UI for it... | 06:51 |
| istvanb | they what to archive folders only | 06:51 |
| dhx1 | ah, for backups? | 06:51 |
| istvanb | yeah | 06:51 |
| dhx1 | yeah it should be ok | 06:51 |
| istvanb | sweet | 06:51 |
| dhx1 | just expect it to be a minor pain in the ass to restore :p | 06:51 |
| istvanb | well, have to shut down the sqlserver then overwrite the files and then restart the server | 06:52 |
| istvanb | maybe restart the physical box as well | 06:52 |
| istvanb | but its OK, if this makes them happy, then do it :P | 06:52 |
| istvanb | thanks a lot man! | 06:53 |
| dhx1 | np | 07:00 |
| *** Quits: istvanb (d917e473@gateway/web/freenode/ip.217.23.228.115) (Quit: Page closed) | 07:06 | |
| *** Joins: istvanb (d917e473@gateway/web/freenode/ip.217.23.228.115) | 07:09 | |
| istvanb | actually there is another question as well | 07:10 |
| istvanb | is is possible to make it impossible for the users to assign an issue to the administrator? | 07:10 |
| istvanb | I know mantis defines a minimum level of credentials, but for me its a little bit inconvenient that the users can assign issues to the admin | 07:11 |
| dhx1 | not yet | 07:13 |
| dhx1 | you'd have to hardcode it into the source code | 07:13 |
| dhx1 | (and there would be multiple places in the code you'd need to update) | 07:13 |
| agronholm | I didn't receive a reply for this yesterday, so I'm asking again | 07:47 |
| agronholm | I can't access one of the issues in my bug tracker | 07:47 |
| agronholm | Application error #401 -- database returned error #-1: ERROR: invalid input syntax for integer: "" | 07:47 |
| agronholm | the query was: SELECT * FROM mantis_bug_revision_table WHERE id=? | 07:47 |
| agronholm | I had upgraded from mantis 1.1.x to 1.2.x | 07:48 |
| agronholm | what can I do to get this issue working, or if that's not possible, how should I go about disposing of it? | 07:48 |
| dhx1 | I'd need more information in the form of a backtrace | 07:51 |
| dhx1 | to work out where in the code this error was occurring | 07:51 |
| dhx1 | please read the documentation for information on how to turn on maximum error logging verbosity in MantisBT | 07:52 |
| dhx1 | it could be a "glitch" in your old 1.1.x database | 07:52 |
| dhx1 | it could be a problem with your upgrade (did you do a copy-over-the-top upgrade?) | 07:52 |
| dhx1 | (note: make sure you upgrade by backing up the old MantisBT directory, remove it, extract the latest version, redo the configuration file) | 07:53 |
| dhx1 | on the configuration file, it is vastly different from 1.1.x to 1.2.x and thus needs special attention | 07:53 |
| dhx1 | *vastly = many options removed, added or changed... the format is the same though | 07:54 |
| istvanb | dhx1: thanks! | 07:56 |
| *** Quits: istvanb (d917e473@gateway/web/freenode/ip.217.23.228.115) (Ping timeout: 265 seconds) | 08:10 | |
| agronholm | dhx1: ok, I'll read the docs on that | 08:12 |
| agronholm | dhx1: should it be in the administration guide? | 08:14 |
| dhx1 | agronholm: just add the following to the bottom of your config_inc.php file: | 08:20 |
| dhx1 | $g_show_detailed_errors = ON; | 08:20 |
| dhx1 | $g_display_errors = array(E_WARNING => 'halt', | 08:20 |
| dhx1 | E_NOTICE => 'halt', | 08:20 |
| dhx1 | E_USER_ERROR => 'halt', | 08:20 |
| dhx1 | E_USER_WARNING => 'halt', | 08:20 |
| dhx1 | E_USER_NOTICE => 'halt', | 08:20 |
| dhx1 | E_ALL => 'halt'); | 08:20 |
| dhx1 | perhaps also add: | 08:20 |
| dhx1 | $g_show_queries_list = ON; | 08:21 |
| *** Quits: mellen (~thansen@x1-6-00-22-02-00-0c-40.k253.webspeed.dk) (Ping timeout: 250 seconds) | 08:21 | |
| agronholm | dhx1: http://paradoxx.nextday.fi/~alex/mantiserror.html | 08:24 |
| dhx1 | I see | 08:28 |
| *** Joins: mellen (~thansen@x1-6-00-22-02-00-0c-40.k253.webspeed.dk) | 08:29 | |
| dhx1 | agronholm: inside core/history_api.php find 4 instances of: | 08:29 |
| dhx1 | if ( $p_linkify && bug_revision_exists( $p_new_value ) ) { | 08:30 |
| dhx1 | inside the history_localize_item(...) function | 08:30 |
| dhx1 | replace those 4 lines with: | 08:30 |
| dhx1 | if ( $p_linkify && bug_revision_exists( (int)$p_new_value ) ) { | 08:30 |
| dhx1 | ie. add (int) typecast before $p_new_value | 08:30 |
| dhx1 | agronholm: I think you have found a legitimate bug by the looks of things | 08:31 |
| agronholm | I see | 08:31 |
| agronholm | trying | 08:31 |
| agronholm | dhx1: works now -- I can access the issue | 08:32 |
| agronholm | thanks | 08:32 |
| dhx1 | agronholm: thanks, I'll add it to my list of things to fix :) | 08:35 |
| dhx1 | agronholm: don't forget to turn off verbose logging once you've done debugging :) | 08:35 |
| agronholm | yup | 08:35 |
| dhx1 | agronholm: did you file a bug at mantisbt.org/bugs for this? | 08:35 |
| agronholm | no | 08:35 |
| dhx1 | ok I'll do it :) | 08:36 |
| dhx1 | agronholm: monitor bug #12513 for updates on the official fix | 08:40 |
| agronholm | ok | 08:40 |
| dhx1 | thanks for reporting the issue! | 08:41 |
| dhx1 | (and for being patient for a response in here too) | 08:41 |
| *** Quits: thraxisp (~thraxisp@24.139.16.154) (Read error: Connection reset by peer) | 08:43 | |
| Cupertino | Hi | 08:45 |
| Cupertino | Is it easy to move mantis to another server? | 08:45 |
| agronholm | yes | 08:45 |
| Cupertino | and while doing that upgrade it aswell? | 08:45 |
| *** Joins: Al_Chapone (~chatzilla@85-168-204-15.rev.numericable.fr) | 08:53 | |
| *** Joins: siebrand (~beis@sm.xs4all.nl) | 09:05 | |
| *** Quits: Al_Chapone (~chatzilla@85-168-204-15.rev.numericable.fr) (Remote host closed the connection) | 09:08 | |
| *** Quits: micahg (~micah@ubuntu/member/micahg) (Ping timeout: 265 seconds) | 09:12 | |
| *** Joins: daryn (~daryn@h158.249.190.173.static.ip.windstream.net) | 09:14 | |
| *** Joins: thraxisp (~thraxisp@24.139.16.154) | 09:37 | |
| Cupertino | yay | 10:03 |
| Cupertino | :) | 10:03 |
| Cupertino | some other time i guess | 10:03 |
| *** Quits: siebrand (~beis@sm.xs4all.nl) (Read error: Connection reset by peer) | 10:06 | |
| *** Joins: siebrand (~beis@sm.xs4all.nl) | 10:06 | |
| nuclear_eclipse | Cupertino: yes, an long as you follow the standard upgrade instructions in mantisbt/doc/INSTALL, you should be fine by prefixing that with "dump database from old server and import database to new server" | 10:09 |
| Cupertino | Is still the hard way needed to upgrade? | 10:15 |
| nuclear_eclipse | define "the hard way" :P | 10:16 |
| Cupertino | manual stuff :p | 10:16 |
| nuclear_eclipse | http://git.mantisbt.org/?p=mantisbt.git;a=blob;f=doc/INSTALL;h=dd86049f6f4bc6dcd55eb893939430c74f4c4cde;hb=75159eea2dbcd2be179a6dad4d6aef3e8e2c13b6 | 10:16 |
| Cupertino | looks easy | 10:17 |
| Cupertino | :) | 10:17 |
| Cupertino | ill save it | 10:17 |
| Cupertino | So the upgraded version comes in a new folder? | 10:19 |
| nuclear_eclipse | it doesn't matter if it's the same name as the old installation, just that you don't extract 1.2.x on top of an existing 1.1.x folder because that is known to cause some grief | 10:20 |
| Cupertino | I am on 1.2.0 | 10:21 |
| nuclear_eclipse | it's still best to use a fresh copy of mantis with config copied into it than to extract on top of an old version | 10:22 |
| *** Quits: siebrand (~beis@sm.xs4all.nl) () | 10:38 | |
| *** Quits: Rixie (~Rixie@0x4dd7390e.adsl.cybercity.dk) (Quit: Rixie) | 10:52 | |
| *** Parts: agronholm (~demigod@nblzone-211-37.nblnetworks.fi) | 11:18 | |
| *** Quits: davidinc (~davidinc@213.55.100.134) (Ping timeout: 255 seconds) | 11:50 | |
| Cupertino | tnx | 11:55 |
| *** Quits: Cupertino (~Cupez@unaffiliated/cupertino) (Quit: I give up...) | 11:55 | |
| *** Quits: Ragnor (~Ragnor@dslb-092-072-243-047.pools.arcor-ip.net) (Disconnected by services) | 12:10 | |
| *** Joins: Ragnor (~Ragnor@dslb-092-072-243-047.pools.arcor-ip.net) | 12:11 | |
| *** Joins: siebrand (~beis@sm.xs4all.nl) | 12:34 | |
| *** Joins: micahg (~micah@ubuntu/member/micahg) | 14:33 | |
| *** Joins: djSupport (~djsupport@188-221-240-190.zone12.bethere.co.uk) | 14:40 | |
| *** Quits: djSupport (~djsupport@188-221-240-190.zone12.bethere.co.uk) (Read error: No route to host) | 14:46 | |
| *** Joins: djSupport (~djsupport@188-221-240-190.zone12.bethere.co.uk) | 14:48 | |
| *** Joins: roentgen (~arthur@miranda/user/roentgen) | 15:45 | |
| *** Joins: djSupport_ (~djsupport@188-221-240-190.zone12.bethere.co.uk) | 16:14 | |
| *** Quits: djSupport (~djsupport@188-221-240-190.zone12.bethere.co.uk) (Ping timeout: 245 seconds) | 16:16 | |
| *** Joins: djSupport (~djsupport@188-221-240-190.zone12.bethere.co.uk) | 16:22 | |
| *** Quits: djSupport_ (~djsupport@188-221-240-190.zone12.bethere.co.uk) (Ping timeout: 245 seconds) | 16:24 | |
| *** Joins: djSupport_ (~djsupport@188-221-240-190.zone12.bethere.co.uk) | 17:09 | |
| *** Quits: djSupport (~djsupport@188-221-240-190.zone12.bethere.co.uk) (Ping timeout: 245 seconds) | 17:11 | |
| *** djSupport_ is now known as djSupport | 17:11 | |
| *** Joins: paulr (~IceChat09@2001:470:9310:aaaa:859d:1aa9:6610:9111) | 17:17 | |
| *** Quits: djSupport (~djsupport@188-221-240-190.zone12.bethere.co.uk) (Read error: Connection reset by peer) | 17:46 | |
| *** Quits: daryn (~daryn@h158.249.190.173.static.ip.windstream.net) (Quit: Ex-Chat) | 18:02 | |
| *** Quits: thraxisp (~thraxisp@24.139.16.154) (Quit: thraxisp) | 18:45 | |
| *** Joins: thraxisp (~thraxisp@24.139.16.154) | 18:47 | |
| *** Quits: moto-moi (~hylke@2001:888:13e4:0:21f:e2ff:fe0c:ce28) (Read error: Operation timed out) | 19:07 | |
| *** Quits: micahg (~micah@ubuntu/member/micahg) (Ping timeout: 250 seconds) | 19:48 | |
| *** Quits: thraxisp (~thraxisp@24.139.16.154) (Ping timeout: 276 seconds) | 19:55 | |
| *** Quits: scribe9343423 (~scribe934@static.96.23.63.178.clients.your-server.de) (Remote host closed the connection) | 20:00 | |
| *** Joins: scribe9343423 (~scribe934@static.96.23.63.178.clients.your-server.de) | 20:00 | |
| *** Joins: thraxisp (~thraxisp@24.139.16.154) | 20:05 | |
| *** Quits: paulr (~IceChat09@2001:470:9310:aaaa:859d:1aa9:6610:9111) (Ping timeout: 252 seconds) | 20:21 | |
| *** Quits: wolog (~wolog@87.106.58.253) (Ping timeout: 255 seconds) | 20:41 | |
| *** Joins: wolog (~wolog@87.106.58.253) | 20:47 | |
| *** Quits: thraxisp (~thraxisp@24.139.16.154) (Ping timeout: 264 seconds) | 20:48 | |
| *** Joins: thraxisp (~thraxisp@24.139.16.154) | 20:49 | |
| *** Quits: thraxisp (~thraxisp@24.139.16.154) (Ping timeout: 240 seconds) | 20:59 | |
| *** Joins: thraxisp (~thraxisp@24.139.16.154) | 21:06 | |
| *** Joins: micahg (~micah@ubuntu/member/micahg) | 21:06 | |
| *** Joins: squiggy (~squiggy@adsl-75-18-187-204.dsl.pltn13.sbcglobal.net) | 21:13 | |
| *** Parts: squiggy (~squiggy@adsl-75-18-187-204.dsl.pltn13.sbcglobal.net) | 21:13 | |
| *** Quits: thraxisp (~thraxisp@24.139.16.154) (Ping timeout: 252 seconds) | 21:15 | |
| *** Joins: thraxisp (~thraxisp@24.139.16.154) | 21:19 | |
| *** Quits: thraxisp (~thraxisp@24.139.16.154) (Ping timeout: 245 seconds) | 21:27 | |
| *** Quits: micahg (~micah@ubuntu/member/micahg) (Ping timeout: 276 seconds) | 21:34 | |
Generated by irclog2html.py 2.9.2 by Marius Gedminas - find it at mg.pov.lt!