[01:08] <MMlosh> Made some testing on the program..   the   arguments parsing loop is defective..   It loops on the "default" case.   Hardcoding the config path makes the program run fine
[01:18] <MMlosh> The problem seems to be signed-vs-unsigned shortint..     It returns "255" while the while loops checks for "-1"
[01:39] <MMlosh> Nevermind..   the "ch" variable should be int instead of char..  It's a "normal" application bug
[01:50] <MMlosh> The bug was filled as https://bugs.launchpad.net/ubuntu/+source/getstream/+bug/970520  I am sorry for the flood
[01:50] <ubot2> Launchpad bug 970520 in getstream "Does not work on ARMv7 at all (pandaboard)" [Undecided,New]
[02:15] <infinity> MMlosh: Fixed in precise, thanks for the catch.
[02:16] <MMlosh> If I want it fixed in debian, I need to post a bug there, right?
[02:16]  * infinity notes that he missed the word "on" in his changelog entry.  Oops.
[02:16] <infinity> MMlosh: I can push the patch to Debian in a bit.
[02:16] <MMlosh> also: are you sure that my fix is correct?
[02:16] <MMlosh> thank you
[02:17] <infinity> MMlosh: Your fix is correct.  getopt returns an int.  Casting ints and chars interchangeably works on x86 (hence the bug), because x86 uses signed chars by default.  ARM and PowerPC use unsigned chars by default.
[02:22] <infinity> Of course... getstream currently doesn't build on precise.  I should have checked that before I uploaded.
[02:22] <infinity> *sigh*
[02:23] <stgraber> infinity: and now that you are touched-it-last, congratulations on making this your FTBFS ;)
[02:23] <infinity> stgraber: Yeah, it's just glib include whininess, nothing drastic.
[02:23] <infinity> stgraber: And I can be all revisionist history and fix the typo in my previous changelog. ;)
[02:25] <MMlosh> ahs3, yes, forgot that it won't rebuild because of that..   I workarounded that by including whole <glib.h> in my testbuilds..
[02:25] <infinity> ahs3: Ignore that, MMlosh is tab-complete-impaired. ;)
[02:26] <infinity> MMlosh: Yeah, I'll fix in a bit, after I go get a drink. :P
[02:26] <infinity> My own dumb fault for thinking an obviously-correct 1-line fix wouldn't need a test build.
[02:27] <MMlosh> I wondered where that "3" came from..       hitting tab..  sleepy me..   (europe...)
[02:46] <MMlosh> infinity,  minor question  --  Any idea why it's set to build with  "-O0" ?
[02:47] <infinity> MMlosh: No idea.
[02:47] <infinity> (it is?)
[02:47] <MMlosh> The only guess I have is.. someone actually trying the binary after building..  and trying to debug
[02:48] <infinity> Hrm, so it is.
[02:48] <infinity> That's an upstream decision, not a Debian or Ubuntu modification.  No clue why.
[02:49] <MMlosh> oh..
[02:50] <infinity> I'd change it, but if upstream had a legit reason to do it (I suspect not, but maybe), I'd prefer not to break it and find out later. :P
[02:53]  * infinity testbuilds this time, to avoid further embarrassment.
[03:06] <infinity> MMlosh: Well, I'll forward the patch to Debian, but the Debian maintainer hasn't uploaded since 2009.  I might NMU for some of the outstanding issues, if I'm feeling keen.
[03:06] <infinity> MMlosh: But, anyway, fixed in Ubuntu (no, really, it builds this time!)
[03:06] <MMlosh> great..  I haven't expected such quick reaction..  since there was no update since that 2009...
[03:08] <MMlosh> but the coder itself was kinda-active in 2011
[03:10] <infinity> Oh, curious, the maintainer did respond to a bug for a new upstream version only a few days ago.  Maybe he's not dead.
[03:21] <MMlosh> neat
[03:22] <MMlosh> people want dvb-s2 I guess
[03:38] <infinity> Oh, and not going to bother forwarding that fix to Debian, looks like the new upstream version fixes the cast.
[03:38] <infinity> So, Debian will get it for free when they rev, which the maintainer seems to be working on.
[07:37] <MMlosh> infinity, interesting..   I would bet that the bug was kept    and lose
[07:51] <drinkin_leninade> hi guys, I'm looking for an ARM guru that can help me with a non ubuntu related question…
[11:45] <MMlosh> infinity, do you know, if the debian maintainer plans to release the current version soon?     (Since the program is unable to acquire "signal lock" on our multiplex with highest frequency)
[18:38] <infinity> MMlosh: Not sure, to be honest.