| ../irclogs/#mantishelp.2009-06-04.log | ||
| --- scribe started --- | 00:00 | |
| mantisbot | New bug: Bug 10560 - anthropic - open - new | 04:42 |
|---|---|---|
| mantisbot | New bug: Configuration Arrays - http://www.mantisbt.org/bugs/view.php?id=10560 | 04:42 |
| Testing | I need to change some fields in Mantis | 06:42 |
| Testing | how could I change it... for example I dont need the 'Reproducibility' | 06:43 |
| Maxim1 | hi | 07:41 |
| Maxim1 | how can I configure mantis to send sms messages on new bug reports ? (using php and phpmailer) | 07:43 |
| [KK]Kirill | Maxim1: lo. | 07:52 |
| [KK]Kirill | Maxim1: I ask you yesterday | 07:53 |
| Maxim1 | [KK]Kirill: I didn't get your question , what operator support ? | 07:55 |
| [KK]Kirill | operator must support send sms via email | 07:55 |
| Maxim1 | but what do you mean by "operator" ? php ? phpmailer ? | 07:56 |
| [KK]Kirill | For example Beeline (GSM operator) support this 89062311111@sms.beeline.ru redirect text-mail to sms | 07:57 |
| Maxim1 | o do you mean mobile phone operator ? | 07:57 |
| [KK]Kirill | yes | 07:57 |
| [KK]Kirill | php don't support sms | 07:57 |
| [KK]Kirill | :) | 07:57 |
| Maxim1 | today every phone supports sms and mms | 07:58 |
| [KK]Kirill | today all phone support email :) | 07:58 |
| Maxim1 | could you link me to how could I configure mantis to do it ? | 07:58 |
| Maxim1 | I've seen a program called mantis pager , don't know if it works as it's only 0.0.1 version | 07:59 |
| Maxim1 | 1.5 years old | 08:00 |
| [KK]Kirill | Maxim1: what you mean about configure mantis to do it? | 08:00 |
| Maxim1 | to send sms messages on new bugs | 08:01 |
| [KK]Kirill | add new administrator. set him email-adres with email, witch support redirect to sms. | 08:02 |
| Maxim1 | only admins can receive sms's ? | 08:02 |
| [KK]Kirill | not. | 08:03 |
| Maxim1 | ok, when the email addr is set , I need to configure something in my exchange 2003 account ? (sorry we use exchange for emails :( ) | 08:04 |
| [KK]Kirill | $g_notify_flags['new']['threshold_min'] = DEVELOPER; | 08:05 |
| kenguest | Maxim1: pear/net_sms | 08:19 |
| Maxim1 | kenguest: please explain more... | 08:21 |
| kenguest | Maxim1: if you're feeling up to it you could use the net_sms package from the pear repository @ http://pear.php.net/package/Net_SMS | 08:43 |
| Maxim1 | kenguest: would I need to configure an account for each user/number on some external website ? or will it work without external accounts ? is sending sms free ? | 08:44 |
| Maxim1 | kenguest: is it this package : http://rpm.pbone.net/index.php3/stat/4/idpl/12059087/com/perl-WWW-SMS-0.09-1.el5.rf.noarch.rpm.html ? | 08:49 |
| kenguest | no. it's a pear package - so it's written in php | 08:52 |
| Maxim1 | kenguest: but it is a peral package, it's just rpm but the package is there , the name suites except the www | 08:54 |
| kenguest | Maxim1: read the main page: "PEAR is a framework and distribution system for reusable PHP components. " | 08:56 |
| kenguest | not perl or pearl | 08:57 |
| kenguest | or however you want to spell it ;) | 08:57 |
| Maxim1 | ok , kenguest do I need to register an external account to use it ? | 08:58 |
| kenguest | no. just either download the code or use the pear command to install it | 09:03 |
| Maxim1 | the sms sending is free ? | 09:04 |
| kenguest | that depends on the operator that you configure it to use, I think | 09:09 |
| mantisbot | New bug: Bug 10561 - Buga - open - new | 09:33 |
| mantisbot | New bug: wrong path for internal mantis redirects - http://www.mantisbt.org/bugs/view.php?id=10561 | 09:33 |
| mantisbot | New bug: Bug 10562 - Jimi_Joma - open - new | 11:39 |
| mantisbot | New bug: Printing Bug does not work with configuration $g_show_view= SIMPLE_ONLY; - http://www.mantisbt.org/bugs/view.php?id=10562 | 11:39 |
| Maxim1 | is it possible that all bugs submitted to the mantis will also "synchronize" with bugzilla ? | 12:09 |
| nuclear_eclipse | Maxim1: not currently | 12:15 |
| Maxim1 | nuclear_eclipse: thanks for answering ... so it's not possible that bugs submitted to mantis be "forwarded" or something to bugzilla ? (have to make sure). | 12:17 |
| nuclear_eclipse | it could be implemented using the new plugin system for 1.2, and indeed has been raised as a requested feature (also Launchpad integration), but there is no implementation yet | 12:18 |
| CIA-61 | Mantisbt: s.mazeland * raec020715d0d /lang/strings_english.txt: 'bug' to 'issue' for 8 remaining cases. Sloppy us. Thanks to Jorge Andr?s Brugger for making us aware of this. | 12:18 |
| Maxim1 | nuclear_eclipse: thanks , are there any estimation when will it be implanted ? | 12:19 |
| nuclear_eclipse | Maxim1: see bug 10543 for the most recent request | 12:19 |
| mantisbot | Bug 10543 - oberger - open - new | 12:19 |
| mantisbot | Proposal: Relationships to external bugs in remote bugtrackers - http://www.mantisbt.org/bugs/view.php?id=10543 | 12:19 |
| nuclear_eclipse | Maxim1: no plan yet | 12:19 |
| Maxim1 | thanks | 12:21 |
| nuclear_eclipse | paul_: found a date problem; updating versions destroys their timestamp | 12:27 |
| Maxim1 | I am no expert here , I use mantis and bugzilla equally (meaning almost never use them , just setup mantis a few days ago) , what are the pros/cons of mantis vs bugzilla ? | 12:45 |
| nuclear_eclipse | as I see it, mantis is more configurable/flexible, and has more features; bugzilla is more popular, has a larger development team, which means fewer bugs and problems, and more themable | 12:46 |
| Maxim1 | yeah our "main" bugtracker is bugzilla , but we needed an "external" bugtracker for our program, so I configured mantis for this job - not bad at all I must say. | 12:48 |
| nuclear_eclipse | however, I also think mantis is a lot easier to use for actually viewing and managing all the issues reported; bugzilla always seemed to me to have an awkward interface and workflom | 12:48 |
| nuclear_eclipse | workflow* | 12:48 |
| Maxim1 | yeah it wasn't piece of cake to setup mantis (specially that I had to hunt down all packages and deps one by one via rhn) but after the installation it wasn't that hard to setup it.... had only 2 problems that I've overcome once I undertood where is the problem | 12:52 |
| nuclear_eclipse | what dependencies? | 12:52 |
| Maxim1 | many...some perl libs, php , httpd, mysql , the usual | 12:53 |
| nuclear_eclipse | oh, ok | 12:53 |
| nuclear_eclipse | didn't realize you were including db/web server as dependencies :P | 12:53 |
| Maxim1 | then I had to find some dep for graphs and make changes in the conf file | 12:54 |
| Maxim1 | nuclear_eclipse: yeah well, it was a clean install | 12:54 |
| Maxim1 | I also documented it all in our company's wiki so it will be much easier next time ;) | 12:55 |
| Maxim1 | the "major" problem I had was in the httpd.conf file , it wasn't documented anywhere that I had to include the path to mysql database in the "documents" section so it ill react much faster - ofc this is very logical but still | 12:56 |
| Maxim1 | I've been in this channel for 2 days and asked "what could go wrong" none answered because my question was too global. | 12:57 |
| nuclear_eclipse | my apologies | 12:59 |
| Maxim1 | don't blame anyone | 13:00 |
| Maxim1 | it's just something that needs to be documented somewhere , even if it's not directly mantis related but mysql | 13:01 |
| nuclear_eclipse | I've never had to specify that in my apache configs... | 13:02 |
| siebrand | 'git diff' on windows is giving a load of 'null diffs' on phpmailer. Even after deleting the folder, and reset --hard. | 13:12 |
| siebrand | Any ideas on how to get rid of them? (I assume it has something to do with unix vs. dos line endings) | 13:13 |
| nuclear_eclipse | sorry siebrand, not a clue | 13:13 |
| irenedakota | hi | 13:47 |
| nuclear_eclipse | hello | 13:47 |
| irenedakota | I'm playing around with 1.2 and all the dates are set to 1970... | 13:49 |
| irenedakota | known issue or something I'm doing wrong? | 13:50 |
| nuclear_eclipse | irenedakota: it's probably a result of the recent changes made to the way dates are stored in the database | 13:51 |
| nuclear_eclipse | make sure you run a schema upgrade | 13:51 |
| nuclear_eclipse | eg, visit /admin/install.php | 13:51 |
| irenedakota | Alright. It was a fresh install of 1.2 | 13:51 |
| nuclear_eclipse | oh, ok | 13:51 |
| irenedakota | So, any where in particular I should start looking? | 13:53 |
| nuclear_eclipse | depends on what you're looking for :P | 13:56 |
| irenedakota | Well, I suppose I'd be looking for the cause of the trouble | 13:57 |
| nuclear_eclipse | that's what I'm currently trying to figure out; the problem is more that paulr changed the format of how dates are stored, and didn't actually implement a method of converting user input into the new integer format.... | 13:58 |
| irenedakota | I just did a installation check, and it had quite a bit of "bads" | 13:59 |
| irenedakota | Ah, working now | 14:02 |
| irenedakota | I think I know what happened | 14:03 |
| irenedakota | I originally installed it from the 1.2.0a3 link on the main site, and then I pulled in the latest version from mantiforge. Obviously the time change happened between the two | 14:05 |
| nuclear_eclipse | ah, right | 14:05 |
| nuclear_eclipse | hence the need for the schema upgrade :P | 14:05 |
| [KK]Kirill | siebrand: what troubl with git on windows? | 14:06 |
| irenedakota | Yup. | 14:06 |
| [KK]Kirill | paul_: You around? | 14:06 |
| [KK]Kirill | What with bug 10369? | 14:06 |
| mantisbot | Bug 10369 - Kirill - open - assigned | 14:06 |
| mantisbot | Verification link not work - http://www.mantisbt.org/bugs/view.php?id=10369 | 14:07 |
| * nuclear_eclipse kicks paul_ | 14:49 | |
| [KK]Kirill | nuclear_eclipse: paulr_ is apsend | 14:52 |
| nuclear_eclipse | he always is when I've discovered his bugs... | 14:54 |
| CIA-61 | Mantisbt: jreese * r7104a343a09d /core/version_api.php: Fix #10558: Fix roadmap and changelog ordering bug as introduced in commit ref 0ac196a4. | 15:03 |
| sshirley | Hi everyone. I am currently running Mantis 1.1.0. In terms of new features and bug fixes, would it be worth it for me to update to the latest stable (1.1.7) or wait until the 1.2.x gets out of development? | 15:10 |
| nuclear_eclipse | sshirley: there are a *lot* of security issues fixed in the 1.1.7; I highly recommend that you upgrade asap | 15:10 |
| sshirley | Even if nothing else runs on that machine besides Mantis? | 15:12 |
| nuclear_eclipse | right, it's security issues that could possibly allow someone to gain escalated privileges on your mantis install | 15:13 |
| nuclear_eclipse | which at that point, could potentially open other security issues based on the configuration settings the user could then manipulate, etc | 15:13 |
| sshirley | Ok. I'm looking at the upgrade documentation right now and it doesn't look too tough to do this. Basically backup my files, unzip the new install into the directory, copy over all the config files (config_inc.php, config_defaults_inc.php, custom_*.php) into the new directory, and viola. Now mention of different database schema. Everything in the DB should be fine? | 15:20 |
| nuclear_eclipse | right | 15:20 |
| nuclear_eclipse | between point releases, there are no db schema changes "allowed" | 15:20 |
| sshirley | Excellent | 15:22 |
| sshirley | Sourceforge is acting funky right now. Can't get 1.1.7. | 15:38 |
| sshirley | Back up | 15:39 |
| nuclear_eclipse | you can get a copy from Git | 15:39 |
| sshirley | Ah | 15:39 |
| nuclear_eclipse | http://git.mantisbt.org/?p=mantisbt.git;a=commit;h=b127306f8c06fafe206f27a60bd55716320ba00d | 15:39 |
| nuclear_eclipse | either checkout, or just grab a snapshot | 15:40 |
| CIA-61 | Mantisbt: jreese live * r924d5897f293 /core/bugnote_api.php: Fix #10544: Fix bugnote order and limit when generating emails. | 15:49 |
| CIA-61 | Mantisbt: jreese * r4fc213a34c55 /core/bugnote_api.php: Fix #10544: Fix bugnote order and limit when generating emails. | 15:49 |
| CIA-61 | Mantisbt: jreese * r845925e4c2c6 / (core.php core/events_inc.php): Added event CORE_READY to signal a point for plugins to begin processing with API's loaded and the system initialized. | 15:49 |
| sshirley | Hi all. I am running version 1.1.0 and 1.1.7 on the same machine. I can log into 1.1.0 no problem. But when I try 1.1.7, I get a application error #2700 "Invalid session handler". What gives? | 16:56 |
| nuclear_eclipse | means you've incorrectly set $g_session_handler in your config_inc | 16:59 |
| nuclear_eclipse | $g_session_handler = 'php' is currently the only valid handler | 16:59 |
| sshirley | In the 1.1.7? I'm in the config_inc.php and I don't see that. Perhaps config_default_inc.php? | 17:02 |
| nuclear_eclipse | config_defaults should already be set to 'php' | 17:03 |
| sshirley | Great. Thanks nuclear_eclipse! | 17:19 |
| paul_ | nuclear_eclipse: mo? | 17:33 |
| nuclear_eclipse | howdy | 17:33 |
| paul_ | hi | 17:33 |
| paul_ | whats up | 17:34 |
| nuclear_eclipse | dates are quite broken | 17:35 |
| paul_ | probably | 17:35 |
| nuclear_eclipse | or rather, handling user-input dates is quite broken | 17:35 |
| paul_ | in what | 17:35 |
| nuclear_eclipse | anywhere that requires the user to enter a date string | 17:35 |
| paul_ | and i'll look to see if i've already fixed locally | 17:35 |
| paul_ | with the jscript calendar or without? | 17:36 |
| nuclear_eclipse | nothing ever converts the user-input date string back to an integer to store in the database | 17:36 |
| nuclear_eclipse | either way | 17:36 |
| paul_ | i was fixing the jscript ones | 17:39 |
| paul_ | that had to stop whilst I waited for you :P | 17:39 |
| nuclear_eclipse | why were you waiting on me? | 17:39 |
| paul_ | config api fix :P | 17:39 |
| nuclear_eclipse | ah | 17:40 |
| nuclear_eclipse | that's been fixed for days now, wth? | 17:40 |
| * nuclear_eclipse snaps a whip | 17:40 | |
| paul_ | 40MB would be a good min memory limit to suggest to users | 17:40 |
| nuclear_eclipse | even 32M seems perfectly usable, in my experience, unless it's a really gigantic install | 17:41 |
| paul_ | moodle + joomla require 40mb | 17:41 |
| nuclear_eclipse | so/ | 17:41 |
| paul_ | anyway, ram's cheap | 17:42 |
| paul_ | imo it's silly to be running php with some really low llimit | 17:42 |
| paul_ | mediawiki suggests 20 i think | 17:43 |
| nuclear_eclipse | well, it's not silly for a small site/server running on a VPS... | 17:43 |
| paul_ | sure | 17:44 |
| paul_ | otoh | 17:44 |
| paul_ | if a request users more ram and is faster | 17:44 |
| nuclear_eclipse | but gratned, a small site/server is not likely to be hosting a gigantic installation :P | 17:44 |
| paul_ | that might be better then using less ram, taking longer and having more requests being processed | 17:44 |
| paul_ | MediaWiki needs sufficiently memory to work. The minimal limit should be something like 20 Mo, but if you want MediaWiki to work correctly, consider using at least 50 Mo. | 17:45 |
| paul_ | so basically | 17:45 |
| paul_ | mediawiki/joomla/moodle are all saying 40mb | 17:45 |
| paul_ | drupal was saying 16 or 20 i beleive | 17:45 |
| * paul_ wonders what else people run | 17:45 | |
| paul_ | phpbb says 16m min | 17:46 |
| * nuclear_eclipse runs 24mb on VPS | 17:46 | |
| nuclear_eclipse | and that hosts a WordpressMu install and other PHP apps as well as Mantis | 17:46 |
| paul_ | but i think you might find that's too low soon | 17:47 |
| paul_ | from what I can tell | 17:47 |
| paul_ | in php5.3 | 17:47 |
| paul_ | the memory limit is going to start including mysql memory usage (for the client) at least for some drivers | 17:47 |
| nuclear_eclipse | ugh | 17:47 |
| paul_ | well | 17:48 |
| paul_ | that's arguably more accurate | 17:48 |
| nuclear_eclipse | btw, what opcode caching system do we use on mantisbt.org? | 17:50 |
| paul_ | apc | 17:51 |
| nuclear_eclipse | url? | 17:52 |
| paul_ | http://pecl.php.net/package/APC | 17:52 |
| nuclear_eclipse | ty | 17:52 |
| nuclear_eclipse | I'm wanting to propose that to our IT because they insist on running the web server from files over NFS, which kills performancne on Mantis with how many files it uses... | 17:53 |
| paul_ | hmm | 17:53 |
| paul_ | I changed an ordr by? | 17:53 |
| nuclear_eclipse | no, you never added one | 17:54 |
| paul_ | i'm confusing my working dir | 17:55 |
| nuclear_eclipse | you added caching to version_api, but didn't use an order by clause, which "broke" roadmap/changelog because they were expecting data as sorted by the API, and caching everything first resulted in that data not being in the correct order | 17:55 |
| paul_ | ahh | 17:55 |
| paul_ | and probably why I didn't spot it then | 17:55 |
| paul_ | if a plugin uses a library | 17:56 |
| paul_ | should library live in /library? | 17:56 |
| paul_ | or /plugin/foo/library ? | 17:56 |
| paul_ | I assume in /library | 17:56 |
| nuclear_eclipse | if it's a library used by mantis, it should be in /library; if it's specific to the plugin, it should be in a subdirectory of the plugin | 17:56 |
| paul_ | i'd be inclined to disagree abit there | 17:57 |
| paul_ | as if it's a 3rd party library, we dont want >1 copy of it | 17:57 |
| nuclear_eclipse | I wouldn't; admins a) shouldn't be messing with mantis' /library, b) necessary libraries should be included with the plugin, or c) plugins should try to see if the library is already loaded or not | 17:58 |
| nuclear_eclipse | or d) make a plugin that does nothing but provide that library, eg, jQuery plugin | 17:58 |
| * paul_ thinks that shouldn't be a plugin | 17:58 | |
| nuclear_eclipse | point being that multiple plugins can declare a dependency on the jQuery plugin, and then there's only one copy of the dependency | 17:59 |
| paul_ | sure, but my point is, for something like jquery that we might want to use in core and for a jscript library | 18:00 |
| paul_ | we shouldn't have the overhead of php | 18:00 |
| nuclear_eclipse | well, yes, but that's an orthogonal issue | 18:00 |
| paul_ | similarly | 18:01 |
| nuclear_eclipse | the jQuery plugin atm is just a stopgap until we make a final decision on including jQuery in core | 18:01 |
| paul_ | if plugins refer to /library/jquery | 18:01 |
| paul_ | or whatever | 18:01 |
| paul_ | that should make life easier for packagers | 18:01 |
| paul_ | who can set up symlinks or whatever | 18:01 |
| nuclear_eclipse | not really | 18:01 |
| paul_ | then if each plugin has a copy of library | 18:01 |
| paul_ | and potentially different versions etc | 18:01 |
| nuclear_eclipse | that's why I say that a library dependency would be better as its own plugin that multiple others can list as a dependency, resulting in only one copy | 18:02 |
| nuclear_eclipse | and the way I propose doesn't require mantis admins to muck about with finding/downloading/moving dependencies into mantis's primary /library/ | 18:02 |
| paul_ | brb | 18:03 |
| paul_ | if i work on graphs branch tonight | 18:03 |
| paul_ | you should be able to look a bit later | 18:03 |
| nuclear_eclipse | please work on dates first | 18:03 |
| nuclear_eclipse | dates *really* need to be fixed for any weekend release | 18:04 |
| nuclear_eclipse | graphs are ancillary fluff | 18:04 |
| paul_ | thursday today/ | 18:04 |
| nuclear_eclipse | yes? | 18:04 |
| paul_ | right | 18:04 |
| paul_ | dinner brb | 18:04 |
| paul_ | bk | 18:15 |
| paul_ | nuclear_eclipse: did you have a summary? | 18:16 |
| nuclear_eclipse | of what? | 18:16 |
| paul_ | what i'd broken ;p | 18:17 |
| nuclear_eclipse | project/version dates, due date field, custom date fields (i think), and any other place that lets the user input a date string | 18:17 |
| [KK]Kirill | paul_: lo | 18:18 |
| paul_ | hi | 18:22 |
| nuclear_eclipse | paul_: http://admin.leetcode.net/apc.php | 18:36 |
| nuclear_eclipse | any suggestions for how to optimize APC configs for a VPS with 360MB memory | 18:36 |
| irenedakota | Get more? :P | 18:37 |
| paul_ | heh | 18:38 |
| irenedakota | I'm paying for a 256mb VPS and getting a 1GB VPS :) | 18:39 |
| paul_ | nuclear_eclipse: step 1: probably run the newer version | 18:39 |
| nuclear_eclipse | paul_: step0: get Ubuntu to include the newer version in their packages ;) | 18:46 |
| * nuclear_eclipse makes a mental note to upgrade to Jaunty | 18:49 | |
| nuclear_eclipse | well, Jaunty is only on 3.0.19... | 18:51 |
| paul_ | nuclear_eclipse: hmm | 19:40 |
| paul_ | nuclear_eclipse: you gone for the night? | 19:51 |
| nuclear_eclipse | paul_: not yet | 19:52 |
| paul_ | in which case | 19:55 |
| paul_ | how do plugins config work | 19:55 |
| nuclear_eclipse | plugins define their default configuration values within their ->config() call, those can be overridden by values in the db via plugin_config_set() | 19:57 |
| paul_ | brb game | 19:57 |
| paul_ | what day are we aiming for? | 19:58 |
| nuclear_eclipse | would like to have it out on saturday if possible | 20:01 |
| paul_ | lol | 20:01 |
| CIA-61 | Mantisbt: jreese * r415b97129196 /core/session_api.php: Fix #10559: Implemented session_delete(). | 20:02 |
| paul_ | jreese: why;/ | 20:12 |
| nuclear_eclipse | because it was part of the original session_api design, I had just never implemented the wrapper function | 20:13 |
| paul_ | I partly feel we shouldn't have foo_bar { foo->bar() } wrappers | 20:22 |
| nuclear_eclipse | well, it's the simplest way to handle singletons that require special initialization :P | 20:23 |
| paul_ | nuclear_eclipse: out of interst, why do we have users reporting bugs on that? | 20:43 |
| nuclear_eclipse | good question | 20:44 |
| nuclear_eclipse | that was actually my first thought, but I assume it's probably to do with plugins and/or custom functions | 20:44 |
| CIA-61 | Mantisbt: jreese * r2b07479de61f / (4 files in 2 dirs): Fix #10217: Implemented configurable action button position. | 20:59 |
| paul_ | need to work out how both works now | 21:00 |
| nuclear_eclipse | time to head home | 21:01 |
| nuclear_eclipse | cheers | 21:01 |
Generated by irclog2html.py