IRC log for #asterisk-dev on 20090130

00:00.19outtoluncoops misread
00:02.23lmadsenis looking on newegg.ca :)
00:02.50lmadsenat least is hoping newegg.ca actually resides in canada S
00:02.52lmadsen:S
00:02.56filelmadsen: it does not.
00:03.03filelmadsen: but the customs is paid ahead of time
00:03.07filelmadsen: or rather, taxes
00:05.11lmadsenok sweet
00:05.18lmadsenis that included in the price of the phone or something?
00:05.30lmadsenhates getting an $80 bill when his equipment arrives
00:06.25QwellThey should make 80 dollar bills.
00:06.36putnopvutI'd buy one
00:06.43lmadsenheh
00:08.59*** part/#asterisk-dev Deeewayne (n=Deeewayn@nat/digium/x-30026985dab3097d)
00:20.23Corydon76-digputnopvut: I have an $80 bill you can buy... only $160
00:20.43putnopvutomg how can I refuse?
00:21.10putnopvutCorydon76-dig: whose portrait is on the obverse of an $80 bill?
00:21.31Corydon76-digJefferson, I think
00:27.42*** join/#asterisk-dev codefreeze-lap (n=murf@72.21.67.40)
00:27.42*** mode/#asterisk-dev [+o codefreeze-lap] by ChanServ
00:29.57codefreeze-lapHint: if anybody comes up and says: I just put in a new card, and now my 4 port dahdi card doesn't handle audio-- you can call the phone, but no audio, then you tell him: rmmod all your dahdi drivers, and modprobe them back (in the right order), and manually run the dahdi_cfg, and you should be ready to go!
00:37.32lmadsencodefreeze-lap: yay! :)
00:37.45lmadsen(these are the kinds of tips that would be useful on asteriskdocs.org :))
00:38.02lmadsenjsmith: ok, I did it...
00:38.06lmadsenhas an E71 on the way
00:38.21lmadsenanyone wanna buy a used Nokia E61i? :)
01:11.56*** join/#asterisk-dev anthm][ (n=anthm@173-107-183-112.pools.spcsdns.net)
01:15.08*** join/#asterisk-dev snuff-home (n=snuffy@C-59-101-165-33.mel.connect.net.au)
01:15.08*** mode/#asterisk-dev [+o snuff-home] by irc.freenode.net
01:17.59*** join/#asterisk-dev ta^3 (n=tacvbo@189.146.181.195)
01:23.17codefreeze-laplmadsen: My area only does CDMA; none of the cool new phones is really available here...
02:10.24lmadsencodefreeze-lap: that's too bad :(
02:27.25*** join/#asterisk-dev atglenn (n=atglenn@wiktionary/ArielGlenn)
03:02.09*** join/#asterisk-dev CunningPike (n=arodgers@S01060014bf81366b.vc.shawcable.net)
03:03.03Juggiecdma :(
03:07.03*** join/#asterisk-dev angler_ (n=angler@nat/digium/x-9c4a2a2b7643e5f0)
03:20.36*** join/#asterisk-dev mnicholson (n=mnichols@nat/digium/x-d5739f07ac479de2)
03:39.25*** join/#asterisk-dev Deeewayne (n=dwayne@c-76-29-245-9.hsd1.al.comcast.net)
03:39.25*** mode/#asterisk-dev [+o Deeewayne] by ChanServ
03:41.53*** join/#asterisk-dev CunningPike (n=arodgers@S01060014bf81366b.vc.shawcable.net)
03:51.07*** join/#asterisk-dev obnauticus (n=lol@about/windows/regular/obnauticus)
04:12.14*** join/#asterisk-dev kerframil (n=kerframi@gentoo/user/kerframil)
04:21.06*** join/#asterisk-dev moy (n=moy@CPE001cdfec4cee-CM00080dab8485.cpe.net.cable.rogers.com)
04:26.15*** join/#asterisk-dev snuff-home (n=snuffy@C-59-101-165-33.mel.connect.net.au)
04:26.15*** join/#asterisk-dev CunningPike (n=arodgers@S01060014bf81366b.vc.shawcable.net) [NETSPLIT VICTIM]
04:26.15*** mode/#asterisk-dev [+o snuff-home] by irc.freenode.net
04:27.39*** join/#asterisk-dev snuff-home (n=snuffy@C-59-101-165-33.mel.connect.net.au)
04:27.40*** mode/#asterisk-dev [+o snuff-home] by ChanServ
04:42.04*** join/#asterisk-dev JunK-Y (n=junky@modemcable156.137-20-96.mc.videotron.ca)
07:01.52*** join/#asterisk-dev sergee (n=serg@voip1.west-call.com)
07:07.32*** join/#asterisk-dev steliosk (n=Stelios@ipa107.2.tellas.gr)
08:02.05*** join/#asterisk-dev oej (n=olle@ns.webway.se)
08:02.05*** mode/#asterisk-dev [+o oej] by ChanServ
08:31.47oejMorning folks
08:34.02*** join/#asterisk-dev vi390 (n=fc@unaffiliated/vi390)
08:35.36vi390how can I use dead Agi with asterisk > 1.4 -- I know there changed something, but can not find WHAT has changed
08:36.24vi390exten => h,1,AGI(...)  seems not to work. I saw somewhere, that DeadAGI is deprecated. Is there more info on this subject somewhere ?
08:42.34*** join/#asterisk-dev Mw3 (n=mw3@ip59934bd1.rubicom.hu)
09:29.01janingemornings
10:09.47*** join/#asterisk-dev kamanashisroy (n=kamanash@202.56.7.213)
10:42.51*** join/#asterisk-dev oej (n=olle@80.251.192.3)
10:42.51*** mode/#asterisk-dev [+o oej] by ChanServ
11:24.41*** join/#asterisk-dev caio1982 (i=caio1982@CAcert-br/caio1982)
11:43.30*** join/#asterisk-dev jpmcallister (n=jpmcalli@kapla.escelsa.com.br)
12:11.58*** part/#asterisk-dev janinge (i=j@ninge.net)
12:22.56jsmithG'morning all...
12:26.47*** join/#asterisk-dev oej (n=olle@ns.webway.se)
12:26.47*** mode/#asterisk-dev [+o oej] by ChanServ
12:55.42*** join/#asterisk-dev shazaum (n=shazaum@unaffiliated/shazaum)
13:42.07*** join/#asterisk-dev russellb (n=russell@asterisk/digium-open-source-team-lead/russellb)
13:42.07*** mode/#asterisk-dev [+o russellb] by ChanServ
14:00.45*** join/#asterisk-dev lmadsen (n=Leif@asterisk/documenteur-extraordinaire/blitzrage)
14:00.45*** mode/#asterisk-dev [+o lmadsen] by ChanServ
14:08.42*** join/#asterisk-dev schmooze (n=schmooze@h69-129-142-83.mdsnwi.tisp.static.tds.net)
14:13.24*** join/#asterisk-dev kamanashisroy (n=kamanash@202.56.7.195)
14:34.06oejAfternoon
14:36.12lmadsenmoanin!
14:51.39*** join/#asterisk-dev ACiDV (n=joel@205.237.45.129)
14:54.39*** join/#asterisk-dev sruffell (n=sruffell@adsl-074-185-078-025.sip.bhm.bellsouth.net)
14:54.39*** mode/#asterisk-dev [+o sruffell] by ChanServ
14:54.48*** join/#asterisk-dev DarkRift (n=dark@65.92.166.160)
14:55.19ACiDVusing latest SVN branches/1.4  + Zaptel 1.4.12.1, each time I try to compile, I have error related to 'expected specified-qualifier-list before __s32' ... see http://pastebin.ca/1322782
14:56.11ACiDVI can fix by adding #include <linux/types.h> but have this problem only since yesterday using latest svn, maybe something changed on dahdi/zaptel ?
14:59.40lmadsencodefreeze-lap: did you put your change in yesterday that you were working on?
15:03.51fiddurHi.  I've upgraded my production system to branch 1.6.0 from svn recently, to get new functions.  Today, asterisk started giving warnings about "Too many open files" from just about every dialplan application, and no sockets could be opened.  I don't know how to go about debugging that, more than checking the message- and debug-logs, and they don't say anything out of the ordinary before all applications starts getting these "Too many open files"-errors.
15:04.20lmadsenupgrading your production server to 1.6.0 without testing was not really a great idea.
15:04.33lmadsenI'd try #asterisk for help - see the topic and the join message.
15:04.44*** join/#asterisk-dev putnopvut (n=putnopvu@nat/digium/x-5e73f9b25601b35e)
15:04.44*** mode/#asterisk-dev [+o putnopvut] by ChanServ
15:06.20*** join/#asterisk-dev moy (n=chatzill@bas1-unionville55-1177733953.dsl.bell.ca)
15:14.58fiddurlmadsen: I realise it wasn't so good.  I guess I should patch specific files for backporting instead.  Thank's for the pointer.
15:15.16lmadsenfiddur: actually you should be running everything in a test environment
15:15.25lmadsennot updating a production server all  "willy-nilly"
15:16.15fiddurlmadsen: I did try the svn-version on a test-server first, but the test-server hasn't got 100 incoming lines and a thousand calls a day... so I guess I didn't find that bug then
15:35.33*** join/#asterisk-dev Deeewayne (n=Deeewayn@nat/digium/x-6e367bc594bc4f23)
15:35.33*** mode/#asterisk-dev [+o Deeewayne] by ChanServ
15:39.16*** join/#asterisk-dev russellb (n=russell@asterisk/digium-open-source-team-lead/russellb)
15:39.16*** mode/#asterisk-dev [+o russellb] by ChanServ
15:42.19oejOk, cause codes seems broken. I had problems with cause codes in trunk yesterday and now a bug reporter reports similar problems.
15:42.51oejI discovered yesterday that they where attached to the HANGUP control frame. Seems like it's not unpacked and handled by the channel in ast_hangup
15:42.56codefreeze-lapoej:  funny you should mention that
15:43.03oejIt should be in ast->hangupcause at that time
15:43.30oejI blame Corydon, since it was him suggesting that I convert to Cause codes...
15:44.00codefreeze-lapI'm trying to clean up some cause stuff in chan_dahdi right now. Wouldn't hurt to do the same in sip, I'd imagine.
15:46.37codefreeze-lapI also notice that they don't seem to be percolated up.
15:48.21oejHow do you mean?
15:48.56oejIn chan_sip we have pretty advanced conversions from SIP to AST causes codes
15:50.10oejThe big issue now is that it seems like hangup(xxx) seems broken, which propably also means that an incoming SIP call won't get the cause from an ISDN channel on DAHDI.
15:52.57*** join/#asterisk-dev anthm (n=anthm@freeswitch/developer/anthm)
15:54.49*** join/#asterisk-dev M1s3ry (n=M1s3ry@nat/digium/x-1de4a93192ef98b1)
15:55.28*** join/#asterisk-dev jpeeler (n=jpeeler@asterisk/digium-software-dev/jpeeler)
15:55.31*** mode/#asterisk-dev [+o jpeeler] by ChanServ
15:55.41*** part/#asterisk-dev M1s3ry (n=M1s3ry@nat/digium/x-1de4a93192ef98b1)
16:38.36*** join/#asterisk-dev jameswf (n=james@unaffiliated/jameswf-home)
16:39.34jameswfFonality seems to be the new leader in voip **Cough** http://download.intel.com/design/intarch/ep80579/320304.pdf **Cough**
16:41.25jameswfs/new leader/future/
16:45.56codefreeze-lapoej: are there places in chan_sip, where a channel is not yet formed, yet an incoming call is rejected?
16:47.04oejwell, yes
16:47.13oejwe have kind of a quick and dirty "go to hell" section
16:47.24oejmaybe not for calls, I have to check.
16:47.31oejWhat are you looking for?
16:48.28oejI'm thinking of transmit_response_using_temp
16:48.39oejWhich really doesn't create a PVT either
16:49.04oejBut don't think it's used for calls
16:49.14oejOnly if we get 500 server errors
16:49.44oejAnything special you're looking for?
16:50.07codefreeze-lapoej: a user points out in a bug (13892) that in dahdi, there are cases where an incoming call gets no CDR. In his case, when an incoming call specifies an exten that doesn't exist. In this case, I have to create the CDR 'by hand'. How far should we go in recording these attempts?
16:50.57oejWell, in SIP it could lead to a DOS attack.
16:51.14*** join/#asterisk-dev fred-tmft (n=fred-tea@c-69-244-180-112.hsd1.mi.comcast.net)
16:51.21oejOn PRI, you have a limited number of lines, but you could still generate a lot of stuff
16:51.25*** part/#asterisk-dev fred-tmft (n=fred-tea@c-69-244-180-112.hsd1.mi.comcast.net)
16:51.36oejOn SIP, imagine the amount of INVITEs you can send and get 404... Wow.
16:51.51oejYour CDR system would be a bit stressed out.
16:52.09oejOne option would be to do that only for authenticated calls
16:52.33filethis CDR behavior is getting out of controllllll
16:52.48oejI want a CDR on that statement.
16:52.56oejIn fact, everything File says in the channel.
16:53.37codefreeze-lapoej: admittedly, yes it could stress things, but... if you were admin, wouldn't you want to know about these attempts?
16:54.56oejYes, but is it an CDR issue?
16:55.08Corydon76-digThe CDR system should optionally log every call attempt, successful or not.  Ideally, though, it would have a way to reduce the number, based upon admin preference
16:55.11oejThe big question here is what is logging and what is CDRs?
16:55.32oejNormally, attack attempts should go somewhere else, not to the billing system.
16:55.45codefreeze-lapshrugs could probably be relegated to another mechanism, true...
16:55.48oejIs the new CDR system a generic logging system?
16:56.08oejI think we need to define logging and cdr-records again to be sure of what we do
16:56.29oejIn most of my systems, the CDRs are just shipped away for biling.
16:56.44oejs/biling/billing/
16:56.59codefreeze-lapoej: you mean, **will the new CDR system be*** a generic logging system? Dunno. CDR's are your defacto logging system now, it might seem
16:57.08Corydon76-digoej: yes, but CDR is not a billing system
16:57.20Juggiesigh :(
16:57.23oejCDR are billing records for most of my customers
16:57.35oejBut we do have the DOCUMENTATION flag too
16:57.42oejI guess some people want to use them...
16:57.44Corydon76-digCDR may feed into a billing system, though
16:57.54oejYep
16:58.28Corydon76-digYou're taking one customer's needs and generalizing the case
16:58.34oejBut things like "2000 INVITEs from peer 12.12.12.12" is propably better handled somewhere else, than in 2000 CDRs
16:58.43Corydon76-digand I think that's the wrong way to go, when it comes to CDRs
16:58.51oejNot "one customer" corydon, but I get your point
16:59.03oejShould we log in two different channels?
16:59.45codefreeze-lapoej:  CDR's can definitely be used for billing.... but can be used for many things....  I'm definitely writing the spec to accomodate the billing guys, but....
17:00.01Corydon76-digIt's possible that we need something in CDR like we have in syslog... (this case repeated 200 times)
17:00.22codefreeze-lapCorydon76-dig:  that's not a bad idea
17:00.36oejBut only for failed attempts then.
17:00.54oejIf one customer places 200 successful calls, I want CDRs for each one, even if they have the same numbers.
17:00.56Corydon76-digoej: well, we figure out what makes a case identical
17:01.01oejYep
17:01.12Corydon76-digGenerally calls that go through won't be identical to others
17:01.22oejNo, that's right.
17:01.29oejUnless they're exactly the same length.
17:01.30oej:-)
17:01.38oejStill have different timestamps though.
17:01.42Corydon76-digand the same called number
17:01.42oejCausecodes anyone?
17:02.23oejCorydon76-d: Did you see the causecode issue I talked about earlier?
17:02.25citatswell in order to not lose records in the event of a crash, shouldnt there be a unique first record, and then an ending record when the attempts are done and include the number
17:02.26ctooleycausecodes?  knowing why something happened is overrated.
17:02.29codefreeze-lapI see this attempt thing probably in some module like DetectAttacks() or something like that, maybe
17:02.46Corydon76-digoej: that it wasn't passed back through the Local channel?
17:03.01oejcodefreeze: That's something that jtodd worked on during astridevcon. Check the pbwiki.
17:03.06citatscodefreeze-lap: whats the difference between an attack and a misconfigured client?
17:03.33codefreeze-lapcitats: not much!
17:03.46oejCorydon76-d: Seems to be a generic problem in trunk that the causecode is not delivered properly to the channel. I had problems yesterday (trying to implement your suggestion) and someone reported issues with hangup(arg) in the tracker.
17:04.06oejgotta start cooking soon
17:04.29*** join/#asterisk-dev fiddur (n=fiddur@92-32-123-186.tn.glocalnet.net)
17:04.41oejCorydon76-d: You haven't seen this?
17:05.04Corydon76-digoej: No, I saw it
17:05.06oejSomeone implemented cause codes as an attachment to the hangup. WOnder if that's when it broke.
17:05.35Corydon76-digoej: and I'm behind you 100% in you fixing it.  ;-)
17:05.41codefreeze-lapAs to cause codes, in PRI, I'm seeing A uses PRI to call B/5551212;  B has no 5551212 exten, and B gets the not-avail cause code. A just sees NOANSWER. (A & B are two sep * servers)
17:06.03oejCorydon76-d: gotta fix dinner first. Food is prioritized, right jsmith?
17:06.57jsmithoej: Absolutely!
17:07.12Corydon76-digoej: Yeah, I've been meaning to start up the grill so I can season some cast iron
17:07.27putnopvutI need to reseason my cast iron skillet.
17:07.30oejSoemone is trying to install OpenLibPri: "Trying to understand how to setup two PRIs in sip.conf"
17:07.35putnopvutwell, don't need to, but want to.
17:07.39oejLet's merge chan_dahdi and chan_sip.
17:07.48putnopvutheh
17:09.02Corydon76-digoej: speaking of, wasn't there some talk about splitting up chan_sip into several files, much the way chan_iax is split up?
17:09.25oejI proposed that, but Russell wanted to wait.
17:09.38Corydon76-digHopefully making it easier to manage and new developers to understand
17:09.41oejThat's why I have all those function declarations in there. To prepare
17:09.53oejYes, that's the first thing I did with pineapple, so I've done it before.
17:10.06Corydon76-digWhat's the logical split?
17:10.21Corydon76-digsending vs receiving?
17:10.39Corydon76-digand utility functions?
17:10.41oejhttp://www.codename-pineapple.org/doc/html/dir_c03c1fc31b8a79fd455bc0297f2cde0e.html
17:11.10oejDetailed answer...
17:11.20Corydon76-digWow, that's a ton of files
17:11.26oejIt's a ton of code.
17:12.05oejYou can see it by function in the .h file here http://www.codename-pineapple.org/doc/html/sip3funcs_8h-source.html
17:12.09Corydon76-digI'd love to go that direction, though
17:12.46Corydon76-digbut PineMango gets priority, I think
17:13.29oejWell, this doesn't get in the way... Just give me a go-ahead and I'll start cutting.
17:27.07oejWho's working with PineMango?
17:28.10bkw_oej: you have boxen setup for me to call :)
17:28.45oejbkw_: I'm just about to go home and make dinner. Expected you earlier...
17:28.55bkw_sorry running behind :)
17:28.55oejLet's see if I can fix it after dinner, ok?
17:29.05bkw_thats fine enjoy dinner we can do thsi next week
17:29.09bkw_its friday.
17:29.23oejRight. Let's do it next week then! I'll make sure I have two boxes setup up.
17:29.25russellboej: I think splitting it up is a good idea.
17:29.43oejOK, so I'll create a branch and get going... THanks.
17:30.02russellbI don't think we have any huge chan_sip patches in a branch right now
17:30.16russellbthe ipv6 code i guess ... but it's already out of date ...
17:30.16oejThen we can integrate it after 1.6.2 being forked, so we have some time to play
17:30.20russellbthere will always be something
17:30.26oejYes, always something.
17:30.41russellbbut yeah, I think now is probably as good as it will get
17:30.49russellbmaybe we can come up with a plan to do it in stages?
17:31.12russellbanyway, we can talk about it later
17:31.14russellbenjoy dinner!
17:31.46oejLet's talk about in at Fosdem.
17:31.53russellbok :)
17:32.04oejThe problem with doing it in a branch is that we have to port patches every time we change something...
17:32.18oejBut if we take it in small baby steps, then it's easier to handle.
17:32.41oejNo need to make a big cut and split it all out over the disk with no one that understands anything...
17:32.48oejAnyway, we'll discuss it later.
17:33.04oejPlease, please check the cause codes ;-)
17:35.11oejlmadsen: see bug #13385 where there is notes about it...
17:49.51*** join/#asterisk-dev JerJer (n=PhatJ@24-236-207-64.dhcp.aldl.mi.charter.com)
17:51.08*** join/#asterisk-dev shazaum (n=shazaum@unaffiliated/shazaum)
18:05.31*** part/#asterisk-dev macli (n=macli@nmc.brc.ubc.ca)
18:28.20lmadsenM13385
18:28.22MuffinMan[assigned] [Asterisk] Channels/chan_sip/NewFeature 0013385: [patch] Reason header support reported by adomjan (Karma: +12.50) http://bugs.digium.com/view.php?id=13385
18:58.58*** join/#asterisk-dev russellb (n=russell@asterisk/digium-open-source-team-lead/russellb)
18:58.58*** mode/#asterisk-dev [+o russellb] by ChanServ
19:13.01*** join/#asterisk-dev eliel (n=eliels@201.220.173.63)
19:13.01*** mode/#asterisk-dev [+o eliel] by ChanServ
19:13.44elielhello all
19:15.38putnopvuthie eliel
19:15.42putnopvuts/hie/hi/
19:18.17elielback again  submitting my trivial bugs :-)
19:18.36putnopvutany bug fix is a good bug fix
19:23.12lmadseneliel: you're back!
19:24.31elielhey! I will start working on xml docs to complete the missed stuff (agi at least)
19:25.38lmadsensweet!
19:25.41lmadsenwe love docs
19:41.46Corydon76-diglmadsen: I misread that, first time through
19:42.13lmadsenLOL
19:42.15lmadsenyou would :)
19:51.43*** join/#asterisk-dev sasargen (n=chatzill@174-146-41-34.pools.spcsdns.net)
20:21.07codefreeze-lapI am not impressed with the AST_CONTROL frames, and just how many hang up causes they pass back:  basically  BUSY, CONGESTION, .... that's it folks, besides the standard ANS, NO-ANS... am I missing something?
20:23.55*** join/#asterisk-dev Damin (n=damin@nucleus.nacs.net)
20:57.22Corydon76-digcodefreeze-lap: you're missing that the Hangup app lets you send back any cause you like
20:58.02Corydon76-digSo admins get control over what they signal from the dialplan
21:06.48codefreeze-lapCorydon76-dig: yes, I was missing the Hangup() app.... that's pretty neat.
21:14.02sasargenFunky problem with app_voicemail in 1.4.23.1, seems to have a problem in play_record_review handling 'S' being returned by ast_play_and_record_full when there is a silence timeout, if maxsilence=10 and a 10sec silent call comes in, then vm recording is truncated to 200ms, but duration shows as 10sec, so message isn't discarded even though minmessage=3
21:14.42Corydon76-digsasargen: Please report issues like that on bugs.digium.com
21:27.00seanbrightyou know what sucks?
21:27.06seanbrightbeing smarter than everyone else
21:27.15seanbrightand i have to live with that _everyday_
21:28.20putnopvutseanbright: I have not had to worry about that since I started working at Digium.
21:28.32seanbrightputnopvut: you're lucky.  it's a curse!
21:28.52putnopvutseanbright: I had to deal with it in high school and college
21:29.08putnopvutI sound like such a conceited jackass for saying that.
21:29.17seanbrightyeah you do
21:29.20seanbrighti don't even know you anymore
21:29.56Corydon76-digI've never had to live with that
21:30.28Corydon76-digEverytime I've ever thought that, I get taken down a notch by someone I completely don't expect
21:30.58seanbrightyeah, i've never run into that situation
21:31.05seanbrighti'm simply the smartest person alive.
21:31.13seanbrightthat is the only logical conclusion.
21:31.13filerrrrrrrrrright
21:31.19Corydon76-digYou would have hated growing up in my family
21:31.40seanbrighti don't doubt that
21:31.40seanbright:P
21:31.57Corydon76-digEvery single one of my siblings excels in a distinct area
21:32.37Corydon76-digHistory, physics, geology, computers, and music are where the 5 of us stand
21:32.56seanbrighti'm known for my mastery of all of those fields
21:32.59seanbrightask me anything
21:33.21Corydon76-digWhat's the average wingspeed of an African swallow?
21:33.29seanbrightsaw that one coming from a _mile_ away
21:34.15mnicholsonwhat years were the war of 1812 fought over?
21:34.42seanbright1812 to 1815
21:34.57seanbrightunless you mean the french invasion of russia
21:35.02Corydon76-digWho is buried in Grant's tomb?
21:35.08mnicholsonyou should be able to answer any of our questions, you have google
21:35.16seanbrighti'm not really smart
21:35.23seanbrightjust wanted to know what it felt like for a second
21:35.28seanbrightand it has passed
21:38.23*** join/#asterisk-dev macli (n=macli@nmc.brc.ubc.ca)
21:43.17*** join/#asterisk-dev kpfleming (n=kpflemin@asterisk/digium-director-of-software-tech/kpfleming)
21:43.17*** mode/#asterisk-dev [+o kpfleming] by ChanServ
22:06.39*** join/#asterisk-dev manxpower (n=Administ@router.asteriasgi.com)
22:07.01manxpowerGood job on /etc/dahdi/modules guys!
22:07.02*** join/#asterisk-dev eliel (n=eliels@201.220.173.63) [NETSPLIT VICTIM]
22:07.02*** join/#asterisk-dev seanbright (n=sean@asterisk/contributor-and-bug-marshal/seanbright) [NETSPLIT VICTIM]
22:07.02*** mode/#asterisk-dev [+oo eliel seanbright] by irc.freenode.net
22:09.16*** join/#asterisk-dev lmadsen (n=Leif@asterisk/documenteur-extraordinaire/blitzrage)
22:09.16*** mode/#asterisk-dev [+o lmadsen] by ChanServ
22:10.40*** join/#asterisk-dev russellb (n=russellb@asterisk/digium-open-source-team-lead/russellb)
22:10.40*** mode/#asterisk-dev [+o russellb] by ChanServ
22:11.42*** join/#asterisk-dev eliel_ (n=eliels@201.220.173.63)
22:19.38*** join/#asterisk-dev eliel (n=eliels@201.220.173.63)
22:19.39*** mode/#asterisk-dev [+o eliel] by ChanServ
22:22.14jpeelerwhat do i need to call to do tilda expansion for a path?
22:22.58seanbrightglob?
22:23.28seanbrightthat's a lie
22:23.34russellbi think that's a shell thing ...
22:23.40seanbrightwordexp
22:24.06seanbrightman 3 wordexp
22:24.06russellbooh, nice
22:24.11seanbrightdidn't know that existed
22:24.11seanbright:)
22:24.14russellbi didn't either
22:24.15russellbneat
22:24.16seanbrightand now i know
22:24.19seanbrightand knowing is half the battle
22:24.20jpeelerme either, thanks
22:25.17seanbrightchecks for an openbsd manpage for wordexp
22:25.25russellbit's POSIX
22:25.31seanbrighti know
22:25.36seanbrightbut i want to ensure it's there
22:25.39seanbrightit's a preemptive strike
22:25.42russellbheh
22:26.02seanbright"Sorry, no data found for `wordexp'.
22:26.03seanbright"
22:26.11jpeeleroh man :(
22:26.44seanbrightfreebsd has it
22:27.02jpeeleri guess i'll just handle it in the shell
22:27.05Corydon76-digLinux has it, too
22:27.20seanbrightopenbsd ruins EVERYTHING
22:27.21seanbrightheh
22:27.26seanbrightmvanbaak: earmuffs!
22:27.41seanbrightjeez, irix even has it
22:27.52seanbrightirix.  the latin of operating systems.
22:28.13Corydon76-digseanbright: did you install manpages-posix-dev ?
22:28.19seanbrightCorydon76-dig: no
22:28.32Corydon76-digseanbright: That will make it show up on Linux
22:29.03seanbrighti already saw it here
22:29.19Corydon76-digI know, but you said it was missing
22:29.23seanbrightwhere?
22:29.41Corydon76-dig[16:26:01] <seanbright> "Sorry, no data found for `wordexp'.
22:29.46seanbrightyeah, on openbsd
22:30.03Corydon76-digOh.  Well, who uses obsd, anyway?
22:30.07seanbrightmvanbaak
22:30.18seanbrightand i _think_ that's it
22:30.25Corydon76-digseanbright: that was a rhetorical question
22:30.40seanbrightwell then i shouldn't have responded
22:46.00seanbrightdamn, this function is hardcore
22:46.42seanbrightjust reading the first paragraph of "The expansion" section of the man page gets me all emotional
22:48.59putnopvutwhich function? wordexp?
22:49.11seanbrightyeah
22:55.24*** join/#asterisk-dev w9sh (n=sph@adsl-068-209-117-205.sip.asm.bellsouth.net)
23:05.03jpeelerso i guess we don't use the custom merge commands for changes to menuselect?
23:09.06seanbrightwe do
23:09.09seanbright1.0 -> trunk
23:10.54jpeelerseanbright: you mean just commit to 1.0 and then trunk then?
23:11.06seanbrightcommit to 1.0 and then svnmerge to trunk
23:11.11seanbrighti... think
23:11.45seanbrightohhh
23:11.49seanbrightyou're right
23:11.53seanbrightsorta
23:12.14jpeelerwell i didn't see any particular properties set for menuselect
23:12.24seanbrighttrunk has the blocked and merged props, but not the svnmerge-integrated one
23:12.25jpeelerso i don't know how the proper merge should go
23:12.49jpeelerit does?
23:12.53seanbrightyeah
23:13.04seanbrightaccording to viewvc, anyway
23:13.12jpeeleroh, how did i miss that
23:13.12seanbrightbranch-1.0-blocked /branches/1.0:49,132
23:13.14seanbrightbranch-1.0-merged /branches/1.0:1-316,383,437
23:13.21seanbrightshrugs
23:13.24seanbrightit's friday
23:35.00seanbrightam i imaginging something, or does svn 1.5 auto-resolve conflicts somehow?
23:35.24putnopvutseanbright: I know it has interactive conflict resolution...
23:35.33putnopvutBut not sure beyond that.
23:35.42seanbrightwell i had a file in conflict
23:35.45seanbrighti editted it
23:35.48seanbrightsvn status
23:35.55seanbrightshows an M
23:36.04seanbrightmight be the svn minor mode i have installed.
23:37.33seanbrightgoes home
23:38.28putnopvuthave a good weekend!
23:38.35putnopvut...or I'll have you shot
23:38.55*** part/#asterisk-dev russellb (n=russellb@asterisk/digium-open-source-team-lead/russellb)

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