| 00:02.14 | snuff-work | nope |
| 00:02.17 | snuff-work | *done |
| 00:03.04 | jdoe | danke |
| 00:11.36 | *** join/#asterisk-dev snuff-work (~aaa@210.9.82.197) |
| 00:11.36 | *** mode/#asterisk-dev [+o snuff-work] by ChanServ |
| 00:11.48 | Kobaz | how many developers does it take... |
| 00:12.33 | Kobaz | to get the the center of a tootsie roll |
| 00:14.06 | *** join/#asterisk-dev snuff-work (~aaa@210.9.82.197) |
| 00:14.06 | *** mode/#asterisk-dev [+o snuff-work] by ChanServ |
| 00:16.31 | *** join/#asterisk-dev snuff-work (~aaa@210.9.82.197) |
| 00:16.31 | *** mode/#asterisk-dev [+o snuff-work] by ChanServ |
| 00:20.26 | *** join/#asterisk-dev snuff-work (~aaa@210.9.82.197) |
| 00:20.26 | *** mode/#asterisk-dev [+o snuff-work] by ChanServ |
| 00:24.11 | *** join/#asterisk-dev snuff-work (~aaa@210.9.82.197) |
| 00:24.11 | *** mode/#asterisk-dev [+o snuff-work] by ChanServ |
| 00:25.41 | *** join/#asterisk-dev snuff-work (~aaa@210.9.82.197) |
| 00:25.41 | *** mode/#asterisk-dev [+o snuff-work] by ChanServ |
| 00:29.42 | jdoe | snuff-work: if you're feeling keen, 15483 shouldn't be closed either. The language issue may well be fixed, but the "immediately playing sorry" bit is still in 1.6.2.5 |
| 00:29.51 | jdoe | M15483 |
| 00:29.53 | MuffinMan | [closed] [Asterisk] Applications/app_followme 0015483: FollowMe plays wrong sound files reported by alex70 https://issues.asterisk.org/view.php?id=15483 |
| 00:50.37 | jdoe | guess not. |
| 00:50.40 | jdoe | :) |
| 00:53.16 | *** join/#asterisk-dev snuff-work (~aaa@210.9.82.197) |
| 00:53.16 | *** mode/#asterisk-dev [+o snuff-work] by ChanServ |
| 00:57.16 | alecdavis | corydon76-dig: just swatting up on bamboo, and I notice in the bamboo logs that app_voicemail unit test doesn't run? |
| 00:57.21 | alecdavis | 26-Feb-2010 12:48:42 END apps/app_voicemail/ - test_voicemail_msgcount Time: 17ms Result: NOT RUN |
| 00:59.40 | jdoe | whee, my first patch.. |
| 02:20.31 | *** join/#asterisk-dev kpfleming (~kpfleming@asterisk/digium-director-of-software-tech/kpfleming) |
| 02:20.31 | *** mode/#asterisk-dev [+o kpfleming] by ChanServ |
| 02:42.32 | *** join/#asterisk-dev sruffell (~sruffell@asterisk/the-kernel-guy/sruffell) |
| 02:42.32 | *** mode/#asterisk-dev [+o sruffell] by ChanServ |
| 04:48.05 | *** part/#asterisk-dev alecdavis (~alec@202.36.76.21) |
| 05:48.40 | *** join/#asterisk-dev xpot-mobile (~xpot@70-91-210-233-BusName-Utah.hfc.comcastbusiness.net) |
| 07:07.53 | wedhorn | mvanbaak: ping |
| 07:12.07 | mvanbaak | you caught me on my way to work |
| 07:15.18 | *** join/#asterisk-dev tzafrir (~tzafrir@local.xorcom.com) |
| 07:15.18 | *** mode/#asterisk-dev [+o tzafrir] by ChanServ |
| 07:37.42 | *** join/#asterisk-dev sgimeno (~chatzilla@226.Red-80-33-64.staticIP.rima-tde.net) |
| 08:02.42 | wedhorn | mvanbaak: I got distracted by other stuff |
| 08:03.12 | wedhorn | Was just going to ask about the latest couple of transmit_ patches for skinny |
| 08:03.56 | wedhorn | I've pretty much done a patch for transmit_callstate which was fairly extensive and horrible, testing at the moment, but would be nice to have the others committed |
| 08:26.26 | *** join/#asterisk-dev tamiel (~tamiel@213.30.183.226) |
| 08:26.41 | mvanbaak | wedhorn: I'll commit them after work |
| 08:29.01 | wedhorn | sounds good, I'll update the patch and post when I get up ... |
| 10:10.07 | tzafrir | Is the (read-only) svn.asterisk.org out of sync with origsvn? |
| 10:10.19 | tzafrir | The latest version I see in DAHDI is 8121 |
| 10:10.35 | tzafrir | Both in svnview and in a svn client checkout |
| 11:18.30 | snuff-home | mm.. i see what u mean tzafrir |
| 11:19.24 | snuff-home | 8121 svn.ast... and 8182 is orig |
| 11:19.50 | snuff-home | maybe it is broken.. ask one of the digium guys in bout 1-3 hrs :) |
| 11:55.25 | *** join/#asterisk-dev Victor_Yure (~victor@unaffiliated/victoryure/x-837844) |
| 11:55.56 | *** join/#asterisk-dev atis_work (~atis_work@193.238.212.171) |
| 12:10.30 | *** join/#asterisk-dev caio1982 (~caio1982@CAcert-br/caio1982) |
| 12:39.38 | *** join/#asterisk-dev kpfleming (~kpfleming@asterisk/digium-director-of-software-tech/kpfleming) |
| 12:39.39 | *** mode/#asterisk-dev [+o kpfleming] by ChanServ |
| 13:43.38 | *** join/#asterisk-dev codefreeze-lap (~murf@mail.parsetree.com) |
| 13:43.38 | *** mode/#asterisk-dev [+o codefreeze-lap] by ChanServ |
| 14:03.14 | *** join/#asterisk-dev leifmadsen (~Leif@asterisk/documenteur-extraordinaire/blitzrage) |
| 14:03.14 | *** mode/#asterisk-dev [+o leifmadsen] by ChanServ |
| 14:49.11 | *** join/#asterisk-dev moy (~chatzilla@74.12.129.100) |
| 14:53.35 | *** join/#asterisk-dev putnopvut (~putnopvut@asterisk/master-of-queues/mmichelson) |
| 14:53.35 | *** mode/#asterisk-dev [+o putnopvut] by ChanServ |
| 15:09.13 | *** join/#asterisk-dev hehol (~hehol@buero-gw.dortmund.loca.net) |
| 15:47.14 | tzafrir | <tzafrir> Is the (read-only) svn.asterisk.org out of sync with origsvn? |
| 15:47.14 | tzafrir | <tzafrir> The latest version I see in DAHDI is 8121 |
| 15:53.56 | *** join/#asterisk-dev datachomper (~Adium@nat/digium/x-ngwajyhgzrgnrhgv) |
| 15:57.42 | *** join/#asterisk-dev sruffell (~sruffell@asterisk/the-kernel-guy/sruffell) |
| 15:57.43 | *** mode/#asterisk-dev [+o sruffell] by ChanServ |
| 15:59.01 | *** join/#asterisk-dev jeffg (~jeffg@pdpc/supporter/professional/jeffg) |
| 15:59.38 | *** join/#asterisk-dev jpeeler (~jpeeler@asterisk/digium-software-dev/jpeeler) |
| 15:59.38 | *** mode/#asterisk-dev [+o jpeeler] by ChanServ |
| 16:03.30 | *** join/#asterisk-dev marv (~timr@router.asteriasgi.com) |
| 16:04.32 | tzafrir | leifmadsen, here? ==^ |
| 16:05.03 | leifmadsen | tzafrir: eh? |
| 16:05.25 | leifmadsen | tzafrir: about the svn? not really my realm of expertise :) |
| 16:07.58 | *** join/#asterisk-dev codefreeze-lap (~murf@mail.parsetree.com) |
| 16:07.58 | *** mode/#asterisk-dev [+o codefreeze-lap] by ChanServ |
| 16:12.31 | *** join/#asterisk-dev Corydon76-lap (~Corydon76@nat/digium/x-qlfuqrygeqjcqayb) |
| 16:12.31 | *** mode/#asterisk-dev [+o Corydon76-lap] by ChanServ |
| 16:16.45 | *** join/#asterisk-dev Deeewayne (~dwayne@75.76.254.162) |
| 16:16.46 | *** mode/#asterisk-dev [+o Deeewayne] by ChanServ |
| 16:21.56 | tzafrir | M16906 |
| 16:21.58 | MuffinMan | [new] [Asterisk] Resources/res_musiconhold 0016906: moh files install under datadir, at runtime: under varlibdir reported by tzafrir https://issues.asterisk.org/view.php?id=16906 |
| 16:23.15 | tzafrir | Any idea what can be done with this? I can fix it either way, but this in my way of making MoH packages |
| 16:24.03 | *** join/#asterisk-dev kpfleming (~kpfleming@asterisk/digium-director-of-software-tech/kpfleming) |
| 16:24.03 | *** mode/#asterisk-dev [+o kpfleming] by ChanServ |
| 16:52.07 | *** join/#asterisk-dev jameswf (~james@unaffiliated/jameswf-home) |
| 16:56.32 | *** join/#asterisk-dev Victor_Yure (~victor@unaffiliated/victoryure/x-837844) |
| 16:56.34 | *** join/#asterisk-dev anthm (~anthm@freeswitch/developer/anthm) |
| 17:05.14 | *** join/#asterisk-dev ArtemMakhutov (~ArtemMakh@ip-95-223-6-41.unitymediagroup.de) |
| 17:05.24 | Kobaz | what's the max length of an agument to a ami command? |
| 17:05.27 | Kobaz | argument |
| 17:09.01 | kpfleming | there probably isn't one; they are parsed and stored in a variable list using dynamically allocated memory |
| 17:09.02 | seanbright | let me take a quick look at the source code |
| 17:09.09 | Kobaz | i'm digging |
| 17:09.12 | Kobaz | i think i found something |
| 17:09.18 | seanbright | i'll go ahead and open main/manager.c to have a look for you |
| 17:09.22 | Kobaz | struct mansession_session { |
| 17:09.28 | Kobaz | <PROTECTED> |
| 17:10.11 | Kobaz | seanbright: you don't have to look, i was just wondering if anyone knew offhand |
| 17:11.08 | Kobaz | in get_input, maxlen is set to the size of inbuf... and then you get "Dumping long line with no return from %s", if it's bigger |
| 17:11.24 | Kobaz | i thought it was dynamically sized too, until i started sending large chunks of data |
| 17:11.29 | seanbright | hmm. |
| 17:11.41 | Kobaz | it creates invalid manager events, with oversized data |
| 17:11.50 | Corydon76-lap | and you needed to send large chunks of data, because... ? |
| 17:11.56 | Kobaz | Action: UserEvent |
| 17:11.58 | Kobaz | ICAgICAgICAgICAgI.... |
| 17:12.13 | Kobaz | Corydon76-lap: because i'm using the ami as a data transport for my unit tests |
| 17:12.15 | Corydon76-lap | Sick |
| 17:12.39 | seanbright | m.headers[m.hdrcount++] = ast_strdupa(header_buf); |
| 17:13.00 | Corydon76-lap | seanbright: that's in a loop, isn't it? |
| 17:13.04 | seanbright | yes. |
| 17:13.12 | seanbright | i'm scared |
| 17:13.13 | seanbright | heh. |
| 17:13.15 | Kobaz | heh |
| 17:13.42 | Corydon76-lap | puts seanbright in a loop |
| 17:14.44 | *** join/#asterisk-dev paulc (~paulc@unaffiliated/paulc) |
| 17:15.05 | Corydon76-lap | Morning, Paul |
| 17:16.35 | Kobaz | so it allocates the space for it, but then dumps it and causes malformed events if it goes over the magic limit |
| 17:16.40 | paulc | Morning :) |
| 17:16.52 | paulc | Olympics over, it's back to the daily grind in earnest.. Zzzz |
| 17:16.55 | paulc | How's things? |
| 17:17.12 | Corydon76-lap | A little low on caffeine... |
| 17:19.10 | paulc | I hear you.. not a coffee drinker, but I could do with something to kickstart my Monday morning |
| 17:19.16 | *** join/#asterisk-dev The_Boy_Wonder (~vossel@asterisk/batman-developer/dvossel) |
| 17:19.16 | *** mode/#asterisk-dev [+o The_Boy_Wonder] by ChanServ |
| 17:19.35 | Kobaz | you can kickstart your morning with some lovely bugs |
| 17:19.37 | paulc | Got a whiteboard session with the boss coming up, him explaining out 2010 deliverables.. "watching paint dry" springs to mind.. |
| 17:19.44 | paulc | Kobaz: or that :-) |
| 17:28.29 | tzafrir | sruffell, if most users don't need codec_dahdi, maybe just change the error message |
| 17:28.58 | sruffell | as opposed to changing it so it's not loaded by default? |
| 17:29.22 | tzafrir | Please consider the documented procedure for a customer of yours who needs to install such a card from supported binary packages |
| 17:30.43 | sruffell | Wouldn't it be: insert the card, add the driver to /etc/dahdi/modules, add load => codec_dahdi.so to /etc/asterisk/modules.conf? |
| 17:37.32 | *** join/#asterisk-dev ManxPower-work (~manxpower@216.186.151.147) |
| 17:39.41 | ManxPower-work | Any idea how to get in contact with issues.digium.com reporter "gareth"? |
| 17:44.14 | kpfleming | leifmadsen: ^^^ you could email gareth on ManxPower-work's behafl |
| 17:44.22 | kpfleming | s/behafl/behalf/ |
| 17:45.11 | ManxPower-work | He wrote the CONNECTEDLINE patch for 1.4.23.1, we wanted to give him first option to do a bounty to port it to 1.4.29.mumble |
| 17:46.25 | leifmadsen | kpfleming: ya, I could email him |
| 17:46.38 | leifmadsen | ManxPower-work: email me whatever information you'd like to pass along to lmadsen AT digium DOT com |
| 17:46.38 | kpfleming | well.. at the risk of offending anyone's sensibilities, that functionality is also available in Asterisk Business Edition C.3.x, which is 1.4-based |
| 17:49.36 | ManxPower-work | leifmadsen, thanks |
| 17:49.52 | ManxPower-work | acts all offended and stuff |
| 17:50.02 | seanbright | Kobaz: if when you say "argument to an AMI command" you mean maximum header length, then yes, you are right. it is 1024 less the length of the header name and such. |
| 17:50.18 | ManxPower-work | 8-) |
| 17:50.32 | Kobaz | yeah |
| 17:59.48 | *** join/#asterisk-dev TheDavidFactor (~chatzilla@nc-71-0-16-133.dhcp.embarqhsd.net) |
| 18:07.25 | *** join/#asterisk-dev kerframil (~kerframil@gentoo/user/kerframil) |
| 18:35.20 | mvanbaak | hhmm, asterisk wont compile on osx ;) |
| 18:35.36 | mvanbaak | <--- known for finding non-compiling setups |
| 18:36.14 | mvanbaak | ManxPower-work: it's already been ported :) |
| 18:36.36 | mvanbaak | ManxPower-work: have a look at the issue on mantis |
| 18:36.48 | ManxPower-work | mvanbaak, I only see it ported to 1.6.x |
| 18:37.07 | mvanbaak | ManxPower-work: I added a new version of the patch. Work was sponsored by Israpunt (dutch company) |
| 18:37.27 | ManxPower-work | mvanbaak, Ah! Are you "gareth"? |
| 18:37.45 | mvanbaak | nope |
| 18:38.47 | ManxPower-work | Heh! Last time I looked at the patch was the first week of Feb. |
| 18:39.14 | mvanbaak | ManxPower-work: I can find the issue number for you if you want |
| 18:39.36 | ManxPower-work | Oh, I found it. |
| 18:39.54 | mvanbaak | ah, ok |
| 18:39.57 | ManxPower-work | hopefully leifmadsen has not forwarded the bounty yet. 8-) |
| 18:40.04 | mvanbaak | ManxPower-work: lol |
| 18:40.18 | ManxPower-work | that's what I get for not reconfirming ALL my facts. |
| 18:40.24 | leifmadsen | ManxPower-work: I haven't done anything as I was at lunch and am now working on documentation. I won't get to your email until later this afternoon |
| 18:40.43 | ManxPower-work | leifmadsen, just delete the message. |
| 18:40.47 | leifmadsen | ManxPower-work: okie |
| 18:40.52 | ManxPower-work | leifmadsen, thanks! |
| 18:41.07 | Corydon76-lap | mvanbaak: which branch are you trying to compile on OS X? |
| 18:41.22 | mvanbaak | Corydon76-lap: trunk |
| 18:41.42 | Corydon76-lap | What version of OS X? |
| 18:42.00 | mvanbaak | 10.5.8 |
| 18:42.03 | mvanbaak | app_voicemail.c:9588: warning: control may reach end of non-void function 'vm_intro' being inlined |
| 18:42.38 | mvanbaak | and some other obscure lines after that |
| 18:42.55 | mvanbaak | standard input}:54426:non-relocatable subtraction expression, "_vm_execmain" minus "L00000000103$pb" |
| 18:42.58 | mvanbaak | {standard input}:54426:symbol: "_vm_execmain" can't be undefined in a subtraction expression |
| 18:43.01 | Corydon76-lap | I regularly test 10.4, so maybe you just need to downgrade until Apple fixes it |
| 18:43.29 | Corydon76-lap | Tiger FTW |
| 18:43.53 | mvanbaak | maybe I should ditch osx and install a real operating system |
| 18:44.12 | Kobaz | heh |
| 18:44.43 | Corydon76-lap | I won't argue that point |
| 18:45.08 | Corydon76-lap | It is, after all, my game platform |
| 18:45.17 | mvanbaak | ah well, wedhorn will have to wait some more |
| 18:45.40 | Corydon76-lap | Yep, 10.4 compiles fine |
| 18:49.25 | Corydon76-lap | Welcome to heaven; here's your Mac. Welcome to hell; here's your Windows Vista machine. Welcome to purgatory; here's your computer with no OS and the installation media of your choice. |
| 18:50.59 | mvanbaak | nah, I really like osx |
| 18:51.08 | mvanbaak | I just think it sux as development machine |
| 18:51.38 | Corydon76-lap | It rocks, as long as you're writing a Cocoa app with Objective C. |
| 18:51.43 | mvanbaak | and that's probably because I spent very little time on it |
| 18:52.04 | Corydon76-lap | For any other combination, however..... |
| 18:52.29 | mvanbaak | I use my iBook in my livingroom because it's small and looks better then a ThinkPad |
| 18:52.47 | Corydon76-lap | but then again, why do you need any environment other than the vim editor, gcc, and a command line interface? |
| 18:52.55 | *** join/#asterisk-dev Marquis42 (~bfhbmw0@65-127-126-34.dia.static.qwest.net) |
| 18:53.02 | mvanbaak | agreed |
| 18:53.11 | mvanbaak | ah well |
| 18:53.17 | mvanbaak | time for ssh ;) |
| 18:53.22 | Corydon76-lap | Yay for 'make menuselect' being fixed... |
| 18:53.48 | Corydon76-lap | mvanbaak: Oh, and I compile on 10.4 on both PPC and x86 platforms |
| 18:54.02 | Corydon76-lap | so doubleplusgood |
| 18:55.52 | mvanbaak | nice |
| 18:55.57 | mvanbaak | 10.5 is borked |
| 18:56.11 | Corydon76-lap | Not as badly as 10.6, apparently |
| 18:56.30 | Corydon76-lap | oej has all sorts of problems on 10.6 |
| 18:56.41 | mvanbaak | yeah, I noticed |
| 18:57.04 | mvanbaak | compiles on openbsd current as well |
| 18:57.34 | mvanbaak | had to get up from the sofa, walk into the office, and poweron my thinkpad |
| 18:57.53 | Corydon76-lap | Meeting time, bbl |
| 18:58.19 | mvanbaak | now I can start committing patches again ;) |
| 19:00.48 | *** join/#asterisk-dev niekvlessert (~niek@5ED25657.cable.ziggo.nl) |
| 19:01.54 | mvanbaak | hey Niek |
| 19:02.27 | mvanbaak | ManxPower-work: niekvlessert is the one who sponsored the connected_line backport |
| 19:03.39 | niekvlessert | hey mvanbaak :) |
| 19:03.39 | niekvlessert | yeah :) |
| 19:03.40 | ManxPower-work | mvanbaak, do you know of any G722 transcoding backports for 1.4.x? |
| 19:03.40 | ManxPower-work | niekvlessert, Thanks for doing the connected line patch! |
| 19:03.40 | niekvlessert | well no problem :) |
| 19:04.29 | niekvlessert | only problem now is that i want to run it on 1.4.26.2, tomorrow I will change the patch :D |
| 19:05.14 | snuff-home | i dont think g722 16k is an easy backport |
| 19:05.44 | mvanbaak | ManxPower-work: not that I know of |
| 19:05.54 | mvanbaak | snuff-home: nope, wont be a simple task |
| 19:06.40 | ManxPower-work | snuff-home maybe the codec neg patch, to make passthru work well. |
| 19:08.17 | ManxPower-work | There is some support for g722 already in 1.4 |
| 19:09.29 | snuff-home | passthru wouldn't be so bad from what i remember.. |
| 19:09.48 | jdoe | another dumb question... having submitted a patch, is there anything that needs to be done to put it in front of someone to approve/reject, or will it filter to them eventually on its own? |
| 19:10.13 | snuff-home | jdoe: a dev will eventually pick it up |
| 19:10.23 | jdoe | snuff-home: cool, thanks. |
| 19:10.32 | snuff-home | best thing u can do is get OTHERS to try it and put if it works for them |
| 19:10.41 | snuff-home | on the bug |
| 19:10.56 | jdoe | not sure how well I can do that. Apparently nobody uses followme if neither of these have been caught by now, they've been broken for at least 5 versions :) |
| 19:11.22 | mvanbaak | food, brb |
| 19:11.42 | snuff-home | gets ready for work.. |
| 19:12.05 | *** join/#asterisk-dev hardwire (~spencersr@69-161-26-211.static.acsalaska.net) |
| 19:12.08 | hardwire | seanbright: better? |
| 19:12.14 | seanbright | whichev |
| 19:12.32 | hardwire | ok.. I just set the stacksize to a static size to test |
| 19:12.34 | hardwire | buuuuut |
| 19:12.43 | hardwire | I'd rather you were awesome and fixed it |
| 19:12.45 | hardwire | lemme check |
| 19:12.46 | seanbright | ditto |
| 19:13.40 | hardwire | heh |
| 19:14.15 | hardwire | seanbright: weird.. why would that work on the first attempt to enter voicemail but crash on the second attempt? |
| 19:14.23 | hardwire | nevermind.. I'll patch and see if it fixes it |
| 19:14.34 | seanbright | because there are no items in the container the first time through so the callback is never called |
| 19:14.42 | hardwire | ok |
| 19:14.45 | seanbright | and arg is never dereferenced |
| 19:14.57 | hardwire | you know what's nice about this? |
| 19:15.00 | hardwire | I'm not crazy. |
| 19:16.58 | *** join/#asterisk-dev atis_work (~atis_work@193.238.212.171) |
| 19:17.24 | hardwire | grabs a paper towel roll and waits for the compile |
| 19:17.43 | seanbright | pretends to get the reference |
| 19:18.10 | hardwire | http://xkcd.com/303/ |
| 19:18.15 | hardwire | they have swords tho.. I only have rolls. |
| 19:18.29 | seanbright | aha. |
| 19:18.41 | hardwire | seanbright: sorry.. I'm trying to make the most of my monday. |
| 19:19.08 | hardwire | I was supposed to move from asterisk 1.2 to 1.6 on a different machine over the weekend.. and my boss thinks "just move all the extensions, what's the big deal" |
| 19:19.12 | hardwire | different IPs.. different everything |
| 19:19.24 | hardwire | it's a lot of planning and reorganizing that needed to be done in the first place by the previous admin |
| 19:19.30 | hardwire | so this bug is a welcome break |
| 19:19.42 | seanbright | well then i hope i didn't fix it |
| 19:22.58 | *** join/#asterisk-dev elguero (~miguel323@12.187.84.162) |
| 19:27.40 | tzafrir | hmm... any idea why all of a sudden menuselect would ask me to delete the makeopts file after a second build? |
| 19:31.12 | hardwire | hugs seanbright |
| 19:31.16 | seanbright | excellent |
| 19:31.48 | hardwire | tzafrir: are you adding fixup patches to your asterisk package? if so seanbright has a pretty one that fixes voicemail problems :) |
| 19:32.18 | tzafrir | hardwire, "my"? pkg-voip's |
| 19:32.24 | hardwire | updates.xorcom.com |
| 19:32.33 | hardwire | I suppose this patch should be done universally however. |
| 19:32.37 | tzafrir | I build it directly from the pkg-voip repo |
| 19:32.42 | hardwire | orly? |
| 19:32.46 | hardwire | sexy. ok then |
| 19:33.21 | tzafrir | Do you have a tested patch? |
| 19:33.27 | hardwire | yes |
| 19:33.32 | hardwire | https://issues.asterisk.org/file_download.php?file_id=25456&type=bug |
| 19:33.34 | mvanbaak | wedhorn: committed |
| 19:35.41 | seanbright | hardwire: committed |
| 19:35.43 | seanbright | heh |
| 19:37.03 | niekvlessert | seanbright, mvanbaak: |
| 19:37.18 | niekvlessert | today we tried the TON/NPI stuff again with Asterisk 1.6 |
| 19:37.24 | niekvlessert | and we passed the tests |
| 19:37.31 | seanbright | very nice |
| 19:37.47 | niekvlessert | so I would like to thank you ppl and the other for the information concerning these issues! |
| 19:39.08 | hardwire | seanbright: thanks a ton |
| 19:39.19 | hardwire | digium needs a "feed a programmer a cookie" button on the website. |
| 19:39.41 | datachomper | I like this cookie idea |
| 19:40.11 | seanbright | paypal has a similar feature |
| 19:40.19 | seanbright | "pay a person some money" |
| 19:40.22 | seanbright | heh |
| 19:40.30 | seanbright | so in lieu of a cookie, i except cash |
| 19:40.32 | seanbright | ;-) |
| 19:44.38 | hardwire | seanbright: hehe |
| 19:45.07 | hardwire | seanbright: somebody recently got me a gift certificate to a local brew pub for helping them with an NEC system which was nice. |
| 19:45.14 | hardwire | ok.. thank you seanbright |
| 19:45.20 | hardwire | gets rid of another IRC tab |
| 19:45.24 | *** part/#asterisk-dev hardwire (~spencersr@69-161-26-211.static.acsalaska.net) |
| 20:04.36 | tzafrir | menuselect insists that I should build the test framwork, even though it is not enabled |
| 20:04.41 | tzafrir | category 'MENUSELECT_TESTS' not found! Can't mark 'test_skel' as disabled. |
| 20:04.51 | tzafrir | (and such) |
| 20:16.02 | tzafrir | the name of the category in tests/Makefile is TEST*S* :-( |
| 20:16.59 | tzafrir | Wow, that's really bad. Nobody test-built building without tests? |
| 20:17.14 | *** join/#asterisk-dev atis_work (~atis_work@193.238.212.171) |
| 20:24.28 | *** join/#asterisk-dev hardwire (~spencersr@69-161-26-211.static.acsalaska.net) |
| 20:24.55 | hardwire | I found another book with localtime.c and the nanosleep(&ten_seconds, NULL); |
| 20:25.15 | hardwire | or something like that. posting now. |
| 20:25.33 | hardwire | the for loop that line is in is in a for loop that lasts forever |
| 20:25.37 | hardwire | weeee |
| 20:30.30 | hardwire | book/bug |
| 20:47.03 | niekvlessert | if i change a bunch of files, do a make and chan_features.c does not get compiled, but there's no error, where can i find the problem? |
| 20:47.56 | niekvlessert | excuse me; changelog states this |
| 20:54.20 | hardwire | woot.. I guess it has to do with pbx_spool and scan_thread |
| 20:59.06 | seanbright | i don't really understand what you are reporting |
| 20:59.48 | hardwire | seanbright: there's a better chance that I don't either |
| 20:59.52 | seanbright | is there a crash? |
| 20:59.56 | seanbright | does something not work? |
| 21:00.14 | hardwire | one sec. did you see the ticket or are you just commenting on my IRC banter? |
| 21:00.22 | seanbright | reading the ticket |
| 21:00.41 | hardwire | ok.. there is an eternal for loop with 0 usecs of sleep in it |
| 21:00.44 | hardwire | causes massive CPU trauma |
| 21:00.48 | *** join/#asterisk-dev datachomper (~Adium@nat/digium/x-celutotxjkdtpdiv) |
| 21:00.51 | seanbright | ok |
| 21:00.59 | seanbright | what distro? |
| 21:01.00 | *** join/#asterisk-dev datachomper (~Adium@nat/digium/x-zdsvbhalayixiemy) |
| 21:01.09 | hardwire | using tzafrirs debian x86_64 packages |
| 21:01.28 | hardwire | apparently from pkg-voip |
| 21:02.26 | seanbright | do they uses patches that aren't in our repository? |
| 21:02.37 | hardwire | one sec |
| 21:03.00 | tzafrir | seanbright, not many |
| 21:03.17 | tzafrir | Nothing big |
| 21:03.23 | tzafrir | what ticket is it? |
| 21:03.32 | seanbright | M16938 |
| 21:03.35 | MuffinMan | [new] [Asterisk] PBX/pbx_spool 0016938: For loop never exists when calling an extension that exists with BUSY, failure to leave 'for' loop in 'scan_thread' reported by whardier https://issues.asterisk.org/view.php?id=16938 |
| 21:03.57 | seanbright | i feel like this is the detached daemon while trying to read from /dev/null issue |
| 21:03.59 | hardwire | yeh.. monday isn't my best day to use english |
| 21:04.08 | hardwire | inotify_daemon? |
| 21:04.11 | seanbright | no |
| 21:04.44 | seanbright | ps -ef | grep asterisk |
| 21:04.47 | seanbright | and pastebin that |
| 21:05.14 | hardwire | http://hardwire.pastey.net/133629 |
| 21:05.15 | *** join/#asterisk-dev alecdavis (~alec@202.36.76.21) |
| 21:05.22 | hardwire | I need to write a pastebin CLI |
| 21:05.41 | tzafrir | hardwire, try pastebinit |
| 21:05.42 | seanbright | i feel like taking that -c off the end will fix it |
| 21:05.43 | hardwire | dostuff | pastebin |
| 21:05.49 | hardwire | tzafrir: ooooh |
| 21:05.54 | leifmadsen | uh, isn't there already a fix for that in the tracker? |
| 21:06.00 | hardwire | seanbright: so don't run it in the console on tty 9? |
| 21:06.01 | hardwire | :P |
| 21:06.03 | leifmadsen | are you talking about asterisk -c in an init script on debian? |
| 21:06.06 | hardwire | I'll test it |
| 21:06.10 | seanbright | leifmadsen: yes |
| 21:06.42 | leifmadsen | seanbright: there is already a bug filed and I even provided a patch :) |
| 21:06.53 | leifmadsen | taking out the -c will fix it |
| 21:07.05 | seanbright | leifmadsen: ah. good. may not be his problem, but it sounds like the same symptoms. |
| 21:07.17 | seanbright | leifmadsen: what issue number? |
| 21:07.28 | seanbright | nm, i'll find it |
| 21:07.51 | leifmadsen | uhhh... ya, I don't have it assigned ot me |
| 21:07.52 | leifmadsen | sorry |
| 21:07.56 | leifmadsen | and I have to head out right now |
| 21:08.02 | leifmadsen | back in a bit! let me know if that fixed the problem |
| 21:08.08 | leifmadsen | I've been meaning to commit it |
| 21:08.17 | leifmadsen | someone else said it already fixed for them doing that |
| 21:08.28 | hardwire | sigh |
| 21:08.28 | seanbright | k |
| 21:08.44 | seanbright | M16887 |
| 21:08.46 | MuffinMan | [feedback] [Asterisk] General 0016887: /etc/init.d/asterisk.debian consumes 100% CPU reported by jlpedrosa https://issues.asterisk.org/view.php?id=16887 |
| 21:09.04 | seanbright | better yet... |
| 21:09.09 | seanbright | M16784 |
| 21:09.11 | MuffinMan | [ready for testing] [Asterisk] Core/General 0016784: [patch] 99.9 cpu when asterisk started with init.d script reported by pabelanger https://issues.asterisk.org/view.php?id=16784 |
| 21:09.50 | alecdavis | unit testing question. do we think it would be useful to catch segfaults and report them when unit testing, using the TEST_FRAMEWORK. currently most will let us know some thing is wrong in a harsh sort of way. |
| 21:09.50 | seanbright | M16784#118067 |
| 21:09.52 | MuffinMan | [16784#0118067] Commented by seanbright on 2010-02-14 at 11:16: Right, because we busy-loop trying to read from /dev/null since we lose our controlling terminal when we go into the background. |
| 21:09.58 | seanbright | smart guy! ^^^^ |
| 21:10.09 | hardwire | seanbright: ok.. I knocked the -c out.. I'm down to /usr/sbin/asterisk -p -g -U asterisk |
| 21:10.24 | hardwire | problem still exists. |
| 21:10.27 | seanbright | ok cool |
| 21:10.31 | seanbright | someone else will have to take a look then |
| 21:10.33 | wedhorn | mvanbaak: and another skinny patch for you. You should probably do a bit more testing on this one |
| 21:10.37 | hardwire | thank you anyways. |
| 21:10.40 | seanbright | no sweat |
| 21:10.45 | mvanbaak | wedhorn: I will |
| 21:11.07 | mvanbaak | wedhorn: that will also mean I wont commit it today |
| 21:11.20 | mvanbaak | 10:15 PM here |
| 21:11.32 | mvanbaak | and I'm working on some AGI shit |
| 21:11.46 | mvanbaak | hates customers |
| 21:12.05 | mvanbaak | they take too much time. time I want to spend on other stuff |
| 21:12.27 | hardwire | seanbright: yar.. ran it using strace and the nanosleep persists.. definately not fixed. :( oh well. I'll just disable device states! |
| 21:12.30 | hardwire | :P |
| 21:12.34 | wedhorn | mvanbaak: no problems, this one's fairly extensive and has the possibility of insidious bugs |
| 21:12.58 | mvanbaak | I noticed :) |
| 21:13.24 | mvanbaak | I'll run the normal set of tests, and see if my wife starts to yell at me |
| 21:13.50 | hardwire | is it noisy? |
| 21:13.57 | hardwire | I got barked at last night for that. |
| 21:14.03 | mvanbaak | lol |
| 21:14.11 | hardwire | paging a bunch of phones in the living room |
| 21:14.23 | hardwire | "BONG" "BONG" "BONG" "BONG" |
| 21:15.37 | wedhorn | mvanbaak: I'm doing the same, god bless our personal testers ... |
| 21:15.44 | mvanbaak | wedhorn: amen |
| 21:16.00 | tzafrir | alecdavis, how much do you trust code that runs after a segfault? |
| 21:17.18 | alecdavis | I don't, but so that bamboo can advise of failure would be good, otherwise what does bamboo report. |
| 21:17.36 | alecdavis | pass fail or didn't finish? |
| 21:17.49 | tzafrir | alecdavis, whatever you do, also consider SIGBUS |
| 21:18.09 | *** join/#asterisk-dev ArtemMakhutov (~ArtemMakh@ip-95-223-6-41.unitymediagroup.de) |
| 21:20.59 | tzafrir | will post-review also work from a anon-svn checkout? |
| 21:21.44 | tzafrir | hardwire, do we have that -c in the init.s script in the Debian deb? |
| 21:25.44 | hardwire | yes.. for asterisk safe and asterisk safe + console |
| 21:25.57 | seanbright | hardwire: do me a favor. download this http://pastebin.ca/1817871 |
| 21:26.00 | seanbright | save it as tspec.c |
| 21:26.06 | seanbright | gmake tspec |
| 21:26.09 | seanbright | ./tspec |
| 21:26.09 | hardwire | seanbright: sure |
| 21:26.11 | seanbright | and tell me the output |
| 21:27.00 | hardwire | installs build-essential |
| 21:27.23 | seanbright | oh. heh. my bad. |
| 21:27.30 | hardwire | http://pastebin.ca/1817876 |
| 21:28.08 | hardwire | seanbright: if you want access just shoot me an ssh key |
| 21:28.20 | hardwire | I'm less interested in security than I am crashing atm. :P |
| 21:29.00 | seanbright | meh... just testing a theory. |
| 21:29.13 | hardwire | that's fine |
| 21:29.27 | seanbright | everywhere we use nanosleep we properly initialize the timespec |
| 21:29.37 | hardwire | I usually don't bite on that one either.. not if I don't have a severe need |
| 21:30.02 | hardwire | seanbright: I was looking at that as well and it seemed like ten_second != ten seconds |
| 21:30.10 | hardwire | one sec.. I have a test |
| 21:33.03 | seanbright | in the version you are using, we use nanosleep in func_lock, pbx_spool, and localtime |
| 21:33.17 | hardwire | agreed |
| 21:33.30 | seanbright | let me look at localtime |
| 21:33.43 | hardwire | it appears as though nanosleep in localtime is not at fault |
| 21:33.45 | hardwire | just tested it |
| 21:34.03 | hardwire | it executed nanosleep({10, 0}, NULL) correctly |
| 21:34.08 | hardwire | according to strace |
| 21:34.14 | *** join/#asterisk-dev The_Boy_Wonder (~vossel@asterisk/batman-developer/dvossel) |
| 21:34.14 | *** mode/#asterisk-dev [+o The_Boy_Wonder] by ChanServ |
| 21:34.21 | *** part/#asterisk-dev The_Boy_Wonder (~vossel@asterisk/batman-developer/dvossel) |
| 21:35.00 | hardwire | same with pbx_spool |
| 21:35.30 | hardwire | and you had me test the timespec in func_lock |
| 21:35.45 | seanbright | did i? |
| 21:35.56 | seanbright | well, you tested it in a separate piece of code. |
| 21:35.59 | hardwire | in your pastebin.. same as forever in func_lock |
| 21:36.00 | hardwire | yeh |
| 21:36.08 | seanbright | let's try something silly... hold on |
| 21:36.10 | hardwire | the nanosleep that I'm dealing with may be part of a library |
| 21:36.18 | hardwire | <PROTECTED> |
| 21:36.26 | hardwire | thats bad mmkay |
| 21:36.28 | hardwire | heh |
| 21:37.29 | tzafrir | no. Can't post a review from the anon svn repo |
| 21:38.01 | seanbright | http://pastebin.ca/1817895 |
| 21:38.18 | hardwire | heh.. seanbright two processes in my strace, 17199 and 17198 are stuck in the loop |
| 21:38.29 | seanbright | which processes?/ |
| 21:38.46 | hardwire | and the nanosleep call doesn't finish in one before the other starts.. |
| 21:38.52 | tzafrir | ps -eLf #? |
| 21:38.57 | tzafrir | (to show threads) |
| 21:39.02 | hardwire | check out the strace.txt.gz if you have a chance.. It's not currently running |
| 21:39.13 | hardwire | I'll get you that real quick with a new strace and ps list |
| 21:40.07 | tzafrir | or 'H' in top |
| 21:40.36 | tzafrir | if you just want to see the top threads |
| 21:41.52 | hardwire | http://hardwire.pastey.net/133633 |
| 21:42.30 | hardwire | I chopped the long lines.. I can rerun the test if you need to see the process strings all the way through.. but they wouldn't be very different would they? |
| 21:43.16 | seanbright | ok, i don't know what the issue is |
| 21:43.18 | hardwire | I don't suppose thread 20795 would have been asterisk.. interesting.. /me checks the process list again |
| 21:43.44 | seanbright | it's poll() or read() or something calling nanosleep() |
| 21:44.21 | hardwire | the thread err.. pid?.. doesn't exist in the ps output |
| 21:44.31 | hardwire | the one that strace is reporting at least |
| 21:45.06 | hardwire | ah.. thread 20794 opens up /dev/dahdi/timer |
| 21:45.15 | hardwire | I don't have anything other than a dummy device |
| 21:45.32 | hardwire | should I try using the pthread timer if it isn't already that way? |
| 21:45.49 | seanbright | this is a wild goose chase |
| 21:45.49 | hardwire | then it clones itself.. then both do evil things |
| 21:45.51 | hardwire | and I want to cry. |
| 21:45.54 | hardwire | seanbright: thanks anyways |
| 21:45.59 | *** join/#asterisk-dev matt_d (~matt@70.134.98.183) |
| 21:46.07 | *** part/#asterisk-dev matt_d (~matt@70.134.98.183) |
| 21:48.09 | seanbright | hardwire: so if you just start asterisk and make no calls, your processor utlization stays low? |
| 21:48.18 | seanbright | or is it only when a call is made? |
| 21:48.19 | hardwire | yup |
| 21:48.48 | hardwire | when a call is made to a sip extension, only one tested, and that sip extension is in DND mode it will often have a problem and the thread will go nuts |
| 21:49.09 | hardwire | I've replaced Dial(SIP/xxxx) with Congestion() and there were no problems |
| 21:49.12 | seanbright | and asterisk becomes unresponsive? |
| 21:49.14 | hardwire | and Busy() |
| 21:49.21 | hardwire | seanbright: the entire machine goes out to lunch after about a minute |
| 21:49.26 | seanbright | gotcha |
| 21:50.56 | hardwire | ok I switched to pthread timer. |
| 21:51.02 | hardwire | attempts death |
| 21:51.19 | hardwire | death.. woo.. that gets me nowhere. |
| 21:51.52 | seanbright | and you're running 1.6.2.3-rc2? |
| 21:51.58 | hardwire | yup |
| 21:52.01 | seanbright | alrighty |
| 21:52.10 | hardwire | should I know better? |
| 21:52.11 | seanbright | you should upgrade to the latest version and test again |
| 21:52.15 | seanbright | 1.6.2.5 is out |
| 21:52.29 | seanbright | there have been 97 changes to asterisk 1.6.2 since 1.6.2.3-rc2 was tagged |
| 21:52.29 | hardwire | erm.. ok |
| 21:52.47 | hardwire | I bet I can pull that in from pkg-voip and get it going |
| 21:52.52 | seanbright | excellent |
| 21:53.15 | hardwire | I was hoping I could put this project off until 1.8 |
| 21:53.18 | hardwire | I nwant/need CEL |
| 21:53.23 | hardwire | nwant/want |
| 21:53.24 | hardwire | heh |
| 21:53.42 | seanbright | i don't even see 1.6.2.3-rc2 in pkg-voip |
| 21:53.53 | hardwire | that's cause you aren't awesome like me |
| 21:54.01 | seanbright | clearly |
| 21:54.18 | hardwire | heh.. what the crap |
| 21:54.35 | hardwire | tzafrir: you building from the trunk? is trunk at 1.6.3.2-rc2? |
| 21:54.43 | hardwire | err.. 1.6.2.3-rc2 |
| 21:54.47 | tzafrir | trunk of pkg-voip? yes |
| 21:55.09 | hardwire | ok.. seanbright stay tuned. |
| 21:55.17 | hardwire | does some regular expression magic |
| 21:55.19 | tzafrir | 1.6.2.4 and 1.6.2.5 were branched from 1.6.2.2 |
| 21:55.24 | Corydon76-lap | detunes seanbright |
| 21:55.35 | hardwire | Corydon76-lap: wot.. like you OWN HIM? |
| 21:55.47 | seanbright | i'm basing 97 changes on ./changes_since asterisk 1.6.2.3-rc2 |
| 21:56.36 | hardwire | seanbright: just asterisk I'm guessing.. not dahdi/pri/ss7/etc.. |
| 21:56.40 | tzafrir | hardwire, all the regex stuff matters only if you use get-orig-source or uscan |
| 21:56.56 | seanbright | hardwire: correct |
| 21:57.00 | Corydon76-lap | hardwire: only when he wears the studded dog collar |
| 21:57.04 | hardwire | tzafrir: so just unpack the debian.tar.gz with ./debian/ and update changelog? |
| 21:57.35 | tzafrir | provide an orig tarball with a name that matches the version number in the changelog |
| 21:57.43 | hardwire | tzafrir: that's sneaky. |
| 21:57.48 | hardwire | will do |
| 21:58.07 | tzafrir | it must have a single top-level directory, but its name does not really matter |
| 21:58.25 | hardwire | tzafrir: when running dpkg-buildpackage -s right? |
| 21:58.42 | tzafrir | hardwire, if you build from svn: svn-buildpackage |
| 21:58.51 | tzafrir | if you extracted: debuild -uc -us |
| 21:58.58 | hardwire | 1.6.2.5 isn't in pkg-voip |
| 21:59.01 | tzafrir | (I assume you have devscripts0 |
| 21:59.51 | tzafrir | right, because it was branched off 1.6.2.2 and does not have some fixes I really needed |
| 22:00.00 | tzafrir | still denies that package is his own |
| 22:00.09 | hardwire | heh |
| 22:01.24 | hardwire | tzafrir: I do. I'm planning on extracing the digium tarball.. extracting the debian tarball from updates.xorcom.com.. and updating the changelog if at all then running dpkg-buildpackage -s |
| 22:01.37 | hardwire | or -us -uc -s |
| 22:01.48 | hardwire | I don't really care.. but I assume that just works.. if not please let me down gently. |
| 22:02.06 | hardwire | I attempted to do debian package maint a long time ago and I just wasn't cut out for it :) |
| 22:02.44 | hardwire | seanbright: all this so my damn voicemail and init scripts are happy. |
| 22:02.55 | hardwire | happy happy happy. |
| 22:05.44 | hardwire | it appears to be building.. it also thinks I'm tzafrir .. so that's awesome. |
| 22:05.47 | hardwire | :P |
| 22:05.58 | hardwire | just copied the last changelog entry.. didn't bother to fill out my name.. this is all your fault now. |
| 22:06.38 | tzafrir | hardwire, next time use 'dch -i' to add a changelog entry |
| 22:06.49 | *** join/#asterisk-dev ariel_ (~chatzilla@63.214.236.169) |
| 22:06.57 | hardwire | doy. |
| 22:07.03 | ariel_ | afternoon |
| 22:08.02 | ariel_ | I am looking for a iax2 developer and I am willing to pay money to get an issue worked and fixed. |
| 22:08.30 | seanbright | is it in the issue tracker? |
| 22:08.51 | ariel_ | I do not believe it there |
| 22:08.51 | hardwire | ariel_: is it iax over serial devices.. cause I'd love that. |
| 22:09.01 | ariel_ | no over sat |
| 22:09.12 | hardwire | ariel_: I have to deal with that a lot |
| 22:09.25 | hardwire | are you in northern america? |
| 22:09.27 | ariel_ | I have iax2 working but one way only |
| 22:09.31 | ariel_ | yes |
| 22:09.39 | seanbright | ariel_: and you are sure it is a bug and not a configuration problem? |
| 22:09.45 | hardwire | ariel_: whereabout? |
| 22:09.53 | ariel_ | don't know if it's either |
| 22:10.03 | seanbright | alright. |
| 22:10.08 | ariel_ | But I am at the end of my rope |
| 22:10.14 | ariel_ | Miramar Fl |
| 22:10.56 | ariel_ | I have 2 systems both HP's Xeons with Digium boards for time and digium g729 boards |
| 22:11.23 | hardwire | I'm not sure how the "pay for happyness" thing works in here with dibs. But if the digifolk in here aren't available just email me and I should be able to help. |
| 22:11.28 | hardwire | shane at bogomip dot com |
| 22:13.25 | seanbright | ariel_: if you believe the problem you are having (which you have yet to even attempt to describe) is a bug, you should post it to the issue tracker @ https://issues.asterisk.org/ |
| 22:13.55 | ariel_ | I need to see if it's a bug first |
| 22:14.17 | Corydon76-lap | hardwire: is "pay for happiness" related to "gay for pay"? |
| 22:14.22 | seanbright | https://issues.asterisk.org/search.php?project_id=0&category=Channels%2Fchan_iax2&sticky_issues=on&sortby=last_updated&dir=DESC&hide_status_id=90 |
| 22:14.32 | seanbright | ariel_: all open iax bugs ^^^^ |
| 22:14.42 | mvanbaak | tadaaa, and another bill payed |
| 22:15.15 | alecdavis | mvanbaak: customers, don't you just love them. |
| 22:15.39 | mvanbaak | they should pay the bills, and not contact me ;) |
| 22:15.44 | Corydon76-lap | alecdavis: if we ignore our customers, maybe they'll stop bothering us. |
| 22:15.45 | alecdavis | I thought you said earlier, I hate customers. |
| 22:15.59 | *** join/#asterisk-dev datachomper (~Adium@nat/digium/x-dzgdsbtsvtqjdjbs) |
| 22:16.08 | mvanbaak | alecdavis: I do. they should simply pay my bills, and dont bother me with their problems |
| 22:16.21 | ArtemMakhutov | Can somebody help me to find out, why asterisk is crashing when calling ast_frfree(f)? The crash only happends when playing back a .wav file but not with other codecs... http://pastebin.com/tXFxHAHy |
| 22:16.57 | snuff-work | leifmadsen: enjoy the olympics final of the ice hockey? :) |
| 22:17.06 | Corydon76-lap | ArtemMakhutov: best guess is that the frame was freed twice |
| 22:17.16 | alecdavis | hope I'm not considered a customer :( |
| 22:17.21 | leifmadsen | snuff-work: oh heck ya -- was very entertaining :) |
| 22:17.37 | mvanbaak | alecdavis: you're not. you're not paying |
| 22:17.45 | mvanbaak | you're a general pain in the butt ;) |
| 22:17.49 | ariel_ | seanbright: I don't see anything there close to my issue |
| 22:18.04 | hardwire | pbx01*CLI> core show version |
| 22:18.05 | hardwire | Asterisk 1.6.2.5 built by root @ pbx01 on a x86_64 running Linux on 2010-03-01 22:05:35 UTC |
| 22:18.05 | seanbright | ariel_: then you should submit an issue. so that someone will work on it and get it committed. |
| 22:18.10 | hardwire | let the awesome commence |
| 22:18.22 | Corydon76-lap | mvanbaak: General PITA or Major PITA? |
| 22:18.24 | snuff-work | no public unrest after the big win?.. the nfl in USA seems to get a little rowdy |
| 22:18.33 | hardwire | seanbright: damned you for being awesome. |
| 22:18.38 | seanbright | s/n ratio is horrible today |
| 22:18.46 | mvanbaak | Corydon76-lap: both: general major PITA |
| 22:18.48 | ariel_ | I have an actual support ticket open over the issue with digum, but I need to see if can get this worked faster |
| 22:18.49 | hardwire | tzafrir: damned you for being helpfull. |
| 22:19.00 | hardwire | closes out some tickets |
| 22:19.04 | Corydon76-lap | Also, Private PITA, Sargeant PITA, Colonel PITA |
| 22:19.15 | seanbright | hardwire: remember to manually at the crash fix i did earlier |
| 22:19.32 | seanbright | that won't be in until 1.6.2.6 or whatever is released next that is not a security fix |
| 22:19.34 | hardwire | seanbright: that code doesn't exist in 1.6.2.5 |
| 22:19.37 | mvanbaak | pita shoarma |
| 22:19.53 | snuff-work | leifmadsen: i was lookin the other day @ bug tracker.. bit over 100 bugs in ready for test |
| 22:19.55 | hardwire | seanbright: I looked.. not there.. no reason to patch yet.. going to test the new app_voicemail.so to see if it's crashy |
| 22:20.20 | seanbright | hardwire: hmmm. if it was in 1.6.2.3-rc2 it would be in 1.6.2.5 |
| 22:20.21 | mvanbaak | snuff-work: one in chan_skinny. dont think digium is looking at that ;) |
| 22:20.53 | seanbright | ariel_: digium is the best group to be addressing it |
| 22:21.04 | seanbright | ariel_: IMO, anyway. |
| 22:21.30 | hardwire | seanbright: got me homes. |
| 22:21.43 | snuff-work | true.. there was a bit of ss7 work committed lately.. but i dont think they were to do with any of the ss7 bug trackers issues.. |
| 22:22.25 | hardwire | seanbright: 0 problems |
| 22:23.04 | mvanbaak | snuff-work: but good news. work on skinny has resumed |
| 22:23.04 | seanbright | well that is confusing as hell... 1.6.2.5 is a copy of 1.6.2.2 with some security fixes |
| 22:23.05 | leifmadsen | snuff-work: ya, its getting a bit crazy in there :) |
| 22:23.18 | leifmadsen | seanbright: nope -- 1.6.2.5 is just 1.6.2.2 (as you've just said) |
| 22:23.30 | seanbright | so this is interesting... |
| 22:23.32 | leifmadsen | seanbright: yes, we're likely going to change the version numbering scheme slightly |
| 22:23.43 | alecdavis | The bamboo test for app_voicemail unit test isn't running, is that intentional? |
| 22:23.43 | leifmadsen | seanbright: let me explain why the numbers were skipped like that |
| 22:23.55 | seanbright | leifmadsen: i understand why |
| 22:24.02 | leifmadsen | oh ok :) |
| 22:24.02 | seanbright | leifmadsen: the average joe would not |
| 22:24.12 | leifmadsen | well, if you read the release announcement, it always explains it |
| 22:24.16 | seanbright | well no one does that |
| 22:24.18 | seanbright | :P |
| 22:24.22 | leifmadsen | of course, just like docs :) |
| 22:24.23 | ArtemMakhutov | How can I prevent that a frame get freed twice? A "if (f) ast_frfree(f);" does not help |
| 22:24.32 | hardwire | seanbright: there's a rather large diff between the two versions of app_voicemail |
| 22:24.32 | seanbright | leifmadsen: love the book though! <3 |
| 22:25.04 | leifmadsen | seanbright: well, we're highly considering switching to something like 1.6.2.2-sec1, 1.6.2.2-sec2 (which would be the equivalent of 1.6.2.4 and 1.6.2.5 respectively) |
| 22:25.29 | seanbright | hardwire: yeah. so the next 1.6.2 release (that is not purely a security release) will contain the changes to message counting that tilghman introduced, along with the bug fix i committed earlier. |
| 22:25.37 | seanbright | leifmadsen: i would like that. |
| 22:25.42 | hardwire | Corydon76-lap++ |
| 22:25.53 | hardwire | buys this channel a round of warm fuzzies. |
| 22:25.59 | leifmadsen | seanbright: yep, so I'll probably release an announcement tomorrow and post it on the blogs and mailing lists |
| 22:26.03 | seanbright | awesome |
| 22:26.08 | Qwell | hardwire: Sir, your card was declined. |
| 22:26.13 | hardwire | Qwell: :( |
| 22:26.19 | seanbright | Qwell: cut it up in front of his wife |
| 22:26.22 | leifmadsen | give some people a chance to change their release policies if that's necessary, etc... |
| 22:26.37 | Corydon76-lap | So did you hear that teams that get touchy-feely with each other work better together? |
| 22:26.45 | seanbright | leifmadsen: anything to reduce confusion is a good thing methinks |
| 22:26.58 | leifmadsen | seanbright: totally agreed |
| 22:26.58 | seanbright | it's friday! |
| 22:27.01 | seanbright | err |
| 22:27.03 | leifmadsen | seanbright: tease |
| 22:27.04 | seanbright | it's not friday |
| 22:27.15 | leifmadsen | for a brief moment there I thought it was :( |
| 22:27.48 | seanbright | in other news comcast showed up and actually got my tivo working with my cablecard |
| 22:27.55 | leifmadsen | hawt |
| 22:28.02 | seanbright | only took 3 different techs over 2 weeks |
| 22:28.30 | mvanbaak | -sec1 etc sux |
| 22:28.31 | hardwire | seanbright: soon to be wife. |
| 22:29.01 | seanbright | hardwire: potato potate. |
| 22:29.05 | seanbright | err |
| 22:29.06 | Corydon76-lap | Sean Bright is your soon to be wife? |
| 22:29.09 | seanbright | no.. that works too |
| 22:29.10 | hardwire | potate eh? |
| 22:29.17 | seanbright | i say potate |
| 22:29.21 | hardwire | Corydon76-lap: his dress is lovely. |
| 22:29.23 | leifmadsen | mvanbaak: better idea? :) |
| 22:29.30 | mvanbaak | leifmadsen: .1 |
| 22:29.40 | seanbright | leifmadsen: OPENBSD-ROCKS-BALLS-1 |
| 22:29.40 | mvanbaak | that's what version numbers are for |
| 22:29.49 | seanbright | OPENBSD-ROCKS-BALLS-2 |
| 22:29.53 | seanbright | etc, etc. |
| 22:30.09 | leifmadsen | mvanbaak: 1.6.2.2.1 has already been veto'd |
| 22:30.18 | hardwire | leifmadsen: I forget if debian chokes on funny version names.. probably not.. but I know it makes it hard to auto-increment using the debian packaging tools |
| 22:30.31 | mvanbaak | leifmadsen: at least that is parseble without too much hassle |
| 22:30.42 | leifmadsen | hardwire: well we're already using -rc1, etc... so if they can handle those, then it should be able to handle -secX |
| 22:30.44 | leifmadsen | :D |
| 22:31.00 | leifmadsen | mvanbaak: ya, but not any more clear for people |
| 22:31.05 | hardwire | finefinefine |
| 22:31.25 | mvanbaak | leifmadsen: why not ? |
| 22:31.42 | mvanbaak | leifmadsen: 1.6.2 is the line (branch) |
| 22:31.46 | seanbright | -secX it is |
| 22:31.47 | seanbright | moving on |
| 22:31.55 | mvanbaak | leifmadsen: 1.6.2.2 is the second release of that tree |
| 22:31.56 | hardwire | so 1.6.2.5 will still be the current stable tomorrow.. right? :) |
| 22:32.02 | leifmadsen | yes :) |
| 22:32.08 | mvanbaak | 1.6.2.2.2 is the second security release of that version |
| 22:32.13 | hardwire | ouch |
| 22:32.15 | leifmadsen | RCs will likely go out sometime next week though |
| 22:32.23 | leifmadsen | well the first one was just a documentation update :) |
| 22:32.38 | leifmadsen | so 1.6.2.2 -> 1.6.2.4 didn't get you any new code |
| 22:32.52 | mvanbaak | so ? |
| 22:32.58 | seanbright | wow |
| 22:33.03 | seanbright | this is exhausting |
| 22:33.11 | mvanbaak | 1.6.2.2 is second release of 1.6.2 branch |
| 22:33.11 | seanbright | leifmadsen: say something. anything. |
| 22:33.15 | leifmadsen | that's why I'm leaving :) |
| 22:33.17 | seanbright | so? |
| 22:33.20 | seanbright | so? |
| 22:33.20 | mvanbaak | 1.6.2.4 is 4th release of the 1.6.2 branch |
| 22:33.25 | seanbright | so? |
| 22:33.34 | seanbright | heads home |
| 22:33.38 | mvanbaak | I dont see why you need actual code changes between releases of a branch |
| 22:34.09 | mvanbaak | if it's only doc updates, and release manager states it's time for a new version of that branch, just increment the 'release for this branch' counter |
| 22:34.24 | mvanbaak | instead of introducing alphanumeric release names |
| 22:34.32 | seanbright | i love me some mondays |
| 22:34.52 | seanbright | how about those canadians and their gold medals, huh? |
| 22:35.07 | kpfleming | gold-plated chocolate |
| 22:35.31 | seanbright | and we looked like a bunch of spoiled childen getting our silver medals |
| 22:36.01 | seanbright | thats why we need to take over canada. it's in my manifesto. |
| 22:36.17 | leifmadsen | mvanbaak: I don't understand... I think you're saying keep it the same as we do now, however doing that also introduces skipping version numbers which is confusing for everyone (including myself when creating releases) |
| 22:36.42 | mvanbaak | leifmadsen: so stop skipping numbers |
| 22:36.50 | kpfleming | we can't |
| 22:36.51 | mvanbaak | I really dont see the actual problem |
| 22:37.09 | kpfleming | if we release x.y-rc1, and then x.y doesn't have the same code as -rc1 did, confusion would abound |
| 22:37.19 | jdoe | seanbright: when it was that close? looking shellshocked is an appropriate response |
| 22:38.03 | seanbright | jdoe: they didn't look shocked. they looked down at the ice. they didn't make eye contact with the olympic officials. |
| 22:38.22 | jdoe | seanbright: I dunno, the ones I saw looked like they'd been punched in the stomach. |
| 22:38.42 | leifmadsen | mvanbaak: what kpfleming said -- we wouldn't be able to use 1.6.2.3 if 1.6.2.3-rc1 was released, because people would think that version included fixes they were testing in the release candidate |
| 22:38.54 | jdoe | it was a great game, but it's easy to lose sight of "holy shit we're still #2" when it's that close. |
| 22:38.56 | leifmadsen | mvanbaak: so skipping version numbers is necessary |
| 22:38.58 | seanbright | leifmadsen: so? |
| 22:39.09 | leifmadsen | eyes the kick+ban button |
| 22:39.11 | seanbright | (sorry... i'll stop trolling and actually go home) |
| 22:40.06 | mvanbaak | then add an extra digit |
| 22:40.25 | mvanbaak | 1.6.2.3.1 |
| 22:40.38 | mvanbaak | security fix 1 for release 3 of the 1.6.2 branch |
| 22:40.42 | mvanbaak | not that hard to parse |
| 22:40.42 | jdoe | at what point does it stop becoming a version number and start looking like an OID? |
| 22:40.57 | kpfleming | exactly |
| 22:41.20 | mvanbaak | well, adding -sec1 does not make it look any better |
| 22:41.24 | mvanbaak | 1.6.2.3-sec1 |
| 22:41.32 | jdoe | wouldn't it be 1.6.2.2-sec1? |
| 22:41.34 | kpfleming | well... it does, actually |
| 22:41.39 | jdoe | then you couldn't need to skip versions at all |
| 22:41.39 | leifmadsen | jdoe: yes |
| 22:41.42 | jdoe | which I figured was the point. |
| 22:41.44 | leifmadsen | jdoe: exactly :) |
| 22:41.51 | kpfleming | because we sometimes make point releases containing only regression fixes |
| 22:42.03 | leifmadsen | we're already using the -rcX convention so we're not doing anything new there |
| 22:42.06 | kpfleming | so using a tag like that makes it obvious whether the release is caused by a security fix or a regression fix |
| 22:42.16 | niekvlessert | why release a new version for this, just mention it on asterisk.org, will gain more attention to asterisk.org |
| 22:42.18 | mvanbaak | no |
| 22:42.34 | jdoe | niekvlessert: the doc updates were common mistakes |
| 22:42.47 | mvanbaak | in that case we need: 1.6.2.3-regression1 and 1.6.2.3-security2 |
| 22:43.05 | mvanbaak | or even loose the 3 |
| 22:43.11 | niekvlessert | jdoe: yeah, so ppl won't care about the new version |
| 22:43.15 | mvanbaak | and make it 1.6.2-feature1 |
| 22:43.31 | mvanbaak | for feature additions |
| 22:43.39 | mvanbaak | 1.6.2-bugfixX |
| 22:43.41 | mvanbaak | for bugfixes |
| 22:43.43 | mvanbaak | etc |
| 22:43.51 | jdoe | mvanbaak: distro packages keep the version the same when they backport security fixes |
| 22:43.53 | niekvlessert | how does kernel.org do it |
| 22:43.57 | tzafrir | why not just release 1.6.2.6-rc1 ? |
| 22:44.01 | jsmith | kpfleming: The problem is, you have to worry about other systems (dpkg? rpm?) that order these tags in a consistent order. How does RPM know that -security comes before or after -RC? |
| 22:44.13 | kpfleming | people should not be packaging -rc releases |
| 22:44.18 | mvanbaak | tzafrir: because they want to rush out security fixes |
| 22:44.31 | leifmadsen | tzafrir: because we don't want to force people to get other changes just to get a security fix |
| 22:44.40 | kpfleming | right |
| 22:44.45 | kpfleming | we used to do that, and got flamed for it |
| 22:44.58 | mvanbaak | hhmm |
| 22:45.00 | mvanbaak | how about |
| 22:45.00 | tzafrir | well, 1.6.2.[45] were just that, right? |
| 22:45.03 | leifmadsen | jsmith: because -sec will always be on the same version as the latest full release |
| 22:45.06 | Corydon76-lap | ArtemMakhutov: when you free the frame, set the pointer back to NULL. Freeing the pointer doesn't do that |
| 22:45.26 | leifmadsen | tzafrir: yes, but we had to skip 1.6.2.3 because 1.6.2.3-rc2 existed |
| 22:45.32 | mvanbaak | 1.6.2.3 is there, a security issue is found, release an errata, and commit it to 1.6.2.4-rcX as well |
| 22:45.34 | jsmith | leifmadsen: Right... but dpkg/RPM don't know that |
| 22:45.35 | tzafrir | I don't see any problem with that. |
| 22:45.38 | leifmadsen | which is confusing, because people think 1.6.2.4 contains new stuff 1.6.2.2 doesn't |
| 22:45.51 | mvanbaak | so ppl that care can patch their 1.6.2.3, or upgrade to 1.6.2.4-rc1 |
| 22:45.58 | tzafrir | dpkg / rpm would originally have an issue with the -rc idea |
| 22:46.09 | niekvlessert | well, if security stuff gets fixed in a new release and ppl get new stuff with it, ppl just need to accept it... |
| 22:46.11 | mvanbaak | then when rc stage is done release 1.6.2.4 which is 1.6.2.3 + bugfixes + errata's |
| 22:46.20 | ArtemMakhutov | Corydon76-lap: thx, I'll try that |
| 22:46.22 | kpfleming | i will say it again. distros should not be packaging -beta or -rc releases. period. |
| 22:46.30 | mvanbaak | kpfleming: agreed |
| 22:46.40 | mvanbaak | kpfleming: but what about my idea to release errata's |
| 22:46.43 | leifmadsen | kpfleming: I think the point is that the -anything part is confusing |
| 22:46.48 | kpfleming | it's not |
| 22:46.50 | tzafrir | well, right now Debian Testing is a rolling release, which *should* package RCs |
| 22:46.51 | mvanbaak | it is |
| 22:47.06 | leifmadsen | someone let me know what the concensus is because I'm being called for dinner. |
| 22:47.06 | kpfleming | one set of tags is fine, it's two sets of tags that are the problem for packaging systems |
| 22:47.10 | tzafrir | (although rc2 was not yet uploaded) |
| 22:47.32 | kpfleming | i disagree. i don't think any distro should be packaging -rcs |
| 22:47.54 | Corydon76-lap | kpfleming: well, not for our RCs, which last a month or so |
| 22:47.56 | kpfleming | we release often enough that a testing release can just package our monthly releases |
| 22:48.05 | mvanbaak | distro's should _NEVER_ packag -rcX releases of asterisk |
| 22:48.05 | kpfleming | right... we said the same thing :-) |
| 22:48.09 | niekvlessert | http://en.wikipedia.org/wiki/Linux_kernel |
| 22:48.11 | Corydon76-lap | kpfleming: some projects have RCs that last 3 years... |
| 22:48.14 | tzafrir | kpfleming, this is a rolling release. Not a stable one |
| 22:48.15 | kpfleming | right |
| 22:48.31 | kpfleming | i don't care. we release once a month, it's fine for debian testing to update asterisk once a month, to a full release |
| 22:48.34 | mvanbaak | tzafrir: then you should package straight from svn |
| 22:48.39 | kpfleming | right |
| 22:48.40 | niekvlessert | In the current scheme, the main branch of development is not a traditional "stable" branch, instead it incorporates all kinds of changes, both the latest features as well as security and bug fixes. For users who do not want to risk updating to new versions containing code that may not be well tested, a separate set of "stable" branches exist, |
| 22:48.43 | tzafrir | When it gets to setting the release for Debian Stable, it shouldn;t indeed be an RC |
| 22:48.43 | kpfleming | and avoid version numbers entirely |
| 22:49.06 | mvanbaak | tzafrir: just create packages from 1.6.2 svn |
| 22:49.23 | mvanbaak | tzafrir: and label it asterisk-1.6.2-svn<revision_number> |
| 22:49.24 | kpfleming | yep. that's a much better plan for a rolling release distro. |
| 22:49.25 | tzafrir | mvanbaak, right now it's technically complicated |
| 22:49.57 | Corydon76-lap | Right now, it's technically silly |
| 22:49.59 | ArtemMakhutov | Corydon76-lap: it also did not worked, asterisk still crashing, will get to it tomorrow again, cya |
| 22:50.06 | tzafrir | If it were simple, I would have made packaging this simple, so every user would have been able to easily test that |
| 22:50.26 | tzafrir | Corydon76-dig, oh, and you never recommend anyone to test SVN? |
| 22:50.29 | mvanbaak | I dont see why it's complicated |
| 22:50.40 | kpfleming | tzafrir: what's hard about packaging an svn export? |
| 22:50.56 | tzafrir | because release tarballs are not simple svn exports |
| 22:51.03 | hardwire | all of my excuses to not finish up this dialplan are gone. |
| 22:51.04 | hardwire | :( |
| 22:51.04 | niekvlessert | i agree with mvanbaak, what's difficult in creating a package from svn |
| 22:51.13 | tzafrir | and I never had the time to properly review the differences |
| 22:51.18 | Corydon76-lap | tzafrir: you could just use our mkrelease script... |
| 22:51.22 | kpfleming | release tarballs are very, very close to svn exports |
| 22:51.32 | kpfleming | and the only things done do the export are done by a script included in the export itself |
| 22:51.41 | Corydon76-lap | modify it for use with git |
| 22:51.49 | niekvlessert | nightly build |
| 22:52.09 | tzafrir | for starters, they don't include a changelog, which would break packaging |
| 22:52.26 | tzafrir | (I worked around that with a silly exposrt script in dahdi) |
| 22:52.28 | Corydon76-lap | The mkrelease script does |
| 22:52.28 | mvanbaak | that's an easy fix |
| 22:53.07 | tzafrir | that's one thing. I looked at mkrelease. It seems to me a bit too complicated to replicate / understand, so I left it as-is |
| 22:53.23 | kpfleming | thats because it is also involved in making the tags themselves |
| 22:53.26 | kpfleming | and signing |
| 22:53.35 | Corydon76-lap | Now I'm hearing, "It's too hard", which is hard to swallow from a kernel developer |
| 22:53.35 | kpfleming | the parts that modify the export are quite straightforward |
| 22:53.48 | jsmith | kpfleming: Don't forget the PDF docs and the sounds... |
| 22:53.50 | kpfleming | but you are right, we don't keep a text changelog, because we don't need one, our SCM does |
| 22:53.58 | kpfleming | jsmith: those are made by the script in the export itself |
| 22:54.02 | tzafrir | well, for tags I generally have a reasonable convension. Assuming I can expect the numbering scheme: |
| 22:54.32 | tzafrir | 1.6.2.5.9.svn.r<rev> |
| 22:54.39 | kpfleming | and i don't understand why you need a changelog from us anyway. there are plenty of packages where debian/changes is very different from the upstream changelog (which may not exist at all) |
| 22:54.40 | tzafrir | or something along those lines |
| 22:54.47 | mvanbaak | I've been creating OpenBSD ports from svn for years now, it's so freaking easy |
| 22:54.57 | mvanbaak | my script is like 25 lines or something |
| 22:55.18 | tzafrir | kpfleming, the building of the package would fail without a changelog. I need to provide a changelog somehow (be it a dummy one). I prefer to provide a proper one |
| 22:55.28 | *** part/#asterisk-dev ArtemMakhutov (~ArtemMakh@ip-95-223-6-41.unitymediagroup.de) |
| 22:55.30 | Corydon76-lap | mvanbaak: because clearly, svn is too difficult to use for a kernel developer. /me ducks |
| 22:55.33 | niekvlessert | kpfleming: agree, if u want to be bleeding edge, bare with it :) |
| 22:55.47 | tzafrir | I'm not saying it's impossible. I automated most of it for zaptel |
| 22:55.58 | mvanbaak | svn export, create changelog, run prep_tarball, compile, fake_install, tgz |
| 22:56.08 | kpfleming | i don't understand.... i rebuild debian packages frequently that don't have any upstream changelog at al.. |
| 22:56.27 | mvanbaak | kpfleming: indeed |
| 22:56.31 | mvanbaak | kpfleming: same here |
| 22:56.54 | tzafrir | btw: as the packaging in Debian switched to dpkg v.3, having a debian/ subdirectory now would be harmless |
| 22:57.03 | tzafrir | (it just gets overriden by the packaging) |
| 22:57.12 | hardwire | tzafrir: that would be snazzy. |
| 22:57.21 | seanbright | Qwell: while you're messing with lock.h... rid it of the assumption that a pthread_mutex_t is a primitive type |
| 22:57.25 | seanbright | kthx |
| 22:57.36 | mvanbaak | kpfleming: if upstream has no changelog I simply do: echo 'build from upstream rev X' > ChangeLog |
| 22:57.45 | kpfleming | yeah, that works for me |
| 22:57.57 | Qwell | seanbright: mmm? |
| 22:58.03 | seanbright | if ((t->mutex) == ((pthread_mutex_t) PTHREAD_MUTEX_INITIALIZER)) { |
| 22:58.12 | file | problem solved! up next cold fusion |
| 22:58.17 | Qwell | patches welcome |
| 22:58.21 | seanbright | damn you |
| 22:58.22 | mvanbaak | tzafrir: debian/ stuff should not be in upstream sources |
| 22:58.24 | mvanbaak | never ever |
| 22:58.40 | mvanbaak | it's ok if it's in a seperate repo |
| 22:59.02 | tzafrir | mvanbaak, well, with dpkg v.3 it simply gets ignored, rather then messing things up |
| 22:59.19 | mvanbaak | but if you allow debian/ you should add a subdir for every possible distro/os that your software compiles/runs on |
| 22:59.24 | mvanbaak | that would create a huge mess |
| 22:59.31 | tzafrir | kpfleming, because of the explicit: dh_installchangelogs ChangeLog |
| 22:59.38 | kpfleming | ahh |
| 22:59.54 | mvanbaak | tzafrir: see my remark about adding a ChangeLog if none is provided |
| 23:00.12 | kpfleming | well... do what mvanbaak said. "This is a Subversion snapshot generated from rXXXXX. Please see http://svnview.digium.com/view/... for a change listing." |
| 23:00.42 | niekvlessert | jay, great |
| 23:01.02 | mvanbaak | you have it working with bristuff niekvlessert ? |
| 23:01.40 | niekvlessert | well, dunno, i'll test tomorrow, phones are 90 km away |
| 23:01.49 | niekvlessert | but it compiles :) |
| 23:02.01 | mvanbaak | hurray ! |
| 23:02.41 | tzafrir | speaking of numbering schemes: bristuff-0.3.0-PRE-1z-b.tar.gz , bristuff-0.4.0-RC3l.tar.gz (quite recent, actually) |
| 23:02.42 | niekvlessert | I even found out how to remove a bri stuff patch |
| 23:03.41 | kpfleming | let's not get started posting example of stupid broken version numbering schemes :-) |
| 23:03.41 | kpfleming | there are way too many to count |
| 23:03.41 | leifmadsen | ok, so looks like I didn't miss anything |
| 23:04.41 | tzafrir | 1z-b is after completing the whole alphabet after being 1y-<letter> . And that was after using 1<letter> |
| 23:05.07 | niekvlessert | kpflemings idea sounds best to me |
| 23:06.31 | leifmadsen | can someone restate the idea? |
| 23:06.47 | leifmadsen | I'm just trying to figure out what we're calling releases so I can stop skipping version numbers :) |
| 23:06.47 | kpfleming | i mean, there is spandsp, which is in use around the world in production and is still 0.0.6 |
| 23:07.17 | kpfleming | but my favorite is Sun's 'Java 6', which is version number 1.6.x |
| 23:09.06 | leifmadsen | ok cool, glad we all agree on 1.6.2.X-secY :) |
| 23:09.35 | mvanbaak | mark down: not all, but majority |
| 23:09.43 | mvanbaak | s/mark/write/ |
| 23:11.38 | mvanbaak | ok all, time for some sleep |
| 23:11.41 | mvanbaak | latero |
| 23:12.28 | niekvlessert | me 2, l8r |
| 23:19.08 | tzafrir | hmm... I don't. 'sec' is not the only reason for that. There are also "important bug fixes" |
| 23:19.44 | tzafrir | And having a '-' in the name of the tarball makes life more interesting |
| 23:20.35 | Corydon76-lap | Uh, there's always a dash in the tarball name: asterisk-1.4.29.tar.gz |
| 23:20.47 | tzafrir | inside the version string |
| 23:20.59 | tzafrir | (and yes: we mangle the -beta and -rc) |
| 23:21.21 | Corydon76-lap | with what, a tilde? |
| 23:21.45 | Corydon76-lap | I don't understand why you package betas and release candidates |
| 23:21.53 | tzafrir | '~' means that the coming part is less that. |
| 23:22.00 | tzafrir | s/that/than/ |
| 23:22.23 | tzafrir | that is: 1.6.2~rc4 is a lower version number than 1.6.2 |
| 23:23.58 | tzafrir | however 1.6.2.1 > 1.6.2-sec1 |
| 23:24.15 | leifmadsen | which has caused so many people in #asterisk reporting issues with 1.6.2.0~rc2 (for whatever reason their system still installs RC2, which is just one of two problems I see with the pkg mgmt system using 1.6.2.0-rc2) |
| 23:24.28 | leifmadsen | 1.6.2.1 < 1.6.2.1-sec1 |
| 23:24.40 | tzafrir | leifmadsen, that happened to be the version of ubuntu |
| 23:24.44 | leifmadsen | you would only have -sec1 on top of an existing release |
| 23:25.13 | leifmadsen | so -secY would always be greater than the 1.6.2.x version it was attached to |
| 23:25.18 | tzafrir | I'll try to have a better one for their next release. But I have much less control over that |
| 23:25.30 | leifmadsen | So I don't see the issue |
| 23:25.47 | leifmadsen | you will always want the latest 1.6.2.x unless 1.6.2.x-secY exists, in which case you want the latest Y |
| 23:26.13 | leifmadsen | and if you never package an RC, then I don't see an issue |
| 23:27.11 | tzafrir | leifmadsen, well, at the time there were some features someone really needed from 1.6.2, and we were very far from a stable Debian release |
| 23:27.29 | tzafrir | (but in retrospect, I would have stayed with 1.6.1) |
| 23:27.53 | *** join/#asterisk-dev snuff-home (~snuffy@203-219-29-182.tpgi.com.au) |
| 23:27.53 | *** mode/#asterisk-dev [+o snuff-home] by ChanServ |
| 23:28.16 | leifmadsen | I'm not sure how that is the Asterisk projects problem. There must be other projects that have much more complicated release policies than what we do |
| 23:29.16 | tzafrir | The main problem was that Ubuntu never bothered with proper freezing. We new we had enough time till 1.6.2 was released for Debian Stable |
| 23:41.28 | tzafrir | hmm... and in the end I forgot to ask about: |
| 23:41.38 | tzafrir | M16906 |
| 23:41.40 | MuffinMan | [new] [Asterisk] Resources/res_musiconhold 0016906: moh files install under datadir, at runtime: under varlibdir reported by tzafrir https://issues.asterisk.org/view.php?id=16906 |
| 23:41.47 | tzafrir | Well, I guess this is for tommorow |
| 23:42.54 | alecdavis | it'll will be wednesday tomorrow. Half way through week. |
| 23:43.47 | alecdavis | https://reviewboard.asterisk.org/r/481/ ready to go. |
| 23:44.45 | *** part/#asterisk-dev datachomper (~Adium@nat/digium/x-dzgdsbtsvtqjdjbs) |
| 23:45.06 | alecdavis | M16909 |
| 23:45.08 | MuffinMan | [new] [LibPRI] Channels/chan_dahdi 0016909: [patch] pritimer's in chan_dahdi.conf not honoured reported by alecdavis https://issues.asterisk.org/view.php?id=16909 |
| 23:45.29 | alecdavis | 16909 was good in 2004, don't know when it went wrong. |
| 23:55.08 | hardwire | I fixed him up |
| 23:55.13 | Corydon76-lap | Write a unit test for it, once you fix it... but don't commit a unit test that fails |
| 23:55.14 | hardwire | he was abusing the power of type=user |
| 23:55.58 | *** join/#asterisk-dev dseeb_ (~Adium@CPE-58-169-81-65.lns1.bat.bigpond.net.au) |