| ../irclogs/#mantishelp.2009-06-08.log | ||
| --- scribe started --- | 00:00 | |
| mantisbot | New bug: Bug 10571 - sheejamantis - open - new | 07:55 |
|---|---|---|
| mantisbot | New bug: Link not working - http://www.mantisbt.org/bugs/view.php?id=10571 | 07:55 |
| nuclear_eclipse | paul_: there? | 12:25 |
| nuclear_eclipse | pa | 13:24 |
| nuclear_eclipse | hmm, paul not here... =\ | 13:25 |
| irenedakota | How do I uninstall a plugin properly? | 14:21 |
| nuclear_eclipse | irenedakota: depends on how uninstalled you want it; doing "uninstall" from the manage plugins page is more akin to disabling the plugin | 14:25 |
| nuclear_eclipse | if you're looking for a permanent uninstall, then you can uninstall through the UI, and then drop tables from the database named like plugin_<plugin>_*table, and then delete the plugin from the filesystem | 14:26 |
| irenedakota | never mind, figured it out | 14:34 |
| irenedakota | How do I use the source-integration plugin for 1.2 to integrate with Github? | 14:41 |
| nuclear_eclipse | irenedakota: github integration is not working atm; I suspect GitHub changed their API, and I just need to get the time to investigate | 14:52 |
| irenedakota | Hi again. | 15:01 |
| irenedakota | Anyway, how do I import Github info? | 15:01 |
| nuclear_eclipse | irenedakota: github integration is not working atm; I suspect GitHub changed their API, and I just need to get the time to investigate | 15:02 |
| CIA-61 | Mantisbt: jreese * r33743493f968 /docbook/developers/en/ (3 files): Event reference title and layout consistency. | 15:28 |
| CIA-61 | Mantisbt: jreese * r6346e360b5f9 /docbook/developers/en/event-reference-bug.sgml: Removed some inline <programlisting> elements that used to be <code>, as they break the layout. | 15:28 |
| CIA-61 | Mantisbt: jreese * rddb8b7c3fa75 /docbook/developers/en/event-reference.sgml: Documented EVENT_CORE_READY. | 15:28 |
| CIA-61 | Mantisbt: jreese * r78ddc8d76186 /docbook/developers/en/event-reference-bug.sgml: Documented the REPORT_BUG* events. | 15:28 |
| CIA-61 | Mantisbt: jreese * r120447b4e9c2 /docbook/developers/en/ (3 files): Added documentation page for user account events. | 15:28 |
| CIA-61 | Mantisbt: jreese * r6ff9f5e1201a /docbook/developers/en/event-reference-bug.sgml: Documented UPDATE_BUG* events. | 15:28 |
| CIA-61 | Mantisbt: jreese * rc38e1152f125 /docbook/developers/en/event-reference-bug.sgml: Documented remaining bug action events. | 15:28 |
| CIA-61 | Mantisbt: jreese * r29f7e63a7eb0 /docbook/developers/en/event-reference-manage.sgml: Documented MANAGE* events. | 15:28 |
| CIA-61 | Mantisbt: jreese * rb17ba8dea561 /docbook/developers/en/event-reference-bug.sgml: Documented BUGNOTE* events. | 15:29 |
| CIA-61 | Mantisbt: jreese * r2742f8db024e /docbook/developers/en/event-reference-account.sgml: Documented ACCOUNT_PREFS* events. | 15:29 |
| nuclear_eclipse | blam! | 15:29 |
| daryn | good lord | 15:29 |
| nuclear_eclipse | we have documentation now! | 15:29 |
| daryn | real documentation? that isn't possible... | 15:31 |
| nuclear_eclipse | well, it *is* confined to just the event reference sections :P | 15:31 |
| daryn | :) | 15:31 |
| daryn | at least it's a start | 15:32 |
| CIA-61 | Mantisbt: jreese * r5db9ffaef06c /docbook/template/stylesheet.css: Updated docbook templates to use slightly smaller font, and prefer sans-serif font faces. | 15:45 |
| mib_ursng7 | Hi, Anybody knows where I could get a wiki plugin for Mantis 1.2? | 15:52 |
| mib_ursng7 | http://www.mantisbt.org/blog/?p=19 says 2 have been developped but can't find any | 15:52 |
| nuclear_eclipse | mib_ursng7: those are included out of the box with Mantis | 15:53 |
| nuclear_eclipse | look into config_defaults_inc for wiki settings, and copy those to your config_inc.php and make changes there | 15:54 |
| mib_ursng7 | great thanks. Which engine do you recommend? | 16:24 |
| MkJackson | Hey Folks, is there any way I can make it so that certain people are notified EVERY time a new bug is reported? right now only I (the admin) get notified... | 16:32 |
| mib_ursng7 | none of the wikis in there seem installed. I use 1.2.0 | 16:37 |
| nuclear_eclipse | mib_ursng7: you'll need to install an external wiki system yourself; the integration system in 1.2 is just a method of linking from mantis to the wiki | 17:18 |
| nuclear_eclipse | MkJackson: go to manage configuration -> email notifications, or optionally look into config_defaults_inc for how to set $g_notify_flags in your config_inc | 17:22 |
| MkJackson | nuclear_eclipse: thanks, I (should have done this first) checked the manual a bit and decided to add to the config_inc.php "$g_notify_flags['new']['threshold_max'] = DEVELOPER; $g_notify_flags['new']['threshold_max'] = MANAGER;" | 17:22 |
| MkJackson | hopefully that will do the trick | 17:24 |
| irenedakota | hi there | 17:25 |
| nuclear_eclipse | hello | 17:33 |
| irenedakota | Hopefully my connection is stable enough now to actually ask my question | 17:41 |
| irenedakota | I'm trying to figure out how to get the source-integration plugin to work with github. I enter all the details, but when I click on the import everything button, it doesn't import anything | 17:46 |
| nuclear_eclipse | irenedakota: github integration is not working atm; I suspect GitHub changed their API, and I just need to get the time to investigate | 17:49 |
| irenedakota | ah ok. | 17:55 |
| --- scribe started --- | 18:02 | |
| irenedakota | In which case it gave a database error | 18:02 |
| nuclear_eclipse | ah, gotcha | 18:02 |
| irenedakota | hence why I added it | 18:02 |
| nuclear_eclipse | ok, hadn't considered that case | 18:02 |
| irenedakota | neither had I, wouldn't have caught if our router isn't having issues | 18:03 |
| irenedakota | is json_url a Mantis function? | 18:03 |
| nuclear_eclipse | irenedakota: what's your preferred author name, or do you not care about attribution? | 18:03 |
| irenedakota | dakota, but it doesn't really bother me | 18:04 |
| nuclear_eclipse | yes, json_url() is a mantis api wrapping curl+json | 18:04 |
| irenedakota | That would explain why it isn't in the php manual :) | 18:04 |
| nuclear_eclipse | yep :P | 18:04 |
| nuclear_eclipse | and by author name, git wants "First Last <email@domain>" style | 18:05 |
| irenedakota | Alright. Walther Lalk <wlalk@cmscout.co.za> | 18:06 |
| nuclear_eclipse | cheers | 18:06 |
| irenedakota | This would be why I choose mantis over the others I looked at. I can actually fix issues if I find them :) | 18:07 |
| nuclear_eclipse | ;) | 18:07 |
| nuclear_eclipse | thanks for taking the time to find it | 18:08 |
| irenedakota | not a problem | 18:08 |
| nuclear_eclipse | I've pushed both fixes, so you can pull them to your checkout now | 18:08 |
| nuclear_eclipse | paul_: any chance I could ever specify custom hooks for the repos on mantisforge.org ? | 18:11 |
| paul_ | I don't see why not.. | 18:13 |
| paul_ | btw, I git supports submodules right? | 18:15 |
| nuclear_eclipse | somewhat | 18:15 |
| nuclear_eclipse | it's rather clunky and unintuitive, IMO | 18:15 |
| paul_ | hmm ;/ | 18:15 |
| paul_ | I was thinking that could be something nice to use ;/ | 18:16 |
| irenedakota | Mmmm, I'm getting "APPLICATION WARNING #2702: Your session has become invalidated." when I try to access the repository plugin now | 18:17 |
| nuclear_eclipse | it would be, but everytime I try to figure it out, I get lost on what I need to be doing, and go work on something else =\ | 18:17 |
| nuclear_eclipse | irenedakota: are you behind a proxy with multiple exit points? | 18:18 |
| irenedakota | Might be. Currently running via my cell, ADSL is bonkers tonight. | 18:18 |
| nuclear_eclipse | ah, then that's probably the problem | 18:19 |
| irenedakota | It's perfectly happy letting me into the manage section, just throwing the error when I try to access repositories | 18:19 |
| irenedakota | Ok. | 18:19 |
| nuclear_eclipse | set $g_session_validation == OFF in your config_inc.php to stop that | 18:19 |
| nuclear_eclipse | I've got a side project in the works that will allow users to selectively enable/disable session validation at the time of login, rather than enforcing it on/off site-wide | 18:20 |
| irenedakota | Thanks. | 18:21 |
| nuclear_eclipse | np | 18:21 |
| irenedakota | That would be handy | 18:21 |
| paul_ | nuclear_eclipse: incidently, I still want to change .sgml->.xml | 18:22 |
| irenedakota | mmmm, same error | 18:23 |
| nuclear_eclipse | irenedakota: wonder if your cell company is caching the error page =\ | 18:23 |
| irenedakota | Wouldn't surprise me. | 18:24 |
| nuclear_eclipse | irenedakota: just realized I put two "=" in my example to you; make sure you only have one in your config_inc | 18:25 |
| irenedakota | our internet providers love to use horribly configure transparent proxies | 18:25 |
| irenedakota | nuclear_eclipse: Saw when I pasted into the file | 18:25 |
| nuclear_eclipse | k | 18:25 |
| irenedakota | Ah, there we go | 18:26 |
| irenedakota | Thanks | 18:26 |
| irenedakota | Adding a comma-seperated list of primary branches for the github plugin causes an error. | 18:31 |
| nuclear_eclipse | hmm | 18:32 |
| irenedakota | Application Error #0 to be exact | 18:33 |
| nuclear_eclipse | well, there's only ten places in the code that throw error #0 :P | 18:34 |
| irenedakota | ah, found the problem. The branch I'm trying has a . (period) in it's name | 18:35 |
| irenedakota | And the regex doesn't accept periods as a valid character | 18:36 |
| nuclear_eclipse | k | 18:37 |
| nuclear_eclipse | I'm surprised I haven't come across that one yet :P | 18:39 |
| nuclear_eclipse | fixed and pushed | 18:39 |
| irenedakota | Suppose I'm just good at find edge cases :) | 18:39 |
| paul_ | nuclear_eclipse: do version dates seem to be working now? | 18:40 |
| nuclear_eclipse | I wouldn't even call that an edge case; the mantisbt.git repo uses periods in branch names :P | 18:40 |
| nuclear_eclipse | paul_: yes, version dates are working | 18:40 |
| nuclear_eclipse | due dates still are not | 18:40 |
| irenedakota | What do the various source integration features do? | 18:41 |
| nuclear_eclipse | a lot :P | 18:41 |
| paul_ | what do duedates fail at? | 18:41 |
| nuclear_eclipse | I've started some documentation on the matter, but nothing very complete | 18:41 |
| nuclear_eclipse | paul_: when report/update a bug, due_date breaks because it doesn't properly handle the date string from the user | 18:42 |
| nuclear_eclipse | irenedakota: quick rundown is: | 18:42 |
| nuclear_eclipse | branch mappings allows you to map changesets wwith a "fixed" issue to automatically set the issue's fixed-in-version field... | 18:43 |
| nuclear_eclipse | resolve fixed issues will similarly use the fixed regex to auto-resolve any fixed issues, and bug fixed message will automatically add a note to the issue at the same time | 18:45 |
| nuclear_eclipse | porting status is altogether different, and allows changesets to track a "porting status", ie whether the commit has been ported to other branches, or doesn't need to be ported anywhere | 18:45 |
| paul_ | nuclear_eclipse: still in current trunk? | 18:46 |
| nuclear_eclipse | afaik, yes | 18:46 |
| paul_ | erm | 18:47 |
| paul_ | does trunk still run? | 18:47 |
| * paul_ tries to work out what he's done | 18:48 | |
| paul_ | anyway, reason I asked about submodules | 18:48 |
| paul_ | is that could be a nice way to structure stuff | 18:48 |
| nuclear_eclipse | irenedakota: I use the "fixed" regex stuffs on my tracker, so that when I commit an issue to source-integration.git with a message of "Fix #123: blah", it not only sets the issue's fixed-in version to "0.X", it adds a note "Fix committed to <branch> at <time>." and resolves the issue, all automatically when it imports the changeset | 18:48 |
| nuclear_eclipse | submodules aren't really "useful" for anything but having a "simple" method to pull in external project repositories, generally meant for handling lib depends, etc | 18:49 |
| paul_ | exactly, docbook/adodb/plugins... | 18:50 |
| nuclear_eclipse | well, plugins, yes | 18:51 |
| nuclear_eclipse | docbook, no | 18:51 |
| nuclear_eclipse | adodb, yes | 18:51 |
| irenedakota | nuclear_eclipse: Thanks. Understand what they are doing now. | 18:51 |
| nuclear_eclipse | but really, docbook and core plugins should still be contained within the core repository | 18:51 |
| paul_ | argh | 18:59 |
| paul_ | nuclear_eclipse: can you review a function? | 19:01 |
| paul_ | error: patch failed: bug_view_advanced_page.php:43 | 19:03 |
| paul_ | error: bug_view_advanced_page.php: patch does not apply | 19:03 |
| paul_ | error: patch failed: bug_view_inc.php:29 | 19:03 |
| paul_ | error: bug_view_inc.php: patch does not apply | 19:03 |
| paul_ | error: patch failed: bug_view_page.php:44 | 19:03 |
| nuclear_eclipse | good luck on that :P | 19:06 |
| paul_ | .... | 19:07 |
| paul_ | so erm | 19:08 |
| paul_ | wtf ? :) | 19:08 |
| paul_ | why error and not a conflict | 19:08 |
| paul_ | right, how can I generate a diff of that branch | 19:09 |
| nuclear_eclipse | that is a conflict... | 19:12 |
| nuclear_eclipse | what command did you run? | 19:12 |
| paul_ | rebase | 19:12 |
| nuclear_eclipse | then it's probably stopped on that commit, waiting for you to fix the conflicts, `git add` the conflicting files, and then do `git rebase --continue` | 19:12 |
| paul_ | but i need to know what's wrong | 19:13 |
| paul_ | I aborted tbh | 19:13 |
| paul_ | might just make a patch | 19:13 |
| nuclear_eclipse | making a patch is no different than running rebase.... | 19:13 |
| nuclear_eclipse | hi siebrand | 19:34 |
| CIA-61 | Mantisbt: jreese master-1.1.x * rd6cffa48fcaa / (core/constant_inc.php doc/ChangeLog): Updating for 1.1.8 release. | 19:56 |
| nuclear_eclipse | hi vb123 | 20:09 |
| nuclear_eclipse | I investigated your issues with Git, and could not find any problems, so I cherry-picked the commit for you, and I'm rollng the 1.1.8 release atm so we can be done with 1.1.x forever | 20:10 |
| vb123 | ok thanks nuclear_eclipse . Do we have the set of steps to cherry pick from trunk to 1.1.x or to 1.2.x in the future? | 20:13 |
| vb123 | maybe I'm doing something wrong. | 20:14 |
| nuclear_eclipse | well, it should be as simple as `git checkout <branch>; git cherry-pick <ref>` | 20:14 |
| vb123 | e.g. clone repo, switch to 1.1.x, cherry pick, commit, push. | 20:14 |
| nuclear_eclipse | `git cherry-pick -s <ref>` is preferred if you're porting a commit made by someone else... | 20:14 |
| vb123 | do you push after cherry pick? | 20:15 |
| nuclear_eclipse | yep | 20:15 |
| vb123 | what should be the state (branch) before you call cherry pick? | 20:15 |
| vb123 | what about origin? | 20:15 |
| nuclear_eclipse | well, you should make sure your branch is in sync with origin before cherry-picking via `git pull`, but other than that, it should be rather straightforward | 20:17 |
| vb123 | ok so apply this on a local 1.1.x branch that follows origin/master-1.1.x | 20:17 |
| vb123 | which is up to date. | 20:17 |
| nuclear_eclipse | I have a feeling your clone might be corrupted or something, causing the error you saw; if you see that sort of error again, I'd reccommend making a new clone and trying again | 20:17 |
| nuclear_eclipse | right | 20:18 |
| vb123 | I've created a new clone and tried on that. All succeeded but couldn't push. I will try again after the rc1 release. | 20:18 |
| vb123 | are we ready for that? | 20:18 |
| nuclear_eclipse | vb123: while I have your attention, a) could I get added to a whitelist for the mantisbt-announce mailing list, and b) could I perhaps get moderator access to the mailing lists and/or everything on SF? | 20:19 |
| nuclear_eclipse | vb123: got a private branch fixing the proxy issues, and I'm investigating a couple other issues that I think are related to paul_'s dates overhaul | 20:20 |
| vb123 | I will add you to the mailing lists. | 20:20 |
| vb123 | ok good. | 20:20 |
| vb123 | The most important thing is to make sure we don't mess up users data as far as dates are concerned. | 20:21 |
| nuclear_eclipse | also, as has been brought up by paul, can we disable CVS/SVN repos on sf.net? they still seem to be causing confusion for users... =\ | 20:21 |
| nuclear_eclipse | vb123: data is all correct at this point; the problem is that we're not yet handling new input from users relating to date strings | 20:21 |
| nuclear_eclipse | paul_ fixed date input for project versions, so I'm going to investigate making similar changes elsewhere as needed | 20:22 |
| nuclear_eclipse | actually vb123, can you review the proxy fix? I ended up reimplementing the session validation as an option selectable by the user at login time, so that users behind proxies can turn it off, while other users can remain protected | 20:23 |
| nuclear_eclipse | http://git.mantisforge.org/w/mantisbt/jreese.git?a=shortlog;h=refs/heads/proxy-login | 20:23 |
| nuclear_eclipse | hi giallu | 20:56 |
| giallu | hi nuclear_eclipse | 20:57 |
| giallu | so you're givin me some packaging work... | 20:57 |
| nuclear_eclipse | poor giallu | 20:57 |
| giallu | :P | 20:57 |
| nuclear_eclipse | just look at aptituz_, he has to deal with *Debian* :P | 20:58 |
| aptituz_ | lol | 20:58 |
| nuclear_eclipse | *he's* the one with packaging trouble ;) | 20:58 |
| * nuclear_eclipse hides behind an Ubuntu logo | 20:58 | |
| aptituz_ | well actually dealing with Debian is the easy part | 20:58 |
| aptituz_ | dealing with mantis and its edges isn't :D | 20:59 |
| nuclear_eclipse | :'( | 20:59 |
| * giallu playin with exceptions | 21:01 | |
| nuclear_eclipse | uh oh | 21:02 |
| * aptituz_ playing with his oropax, preparing to get some sleep | 21:02 | |
| giallu | oropax... I don't call it that way... :P | 21:02 |
| aptituz_ | but? | 21:02 |
| * giallu hides, was just a lame joke | 21:03 | |
| aptituz_ | uhm lol | 21:04 |
| * nuclear_eclipse missed the joke completely.... | 21:04 | |
| giallu | it's just I didn't know that word | 21:04 |
| nuclear_eclipse | joke ---> | 21:05 |
| nuclear_eclipse | me \o/ | 21:05 |
| giallu | anyway, victor noted in bug 668 API should raise exceptions rather than triggering errors | 21:05 |
| mantisbot | Bug 668 - jkorab - open - assigned | 21:05 |
| mantisbot | Voting for bugs appears to be unavailable - http://www.mantisbt.org/bugs/view.php?id=668 | 21:05 |
| nuclear_eclipse | orly? | 21:05 |
| aptituz_ | its not a word itself. in reality its a brand, but germans are used to call the more generic ear protectors which you put into your ear this wy | 21:05 |
| giallu | which sorta makes sense | 21:05 |
| aptituz_ | way* | 21:05 |
| giallu | aptituz_, yeah found out. I just run out of things one could play with before sleeping... | 21:07 |
| aptituz_ | lol | 21:07 |
| aptituz_ | gn8 ;) | 21:07 |
| giallu | bye | 21:07 |
| paul_ | giallu: I can fix nusoap :) | 21:26 |
| paul_ | nuclear_eclipse: gone home yet? | 21:34 |
| nuclear_eclipse | home now | 21:42 |
| * paul_ growls | 22:28 | |
| nuclear_eclipse | hi paul_ | 22:30 |
| paul_ | I need to create a diff against a revision | 22:31 |
| paul_ | I think ;/ | 22:31 |
| paul_ | yay merged | 23:06 |
| paul_ | now nn | 23:06 |
Generated by irclog2html.py