[06:46] <dholbach> good morning
[06:54] <ajmitch> morning dholbach
[06:59] <geser> Hi dholbach and ajmitch
[06:59] <dholbach> hi ajmitch, hi geser
[06:59] <ajmitch> hi geser
[09:13] <Whoopie> broder: Hi, do you have time to discuss bug 898003? What's the right way to get usbip updated?
[09:21] <tumbleweed> Whoopie: get it on the sponsorship queue
[09:21] <tumbleweed> !sponsorship
[09:22] <Whoopie> tumbleweed: yes, but we need to agree how to package usbip as it's in the kernel tree now. Just make a snapshot of the folder? What should be the version number, e.g. 3.2.0?
[09:22] <tumbleweed> yes, sounds sensible
[09:23] <tumbleweed> err, 3.2.0-0ubutnu1 obviously
[09:23] <tumbleweed> and assume I can spell Ubuntu
[09:24] <Whoopie> hehe
[09:27] <Whoopie> tumbleweed, broder: I subscribed the sponsors team. I'm idling here if you have any questions/remarks.
[09:28] <tumbleweed> Whoopie: the current sponsorship turnaround time is a week or so, so hopefully broder doesn't neglect you :)
[09:29] <tumbleweed> are there significant changes in the new version?
[09:30] <Whoopie> usbip_bind_driver binary was merged with the usbip binary. And the command syntax changed. That's all I can see from user perspective.
[09:30] <Whoopie> tumbleweed: and btw, I'm good in prodding, so broder has no chance. :-D
[09:31] <tumbleweed> he does seem rather busy atm, though
[09:32] <tumbleweed> those changes sound significant enough to need a feature freeze exception at this point, but also likely something that'll be easily approved (I don't see any reverse dependencies)
[09:32] <tumbleweed> !ffe
[09:33] <Whoopie> it "should" be approved as the current usbip package doesn't work at all with the current kernel modules.
[09:33] <tumbleweed> ah, then don't bother :)
[10:03] <Whoopie> tumbleweed: just found a version number in usbip's configure.ac (https://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h=0aee58894551d7a9992f79d77d89f5846eb5e938)
[10:03] <Whoopie> Should I use this version number then?
[10:10] <tumbleweed> Whoopie: yeah, probably a better choice. And it's still less than 3.2.0, so when this does eventually come from the kernel, that can use a kernel version without causing any harm
[13:53] <dholbach> thanks ScottK for reassigning bug 978671 - I originally meant to mark it 'fix committed', but seem to have missed that status :)
[13:55] <ScottK> dholbach: No problem.
[13:55] <dholbach> ScottK, is release team activity higher than in past releases?
[13:55] <ScottK> I don't think so.
[13:56] <ScottK> No metrics though.
[13:56] <dholbach> sure, I was more interested in gut feeling than pie charts ;-)
[13:56] <dholbach> cool
[15:23] <ahasenack> hi, quick initscript question that http://refspecs.linuxbase.org/LSB_3.1.0/LSB-Core-generic/LSB-Core-generic/iniscrptact.html didn't answer me
[15:23] <ahasenack> if a service isn't running and I issue "/etc/init.d/<service> reload", should it fail?
[15:25] <ahasenack> http://www.debian.org/doc/debian-policy/ch-opersys.html#s-sysvinit also didn't help
[15:27] <ahasenack> /etc/init.d/skeleton has a sample do_reload() function that always returns 0
[16:10] <jcfp> ahasenack: you could argue that the expected result of a reload is for the service to be active with the latest config loaded, along the lines of a restart action on an inactive service
[18:50] <matttbe> Hello,
[18:50] <matttbe> Currently, Alacarte (a menu editor for menus made with libgnome-menu) recommends gnome-panel (Gnome Classic session) and exo-utils (XFCE session) packages but Alacarte can be used with other sessions: e.g. Cairo-Dock (but I'm sure there is also other applications) also uses libgnome-menu in order to have a "Gnome-Menu-like" and we can use Cairo-Dock without Gnome/XFCE Panel. Alacarte can be used to edit this menu but currently if we
[18:50] <matttbe> install Alacarte on Ubuntu, Gnome-Panel and the Gnome Classic session will be installed...
[18:50] <matttbe> A solution is to no longer recommend these packages but we can add them as suggestions. Do you think it's a good solution?
[18:50] <matttbe> This is what I said on the bug #975299
[18:50] <matttbe> A bzr branch has been linked to this bug report.