| ../irclogs/#mantishelp.2010-02-05.log | ||
| --- scribe started --- | 00:00 | |
| alemayo | hi --- how can I change the summary of issues on mantisbt.org/bugs ? | 08:36 |
|---|---|---|
| giallu | alemayo, click on "Edit issue" | 08:43 |
| giallu | actually | 08:43 |
| giallu | the button is "Edit" | 08:43 |
| alemayo | I think I do not have it as a repoter | 08:44 |
| alemayo | user: am-gtz | 08:44 |
| alemayo | maybe somebody can increase my level :) | 08:44 |
| giallu | yeah, reporter can't edit | 08:45 |
| kirillka | giallu: around? | 11:01 |
| giallu | more or less | 11:03 |
| kirillka | Can you talk me: why monitor-users don't recive notice for add note? | 11:05 |
| kirillka | This bug? misconfig? Or this right work? | 11:05 |
| alemayo | is it normal that due date always defaults to "1970-01-01 03:00" ? | 11:30 |
| alemayo | I think it should be empty instea? | 11:30 |
| alemayo | instead | 11:30 |
| giallu | kirillka, I think it's some misconfiguration; they should definitely get mails | 11:49 |
| giallu | alemayo, it seems we don't support null fields, so we can't keep that empty | 11:49 |
| alemayo | giallu: but at least in the UI we should not show 1970-01-01 ??? | 12:02 |
| alemayo | and why don't we support null fields ? | 12:02 |
| giallu | alemayo, yeah, we should not | 12:04 |
| giallu | I don't really know details of why we have this stuff | 12:05 |
| nuclear_eclipse | alemayo: we can't support "null" fields due to the way some of our supported database backends work | 12:32 |
| kirillka | nuclear_eclipse: mo | 12:33 |
| nuclear_eclipse | eg, oracle doesn't support "null" values for fields | 12:33 |
| nuclear_eclipse | hi kirillka | 12:35 |
| kirillka | How I can set config, that all add bugnote send to administartors too? | 12:36 |
| kirillka | for now I have http://mantis.pastebin.com/d4605dfaa | 12:37 |
| nuclear_eclipse | $g_notify_flags['bugnote']['threshold_min'] = ADMINISTRATOR; | 12:41 |
| kirillka | This option not misconfig, that monitored user don't receive notification? | 12:43 |
| nuclear_eclipse | I dunno | 12:43 |
| nuclear_eclipse | I would think that monitoring users would get mailed if someone adds a note though | 12:44 |
| kirillka | ok. I remove some config in config_table, than monitor-user receive email, but administrator - not. Before - administrator receive, monitor - not :) | 12:46 |
| kirillka | nuclear_eclipse: Thanks - work | 12:48 |
| nuclear_eclipse | yw | 12:48 |
| webgambit | paul_: are you here? | 14:18 |
| alemayo | nuclear_eclipse: but at least we should support null values ... i.e. if the internal date is 1970 the due date field should be empty and so on | 14:25 |
| jasminam | hello | 14:42 |
| jasminam | can someone shed some light on upgrading from version 1.1.1 | 14:43 |
| jasminam | initial upgrades are applied up to Drop votes column of mantis_bug_table0.17-jf-8 | 14:43 |
| nuclear_eclipse | unzip the new release tarball, copy your config_inc and any custom_* files from the old install, and run admin/install.php from the new install to upgrade the database schema if necessary | 14:44 |
| jasminam | i tried that too, but it got stuck | 14:45 |
| nuclear_eclipse | stuck? | 14:45 |
| jasminam | i get this far | 14:46 |
| jasminam | BAD | 14:46 |
| jasminam | CREATE TABLE _config_table ( config_id VARCHAR(64) NOT NULL, project_id INTEGER NOT NULL DEFAULT 0, user_id INTEGER NOT NULL DEFAULT 0, access_reqd INTEGER DEFAULT 0, type INTEGER DEFAULT 90, value LONGTEXT NOT NULL, PRIMARY KEY (config_id, project_id, user_id) )TYPE=MyISAM | 14:46 |
| jasminam | Table '_config_table' already exists | 14:46 |
| nuclear_eclipse | jasminam: were you running a version of mantis packaged for a linux distro? | 14:47 |
| jasminam | yes | 14:47 |
| jasminam | from plesk | 14:47 |
| jasminam | but can't upgrade from plesk | 14:48 |
| jasminam | main reason i wanted to update is to have search and filtering functionality | 14:49 |
| nuclear_eclipse | basically, mantis by default keeps track of schema revisions from admin/schema.php in your config_table, so you would need to go through and set the appropriate database_version value in config_table to match the database revision last applied in your install | 14:50 |
| nuclear_eclipse | debian did something similar with their packages on mantis, and it seems that 99% of upgrade issues are related to people trying to migrate from a distro package to one of our tarballs.... =\ | 14:51 |
| jasminam | can you give me an example of what i would need to do please once i'm in config_table | 14:52 |
| jasminam | and would i run install or upgrade script? | 14:52 |
| nuclear_eclipse | install | 14:52 |
| nuclear_eclipse | upgrade scripts are only needed to go from 0.X to 1.0 | 14:53 |
| nuclear_eclipse | past 1.0, the install script handles both installs and upgrades | 14:53 |
| jasminam | ok | 14:53 |
| jasminam | ta | 14:53 |
| nuclear_eclipse | anyways, you'd need to insert a row in your config_table with "config_id" of "database_version", and set its value to an integer of the last applied schema revision from admin/schema.php | 14:54 |
| nuclear_eclipse | in my 1.2 install, the value is 173, but 1.1 would be much lower | 14:54 |
| jasminam | how can i find out my revision number? | 14:55 |
| nuclear_eclipse | you'd have to count through the array in admin/schema.php and compare each one to your database schema... =\ | 14:57 |
| nuclear_eclipse | this is why I never use web apps from distro packages, never know what they've done to them.... | 14:57 |
| jasminam | this is presumably in my current version of admin/schema.php | 14:58 |
| nuclear_eclipse | I'd recommend comparing against the one from 1.1.8 | 14:59 |
| jasminam | ok | 14:59 |
| jasminam | my database_version in 1.1.1 install is set to 63 | 15:01 |
| jasminam | i've been looking at admin/schema.php and i don't know what i need to do here, can someone explain this a bit more please? | 15:47 |
| jasminam | i ended up commenting the first few arrays in the schema.php and it completed the job, now have to see if this actually works | 15:57 |
| jasminam | after doing this i get to continue to login page and see "WARNING: The database structure may be out of date. Please upgrade here before logging in." | 16:00 |
| jasminam | then it gets stuck if i try to upgrade as it can't apply all changes | 16:01 |
| webgambit|afk | jasminam: I'm not very knowledgable with mantis yet, but from what I understand that warning about the database structure being out of date is just based on the value of one of the fields in the database. Maybe some of the stuff you commented out earlier would have updated that value? Just guessing. | 16:04 |
| jasminam | maybe, the value of database_version hasn't changed | 16:07 |
| jasminam | ok, aside from the update, how can i search and filter in mantis? | 16:08 |
| jasminam | can someone tell me what should be database_version for 1.1.8 please? | 16:24 |
| webgambit | paul_ are you here? | 19:41 |
| paul__ | lo | 19:49 |
| paul__ | now | 19:50 |
| paul__ | just got in not long ago | 19:50 |
| webgambit | got time to help me out with that active directory issue I was telling you about yesterday? | 19:50 |
| paul__ | yea I guess | 19:51 |
| paul__ | first off, sanitize and show me what you have in config | 19:51 |
| paul__ | for ldap atm | 19:51 |
| paul__ | and remind me | 19:51 |
| paul__ | are you on 1.1.8, 1.2rc2 or trunk | 19:51 |
| webgambit | 1.1.8 | 19:51 |
| webgambit | my config is posted at http://www.mantisbt.org/forums/viewtopic.php?f=3&t=9829 | 19:52 |
| paul__ | $g_ldap_bind_dn needs to be a username | 19:54 |
| paul__ | i.e. user/pass combinations | 19:54 |
| paul__ | iirc | 19:54 |
| webgambit | ok, I'm checking with our active directory guy | 19:57 |
| paul__ | is 389 the non ldaps:// port? | 19:59 |
| webgambit | I'll ask | 19:59 |
| webgambit | yes, 389 is the non ssl port | 20:01 |
| webgambit | okay, on the $g_ldap_bind_dn... | 20:01 |
| paul__ | ldap_bind should be a user that the password relates to | 20:01 |
| paul__ | low priv user | 20:01 |
| webgambit | right. | 20:02 |
| webgambit | we have a very low priv user set up. The username is corridor. | 20:02 |
| paul__ | ahh right | 20:02 |
| paul__ | i'd be inclined to set $g_ldap_root_dn = 'dc=subdomain,dc=domain,dc=com'; to CN=Users,dc= | 20:03 |
| webgambit | I tried just putting $g_ldap_bind_dn = 'corridor'; but that didn't change anything. | 20:03 |
| webgambit | okay, I'll try changing the root | 20:03 |
| webgambit | ok, I changed root a couple of times. here's what I got. $g_ldap_root_dn = 'dc=subdomain,dc=domain,dc=com'; gives operations error | 20:05 |
| webgambit | $g_ldap_root_dn = 'CN=Users,dc=subdomain,dc=domain,dc=com'; gives 'unable to bind' error | 20:06 |
| paul__ | I need to dig out my ldap api | 20:07 |
| webgambit | CN=Cockpit_Admins,CN=Users,DC=gdesign,DC=goredesign,DC=com; doesn't give an error at all. but I'm not sure why that works. | 20:07 |
| webgambit | well, it doesn't work, but it doesn't throw an error | 20:07 |
| paul__ | is there a referrals optin in 1.1.8? | 20:09 |
| webgambit | no. but I found a post somewhere that said to add ldap_set_option( $t_ds, LDAP_OPT_REFERRALS, 0); to the ldap_api.php so I did. however, it didn't say where to add it. | 20:11 |
| webgambit | so I may have it in the wrong place. | 20:11 |
| paul__ | add that to ldap connect | 20:13 |
| paul__ | somewhere | 20:13 |
| paul__ | donth think it matters where | 20:13 |
| webgambit | sweet, that's where I have it. | 20:14 |
| webgambit | hey paul_, if it would help, I could change to a different version, like the RC2 or the trunk. | 20:20 |
| paul__ | I personally hate the ldap_api file in trunk atm ;p | 20:21 |
| webgambit | lol | 20:21 |
| webgambit | ok, so I won't switch to that. | 20:21 |
| paul__ | working on rewriting/changing it | 20:21 |
| webgambit | when I mess something up, it throws a variable saying it can't bind. So I assume that it's binding at the moment. What would be the next thing to check? | 20:24 |
| paul__ | in fact, take the ldap api from trunk | 20:26 |
| paul__ | you can at least turn on logging | 20:26 |
| paul__ | :P | 20:26 |
| webgambit | lol | 20:26 |
| webgambit | okay, can I just grab that one file or will I need to replace it all? | 20:26 |
| paul__ | grab that one file | 20:27 |
| paul__ | you might need to tweak config defaults | 20:27 |
| paul__ | but yea | 20:27 |
| paul__ | should be fine | 20:27 |
| webgambit | ok | 20:27 |
| webgambit | ok, got the ldap api file up. When I refreshed the log in page i got several notices and a couple of warnings. Sorting through those now. | 20:33 |
| paul__ | warnings are probably extra config entriers you need to add | 20:33 |
| webgambit | bingo | 20:33 |
| webgambit | Configuration option "ldap_simulation_file_path" not found. | 20:33 |
| webgambit | Configuration option "ldap_follow_referrals" not found. | 20:33 |
| * paul__ hates ldap simulation | 20:33 | |
| webgambit | first I've heard of it. Looking it up in the docs now to see what it should be set to. | 20:34 |
| paul__ | dead | 20:34 |
| paul__ | pointless | 20:34 |
| paul__ | one of those | 20:34 |
| paul__ | nuclear_eclipse: it's a friday night ok? :) | 20:35 |
| webgambit | okay, I got rid of the warnings. I couldn't find anything for the simulation so I just set it to = '' | 20:40 |
| webgambit | that leaves me the following notice which is thrown 7 times on the login page. Use of undefined constant LOG_LDAP - assumed 'LOG_LDAP' | 20:40 |
| paul__ | constant_inc | 20:41 |
| paul__ | add it | 20:41 |
| webgambit | what do i define it as? | 20:42 |
| paul__ | for now, whatever next log number is | 20:43 |
| paul__ | or whatever's in trunk | 20:43 |
| paul__ | :) | 20:43 |
| webgambit | done | 20:45 |
| webgambit | copied what was in the trunk | 20:46 |
| paul__ | yea that works | 20:46 |
| webgambit | i can refresh the login page and not get any errors, warnings or notices | 20:46 |
| webgambit | but I still can't log in. | 20:46 |
| paul__ | do you know how do to turn on our loggin? | 20:48 |
| paul__ | $g_log_level = LOG_LDAP | 20:48 |
| paul__ | and $g_log_path or something | 20:48 |
| webgambit | ok, I did that. now when I refresh I get SYSTEM NOTICE: Undefined offset: 16 | 20:49 |
| webgambit | 16 is the number LOG_LDAP | 20:49 |
| webgambit | but it did create the log file. | 20:51 |
| webgambit | I just went ahead and uploaded all the files from the trunk. No more notice. got an application error that I'm looking into now. | 21:01 |
| webgambit | ok... it appears that I'm logged in. But I need to update the database now that I'm running the trunk but it won't let me. Says I'm not an administrator. | 21:08 |
| webgambit | paul_: you still around? | 21:20 |
| paul__ | ya | 21:20 |
| paul__ | your not an admin?? | 21:20 |
| webgambit | okay, I've got it up and running, but I can't seem to get mantis to see me as admin | 21:21 |
| paul__ | huh | 21:21 |
| paul__ | you was admin before? | 21:21 |
| webgambit | I'm admin in the AD. In order to get this going I ended up deleting everything and just install the last night's build. | 21:21 |
| paul__ | turn off LDAP then | 21:22 |
| paul__ | and just use the default adminiistrator/root logon? | 21:22 |
| webgambit | ok... | 21:22 |
| webgambit | got it. switched it to md5, logged in as administrator and modified my user then switched it back to ldap. | 21:26 |
| webgambit | thanks for all your help paul_ | 21:28 |
| paul__ | .. | 21:28 |
| paul__ | ? | 21:28 |
| paul__ | ldap's working?? | 21:28 |
| webgambit | yep | 21:28 |
| paul__ | stick around | 21:29 |
| webgambit | ok | 21:29 |
| paul__ | as i might replace that ldap file voer wekened | 21:29 |
| webgambit | gotcha | 21:29 |
| siebrand | what's up with http://git.mantisforge.org/w/ManTweet.git?a=tree ? | 23:21 |
| siebrand | 404 - Reading tree failed | 23:21 |
| siebrand | wasn't that your thing, paul__? Or who's? | 23:22 |
| paul__ | no commits i think | 23:22 |
| siebrand | paul__: completely empty? Where are the sources? | 23:23 |
| paul__ | think victor had them on github originally | 23:23 |
| siebrand | paul__: right, that'd be http://github.com/vboctor/mantis-plugins/tree/master/ManTweet | 23:24 |
| siebrand | paul__: thanks | 23:24 |
Generated by irclog2html.py