IRC log for #asterisk-bugs on 20100503

00:31.38*** join/#asterisk-bugs pabelanger_ (~pabelange@CPE0013f7abc09a-CM0013f7abc096.cpe.net.cable.rogers.com)
01:17.41*** join/#asterisk-bugs pabelanger_ (~pabelange@CPE0013f7abc09a-CM0013f7abc096.cpe.net.cable.rogers.com)
11:29.27*** join/#asterisk-bugs eliel (~eliels@201.234.94.226)
12:22.43*** join/#asterisk-bugs caio1982 (~caio1982@CAcert-br/caio1982)
12:57.59*** join/#asterisk-bugs Deeewayne (~dwayne@c-71-207-214-190.hsd1.al.comcast.net)
12:57.59*** mode/#asterisk-bugs [+o Deeewayne] by ChanServ
13:21.10*** join/#asterisk-bugs Deeewayne (~dwayne@75-150-14-49-Atlanta.hfc.comcastbusiness.net)
13:21.10*** mode/#asterisk-bugs [+o Deeewayne] by ChanServ
13:40.30*** join/#asterisk-bugs malcolmd (~malcolmd@pdpc/sponsor/digium/malcolmd)
13:44.45*** join/#asterisk-bugs corretico (~laguilar@201.201.46.106)
13:45.28Entomologist*** CLOSED (17275) [Applications/app_dial] BAD ROUND TIME FOR ANSWEREDTIME
13:45.28EntomologistReported by: fcois93
13:45.29Entomologisthttps://issues.asterisk.org/view.php?id=17275
13:45.29Entomologist*********************************************************
13:51.04*** join/#asterisk-bugs leifmadsen (~Leif@asterisk/documenteur-extraordinaire/blitzrage)
13:51.04*** mode/#asterisk-bugs [+o leifmadsen] by ChanServ
13:59.51*** join/#asterisk-bugs putnopvut (~putnopvut@asterisk/master-of-queues/mmichelson)
13:59.51*** mode/#asterisk-bugs [+o putnopvut] by ChanServ
14:15.40pabelangerm17270
14:15.42MuffinMan[new] [Asterisk] Channels/chan_dahdi 0017270: getting warning message every 4 seconds reported by jmls https://issues.asterisk.org/view.php?id=17270
14:16.40pabelangerI don't know what the reporter expects.  He has a span configured with NO cable plugged into it, of course asterisk will complain not being able to find a D-channel
14:19.42jsmithpabelanger: Right, but should it repeat the warning every 4 seconds?
14:23.28pabelangerjsmith: Don't know, is that what he is asking?  The idea solutions is for him to disable the span if not being used and maybe increase the delay in warning, but how much?
14:23.48pabelangereither way I replied to the issue asking he for more information
14:24.56jsmithpabelanger: Based on the discussion here in IRC last week, his complaint was that it was logging that error every 4 seconds.
14:25.40jsmithpabelanger: While it's ideal to just shut down the span in question, I think it's reasonable (especially on a development box) to have a span configured but nothing plugged into it
14:26.38pabelangerjsmith: Fair enough, the question now is what do we consider 'reasonable'?
14:27.00pabelanger15, 30 seconds?
14:27.50jsmithpabelanger: I'd say report it when the span goes into alarm or comes out of alarm... I don't think we need a periodic reminder
14:28.04jsmithpabelanger: (or at a minimum, we need a way to disable the periodic reminder)
14:36.24pabelangerjsmith: fair enough. This _maybe_ 1.4 only.  I'm looking into trunk and cannot find the offending code.
14:42.34Entomologist*** CLOSED (17206) [Functions/General] Using SORT strings with comma in them are truncated up to the first comma.
14:42.34EntomologistReported by: freon1
14:42.35Entomologisthttps://issues.asterisk.org/view.php?id=17206
14:42.35Entomologist*********************************************************
14:43.54Entomologist*** CLOSED (17174) [Addons/General] Connection Problem with UnixODBC 2.1.14
14:43.55EntomologistReported by: davidsharon
14:43.55Entomologisthttps://issues.asterisk.org/view.php?id=17174
14:43.56Entomologist*********************************************************
14:50.13pabelangerleifmadsen: ping
14:53.07leifmadsenpabelanger: pong!
14:54.49pabelangervery minor type in the Collecting Debug info: http://pastebin.com/QTneeVWE
14:54.59*** join/#asterisk-bugs jpeeler (~jpeeler@asterisk/digium-software-dev/jpeeler)
14:55.07pabelangerneed mantis issue created?
14:56.30leifmadsenpabelanger: nope, I can change that now
14:56.40leifmadsenjust logging into mantis as we type
14:56.53leifmadsenah ok, I will fix that
14:57.06pabelanger:) very minor
15:00.01leifmadsen<PROTECTED>
15:00.17pabelangersalutes leifmadsen
15:00.49leifmadsenfor some reason I misread that and thought you were calling me a slut
15:01.49pabelangerlol
15:01.58leifmadsenthat's monday for ya :)
15:02.09pabelangerdoh! missed the 2nd typo leifmadsen.  Line :71
15:02.15leifmadsenah crap :)
15:02.22leifmadsenI misread the patch
15:02.46leifmadsenthat's ok, we'll leave it for now -- you can fix it in another patch when you update that documentation in the future :)
15:02.59pabelangerhehe
15:03.04pabelangerroger
15:08.08leifmadsenQwell:  17268 seems to be a regression you introduced, but has a fix for it if you could check it
15:08.35Qwellit's on the short list
15:08.45leifmadsenok coolio!
15:08.55leifmadsenjust making sure you saw it since i know you have many items on that list :)
15:47.39*** join/#asterisk-bugs ccesario (~ccesario@189-19-6-236.dsl.telesp.net.br)
15:50.46*** join/#asterisk-bugs ccesario_ (~ccesario@189-19-6-236.dsl.telesp.net.br)
16:02.08pabelangerQwell: any problems if I try my hand at committing 17268 into trunk?  I was recently approved. :)
16:03.02leifmadsenpabelanger: is that a trunk only problem>?
16:03.14leifmadsenor does it apply to other branches as well?
16:03.30Qwellshould be in all branches, I think
16:03.40pabelangerleifmadsen: let me confirm
16:04.21leifmadsenpabelanger: if all branches (including 1.4), then you want to merge to 1.4 first, then use "merge4trunk" in your checkout of trunk. Then once that is committed, then you use "mergetrunk6" in the 1.6.x branches
16:04.39leifmadsenhopes seanbright has taught him well :)
16:04.45seanbrightuh oh
16:04.57seanbrightthat is correct
16:05.12leifmadsennice
16:05.21leifmadsenbecause if it isn't, I've been effin' up royally :)
16:06.10seanbright<PROTECTED>
16:06.10seanbright<PROTECTED>
16:06.10seanbright1.4 -> trunk ---+--- 1.6.1
16:06.10seanbright<PROTECTED>
16:06.10seanbright<PROTECTED>
16:06.16seanbrightbam
16:06.18leifmadsennice!
16:06.39pabelangerya, looks like all branches. So start with 1.4.  check
16:06.49leifmadsennote that the argument to the merge4trunk is the revision number returned for the commit to 1.4. And the argument to mergetrunk6 is the revision number returned for the commit to trunk.
16:07.41leifmadsenseanbright: sometime in may the ASCII art will turn into:   1.4 -> trunk -> 1.6.2
16:07.46leifmadsens/may/May/
16:08.33seanbrightyes indeed
16:08.52leifmadsenI'm REALLY excited for that
16:09.00seanbrightditto
16:09.06leifmadsendropping support for two 1.6.x branches will make releases much easier
16:09.10seanbrightneeds to get back to asterisk dev at some point
16:09.11leifmadsenwriting 2 less release announcements, etc...
16:09.16leifmadsenseanbright: hells ya!
16:09.23pabelangerleifmadsen: What is the format for a commit message?
16:09.25leifmadsenyou have a branch I'm watching for you to finish :)
16:09.30leifmadsenpabelanger: let me get you the link
16:11.15leifmadsenpabelanger: http://www.asterisk.org/doxygen/trunk/CommitMessages.html
16:11.48leifmadsenpabelanger: in the issue you've filed, you will see "Commit message template
16:11.49leifmadsen"
16:12.08leifmadsenif you hit the + link, then you can automatically generate the template that will close the issue for you upon commit
16:12.31pabelangerok, let me check that out
16:13.07leifmadsensvn commit -m "<some one liner brief message>.
16:13.07leifmadsenA more descriptive commit message if necessary.
16:13.07leifmadsen<paste your commit template here>"
16:14.04leifmadsenNote that you want to try and limit your text to 80 chars wide. The first line will be automatically added to the asterisk-summary-* files (when we get the scripts fixed to start generating them again)
16:14.31leifmadsenSo that's why the first line should just be brief, and then on a newline start your more descriptive summary if it applies.
16:16.24pabelangerleifmadsen: I assume I keep everything listed in the [] too, when pasting it into my commit message?
16:16.50pabelangerlet me get a pastebin
16:17.06leifmadsenpabelanger: sure thing
16:17.12leifmadsenI'm not sure what you mean by the [ ] part
16:20.33pabelangerleifmadsen: http://pastebin.com/jpKB7emk
16:20.46leifmadsenpabelanger: replace the [ ] stuff with your descriptions
16:20.49pabelanger:)
16:20.54pabelangerk, wanted to confirm
16:20.55leifmadsenin your case just remove them
16:21.07leifmadsennp -- they are not templates that get triggered on or anything
16:21.19leifmadsenand the Review line you can remove entirely unless there was a review
16:21.22pabelangerok
16:27.37pabelangerHmm... 403 Forbidden.  Looks to be permission error
16:27.41pabelanger1 sec
16:41.31Entomologist*** CLOSED (17268) [Core/BuildSystem] [patch] [Regression] non-root make install PREFIX=/tmp fails
16:41.32EntomologistAssigned to: qwell
16:41.32EntomologistReported by: pabelanger  Karma: 36.5
16:41.33Entomologisthttps://issues.asterisk.org/view.php?id=17268
16:41.33Entomologist*********************************************************
16:41.43Qwell!
16:41.53pabelangerlets see what happend
16:42.36pabelangerlooks good
16:42.46Qwellshould've removed the /usr/lib/ part though
16:42.58pabelangerblah!
16:43.00Qwellsince that's what $(libdir) is
16:43.13pabelangernot good :(
16:43.31Qwellno big deal - it's version controlled.  you cana lways change it :)
16:43.59QwellI think it should be: $(DESTDIR)$(libdir)/pkgconfig
16:44.38pabelangerQwell: ya, that is what I had.  Just copied over the wrong patch.
16:44.49Qwellwhat I would suggest doing, is making the change in 1.4, and then use the svnmerge stuff but include both revisions
16:45.10Qwell(to merge to trunk) and then just merge the single trunk rev into 1.6.x
16:45.45Qwellso like `merge4trunk 1234,1235` or whatever the revs end up being
16:45.51pabelangerok
16:47.38pabelangerDo I need create a new message template, or will a one-liner be enough?
16:47.48Qwellone-liner is fine
16:56.03*** join/#asterisk-bugs mnicholson (~mnicholso@nat/digium/x-hvfdtgtbepqcdvjo)
16:59.56pabelangerI think I am missing something.  How do I get merge4trunk, mergetrunk6, etc. I don't see them in my repotools folder.
17:00.16leifmadsenI think you have to run 'make install'
17:00.16russellbthey are symlinks created by make install
17:00.20pabelangerI guess I didn't install them :)\
17:03.31pabelangerok, so I run merge4trunk in my trunk directory, correct?
17:04.17Qwellright
17:07.07pabelangerok. Done
17:08.45pabelangerSame applies for mergetrunk6, I run it from trunk also?
17:11.14pabelangermy mistake, I run mergetrunk6 from each 1.6 branch I want the patch merged into
17:13.29pabelangerleifmadsen: ping
17:13.51leifmadsenpabelanger: pong
17:14.58pabelangerleifmadsen: Sorry, just want to confirm.  In each 1.6 branch(1.6.0, 1.6.1, 1.6.2), I would run mergetrunk6 260663?
17:15.00Qwellpabelanger: correct, you run it in the destination branch
17:15.46pabelangerQwell: Thanks. I think I got it
17:38.17pabelangerIt takes a little time to merge from trunk to 1.6 branches
17:45.00pabelangerQwell: Do you mind confirming I did the merge properly from 1.4 > trunk > 1.6 branches?
17:45.30pabelangersome how I don't think I did
17:47.28Qwelltrunk looks right.  I think the properties were removed in the 1.6.x branches though
17:47.43Qwellnot sure why that would've happened
17:47.57pabelangerQwell: Ya, that is what I see too. I'm not sure why that happened.
17:48.04QwellI can fix - one sec
17:50.02*** join/#asterisk-bugs eliel (~eliels@201.234.94.226)
17:50.34pabelangerI did a checkout of each 1.6 branch then ran mergetrunk6 260663 and svn commit -f ../merge.msg in each directory.
17:51.01pabelangermergetrunk6 took about 3-5 mins to run
17:51.16Qwellafter the mergetrunk6, did you do `svn resolved .`?
17:51.38pabelangerno
17:52.16Qwellthe commit should have failed, since there would've (usually) been unresolved property changes.
17:53.09pabelangerso, I should do `svn resolved .` before I commit then?
17:54.13Qwellwell, every time I do merges to 1.6.x (which isn't all that often), I get a conflict on ., because it couldn't merge some properties.  I'm not sure why the commit would have succeeded
17:54.37leifmadsenya, I usually just do 'svn revert .'  but perhaps I'm supposed to be doing 'svn resolved .' :)
17:55.04Qwellif you revert, then it won't update the trunk-merged property
17:55.38leifmadsenahhh
17:55.45leifmadsensomeone told me wrong then :)
17:55.50seanbrightwasn't me
17:55.55leifmadsenI didn't say who!
17:55.58leifmadsen(I don't even know)
17:56.00jsmithBlame me!
17:56.05leifmadsenI blame file
17:56.11seanbrighti sensed your judgemental undertons
17:56.11fileYAY!
17:56.15seanbrightundertones as well
17:56.39leifmadsenI need lunch
17:57.30pabelangerok, I'll watch it for the next round of commits, but I'm taking most of my Q's from http://www.asterisk.org/developers/svn-branching-merging
18:07.57*** join/#asterisk-bugs elguero (~miguel323@h-68-167-124-171.cmbrmaor.static.covad.net)
19:10.15*** join/#asterisk-bugs ccesario (~ccesario@189-19-6-236.dsl.telesp.net.br)
19:22.30*** join/#asterisk-bugs ccesario_ (~ccesario@189-19-6-236.dsl.telesp.net.br)
19:35.31pabelangerblame Canada!
19:35.52pabelangerheh, only 1:30 mins late to the conversation.
20:46.09*** join/#asterisk-bugs ccesario (~ccesario@189-19-6-236.dsl.telesp.net.br)
20:58.47pabelangerThat's alot of mantis emails.
21:00.02leifmadsena lot* :)
21:00.12leifmadsenya -- I just updated all the roadmap information for the current sprint
21:00.16leifmadsenI'm done now though
21:03.18pabelangerya, same.  Out for a bit.
21:33.10*** join/#asterisk-bugs ccesario (~ccesario@189-19-6-236.dsl.telesp.net.br)
21:33.30*** part/#asterisk-bugs jpeeler (~jpeeler@asterisk/digium-software-dev/jpeeler)
21:41.12*** join/#asterisk-bugs jpeeler (~jpeeler@asterisk/digium-software-dev/jpeeler)
22:09.23*** join/#asterisk-bugs pabelanger (~pabelange@CPE0013f7abc09a-CM0013f7abc096.cpe.net.cable.rogers.com)
22:13.27Entomologist*** CLOSED (16379) [Applications/app_meetme] [patch] Patch: New admin features: Roll call, eject all, mute all, record in-conf
22:13.28EntomologistAssigned to: jpeeler
22:13.28EntomologistReported by: rfinnie  Karma: 7
22:13.29Entomologisthttps://issues.asterisk.org/view.php?id=16379
22:13.29Entomologist*********************************************************

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.