[08:25] Laney: tumbleweed: highvoltage: only solution I see to resolve the conflict for ARB members at the MOTU BoF that is doable is to move the MOTU session to 4:15PM, 12PM also seems to work, but that's when the 64 bit session is [08:28] micahg: what did you need? [08:29] ajmitch: ah, was going to ask you about moving the ARB session, but that won't work due to stgraber's commitments, so our only option to allow the ARB MOTUs to be at the MOTU BoF is to move the MOTU session [08:30] so you're going for least-worst time that might suit people? [08:30] I guess so [08:31] 4:15 is ipv6 health check, which stgraber will be rather involved in [08:32] ajmitch: right, he's only interested in the ARB session though [08:32] ok [08:32] or at least scheduled as such :) [08:33] it's hardly guaranteed that I'll still be awake & coherent at any of the listed times, so just schedule around who'll actually be there :) [08:34] ajmitch: thanks [08:34] * micahg wanders off to catch a few hours of sleep [08:34] lucky for some, neighbours just put some music on... :) [08:35] * micahg has to be up in a few hours [08:35] * ajmitch was going to try & be up for all the sessions as well [08:35] :(, well good luck [08:35] we'll see, good night [08:37] night [11:59] tavasti: welcome (; [12:00] Thanks! [12:00] so, to real things, what we started: bug https://bugs.launchpad.net/ubuntu/+source/zabbix/+bug/761730 [12:00] Launchpad bug 761730 in zabbix (Ubuntu) "zabbix-server-pgsql should depend on php5-pgsql" [Undecided,New] [12:01] sure, thats trivial to fix. If I fix it, how I can get my fix to ubuntu? [12:04] tavasti: while waiting others to answer, I suppose this could help: https://wiki.ubuntu.com/MOTU/Contributing [12:04] and when looking at zabbix bugs, most likely zabbix-server-mysql has similar dependency problem [12:05] Tm_T, ok, thats good starting point [12:55] micahg: did you find a suitable time for the MOTU BOF? [12:55] well, haven't heard from the others yet [13:08] micahg: sorry, I was sleeping [13:14] tumbleweed: understandable at the hour I pinged you :) [13:16] well, I got back to my room and decided I didn't want to open my laptop [13:16] tumbleweed: what! [13:16] :) [13:17] nigelb: it *was* 2:30 in the morning, and the laptop was shut down (it had run flat) [13:17] tumbleweed: pffft excuses :P [13:19] tumbleweed: wise decision, opening the laptop kept me up for another hour when I got back :-/ === Quintasan_ is now known as Quintasan [13:24] tumbleweed: almost 2:30 in the morning here, how I love how timezones line up... [13:24] :) [13:25] US UDSs work well for european/african timezones, you can get work done in the morning and listen to UDS in the afternoon [13:25] tumbleweed: This one works well for eme. Starts right at EOD from work. [13:26] but or NZ, it means starting at 2AM & still listening to sessions when at work in the morning [13:26] Except it goes into 1:30 in the morning [13:26] s/or/for/ [13:26] ajmitch: sounds lovely :) [13:26] tumbleweed: oh it is, I was playing civ iv for a few hours while waiting ;) [13:34] ajmitch: Civ IV++ [13:40] tumbleweed: so, what do you think about moving the MOTU session to later [13:48] micahg: when do you think you can fit it in? [13:48] micahg: none of the options are ideal :/ [13:49] tumbleweed: yeah, I know :( [13:49] 1500 is ideal for me, although I'd be triple-booked. Dunno about other people [13:50] I think the 64bit discussion would be too popular [13:50] and I want to get to new package workflow [13:50] MOTU probably has a bit of overlap with the developer advisory team discussion at 1500 [13:50] right, that's why I was thinking 16:15 [13:50] 1600 kinda works [13:51] * ajmitch can listen to 2 streams at once then :) [13:51] 1600...UTC or EDT? [13:51] EDT [13:51] broder: summit time [13:51] ajmitch: that's what recordings are for :) [13:52] also, yeah I move around between sessions a lot more when participating remotely [13:52] tumbleweed: that's what having 2 computers is for [13:52] hah [13:52] i can live with 16:15. i guess i'm the only one who didn't get a conflict with the original block? :-/ [13:52] broder: app review board has a reasonable overlap [13:52] * micahg was hoping a mentoring MOTU could be in the developer advisory team meeting [13:53] broder: no, we don't have a conflict either, it's for the ARB people [13:55] those dastardly ARB folk, messing everything up [14:54] so was it decided to move the MOTU session? [15:00] no [15:02] ah well === tgall_foo is now known as Dr_Who === ara is now known as Guest77757 === tgall_foo is now known as Dr_Who === tgall_foo is now known as Dr_Who === Elbrus_ is now known as Elbrus [19:47] hum, a postinst script is normally run with set -e. now I want to run a command where it is completely safe that it exists with 0 and 1. (but no values other than that because 2 is a real error while 1 is only a warning). but when it exists with 1 postinst fails. I basically do a "run x; ret=$? ; if [ $ret != 0 -a $ret != 1 ] ;" … [20:30] c_korn: i would write that with "run x || [ $? = 1 ]" [20:30] the shell will evaluate that as a single expression, and the whole expression has to be non-0 to trigger set -e [20:31] so if "run x" returns 0, the shell stops and we're good. [20:31] if it returns 1, the shell looks at the second half of the expression and evaluates that to determine if the whole expression returns "true" (i.e. 0) or "false" (i.e. 1) [20:35] oh, this is brilliant broder [20:36] it's just one of those idioms you pick up over time :) [20:39] so the if statement results into this? "if [ run x -o $? = 1 ] ;" [20:40] no, that's incorrect for several reasons [20:40] first, "[ run -x -o $? = 1 ]" won't cause "run -x" to be executed [20:40] you should think of "[" as if it were an actual program [20:40] it used to be [20:40] it just has a funny name [20:40] or a special variable: ret=run x || [ $? = 1 ] [20:40] you don't need an if statement or anything [20:41] just do "run x || [ $? = 1 ]" [20:41] with set -e, it'll either exit, or you keep going [20:41] the thing is, in case the return value of "run x" is neither 0 nor 1 I want to bring a warning and to some clean ups [20:42] hum, is this why there is "ls /usr/bin/\[" ? ;) [20:43] yeah [20:44] maybe you should go into some more detail about what your postinst is doing. my instinctive response is that if you need to do explicit cleanup, your postinst may be too complicated [20:45] ok, here it is: http://pastebin.com/raw.php?i=uucGVP3p [20:46] or with line numbering http://pastebin.com/uucGVP3p it is line 42 (yay) [21:01] c_korn: you just want the script to continue past line 42 with the result of unzip in $ret? [21:02] hm, yeah. but what I basically want is that unzip is allowed to access with both 0 and 1 but nothing else [21:23] c_korn: unzip ... && ret=$? || ret=$? [21:23] or ret=0; unzip ... || ret=$? [21:23] sets ret but doesn't exit asap [21:24] uff, the first one definitely required some thinking ;) [21:24] s/required/requires/ [21:25] an assignment like ret=$? always returns 0 I assume. or does it return the value of $? ? [21:26] it returns 0 [21:26] yup, that always succeeds so it continues with ret set to whatever unzip came up with [21:34] ok, this worked fine, thanks broder and jcfp === jack is now known as Guest53363 [21:52] Hello [21:52] I have a quick question, what do I do after I have read the Packaging Guide and the Getting Started Guide? [21:57] package something? [21:57] or adopt an orphaned package [21:57] or fix bugs [21:57] debian policy is also always a good read [21:58] How do I find a list of aphoned packages? [21:59] http://www.debian.org/devel/wnpp/ [22:00] Guest53363: we also have a project to keep track of bugs that we think would be easy to work on and good starter projects: http://harvest.ubuntu.com/opportunities/?pkg=&opplist=bitesize [22:04] Ok [22:13] Guest53363: but right now UDS (aka our big planning shindig) is just wrapping up, and the closing party starts in an hour, so things may be a bit dead around here this evening === yofel_ is now known as yofel [22:19] Ah ok :) [22:40] Hi all [23:19] benonsoftware: hi. as broder said just before you appeared. UDS (the 6-monthly developer summit) is just starting its closing party, so everyone who is normally helpful here is away from their laptops [23:19] * tumbleweed heads to the party [23:19] :) Ok thanks for letting me know [23:20] of course, not everyone is at UDS, though [23:21] :)