Monday, 2010-01-18

../irclogs/#mantishelp.2010-01-18.log
--- scribe started ---00:00
dhx_msiebrand: are you still about?01:02
siebranddhx_m: I shouldn't be ;(01:13
dhx_msiebrand: I won't bother you then at the moment :)01:14
siebranddhx_m: thanks01:14
paul__dhx_m: thanks11:55
paul__:)11:55
paul__dhx_m: you like the commit police?11:55
dhx_mpaul__: haha yep :)13:02
alemayoHello Git support chat :)13:16
dhx_mhey13:18
alemayoour first table field release is up13:21
dhx_m:)13:21
alemayohttp://git.mantisforge.org/w/TableField.git13:21
alemayobut we have a problem pushing to our mantis fork for the events...13:21
dhx_mwhat error do you get?13:23
alemayot$ git push public current13:23
alemayoerror: src refspec current does not match any.13:23
alemayoerror: failed to push some refs to 'ssh://am-gtz@git.mantisforge.org/srv/git/mantisbt/gtz-et.git'13:23
alemayo$ git push public tracking13:23
alemayoerror: src refspec tracking does not match any.13:23
alemayoerror: failed to push some refs to 'ssh://am-gtz@git.mantisforge.org/srv/git/mantisbt/gtz-et.git'13:23
alemayo$ git status13:24
alemayo# On branch master-1.2.x13:24
alemayo# Your branch is ahead of 'origin/master-1.2.x' by 2 commits.13:24
alemayo#13:24
alemayonothing to commit (working directory clean)13:24
dhx_mtry:13:24
alemayo?13:25
alemayotry nothing :) ?13:30
dhx_msorry, distracted13:32
alemayomaybe it is because locally we reverted two commits .. hm13:32
dhx_mgit push origin master-1.2.x13:32
dhx_m?13:32
dhx_mah wait13:32
dhx_morigin in your case is mantisbt.org, not mantisforge.org?13:32
alemayoorigin is mantisbt13:33
alemayoja13:33
dhx_mok13:33
alemayoyes13:33
dhx_mand yes, mantisforge won't let you modify commits you've already made13:33
dhx_malthough reverting doesn't touch original commits13:33
dhx_mrebasing does though13:33
alemayoI think we did git reset .. but I don't remember well13:34
dhx_mthat should also be ok13:34
alemayoso how to solve ?13:34
dhx_mis "tracking" and "current" branches you have locally?13:34
alemayono idea :)13:34
dhx_mgit push public tracking13:34
dhx_mthat tells git to push the "tracking" branch to the "public" repository13:35
alemayoerror: src refspec tracking does not match any.13:35
dhx_mdo git branch -a13:35
dhx_mto list all brances13:35
dhx_mwait13:35
dhx_myeah that's right13:36
dhx_mgit branch -a to list your refspecs13:37
dvlgiday.13:37
dhx_mhi13:37
alemayo$ git branch -a13:38
alemayo* (no branch)13:38
alemayo  master13:38
alemayo  master-1.2.x13:38
alemayo  remotes/origin/HEAD -> origin/master13:38
alemayo  remotes/origin/live13:38
alemayo  remotes/origin/master13:38
alemayo  remotes/origin/master-1.0.x13:38
alemayo  remotes/origin/master-1.1.x13:38
alemayo  remotes/origin/master-1.2.x13:38
alemayo  remotes/origin/rpxnow13:38
alemayo  remotes/public/master-1.2.x13:38
alemayoah .. because of the reset stuff I lost my branch I guess13:38
dhx_myou shouldn't have13:39
dhx_mit sounds like you never had a branch?13:39
dhx_mremember after you create a branch, you need to check it out13:39
alemayoah wait13:39
dhx_mgit branch something13:39
dhx_mto create a "something" branch13:39
dhx_mthen you need to:13:39
alemayoI did some rebase experiements while you were distracted :)13:39
dhx_mgit checkout something13:39
dhx_mto start using it13:39
alemayo git branch -a13:39
dhx_mahhh :)13:39
alemayo  master13:39
alemayo* master-1.2.x13:39
alemayo  remotes/origin/HEAD -> origin/master13:39
alemayo  remotes/origin/live13:39
alemayo  remotes/origin/master13:39
alemayo  remotes/origin/master-1.0.x13:40
alemayo  remotes/origin/master-1.1.x13:40
alemayo  remotes/origin/master-1.2.x13:40
alemayo  remotes/origin/rpxnow13:40
alemayo  remotes/public/master-1.2.x13:40
alemayoaber rebase --abort that looks better13:40
alemayojust to make troubleshooting not to easy I decided to type random commands when you do not answer fast enough :-)13:40
dhx_mso you probably want to use:13:40
dhx_mgit push public master-1.2.x13:40
dhx_m?13:40
alemayook13:40
alemayo$ git push public master-1.2.x13:40
alemayoTo ssh://am-gtz@git.mantisforge.org/srv/git/mantisbt/gtz-et.git13:40
dhx_mit's one way13:40
alemayo ! [rejected]        master-1.2.x -> master-1.2.x (non-fast forward)13:41
alemayoerror: failed to push some refs to 'ssh://am-gtz@git.mantisforge.org/srv/git/mantisbt/gtz-et.git'13:41
alemayothe question is, were does this reject come from13:41
dhx_myeah your local branch must have been rebased13:41
dhx_mtry this...13:41
dvltrying to get mantis to send notices out to a mailing list.  I've created a user, as an Updater (turns out, it's the only updater), and that user's email address is the mailing list, but nothing goes out to the list (as verified by watching my mail server).13:41
dvlI have; $g_default_notify_flags['threshold_min'] = UPDATER;  && $g_default_notify_flags['threshold_max'] = UPDATER;13:41
dvlin config_inc.php13:41
dvlGetting lost.13:42
dhx_mgit push public :master-1.2.x13:42
dhx_mthat deletes the remote branch you're sharing13:42
alemayo - [deleted]         master-1.2.x13:42
dhx_mthen you can upload your rebased branch13:42
dhx_mthis is normally a *bad* idea if people are tracking your branch (and forking it)13:42
alemayofine .. that did the trick :)13:42
alemayothey did not :)13:42
dhx_min the future, don't rebase commits after they've been pushed :p13:42
dhx_motherwise you'd have to undo the rebasing locally before committing13:43
alemayoon our first expriements we did chmod -R 777 and  then back to 655 ... that messed up the patches a bit13:43
dhx_myep13:43
alemayoalright13:43
dhx_mnoticed that13:43
alemayothanks a lot13:43
dhx_malso it might be better to rename master-1.2.x to something else?13:43
dhx_mhave different branches for different features you add to mantis13:43
alemayohow :) ?13:43
dhx_mrather than just a single branch with lots of stuff13:43
dhx_mgit checkout -b newname13:43
dhx_mmakes a new branch (and switches to it) based on your current working tree13:44
alemayookay ..13:44
dhx_mthen push that branch13:44
alemayobut we already did some changes to that master-1.2.x13:44
alemayois there some kind of rename possible ?13:44
dhx_mthey'll be in your new branch ;)13:44
dhx_mremember that a branch is just a pointer to a commit13:44
alemayoexactly .. can I add a new pointer to that commit 2 days ago ?13:45
dhx_myep13:45
alemayooh there is none .. because we did delete I guess13:45
alemayohm13:45
dhx_mone way is to "git checkout 13414535(commit id)"13:45
dhx_mthen git checkout -b newname13:45
dhx_mactually "master" is the correct name to use13:47
dhx_myou're doing it right at the moment13:47
dhx_mI thought you were referring to branches of the MantisBT codebase itself (not your plugin)13:47
alemayogit checkbout -b custom-fields-events   is that a good name ?13:47
alemayoI do13:47
alemayowe also do some patching in master-1.2.x of mantisbt core13:47
alemayobecause we need some new events13:47
dhx_myeah that's fine for when you're modifying Mantis' master-1.2.x tree13:48
dhx_mthen push that branch to mantisforge as a fork of the master-1.2.x repository13:48
alemayohttp://git.mantisforge.org/w/mantisbt/gtz-et.git13:49
dhx_mcan I suggest not using master-1.2.x13:49
dhx_mand instead use master-1.3.x13:49
alemayono :)13:49
alemayohm .. maybe13:49
dhx_mas we won't be adding features to 1.2.x anymore13:49
alemayobut we are *ggg*13:49
dhx_mactually... we might... if it's just plugin events13:50
alemayothe thing is, that we will plan to use that after around 2 weeks in production environment13:50
alemayojust have a look on it ..13:50
dhx_mbut the idea at the moment is 1.2.x is "final" and "stable"13:50
alemayoI think it should be easy to merge it back to 1.2.x or 1.3.x13:50
alemayoyeah .. but if we use 1.3.x how can we get our features easily in the final :)13:50
dhx_mit's not hard... but it's quite often time consuming ;)13:50
dhx_mI guess it'd be best to use "git cherry-pick" to try and backport or forwardport your patches to 1.2.x or from 1.3.x13:51
dhx_mof course, that isn't the most important thing to worry about at the moment13:51
dhx_mgetting something working is :)13:51
dvlHmm, http://manual.mantisbt.org/ says "Last Modified: April 22, 2005 05:04AM"13:52
dvland This is the manual for Mantis version 1.0.0.13:52
dhx_mdvl: yeah it's outdated :(13:53
dhx_mdvl: maybe try http://docs.mantisbt.org/master/en/13:53
dhx_mfor 1.2.x13:53
dhx_m(which you should probably be using if you're just setting up Mantis from scratch)13:54
dvldhx_m: Still on 1.1.8 FWIW13:54
dvlNo, long time user here.13:54
dhx_mdvl: sorry, I got caught in the other discussion, to answer your question about emails: have you had it working before?13:54
dvldhx_m: Yes, it worked for a long time.  And stopped working with a recent upgrade13:55
dhx_mdvl: an upgrade from 1.1.old to 1.1.8?13:55
dvldhx_m: You might remember me: Dan Langille, no worries.13:55
dvldhx_m: yes13:55
dvlProbably from 1.1.613:56
dvlSo, pretty sure this isn't a '$g_to_email has gone away' issue.13:56
dvlI suspect it's a notify flags issue.13:56
dhx_mdo you get password reset emails, etc (ie. any emails at all?)13:56
dvlI get emails for new bugs etc.13:57
dvlBut not to the list13:57
dvlDirect to me13:57
alemayociao!13:57
dhx_mis your list setup to accept emails from anyone?13:57
dhx_malemayo: cya later :)13:58
dvlYes.13:58
dhx_mdvl: and the account preferences for the user has checkboxes ticked for receiving emails?13:59
dvldhx_m: Hmmm, mantis will send directly... it's not like I give it smtp details.... hmmm.13:59
dvldhx_m: checking.13:59
dhx_mdvl: in that case it'll do so via php's built in mail() I imagine13:59
dvldhx_m: To find that user checkbox, can I do that as an admin user?14:00
dvlI'm in Manege right now14:01
dvlManage..14:01
dhx_mI believe so ;)14:01
dvlOh, this user is a Manager, let me change accounts14:02
dvldhx_m: I don't see any mail option at manage_user_edit_page.php14:05
dhx_mno account preferences section?14:06
dhx_mE-mail on New... etc?14:06
dhx_m(for the record, I've never actually used Mantis < 1.2.0a3)14:07
dvlOh, sorry, I've not logged in on that user, I've logged in as the Admin.14:07
dhx_mit's verrry different :)14:07
dhx_myou shouldn't have to (in 1.2.x at least)14:07
dhx_mthe admin can change account preferences for any used14:07
dhx_m*user14:07
dvlNothing like a preferences section14:08
dhx_mah it must be a newer feature then14:09
dhx_myou'd have to try logging in as the user then14:09
dvlWill try that.14:10
dvlThe account is protected.14:14
dvlAnd the Remove button appears beside it.  Sounds like stuff is afoot....14:14
dhx_mthis is why I never used 1.1.x :P14:14
dhx_mis this the 'anonymous' user?14:15
dvlNo, not the anonymous user14:16
dhx_mah so you'd have to login as an admin, unprotect the account, login as the user, change email settings, login as admin, reprotect the account14:16
dvlFound it.14:16
dvlFound account preferences after unprotecting account.14:16
dhx_myep14:17
dvlAll the email checkboxes are checked.14:17
dhx_mhmmm14:17
dhx_mthe changelog doesn't indicate any glaring changes to email14:18
dhx_mbetween 1.1.6 and 1.1.814:19
dvlIf there was a maillog for mail leaving Mantis....14:19
dvlsetting $g_smtp_host14:19
dhx_mI think there is somewhere14:19
dhx_mcheck config_defaults_inc.php for all email related options14:20
dhx_mthat you can set in config_inc.php14:20
dhx_mit's better than the "documentation" :)14:20
dvlWorking on that now14:23
dhx_mgtg for now14:23
dhx_mwill be back in some hours if you're still stuck14:23
dhx_malso double check that you have the PHPMailer library correct14:24
dhx_myour SMTP client is working ok14:24
dhx_mPHP is configured to use mail() properly14:24
dhx_mor you're using PHPMailer, is it configured ok?14:24
dhx_metc14:24
dhx_malso see admin/test_email.php14:25
dhx_m?14:25
dhx_mfor now though, I'm out of here, cya and good luck :)14:25
dvlsmtp server on locahost is fine.  and $g_smtp_host = "localhost";14:32
dvl$g_debug_email has been set, and copies of outgoing mail are cc'd there.14:33
dvlOnly outgoing mail is to the anonymous user.14:38
dvlwhich is fine, that email goes to me.  Nobody else gets email.14:50
dvlI see no differences between the anonymous user and the MailingList user.14:50
dvloh, now it's sending out emails.  :)15:01
dvlto everyone.15:01
dvlDont' want to do that again.15:03
dvlWhy it would stop working is rather annoying.  90 minutes today trying to find it.16:06
dvlabout 30 minutes earlier this week.16:06
dvlIt seems that manage_config_email_page.php may be the answer.16:06
dvlI think I've fixed it.  Waiting for the mailing list to process it.16:29
paul__dhx_m: mo?21:43
cmc_hi, good afternoon. I wonder if anyone can help me on this. I need to show the project name in the view all bug page. I could only show the project_id but that is useless21:44
paul__erm21:44
paul__I thought we showed that be defalt?21:44
darynit shows when All Projects is selected in the project dropdown21:45
cmc_nope... only shows project_id by default (manage colums)21:45
cmc_Then custom colums must be overriding this21:46
darynthe project name shows next to the category21:46
cmc_maybe because the version? 1.2rc2 but is not showing...21:49
daryndo you have more than one project ?21:50
cmc_sure, about 30 projects and some other 1800 subprojects.... by customizing columns I was only able to show the project_id21:51
darynhm...21:51
cmc_anyway reading somewhere I read it is possible to write custom functions, how does this work?21:52
cmc_i have deleted my custom column fields but still does not show project name21:53
darynthat wouldn't have any effect.  i have both displayed in my tracker21:55
darynhttp://manual.mantisbt.org/manual.customizing.mantis.custom.functions.php21:55
darynactually selecting the project_id column for view issues page does display the project name21:56
cmc_it shows me the id... strange...22:04
darynnot sure how that's possible...it calls the function 'print_column_project_id' from the core/columns_api.php file22:08
cmc_no idea then thanks for the help22:22

Generated by irclog2html.py