Thursday, 2009-12-10

../irclogs/#mantishelp.2009-12-10.log
--- scribe started ---00:00
kirillkadhx_m: around?06:06
dhx_mkirillka: hi09:00
kirillkadhx_m: hi09:14
kirillkaDid you remember about attach and magic datafile?09:15
kirillkaI ask you about this error09:15
kirillkabt I can found solution09:15
kirillkadhx_m: Can you remember me solution?09:19
dhx_mhi09:25
dhx_myep I thought that was fixed?09:25
kirillkadhx_m: Yes, but on forum http://www.mantisbt.org/forums/viewtopic.php?f=3&t=935209:27
dhx_mkirillka: http://git.mantisbt.org/?p=mantisbt.git;a=commitdiff;h=e6bc4638aa54ea8e04742b9171dc65a4ae0e385209:30
dhx_mpost RC2 I think09:30
kirillkadhx_m: I can't check. Send him patch.09:34
dhx_mI'm not signed up to the forums (and don't read them)09:35
dhx_mI imagine most forum users aren't familiar with how to patch things09:36
dhx_mso I suggest just linking to the nightly builds page09:36
kirillkaI try help him to apply patch ;)09:36
dhx_mok :)09:37
dhx_mthanks09:37
kirillkadhx_m: You thanks09:37
dhx_mkirillka: thanks for helping out people on the forum :)09:39
kirillka:)09:39
mantisbt_28712Hi11:52
mantisbt_28712I working now to change all tickets priority and i have hundred of tickets, Is there a way to update them once ?11:53
moto-moiupdate mantis_bug_table set priority = 50 where priority = 3011:55
moto-moi?11:55
moto-moiI don't think there's a webinterface thingie for that11:55
mantisbt_28712let me try it11:57
mantisbt_28712I can't find mantis_bug_table file ???11:59
moto-moiehm.. I gave a database query, not a piece of php?11:59
mantisbt_28712can you please give me more information and how to accomplish it12:00
moto-moiHmm, if you don't know any sql, I wouldn't advise you to try this to be honest :)12:01
mantisbt_28712I worked before on sql12:02
mantisbt_28712but i need to know how to access it .. i am new developer in Mantis12:02
moto-moiYou need access to the database :)12:03
moto-moiwhere there is a table called mantis_bug_table, among others12:03
mantisbt_28712ok thanks12:04
mantisbt_28712i am working on it now12:04
mantisbt_28712thanks12:04
moto-moinp :)12:04
mantisbt_28712one more question12:06
mantisbt_28712i got access to sql and i found that table12:07
mantisbt_28712but if i change priority to 50 this will change it to Urgen but i change it to 80 this will change it to medium according to my setup table ?12:15
mantisbt_28712Is this correct ?12:15
moto-moipoeh12:16
moto-moiI don't know the relation between the numbers12:16
moto-moibut you can find a 'bug' in the db, and look @ the frontend what it sais there?12:16
mantisbt_28712i just found it12:21
mantisbt_28712but let me confirm this12:21
mantisbt_28712if i change the priority table to 80 , this will affect all closed ticket and change all priority to 80 ( medium )12:22
mantisbt_28712correct12:22
mantisbt_28712The idea of doing that12:22
mantisbt_28712is remove normal priority from tables and change it to medium12:22
mantisbt_28712but this there are tickets with normal12:22
mantisbt_28712normal ticket statuts will showing @30# numbers12:23
mantisbt_28712so the idea here is to create medium priority then remove normal12:23
mantisbt_28712how about that  ?12:23
mantisbt_28712Are you still there ?12:32
moto-moiehm, sorry :P12:58
moto-moimantisbt_28712: I don't know if really removing a priority is a good idea, but I'm not a developer of mantis, so maybe it could work :)13:00
kenguestmantisbt_28712: before you try it - I'd suggest you make a backup of the database - just in case ;)13:03
mantisbt_28712i just change the priority from mantis db but this didn't affect anything .. thanks for suggest about backup, this is the first thing i did before making any changes13:24
mantisbt_28712Also I need to change the default value for new issues, ex. Medium for Priority13:27
mantisbt_28712Can you please tell me how to do it ?13:27
dirtyalnuclear_elipse are you there?17:03
nuclear_eclipsedirtyal: howdy17:59
dirtyalhello17:59
dirtyalI came into a king of a bug yesterday18:00
nuclear_eclipseI noticed18:00
dirtyalfunction svn_call18:00
nuclear_eclipseyou kept catching me while I was afk :P18:00
dirtyalthe svn running as apache is trying to open /root/.subversion18:01
nuclear_eclipsefyi, source integration is not yet compatible with the 1.3 branch of mantis18:01
dirtyalaside from that18:01
dirtyalit is workign so far18:01
dirtyalwith 1.3dev18:01
dirtyaljust had to add this18:02
dirtyal$s_call = 'svn --config-dir=/var/www/.subversion';18:02
dirtyaljust to let you know18:02
nuclear_eclipsedirtyal: you should probably configure apache so that a) it's not running as the root user, and b) has /var/www/ as its $home18:03
dirtyalit is no running as root18:03
dirtyalitÅ› running as apache, it is centos 5 default instalation18:03
nuclear_eclipsegranted, I'm planning to add an option to allow users to specify extra params to svn, which would do what you need18:03
dirtyalthat's why I find the behaviour strnage18:04
nuclear_eclipsehmm, I find it odd that CentOS would config apache to run with /root as its $home18:04
dirtyalsvn should be able to run without using .subversion and ignoring bad SSL certificates18:04
dirtyalbut they dont have this opntion in the 1.4 version18:04
dirtyalI think.18:04
nuclear_eclipseyeah, you need 1.5 to be able to ignore ssl certs18:05
dirtyalwe found out that you can do that in 1.4 in .subversoin/servers18:05
nuclear_eclipseyep18:05
dirtyalthis problems are simple but hard to pinpoint18:06
nuclear_eclipseyeah, it's kind of frustrating18:06
dirtyalthe exec_shell function runs svn with the HOME set to /]18:06
dirtyaldont down why18:06
dirtyalset to the root directory18:06
dirtyalrunning as apache18:07
dirtyalmaybe you could add some better error messages for thus SVN integration, just a tought, redirecting the std_err of svn to a file and checking it out.18:08
nuclear_eclipsedirtyal: I accept patches :P18:08
nuclear_eclipsetbh, it's basically an issue of time, ie I don't have enough spare time these days =\18:09
nuclear_eclipseor spare time is taken up by holidays and family :P18:09
dirtyalyehh, you are rught18:10
dirtyalright18:10
dirtyalI will see if I can make something to help with better svn error handling18:10
nuclear_eclipseif you do, I'll be glad to review it and merge it in if I think it's satisfactory18:10
dirtyalok, I just patched the code today to force fixed_in_version as target_version when the ticket is closed by SVN, as we talked a while ago18:14
dirtyaltks for the attention18:19
nuclear_eclipsenp18:19
dirtyalmantis 1.3dev is working for us here better than 1.2rc2, all featrures that we use are ok and the attached image bug is gone18:20
dirtyaljust to let you know18:20
nuclear_eclipsethe image bug should be fixed in master-1.2.x as well18:20
dirtyalI downloaded the snapshot form mantisforge and git 1.3 by mistake18:21
nuclear_eclipseatm, 1.3 is really not too diverged from 1.2 -- biggest difference is how db_get_table works, which is why I say source-integration isn't yet compatible with 1.318:21
dirtyalI wanted the 1.2.x18:21
dirtyal;)18:21
nuclear_eclipseyou should be just fine to grab a snapshot of 1.2.x and use that instead18:21
dirtyaltks18:21
dirtyalthe repository is at mantisforge for all branches?18:22
nuclear_eclipsethe repo at mantisforge should be a direct clone of the primary repo at git.mantisbt.org18:23
dergringohi!21:18
dergringoHow do I customize status names? I don't need a workflow as described here: http://manual.mantisbt.org/manual.customizing.mantis.customizing.status.values.php21:18
nuclear_eclipsedergringo: create a custom_strings_inc.php and define $s_status_enum_string based off the default values in strings/lang_*21:20

Generated by irclog2html.py