Bug#653501: libfreenect : pull request and issues raised

2012-01-28 Thread Nicolas Bourdaud
On 28/01/2012 05:15, Yaroslav Halchenko wrote: > just 1 minor addition toward better python-freenect > https://github.com/yarikoptic/libfreenect/tree/debian-0.1.2 > > ideally we could also update pre-generated freenect.c and patch on older > systems to not re-cython it... but as far as noone compl

Bug#653501: libfreenect : pull request and issues raised

2012-01-27 Thread Yaroslav Halchenko
just 1 minor addition toward better python-freenect https://github.com/yarikoptic/libfreenect/tree/debian-0.1.2 ideally we could also update pre-generated freenect.c and patch on older systems to not re-cython it... but as far as noone complaints -- I am just ok with how it is now so -- make up y

Bug#653501: libfreenect : pull request and issues raised

2012-01-27 Thread Yaroslav Halchenko
my .1 cents on you questions On Fri, 27 Jan 2012, Nicolas Bourdaud wrote: > The udev rules were broken, so I needed to update them, especially, the > permission of "all" is updated by another udev rule that I have not yet > identified but anyways, I am not sure it was a good practice to gran

Bug#653501: libfreenect : pull request and issues raised

2012-01-27 Thread Yaroslav Halchenko
On Sat, 28 Jan 2012, Nicolas Bourdaud wrote: > >> > we might alternatively start libfreenect-maint team on alioth which > >> > would be listed as the maintainer while we all stay in uploaders... what > >> > you think? > If everybody in the neurodebian project, we can stay in it, that what > you pr

Bug#653501: libfreenect : pull request and issues raised

2012-01-27 Thread Nicolas Bourdaud
Hello Arne! On 27/01/2012 18:26, Yaroslav Halchenko wrote: > Hi Arne -- thanks a lot for following up! > So Nicolas -- ready to take the blame? ;) If it is ok for all of you, I am fine with taking the blame! :-) On 27/01/2012 17:32, Yaroslav Halchenko wrote: > I guess you do have a > beast (kin

Bug#653501: libfreenect : pull request and issues raised

2012-01-27 Thread Arne Bernin
> - solution 1: installing libfreenect0.1 package installs a modprobe rule > which blacklist the module gspca_kinect. But it makes the v4l2 interface > unavailable which is bad for those who want to use it. What about asking the user via debconf what he wants and make the blacklisting as an option

Bug#653501: libfreenect : pull request and issues raised

2012-01-27 Thread Yaroslav Halchenko
or may be just bluntly under NeuroDebian Team, since you are pretty much a part of it now ;-) ) On Fri, 27 Jan 2012, Yaroslav Halchenko wrote: > we might alternatively start libfreenect-maint team on alioth which > would be listed as the maintainer while we all stay in uploaders... what > you thin

Bug#653501: libfreenect : pull request and issues raised

2012-01-27 Thread Yaroslav Halchenko
you are great help Nicolas -- thank you a lot. I guess you do have a beast (kinect) to enjoy, right? ;) I think it would be only fair ATM if you place Arne into Uploaders and yourself into the Maintainer, since you seems got a good grap on things we might alternatively start libfreenect-maint te

Bug#653501: libfreenect : pull request and issues raised

2012-01-27 Thread Nicolas Bourdaud
Hi Yaroslav! The package starts to be in good shape, here are the last modifications: - updated to upstream 0.1.2 (+dfsg) - fixes shlibs warnings (not for python module) - add -doc package - fixes udev rules - written backport patches As such, the package is almost over. I ha