| ../irclogs/#mantishelp.2010-06-11.log | ||
| --- scribe started --- | 00:00 | |
| slestak | i am having difficulty with a 1.16 to 1.2.1 upgrade. I am getting a 403 Forbidden on install.php | 12:39 |
|---|---|---|
| nuclear_eclipse | slestak: sounds like a permissions issue with your web server | 12:48 |
| nuclear_eclipse | ie, do you need to chmod the file to world readable, or do you have a configuration directive preventing access to /admin/? | 12:49 |
| slestak | I dont have /admin/ mentioned at all in apache.conf I will be honest that i am not a web admin. My mantis is only on our intranet. | 13:22 |
| slestak | can I pastebin the relevant section maybe? | 13:22 |
| nuclear_eclipse | sure | 13:25 |
| nuclear_eclipse | slestak: you could also try running `chmod -R go+rX /path/to/mantisbt` to make sure read permissions are set | 13:26 |
| slestak | i checked the perms on the files and they are 644 for my user:user | 13:27 |
| slestak | i thnk they should be owned be the apache user? | 13:27 |
| slestak | but 644 still gives world readable | 13:27 |
| nuclear_eclipse | yeah, 644 should be sufficient | 13:28 |
| slestak | okay, the chmod helped, I am at least exeuting sth now. Got app error 401 | 13:29 |
| slestak | Database query failed. Error received from database was #1146: Table 'bugtracker.mantis_plugin_table' doesn't exist for the query: SELECT COUNT(*) FROM mantis_plugin_table WHERE basename=?. | 13:29 |
| nuclear_eclipse | unless you're running SELinux or AppArmor, in which case there might be some other ACLs in place that you need to take into consideration | 13:29 |
| slestak | let me rtfm again, ty for getting me poast that perms bump | 13:29 |
| slestak | tere may be, I just dist upgraded ubuntu server | 13:29 |
| slestak | that looks like check.php is lookign for plugin table. I have not run install.php yet so my 1.1.6 db wont have the new tables | 13:31 |
| slestak | its working now | 13:32 |
| nuclear_eclipse | slestak: congrats :) | 13:32 |
| slestak | nuclear_eclipse: ty again for your fine project. my office is shopping for help desk software, but I am going to try to hold on to my mantis with a tight grip (at least for developers). | 13:33 |
| slestak | my helpdesk ppl and hardware ppl dont want to use it though | 13:34 |
| nuclear_eclipse | hehe | 13:34 |
| nuclear_eclipse | good luck on that :) | 13:34 |
| slestak | which is ok, there is not asset management and whatnot that they are asking for. im hoping we can keep both | 13:34 |
| slestak | one feature thay are not able to provide for me with the packages they are looking at is vcs integration. I hope that will be enough to keep what i have. | 13:35 |
| nuclear_eclipse | slestak: have you seen the VCS integration plugins available for 1.2? | 13:41 |
| slestak | i am looking at the site now, but most of what I see is docs from 2008 and back | 13:42 |
| slestak | is mantisforge or mantisbt the best site to check? | 13:42 |
| slestak | I have checked both and I do not see a contrib section with plugins | 13:44 |
| slestak | i see some things on svn. hoping to see hg soemwhere. | 13:45 |
| nuclear_eclipse | git.mantisforge.org has a list of plugins available as git repositories | 13:47 |
| nuclear_eclipse | I wrote a set of VCS integration plugins based around a generalized framework | 13:48 |
| nuclear_eclipse | it currently supports SVN and Git, and just needs someone familiar with Hg to write a plugin for it :) | 13:48 |
| nuclear_eclipse | dhx_m wrote a first draft plugin for Hg, but iirc he never got around to updating it for some of the framework redesigns I made | 13:49 |
| nuclear_eclipse | so maybe you could get in touch with him about finalizing that plugin, and then I can include it in the main repo/release | 13:49 |
| slestak | i am not a vcs pro, trying to implement it in my shop. | 13:52 |
| slestak | i will look for the work that is started and see what remains to be done. | 13:53 |
| nuclear_eclipse | slestak: iirc, dhx_m's plugin was more or less did a scrape of an hgweb install, so it didn't actually work with the hg command | 13:54 |
| nuclear_eclipse | I'll see if I can dig up the WIP code | 13:54 |
| nuclear_eclipse | ah ha: http://git.mantisforge.org/w/source-integration/dhx.git | 13:56 |
| nuclear_eclipse | it looks like he updated it a few months ago for the redesign while I wasn't paying attention | 13:56 |
| slestak | did he bail so we dont hav eto discuss it :) | 13:57 |
| nuclear_eclipse | hehe | 13:58 |
| nuclear_eclipse | damn aussies | 13:58 |
| slestak | thats a beaut! | 13:58 |
| nuclear_eclipse | think they have some excuse about being on the other side of the world | 13:58 |
| nuclear_eclipse | slestak: at a glance, it looks like the latest form of his plugin might actually work correctly with the framework, assuming you have a publicly-accessible hgweb install for each repo you want to integrate | 13:59 |
| slestak | at a minimum, I think I would like to append a list of changesets to an issue | 14:00 |
| slestak | would rahter they not be a comment field. Have you ever seen teh Files Modified plugin for Trac? | 14:00 |
| nuclear_eclipse | slestak: you can see an example of what the integration plugins do on the tracker at mantisbt.org, or on my tracker at http://leetcode.net/mantis | 14:01 |
| slestak | ty | 14:01 |
| nuclear_eclipse | I personally disliked the old approach of "note per commit", thought it was both ugly and mostly useless | 14:02 |
| slestak | yes | 14:02 |
| nuclear_eclipse | these plugins actually track a lot of the commit metadata in the database so that it can be attached to multiple issues, be searchable, etc | 14:03 |
| nuclear_eclipse | it can quickly balloon your database though if you're importing repos with really large histories, but it generally doesn't affect performance unless you're explicitly searching/browsing changeset data | 14:04 |
| slestak | i liek the Repo tab. What I am considering is a block in the ticket for Changesets | 14:07 |
| nuclear_eclipse | yep, that's already there :) | 14:09 |
| nuclear_eclipse | http://leetcode.net/mantis/view.php?id=144 | 14:09 |
| nuclear_eclipse | that's an issue that has an attached changeset | 14:10 |
| nuclear_eclipse | actually, it's also a good example of some of the optional automation you can use with the framework | 14:10 |
| nuclear_eclipse | when I committed to the repository, it was able to automatically set the fixed-in version, resolve the issue, and add a bugnote, just based on the changeset's commit message | 14:11 |
| slestak | that is exactly what I have been describing to my people | 14:16 |
| nuclear_eclipse | :) | 14:16 |
| nuclear_eclipse | wb dhx_m | 14:16 |
| slestak | i have had to walk around my office asking "did you change this", "are you sure" | 14:16 |
| slestak | for entirely too dang long :) | 14:16 |
| nuclear_eclipse | hehe | 14:20 |
| nuclear_eclipse | I just like being able to a) go back and easily find the changesets for a bug report, and b) being able to automate some tasks just by committing with specific message patterns | 14:21 |
| nuclear_eclipse | and of course, being able to do all that from any type of VCS I'm using | 14:21 |
| slestak | and also be able report easily on all the projects that have touched module foo | 14:22 |
| nuclear_eclipse | yep | 14:22 |
| slestak | thx, this is what i was lookign for. | 14:23 |
| nuclear_eclipse | you're welcome | 14:23 |
| slestak | dhx_m: do you want some assistance with the hgqweb plugin? I am not a dev but I would be glad to test | 14:23 |
| slestak | hgweb* | 14:23 |
| nuclear_eclipse | maybe you should just convert everything to Git ;) | 14:24 |
| nuclear_eclipse | /shameless plug | 14:24 |
| nuclear_eclipse | time to go to a meeting | 14:25 |
| nuclear_eclipse | slestak: feel free to ping me here anytime, on the developer mailing list, or report a bug on my tracker if you have any issues with the plugins | 14:25 |
| slestak | i think in teh long run we all have to have a working knowledge of git|hg|bzr | 14:40 |
| slestak | i actually prefer bzr, but have issue installing it on my aix box. Hg is already installed. I have a very loose environemnt here with some kickback on all of this so I think git may be too much for them. I am counting on Tortoise to make any vcs palatable to them | 14:41 |
| dhx_m | nuclear_eclipse: hi :) | 15:04 |
| dhx_m | slestak: testing should be OK... the plugin "works" at the moment except that it doesn't actually parse the changeset to find which files changed | 15:05 |
| slestak | do all the hgweb repos have to hosted on the mantis webhost? | 15:07 |
| dhx_m | also my draft HgWeb plugin doesn't allow you to import using a local hg binary (importing from a local repository clone)... so it's slow via HgWeb | 15:08 |
| dhx_m | HgWeb also didn't have a way to easily parse out which files changed last time I checked | 15:08 |
| dhx_m | no, they can be hosted anywhere | 15:08 |
| dhx_m | I'm still busy for the next week but after that time I plan to catch up with MantisBT development | 15:12 |
| dhx_m | and get 1.2.2 out the door :) | 15:12 |
| slestak | Oh, HgWeb clones the repo local to its webroot? | 15:14 |
| slestak | Im a vcs noob, but know that I need it | 15:14 |
| dhx_m | not sure... I use Git :) | 15:14 |
| slestak | well, mantis scm integration. Does it make a local copy of the git repo, or does it refer to the remote repo directly? | 15:15 |
| dhx_m | the idea with SourceIntegration is that you can pull VCS data from a web interface (Gitweb, WebSVN, HgWeb, etc) or by using a local SVN binary to pull commit messages | 15:15 |
| dhx_m | s/SVN/SVN or git or HG/ | 15:15 |
| slestak | yes | 15:15 |
| slestak | is this data indexed and put into mantis's db so once it is crawled it can be gotten to quickly, or is it recreated each time? | 15:16 |
| dhx_m | it's ridiculously slow to pull 10,000 commit messages via the web :) | 15:16 |
| dhx_m | yes it's placed in the database... but not the entire commit messages AFAIK | 15:16 |
| dhx_m | it's just the commit message, author information and list of files changed/deleted/added/etc | 15:17 |
| slestak | perfect. | 15:17 |
| tcplomp | dhx_m are you dhx? | 15:33 |
| dhx_m | tcplomp: yep | 15:34 |
| tcplomp | Hi, I have been playing with the hgweb Source integration you placed in mantisforge and have (finally) got the incoming hook working. What would be a good place to write a bit on this? All in all I am missing a platform for the source integration (like a KB). | 15:36 |
| dhx_m | tcplomp: perhaps a blog post? | 15:39 |
| dhx_m | tcplomp: my plugin is still incomplete and I haven't tried it against the latest version of MantisBT 1.3.x yet | 15:39 |
| dhx_m | it's on the TODO list | 15:39 |
| dhx_m | grrr one of my monitors just died | 15:41 |
| tcplomp | Or would the MantisBT.org wiki be a good place. There is definitly a need for more documentation of the source integration when debugging. | 15:42 |
| dhx_m | I guess it could be placed there, nuclear_eclipse might have a better idea :) | 15:43 |
| dhx_m | aaaargh single monitor sucks | 15:46 |
| dhx_m | I feel like I'm back in 1995 | 15:46 |
| slestak | nu-uhh | 15:46 |
| slestak | j/k | 15:46 |
| slestak | i have a 25" widescreen | 15:46 |
| slestak | well, 24" | 15:47 |
| dhx_m | what resolution? | 15:47 |
| slestak | 1920x1280 | 15:47 |
| slestak | samsung syncmaster 2494hm | 15:47 |
| slestak | my ocd kills me with an even number of monitors when apps start straddling the centerline | 15:48 |
| slestak | so I'd have to have 3 | 15:48 |
| dhx_m | yeah I'd like 3... would need more space though | 15:49 |
| slestak | one widescreen is working well, and the prices have dropped a lot | 15:50 |
| dhx_m | I'm surprised that there aren't any thin bezel LED monitors at the moment? | 15:50 |
| slestak | got my wife a 23 16:9 samsung locally for 177 new in box | 15:50 |
| slestak | i usually have my laptop on the desk too, so i wiull have some content there too | 15:51 |
| dhx_m | I don't like the idea of mixing monitors (ie. difference sizes/styles) | 15:51 |
| slestak | i know, that bugged me too. when i did do dual, I had a quality viewsonic next to a crap Planar. drove me crazy | 15:52 |
| slestak | I gave up the VS to get another planar, and the color was still different | 15:52 |
| slestak | more trouble than its worth | 15:52 |
| dhx_m | yep | 15:59 |
| nuclear_eclipse | tcplomp: hi | 16:30 |
| nuclear_eclipse | tcplomp: I'd like to get a full set of documentation four the source integration system written up and included in the source integration repo | 16:32 |
| nuclear_eclipse | s/four/for | 16:32 |
| nuclear_eclipse | if you're willing to write some documentation for various source integration topics, I'd greatly appreciate all the help I could get | 16:33 |
| tcplomp | nuclear_eclipse: Ok I will see what I can get written. I assume it's all stored in a GIT repo? | 17:00 |
| nuclear_eclipse | tcplomp: there's nothing to start from, but yes, I want to keep it all in the existing source-integration.git repo on mantisforge, and then I can make it available on my website for viewing | 17:04 |
| nuclear_eclipse | if you're familiar with Markdown format, that's what I would like to use | 17:05 |
| tcplomp | nuclear_eclipse: let me see what I can come up for in the next week or 2. You should have my email address in your leetcode bugtracker. | 17:05 |
| tcplomp | Is there a Markdown interpreter or something on Windows? I have been using Markdown on Stackoverflow, but that was just for short texts (nothing fancy) | 17:07 |
| nuclear_eclipse | if you can run Python, PHP or Perl, there are Markdown implementations for all three | 17:08 |
| nuclear_eclipse | the Perl implementation is the "canonical" version, if that matters to you, but the other two are compatible | 17:09 |
| slestak | this may work http://codeboje.de/wysiwyg-markdown-editor/ | 17:19 |
| tcplomp | slestak thanks! I'll give it a go | 17:21 |
| slestak | it looks very alpha, but you'll get your moneys worth | 17:21 |
| tcplomp | For starters I would like to document the needs for the hgweb integration. Could somebody create this page http://www.mantisbt.org/wiki/doku.php/mercurial_source_control_integration and give me (tcplomp) write access? | 17:42 |
| nuclear_eclipse | tcplomp: I'd rather keep documentation about plugins off of the wiki, a) afaik it doesn't really get used much, and b) would rather create some generic info that points to the source integration plugin's documentation | 17:45 |
| tcplomp | I would just simply put the changes I made and store my mercurial hooks for the general public, not really going into the details | 17:48 |
| slestak | what about sth like sphinx? | 17:49 |
| slestak | I think it stores its data as marksown | 17:49 |
| nuclear_eclipse | nope | 17:49 |
| slestak | s/s/d | 17:49 |
| nuclear_eclipse | sphinx uses textile | 17:49 |
| nuclear_eclipse | and it's just as painfully complex and finicky to set up as something like Docbook | 17:50 |
| slestak | yeah | 17:50 |
| nuclear_eclipse | I don't want to have to set up an entire toolchain and build process for documentation | 17:50 |
| slestak | i researched doc tool recently, and sphinx was looking pretty complex | 17:50 |
| nuclear_eclipse | slestak: I've been working on something recently that acts as a preprocessor to markdown to give a lot of the benefits of complex documentation tools, without needing to jump through a lot of hoops to do it | 17:53 |
| tcplomp | dhx_m: in the SourceHgWeb commit function you validate, the branch, I am not sure if that's the route to go for Mercurial. I commented these lines out to be able to checkin files from the mercurial hooks. Have you tested that functionality | 17:55 |
| slestak | i think the problem is we cannot even decide where the docs should live | 17:55 |
| nuclear_eclipse | slestak: for your own project, or for mantis you mean? | 17:57 |
| rolfkleef | if it's ok to break in with a question to devs about closing some bugs...? | 17:59 |
| nuclear_eclipse | hi rolfkleef :) | 17:59 |
| rolfkleef | there are a couple of (I think) duplicate issues about admin/move_db2disk.php and I'd like to close a couple | 17:59 |
| slestak | nuclear_eclipse: mantis plugins | 18:00 |
| slestak | tcplomp's question is similar to mine from 2 hours earlier. I installed 1.2.1 but couldnt find any docs on either mantisforge or mantisbr.org that looked newer than 2008 | 18:00 |
| nuclear_eclipse | slestak: I think the problem is that we don't even have a well-defined documentation or development process for the core project, so third party plugin handling is like the wild west | 18:01 |
| slestak | yeah | 18:01 |
| rolfkleef | http://www.mantisbt.org/bugs/view.php?id=7176 could be the one that stays, and http://www.mantisbt.org/bugs/view.php?id=11591 , 9495 and 5836 resolved as duplicates? | 18:01 |
| slestak | im not complaining, | 18:01 |
| nuclear_eclipse | rolfkleef: seems reasonable after a first glance | 18:03 |
| rolfkleef | (I can do that, just wanted to make sure my first real contribution to tracker maintenance isn't breaking rules I don't know yet :-)) | 18:03 |
| nuclear_eclipse | rolfkleef: if only we had rules to break :P | 18:03 |
| nuclear_eclipse | rule #1: do whatever you think is best; rule #2: umm..... :P | 18:04 |
| rolfkleef | be careful what you say :-) someone might start a wiki page on Hg integration since it doesn't break any rules ;-) | 18:04 |
| rolfkleef | I'll go ahead with those issues then | 18:05 |
| slestak | tcplomp: what about make a git repo at mantisforge with your doc contribs and we can determine how they get published after written? | 18:06 |
| slestak | then your docs can be versioned as well? | 18:06 |
| nuclear_eclipse | well, if they really want to start that wiki page, I aint gonna stop them; it's not like I've looked at the wiki in the past 8 months... =\ | 18:06 |
| nuclear_eclipse | tcplomp: you could also fork the source-integration.git repo and add your docs there, and eventually work on merging them upstream | 18:07 |
| tcplomp | slestak: I'm fine with that (I hope I can use hg as a mantisforge client, don't need a 5th SCC to install) Let me think about the fork, that sounds interesting. | 18:08 |
| slestak | or host your docs on your own hg | 18:09 |
| tcplomp | [slightly off topic] in Amsterdam we should have a positive offset to GMT, right (meaning that the US would have a negative offset)? | 18:09 |
| nuclear_eclipse | tcplomp: http://hg-git.github.com/ | 18:09 |
| nuclear_eclipse | correct | 18:09 |
| nuclear_eclipse | I'm GMT-400 in the east US | 18:10 |
| tcplomp | oops, think I found a wee bug in Mercurial raw-rev output | 18:11 |
| slestak | -4 or -5? | 18:19 |
| slestak | oh, dst | 18:19 |
| nuclear_eclipse | slestak: tbh, I don't know which atm, DST is really confusing | 18:20 |
| slestak | its finally drying out here in MI, where you guys at | 18:21 |
| nuclear_eclipse | jreese@T00529019 ~ ยป date | 18:21 |
| nuclear_eclipse | Fri Jun 11 14:21:15 EDT 2010 | 18:21 |
| nuclear_eclipse | I'm near Cincinnati, OH -- it's ungodly humid, hot, and stale | 18:22 |
| slestak | cool. used to have a bunch of friends in Middletown | 18:23 |
| slestak | i have no idea sometimes why business spends so much money on proprietary software | 18:24 |
| slestak | look at this issue. I have been working on this error for 3 weeks with my var and IBM support | 18:24 |
| slestak | http://www.mail-archive.com/u2-users@listserver.u2ug.org/msg26456.html | 18:24 |
| slestak | and it appears it was reported to them in $(^*&^ 2008 | 18:25 |
| tcplomp | I am in Amsterdam with DST so I should have an offset of +02:00 or +7200, my raw-rev output is though -7200, making my repo-commits 4 hours off (and yes for an anal-retentive person like me that's important) | 18:25 |
| slestak | timestamps have to be right. | 18:26 |
| nuclear_eclipse | that would drive me crazy too | 18:27 |
| nuclear_eclipse | I spent about 20 minutes the other day rewriting a branch history because I'd been committing using the wrang email address :P | 18:27 |
| slestak | u can do that in git? | 18:28 |
| nuclear_eclipse | yep | 18:28 |
| nuclear_eclipse | good thing it wasn't a public branch though :P | 18:28 |
| nuclear_eclipse | the simple way is doing a `git commit --amend --author="Author Name <email@domain>"` | 18:29 |
| nuclear_eclipse | but to do a whole branch, I ended up writing a complex `git filter-branch ...` command to automatically do that | 18:30 |
| nuclear_eclipse | same sort of thing I wrote when Mantis moved from SVN to Git and we converted all the SVN usernames to realnames + email | 18:31 |
| tcplomp | Uhm, I don't have my email in my (local) mercurial repo, so I edited the hgweb.php to add <no@email> in the commit function if no email address was found. I don't see why these are required in the 'source' table for changesets | 18:50 |
| slestak | i found the recent docs at mantisforge | 18:52 |
| slestak | can someone point me to plugin install docs? not seeign it at http://mantisforge.org/dev/manual/en/administration_guide/ | 18:53 |
| slestak | looks like just drop them into plugins and then modify plugin.php or plugin_file.php | 18:56 |
| nuclear_eclipse | tcplomp: you should be able to just use a blank string "" for author email -- the only "need" for it is to help match authors to user accounts in mantis | 18:57 |
| nuclear_eclipse | slestak: extract the plugin into mantisbt/plugins/ and then go to Manage Plugins in Mantis to install them | 18:58 |
| tcplomp | Well I got an application error, I think that the hgweb put a 'null' field instead of a n empty field. | 18:58 |
| nuclear_eclipse | that's possible | 18:58 |
| tcplomp | so that would be a bug for dhx_m ;-) | 18:58 |
| slestak | i apologoze, i dont see a raw or dl link on the changeset | 18:58 |
| slestak | lookign at the tag for the 0.8.1 stable release of EmailReporting | 19:00 |
| nuclear_eclipse | gitweb calls it "snapshot" | 19:00 |
| nuclear_eclipse | you probably need to click on the tag in gitweb, and then click snapshot on the next page | 19:00 |
| slestak | wierd, 3 clicks in | 19:00 |
| slestak | snapshot is on the "tree" field? | 19:01 |
| nuclear_eclipse | http://git.mantisforge.org/w/EmailReporting.git?a=commit;h=8891a2a05cf78f556059fe79d309f230b9c2ecf8 | 19:01 |
| nuclear_eclipse | /shrug | 19:01 |
| nuclear_eclipse | I prefer Github tbh :P | 19:02 |
| slestak | k. i know i have elementary questions, taking hg, bzr, and git all in at once | 19:02 |
| nuclear_eclipse | np | 19:02 |
| slestak | basically, anything but svn|cvs | 19:02 |
| tcplomp | any idea how to easily create a bunch of repositories (like 40), I assume it takes some SQL voodoo | 19:03 |
| slestak | sql? maybe shell scripting | 19:03 |
| nuclear_eclipse | one by one :P | 19:03 |
| slestak | you just trying to get a busy page? | 19:04 |
| tcplomp | not really, I had an SVN repo of 40 folders (projects) that I converted into 40 mercurial repos. I'll add them when I need them. | 19:05 |
| kirillka | nuclear_eclipse: around? | 20:01 |
| nuclear_eclipse | hi kirillka | 20:06 |
| kirillka | nuclear_eclipse: Can you help me with git? | 20:06 |
| kirillka | I try ask in #git, but all sleep | 20:06 |
| kirillka | nuclear_eclipse: http://support.github.com/discussions/repos/3316-how-i-can-re-push-repo | 20:08 |
| nuclear_eclipse | kirillka: try `git push -f origin master` | 20:18 |
| kirillka | nuclear_eclipse: thanks. you don't help, but after this I reread man and see git push --tags | 20:23 |
| kirillka | I add tag and push | 20:23 |
| minimoo | moo | 22:08 |
| minimoo | nuclear_eclipse / dhx_m | 22:08 |
Generated by irclog2html.py