| ../irclogs/#mantishelp.2010-06-22.log | ||
| --- scribe started --- | 00:00 | |
| slim_ | hello all, i installed mantis 1.2.1, and i have a database from older mantis, how can i install old database ? | 09:00 |
|---|---|---|
| slim_ | hi | 09:22 |
| slim_ | is it possible to upgrade from version 0.17.5 to 1.2.1 ? | 09:30 |
| slim_ | as i read that to upgrade to version 1.0.0 first, but i got error also when upgrade to version 1.0.0 anyone can help me in this ? | 09:58 |
| dhx_m | slim_: you're on your own with this one... 0.17.5 is older than the internet and it is unlikely anyone here (or on the mailing list) was around that long ago (and/or remembers how such an early version worked) | 10:23 |
| slim_ | dhx_m: we use old version long time ago, yesteday only my manager asked me to upgrate to current version | 10:24 |
| slim_ | after i read i find that i have to upgrade to version 1.0.0 first | 10:24 |
| dhx_m | you should really be updating more frequently or else you run into these situations | 10:35 |
| dhx_m | unless you have the inhouse skills to write your own conversion scripts | 10:35 |
| slim_ | of course , you are right . | 10:36 |
| dhx_m | otherwise you can try crawling the bug tracker and mailing list for historical information about upgrading earlier versions | 10:36 |
| slim_ | this i do now , | 10:36 |
| dhx_m | it's a bit like someone asking how to upgrade from Windows 3.1 to Windows 7... it's easier to just start again and move data across yourself than to upgrade (if it's even possible) | 10:37 |
| dhx_m | except with Windows you are better to start afresh every time you upgrade/reinstall :p | 10:38 |
| slim_ | yes to avoid this i'm working with linux :) | 10:38 |
| slim_ | dhx_m: now the current version working well :) | 11:14 |
| dhx_m | :) | 11:14 |
| dhx_m | that was quicker than I was expecting :D | 11:14 |
| slim_ | yes, there was something near in forum | 11:14 |
| nuclear_eclipse | wow | 11:28 |
| nuclear_eclipse | 0.17.5 | 11:28 |
| nuclear_eclipse | and I thought all those 1.0.x users were really bad at staying up to date... | 11:29 |
| nuclear_eclipse | :P | 11:29 |
| dhx_m | lol | 11:46 |
| dhx_m | maybe we should have asked slim_ for a testimonial for the website... "I upgraded a 5 year old MantisBT installation to the latest version in minutes!" | 11:47 |
| dhx_m | lol at this patent I came across relating to login security (user/pass) | 12:17 |
| dhx_m | they've reinvented challenge/response using something that resembles caeser shift | 12:17 |
| dhx_m | I think there needs to be a law created to ban people from creating their own crap crypto systems :p | 12:19 |
| Draggor | So just to check, dokuwiki and mantisbt integration is currently borked? | 13:34 |
| nuclear_eclipse | Draggor: it just takes a bit of manual work to get them to work with each other... =/ | 13:39 |
| Draggor | nuclear_eclipse: Right now I'm having this "sg function not defined" in the mantis.class.php I added in dok | 13:48 |
| nuclear_eclipse | "sg"? | 13:52 |
| Draggor | http://www.mantisbt.org/wiki/doku.php/mantisbt:issue:7075:integration_with_dokuwiki I'm following this | 13:53 |
| nuclear_eclipse | I have no clue | 13:55 |
| nuclear_eclipse | those instructions are really out of date | 13:55 |
| Draggor | Ahh, heh. Is there a better way I should go about it? | 13:55 |
| nuclear_eclipse | I know that quite a bit of mantis has changed since then | 13:55 |
| nuclear_eclipse | Draggor: pick something other than Dokuwiki ;) | 13:55 |
| Draggor | Aww, but I like dokuwiki :( <3 flat file storage for small stuff | 13:56 |
| nuclear_eclipse | well, then I can't really help =\ | 13:56 |
| Draggor | well, mainly, I greatly enjoy dokwiki's syntax and block editing | 13:56 |
| nuclear_eclipse | I stopped using Dokuwiki years ago because file-based storage is really annoying | 13:57 |
| nuclear_eclipse | makes upgrading and backups a pain | 13:57 |
| Draggor | So far upgrading has been simple and backups divine | 13:57 |
| nuclear_eclipse | permissions also constantly kept creeping up to bite me | 13:57 |
| Draggor | Okay so my conf and data dirs might be a bit.. loose, heh | 13:58 |
| nuclear_eclipse | it's far easier to just dump all your databases at night than to have your data spread out in multiple locations | 13:58 |
| Draggor | I mean, someone asks me for a wiki, so I just unzip the thing and pint the install page to them | 13:58 |
| Draggor | point* | 13:59 |
| Draggor | It's a two minute affair | 13:59 |
| Draggor | Part of it is my own fault for locking down my DB so heavily | 13:59 |
| Draggor | I'd be willing to rediscover how to merge dokiwiki with mantis could be a fun mini project | 14:01 |
| nuclear_eclipse | Draggor: if you do so, it would be nice to have an updated wiki article :P | 14:02 |
| Draggor | I would do that too :3 | 14:03 |
| CIA-22 | Mantisbt: s.mazeland master-1.2.x * r429142a6b0f2 / (7 files in 2 dirs): Localisation updates from http://translatewiki.net | 16:41 |
| slestak | hi guys. I got a curl line workign that runs a repo_import_last for my sourceintegration use. The one question I have is it requires the id arg for the repo. Is there a general call I can use to run it on all the repos? | 18:18 |
| nuclear_eclipse | slestak: id=all | 18:21 |
| slestak | ahh, tyvm | 18:24 |
| slestak | i was just writing a python script to iterate over the rows in mantis_plugin_Source_repository_table | 18:24 |
| slestak | ty for saving me from myself | 18:25 |
| nuclear_eclipse | youre welcome | 18:25 |
| nuclear_eclipse | if at all possible, you should try to use post-commit hooks rather than a cronjob, but I implemented both methods because I know that's not always possible, eg, SourceForge repos | 18:26 |
| slestak | i liek the idea of the cron, because I can have one spot to get tehm all, otherwise I am making X post-commit hooks for X repos | 19:05 |
| slestak | if i used a post commit hook, each repo needs to know its mysql id number, unless I am going to say update all when any have a commit, that would be wasteful | 19:06 |
| slestak | is id 'all' new since sourceintegration 0.14? when I use it I get "Invalid remote import address" returned | 19:07 |
| slestak | would be cool if the repo displayed its last import datetime | 19:08 |
| slestak | i see that in strings. plugins/Source/lang/strings_english.txt:$s_plugin_Source_invalid_import_url = 'Invalid remote import address'; | 19:10 |
| slestak | ok, the error message from above only occurs when i try to go to that url in firefox for testing | 19:14 |
| slestak | when I use curl on the mantis vm, it works for integer id keys, however, id=all does not work with curl | 19:14 |
| nuclear_eclipse | slestak: yes, that's new since 0.14 | 19:32 |
| slestak | i am using dhx_m's hgweb version so I will upfate them indiviually until that reaches 0.16 | 19:33 |
| slestak | is the best method of installing (and tracking) plugins to use git to clone them to mantis/plugins/ ? | 19:34 |
| nuclear_eclipse | my preferred method is cloning plugins to a separate directory and then symlinking from the other location into the mantis/plugins directory | 19:35 |
| slestak | think i will do that. that is how I keep mantis, symlinked to /usr/local/src | 19:37 |
| nuclear_eclipse | slestak: you might also want to considering attempting to run dhx's hgweb plugin with the up-to-date framework at 0.16.1 | 19:37 |
| nuclear_eclipse | and if it doesn't work, I imagine it shouldn't take much to fix it | 19:38 |
| slestak | i think i tried that and had issues. sry, cannot remember | 19:38 |
| nuclear_eclipse | most of the changes since 0.14 took place in the framework features themselves | 19:38 |
| slestak | i'd liek to, but with my workload right now I need to be a user more than dev, | 19:38 |
| nuclear_eclipse | np | 19:38 |
| nuclear_eclipse | just thought I'd sugest it | 19:39 |
| slestak | i'd liek to. I think step one may be to reinstall my existing plugins using the methd you describe so I can maybe keep multiple version | 19:39 |
| nuclear_eclipse | other suggestion is to just bug dhx about getting his hgweb plugin up to date :P | 19:40 |
| slestak | nah, im very pleased and thankful to have what i got | 19:41 |
| nuclear_eclipse | dhx_m: | 23:39 |
| nuclear_eclipse | dhx_m: you broke things | 23:39 |
| nuclear_eclipse | dhx_m: http://git.mantisbt.org/?p=mantisbt.git;a=commit;h=7062c67759c8dd002a187ed24a8a4a710f2e6eb5 | 23:42 |
| nuclear_eclipse | that commit breaks the ability to configure the default next status in the workflow | 23:42 |
| nuclear_eclipse | just because the default configuration settings sucked, doesn't mean you get to ignore them :P | 23:42 |
Generated by irclog2html.py