Re: openni_1.5.4.0-6_amd64.changes ACCEPTED into unstable, unstable
On 11/25/2013 01:49 PM, Jochen Sprickerhof wrote: * Hans-Christoph Steiner h...@eds.org [2013-11-25 11:08]: Uploaded! Let's hope ftp-masters likes it :) Great, thanks :). Could you remove the patches which shouldn't be there? I wouldn't know which ones to keep and which to remove. Done. Cheers Jochen Ok, I tweaked a couple things and uploaded it to NEW :) .hc signature.asc Description: OpenPGP digital signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: openni_1.5.4.0-6_amd64.changes ACCEPTED into unstable, unstable
On 11/24/2013 06:38 AM, Jochen Sprickerhof wrote: Hi Hans-Christoph, * Hans-Christoph Steiner h...@eds.org [2013-11-23 13:28]: * the descriptions in debian/control still mention avin2. Could you add something about what makes this 'pointclouds' fork different than the official one, and avin2? Done in 579de11. * does openni-sensor-pointclouds conflict with the potentially upcoming openni-sensor-primesense and openni-sensor-avin2? I.e. do they share paths to the same files? If so, that will need to be marked in the package once those others are added. Done in d4ba911. Uploaded! Let's hope ftp-masters likes it :) * as for uploading openni-sensor-primesense, isn't that just a matter of removing the patches that are specific to avin2 and pointclouds? That one seemed ready to go for me, except for the issue of new features being added by patches in debian/patches. The package descriptions would need an update as well, otherwise it should be fine. Cheers Jochen Could you remove the patches which shouldn't be there? I wouldn't know which ones to keep and which to remove. .hc signature.asc Description: OpenPGP digital signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: openni_1.5.4.0-6_amd64.changes ACCEPTED into unstable, unstable
* Hans-Christoph Steiner h...@eds.org [2013-11-25 11:08]: Uploaded! Let's hope ftp-masters likes it :) Great, thanks :). Could you remove the patches which shouldn't be there? I wouldn't know which ones to keep and which to remove. Done. Cheers Jochen ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: openni_1.5.4.0-6_amd64.changes ACCEPTED into unstable, unstable
Hi Hans-Christoph, * Hans-Christoph Steiner h...@eds.org [2013-11-23 13:28]: * the descriptions in debian/control still mention avin2. Could you add something about what makes this 'pointclouds' fork different than the official one, and avin2? Done in 579de11. * does openni-sensor-pointclouds conflict with the potentially upcoming openni-sensor-primesense and openni-sensor-avin2? I.e. do they share paths to the same files? If so, that will need to be marked in the package once those others are added. Done in d4ba911. * as for uploading openni-sensor-primesense, isn't that just a matter of removing the patches that are specific to avin2 and pointclouds? That one seemed ready to go for me, except for the issue of new features being added by patches in debian/patches. The package descriptions would need an update as well, otherwise it should be fine. Cheers Jochen ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: openni_1.5.4.0-6_amd64.changes ACCEPTED into unstable, unstable
On 11/09/2013 12:36 PM, Jochen Sprickerhof wrote: * Hans-Christoph Steiner h...@eds.org [2013-11-04 14:20]: tarball to build the package from. Here's your git repo: http://anonscm.debian.org/gitweb/?p=pkg-multimedia/openni-sensor-pointclouds.git;a=summary I've just pushed an adapted version there. Can you have a look at it and sponsor it, if it's ok? Thanks! Jochen Ok, alioth is finally back up, so I'm reviewing this. * I filed an ITP bug report and uploaded a couple small changes to the package * the descriptions in debian/control still mention avin2. Could you add something about what makes this 'pointclouds' fork different than the official one, and avin2? * does openni-sensor-pointclouds conflict with the potentially upcoming openni-sensor-primesense and openni-sensor-avin2? I.e. do they share paths to the same files? If so, that will need to be marked in the package once those others are added. * as for uploading openni-sensor-primesense, isn't that just a matter of removing the patches that are specific to avin2 and pointclouds? That one seemed ready to go for me, except for the issue of new features being added by patches in debian/patches. .hc signature.asc Description: OpenPGP digital signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: openni_1.5.4.0-6_amd64.changes ACCEPTED into unstable, unstable
* Hans-Christoph Steiner h...@eds.org [2013-11-04 14:20]: tarball to build the package from. Here's your git repo: http://anonscm.debian.org/gitweb/?p=pkg-multimedia/openni-sensor-pointclouds.git;a=summary I've just pushed an adapted version there. Can you have a look at it and sponsor it, if it's ok? Thanks! Jochen ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: openni_1.5.4.0-6_amd64.changes ACCEPTED into unstable, unstable
* Hans-Christoph Steiner h...@eds.org [2013-11-04 19:59]: Having a dash in the upstream version number will make it tricky since the package version comes after a dash. Also, I think its good to have as simple tag names as possible. Since PrimeSense has long ones, this repo could use very short ones like '5.1.0.41' Or even '5.1.0.41.1' if you want to throw in a pointcloud-specific version. Sorry my bad, I've pushed Stable-5.1.0.41.1 now. Cheers Jochen ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: openni_1.5.4.0-6_amd64.changes ACCEPTED into unstable, unstable
* Hans-Christoph Steiner h...@eds.org [2013-11-04 14:20]: Looks good. Next step is tagging a release there, so there is an upstream tarball to build the package from. I've just pushed Stable-5.1.0.41-pointclouds-1, can you import it? Otherwise I can do it tomorrow. Here's your git repo: http://anonscm.debian.org/gitweb/?p=pkg-multimedia/openni-sensor-pointclouds.git;a=summary Great, thx. Cheers Jochen ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: openni_1.5.4.0-6_amd64.changes ACCEPTED into unstable, unstable
On 11/04/2013 02:32 PM, Jochen Sprickerhof wrote: * Hans-Christoph Steiner h...@eds.org [2013-11-04 14:20]: Looks good. Next step is tagging a release there, so there is an upstream tarball to build the package from. I've just pushed Stable-5.1.0.41-pointclouds-1, can you import it? Otherwise I can do it tomorrow. Having a dash in the upstream version number will make it tricky since the package version comes after a dash. Also, I think its good to have as simple tag names as possible. Since PrimeSense has long ones, this repo could use very short ones like '5.1.0.41' Or even '5.1.0.41.1' if you want to throw in a pointcloud-specific version. .hc Here's your git repo: http://anonscm.debian.org/gitweb/?p=pkg-multimedia/openni-sensor-pointclouds.git;a=summary Great, thx. Cheers Jochen ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: openni_1.5.4.0-6_amd64.changes ACCEPTED into unstable, unstable
On 10/30/2013 02:30 PM, Jochen Sprickerhof wrote: * Hans-Christoph Steiner h...@eds.org [2013-10-30 12:11]: Patches in a Debian package are not meant for adding new functionality. They are meant to get the code building/working/installing on Debian, and for fixing security bugs. So the package that includes those patches should be named after the source of those patches. Even better, that package should be based off of that source's release. Those patches are not in the referenced git repo (https://github.com/PrimeSense/Sensor) and there is no description in each patch to say where its from. In the spirit of free software, people should be able to find all of the original sources of a package. Huh, every path in [1] should have a reference where it was taken from. I didn't provide a commit id because they are almost all part of one big patch. Is there a source repo somewhere that includes those patches? Then lets use that and name the package after that. It was https://kforge.ros.org/openni/drivers back then, but seems like that doesn't exists anymore. Are any of them from the avin2 repo? As commented in the patches in [1]. I see now, I just grepped for the Description tag. I should have looked closer, sorry for the noise. I think adding a USB ID to support other devices is an OK thing to do in a patch. Great, me too :). Could you comment on which patches you think are not ok then? Cheers Jochen [1] http://anonscm.debian.org/gitweb/?p=pkg-multimedia/openni-sensor-primesense.git;a=tree;f=debian/patches;hb=HEAD So it seems that you gathered a collection of patches from https://github.com/avin2/SensorKinect, https://kforge.ros.org/openni/drivers, and https://github.com/rbrusu/Sensor. This is a great thing to do, gathering all the useful patches in one place. I just think it should be all in a single git repo that anyone can use, i.e. on Fedora, Gentoo, whatever. So how about you make a repo that has all of the general patches in it, then we package that as 'openni-sensor-YOURNAMEHERE'. Then the Debian-specific patches, like for building against the system libjpeg, etc. will be in the packaging. Then 'openni-sensor-primesense' will be the primesense code with only the Debian-specific patches applied, and maybe the ones adding USB ids if that makes sense. .hc ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: openni_1.5.4.0-6_amd64.changes ACCEPTED into unstable, unstable
On 10/29/2013 10:46 AM, Jochen Sprickerhof wrote: * Hans-Christoph Steiner h...@eds.org [2013-10-29 10:10]: My question is more the opposite: when do people use the plain version without any of the avin2 patches? I think we should call the current package 'openni-sensor-avin2-sensorkinect', then leave it open for anyone to make the 'openni-sensor-primesense' package that is the plain version direct from PrimeSense without the avin2 patches. But avin2 is known to be Kinect only. We could name it willow or something (as they made the patches), but from my point the patches are not so big to rename the package. Just for comparison, Fedora ships the patched version as well ;). Cheers Jochen Patches in a Debian package are not meant for adding new functionality. They are meant to get the code building/working/installing on Debian, and for fixing security bugs. So the package that includes those patches should be named after the source of those patches. Even better, that package should be based off of that source's release. Those patches are not in the referenced git repo (https://github.com/PrimeSense/Sensor) and there is no description in each patch to say where its from. In the spirit of free software, people should be able to find all of the original sources of a package. Is there a source repo somewhere that includes those patches? Then lets use that and name the package after that. Are any of them from the avin2 repo? I think adding a USB ID to support other devices is an OK thing to do in a patch. .hc ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: openni_1.5.4.0-6_amd64.changes ACCEPTED into unstable, unstable
* Hans-Christoph Steiner h...@eds.org [2013-10-30 12:11]: Patches in a Debian package are not meant for adding new functionality. They are meant to get the code building/working/installing on Debian, and for fixing security bugs. So the package that includes those patches should be named after the source of those patches. Even better, that package should be based off of that source's release. Those patches are not in the referenced git repo (https://github.com/PrimeSense/Sensor) and there is no description in each patch to say where its from. In the spirit of free software, people should be able to find all of the original sources of a package. Huh, every path in [1] should have a reference where it was taken from. I didn't provide a commit id because they are almost all part of one big patch. Is there a source repo somewhere that includes those patches? Then lets use that and name the package after that. It was https://kforge.ros.org/openni/drivers back then, but seems like that doesn't exists anymore. Are any of them from the avin2 repo? As commented in the patches in [1]. I think adding a USB ID to support other devices is an OK thing to do in a patch. Great, me too :). Could you comment on which patches you think are not ok then? Cheers Jochen [1] http://anonscm.debian.org/gitweb/?p=pkg-multimedia/openni-sensor-primesense.git;a=tree;f=debian/patches;hb=HEAD ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: openni_1.5.4.0-6_amd64.changes ACCEPTED into unstable, unstable
On 10/28/2013 03:24 PM, Jochen Sprickerhof wrote: (just recent my previous reply, to all, sorry for the spam) * Hans-Christoph Steiner h...@eds.org [2013-10-28 15:20]: Is openni-sensor-primesense useful on its own? That seems like a lot of patches to include in the package. Are people using the plain openni-sensor-primesense stuff at all, or do you really need the avin2 stuff to make anything work? openni-sensor-primesense with the patches in the Debian git is usable with the Kinect as well as the Primesense sensor (Asus Xtion and alike). My question is more the opposite: when do people use the plain version without any of the avin2 patches? I think we should call the current package 'openni-sensor-avin2-sensorkinect', then leave it open for anyone to make the 'openni-sensor-primesense' package that is the plain version direct from PrimeSense without the avin2 patches. .hc ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: openni_1.5.4.0-6_amd64.changes ACCEPTED into unstable, unstable
* Hans-Christoph Steiner h...@eds.org [2013-10-29 10:10]: My question is more the opposite: when do people use the plain version without any of the avin2 patches? I think we should call the current package 'openni-sensor-avin2-sensorkinect', then leave it open for anyone to make the 'openni-sensor-primesense' package that is the plain version direct from PrimeSense without the avin2 patches. But avin2 is known to be Kinect only. We could name it willow or something (as they made the patches), but from my point the patches are not so big to rename the package. Just for comparison, Fedora ships the patched version as well ;). Cheers Jochen ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
openni_1.5.4.0-6_amd64.changes ACCEPTED into unstable, unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 01 Oct 2013 20:53:53 -0400 Source: openni Binary: libopenni0 libopenni-java openni-utils libopenni-dev openni-doc Architecture: source amd64 all Version: 1.5.4.0-6 Distribution: unstable Urgency: low Maintainer: Debian Multimedia Maintainers pkg-multimedia-maintainers@lists.alioth.debian.org Changed-By: Hans-Christoph Steiner h...@eds.org Description: libopenni-dev - headers for OpenNI 'Natural Interaction' frameworks libopenni-java - Java framework for sensor-based 'Natural Interaction' libopenni0 - framework for sensor-based 'Natural Interaction' openni-doc - developer documentation for OpenNI frameworks openni-utils - debug and test utilities OpenNI framework Closes: 607160 Changes: openni (1.5.4.0-6) unstable; urgency=low . * Initial upload to Debian (Closes: #607160) * Standards-Version: 3.9.4 * added .docx source to included Documentation/OpenNI_UserGuide.pdf * updated debian/copyright to copyright-format/1.0 * include all relevant copyright statements and licenses * include relevant documentation in doc-base Checksums-Sha1: 20d9f6632e57d6be88cccb6bce4063e7a3bbb2d1 2401 openni_1.5.4.0-6.dsc 873bcfd47af26d615247db2f0e632e651d33834f 22620241 openni_1.5.4.0.orig.tar.gz eacc6af4d1e21a75fd6eaadcd5cd71a1bd14d360 736009 openni_1.5.4.0-6.debian.tar.gz 463aa593765a9f1a42f7ccdd9a8c5d02bc176244 286374 libopenni0_1.5.4.0-6_amd64.deb d121b52bc0dbeecae78eab77c078d81dd780a043 144036 libopenni-java_1.5.4.0-6_amd64.deb 1e99cc78ad2ff3a58b9c5a3a7314110a07be5012 126474 openni-utils_1.5.4.0-6_amd64.deb e66ae22a9ca554e2243a4b6b854a42e41915d2ad 151332 libopenni-dev_1.5.4.0-6_amd64.deb 1721c3471145707c40c609d97fbce9b1fc0713ad 4025832 openni-doc_1.5.4.0-6_all.deb Checksums-Sha256: b761fd8b12fc6066502789dcef94fe92d56479cc9ce81518c34b5037bef2d9e7 2401 openni_1.5.4.0-6.dsc ec3dbc990b0067a776096e88d9171d8e21212115b58feaa800d0d7bfdb9151cb 22620241 openni_1.5.4.0.orig.tar.gz 1231c4a837344ac3686f51c7e32e3ebc92f0a8a763bfbb314b34b3a8d9631df0 736009 openni_1.5.4.0-6.debian.tar.gz f54cce2157e8197a4abae30711eda5713b5b05678a04e57c66bedbcc1a08dbd1 286374 libopenni0_1.5.4.0-6_amd64.deb 2de07a6a97b3c6f912965b46b36be144a1ace41728b071472c5b502e1ca033c7 144036 libopenni-java_1.5.4.0-6_amd64.deb f200a15392eaaa598bf2309ad1d4513aba10832385f67f01a41d8ca6fe3c5898 126474 openni-utils_1.5.4.0-6_amd64.deb 7fa59375d1412d6183a57a6ad26fe74264aa8c9d9b83b2fb6f277d33e4d0047d 151332 libopenni-dev_1.5.4.0-6_amd64.deb ba51d362548ceb15a72a7a0a0748fc8a7dbb1ae2095ca343ae4c7f57904a3487 4025832 openni-doc_1.5.4.0-6_all.deb Files: 5e281a605678aa0bc21a659e3e8cd413 2401 libs optional openni_1.5.4.0-6.dsc 204594b8dc65e3c3acb86dd99ac18c56 22620241 libs optional openni_1.5.4.0.orig.tar.gz 6e0a3b1e80a64f8149598d392e0108a5 736009 libs optional openni_1.5.4.0-6.debian.tar.gz a82d6ce1bf5c8fec7583ada98ab9ab4a 286374 libs optional libopenni0_1.5.4.0-6_amd64.deb 9b0c82d03bf828363ca89403a0cc4aa4 144036 java optional libopenni-java_1.5.4.0-6_amd64.deb 452010e29a21badfe9a46ae0f26298b4 126474 utils optional openni-utils_1.5.4.0-6_amd64.deb 4bfd34296100e90168b7b62c7f67cba3 151332 libdevel optional libopenni-dev_1.5.4.0-6_amd64.deb 852652400073ae93fedda4f2b32ba9d0 4025832 doc optional openni-doc_1.5.4.0-6_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: GPG for Android - https://guardianproject.info/code/gnupg/ iQIcBAEBCAAGBQJSS3thAAoJEJ8P5Yc3S76BPaIQAKzcdPmc0b5cSsTf6u++54gr YQf4nSK+gTFmBSiZJYzTUyui24fwRX+QCBvwKcWcyzw+ja6r66yaU2ijPqVS2N2a PBTQCy9oK93t6WE25ZKIxKHOIFK75LDkbPLQ4IM/e8ZaHvcpdzlMsDL1aZZUhjsM Np4Ul064wqie/8ifhRPMO3xw4YEEvugsBhOagpbk+ieieWTwxCs3mvSKyYeMUrdZ 4N+y3a2Fg3W/AwYs+qqZDWBiAO5vkdyg2LcL+VYDYmlzYS5Gjk54x2Xo67ZofXjg laiXgsvVStay6R+M1gnzoExA8bsAPio/YPgltXMvF4x5DbJ+lFHnhDkJOei0wxjN zl6qzaZhNnLJwfzu1G3ndiBsbA2dNoTPpDmd5ERAmZypELKByHgsJSqir1kwOyLq Kxpci04InJ8YYZz7m6frfUs6zxk6fzCPu5BJvxbCq/3/Kcyd9N6UCD0Gxowtum9b Vdf2MFeh5+pTvsz1iy1ysDp7f9wuBXtdzskdZ7MB5Oe6rl0oWLC66+zRpHBcn7Oa jv7/NL1l2XHMX1YXH+8jlAPUx6kFkeGv1w7QDs6kV89mcZYVgGfJI+couF2+x/KN v8abpax/ZzSI2nDVaqLSale2fUbY6ek5r+kxPrStj1vw/J0//drzFaRwGIb3SzAc 9l7V/HGBOte9RjegFOvd =hZGh -END PGP SIGNATURE- Thank you for your contribution to Debian. ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: openni_1.5.4.0-6_amd64.changes ACCEPTED into unstable, unstable
At long last, we finally did it! openni is officially part of Debian (and soon it'll be automatically included in Ubuntu). The openni2 package should be pretty straightforward then if openni2 is not too different than openni. I don't currently have time to contribute to the packaging of openni2 but I can upload it to the Debian NEW Queue once its ready. Also, is openni-sensor-primesense ready for upload? primesense-nite-nonfree is still waiting in the NEW queue, but hopefully it'll be accepted soon since it was just waiting on openni to be accepted. .hc On Oct 28, 2013, at 1:00 PM, Debian FTP Masters wrote: Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 01 Oct 2013 20:53:53 -0400 Source: openni Binary: libopenni0 libopenni-java openni-utils libopenni-dev openni-doc Architecture: source amd64 all Version: 1.5.4.0-6 Distribution: unstable Urgency: low Maintainer: Debian Multimedia Maintainers pkg-multimedia-maintainers@lists.alioth.debian.org Changed-By: Hans-Christoph Steiner h...@eds.org Description: libopenni-dev - headers for OpenNI 'Natural Interaction' frameworks libopenni-java - Java framework for sensor-based 'Natural Interaction' libopenni0 - framework for sensor-based 'Natural Interaction' openni-doc - developer documentation for OpenNI frameworks openni-utils - debug and test utilities OpenNI framework Closes: 607160 Changes: openni (1.5.4.0-6) unstable; urgency=low . * Initial upload to Debian (Closes: #607160) * Standards-Version: 3.9.4 * added .docx source to included Documentation/OpenNI_UserGuide.pdf * updated debian/copyright to copyright-format/1.0 * include all relevant copyright statements and licenses * include relevant documentation in doc-base Checksums-Sha1: 20d9f6632e57d6be88cccb6bce4063e7a3bbb2d1 2401 openni_1.5.4.0-6.dsc 873bcfd47af26d615247db2f0e632e651d33834f 22620241 openni_1.5.4.0.orig.tar.gz eacc6af4d1e21a75fd6eaadcd5cd71a1bd14d360 736009 openni_1.5.4.0-6.debian.tar.gz 463aa593765a9f1a42f7ccdd9a8c5d02bc176244 286374 libopenni0_1.5.4.0-6_amd64.deb d121b52bc0dbeecae78eab77c078d81dd780a043 144036 libopenni-java_1.5.4.0-6_amd64.deb 1e99cc78ad2ff3a58b9c5a3a7314110a07be5012 126474 openni-utils_1.5.4.0-6_amd64.deb e66ae22a9ca554e2243a4b6b854a42e41915d2ad 151332 libopenni-dev_1.5.4.0-6_amd64.deb 1721c3471145707c40c609d97fbce9b1fc0713ad 4025832 openni-doc_1.5.4.0-6_all.deb Checksums-Sha256: b761fd8b12fc6066502789dcef94fe92d56479cc9ce81518c34b5037bef2d9e7 2401 openni_1.5.4.0-6.dsc ec3dbc990b0067a776096e88d9171d8e21212115b58feaa800d0d7bfdb9151cb 22620241 openni_1.5.4.0.orig.tar.gz 1231c4a837344ac3686f51c7e32e3ebc92f0a8a763bfbb314b34b3a8d9631df0 736009 openni_1.5.4.0-6.debian.tar.gz f54cce2157e8197a4abae30711eda5713b5b05678a04e57c66bedbcc1a08dbd1 286374 libopenni0_1.5.4.0-6_amd64.deb 2de07a6a97b3c6f912965b46b36be144a1ace41728b071472c5b502e1ca033c7 144036 libopenni-java_1.5.4.0-6_amd64.deb f200a15392eaaa598bf2309ad1d4513aba10832385f67f01a41d8ca6fe3c5898 126474 openni-utils_1.5.4.0-6_amd64.deb 7fa59375d1412d6183a57a6ad26fe74264aa8c9d9b83b2fb6f277d33e4d0047d 151332 libopenni-dev_1.5.4.0-6_amd64.deb ba51d362548ceb15a72a7a0a0748fc8a7dbb1ae2095ca343ae4c7f57904a3487 4025832 openni-doc_1.5.4.0-6_all.deb Files: 5e281a605678aa0bc21a659e3e8cd413 2401 libs optional openni_1.5.4.0-6.dsc 204594b8dc65e3c3acb86dd99ac18c56 22620241 libs optional openni_1.5.4.0.orig.tar.gz 6e0a3b1e80a64f8149598d392e0108a5 736009 libs optional openni_1.5.4.0-6.debian.tar.gz a82d6ce1bf5c8fec7583ada98ab9ab4a 286374 libs optional libopenni0_1.5.4.0-6_amd64.deb 9b0c82d03bf828363ca89403a0cc4aa4 144036 java optional libopenni-java_1.5.4.0-6_amd64.deb 452010e29a21badfe9a46ae0f26298b4 126474 utils optional openni-utils_1.5.4.0-6_amd64.deb 4bfd34296100e90168b7b62c7f67cba3 151332 libdevel optional libopenni-dev_1.5.4.0-6_amd64.deb 852652400073ae93fedda4f2b32ba9d0 4025832 doc optional openni-doc_1.5.4.0-6_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: GPG for Android - https://guardianproject.info/code/gnupg/ iQIcBAEBCAAGBQJSS3thAAoJEJ8P5Yc3S76BPaIQAKzcdPmc0b5cSsTf6u++54gr YQf4nSK+gTFmBSiZJYzTUyui24fwRX+QCBvwKcWcyzw+ja6r66yaU2ijPqVS2N2a PBTQCy9oK93t6WE25ZKIxKHOIFK75LDkbPLQ4IM/e8ZaHvcpdzlMsDL1aZZUhjsM Np4Ul064wqie/8ifhRPMO3xw4YEEvugsBhOagpbk+ieieWTwxCs3mvSKyYeMUrdZ 4N+y3a2Fg3W/AwYs+qqZDWBiAO5vkdyg2LcL+VYDYmlzYS5Gjk54x2Xo67ZofXjg laiXgsvVStay6R+M1gnzoExA8bsAPio/YPgltXMvF4x5DbJ+lFHnhDkJOei0wxjN zl6qzaZhNnLJwfzu1G3ndiBsbA2dNoTPpDmd5ERAmZypELKByHgsJSqir1kwOyLq Kxpci04InJ8YYZz7m6frfUs6zxk6fzCPu5BJvxbCq/3/Kcyd9N6UCD0Gxowtum9b Vdf2MFeh5+pTvsz1iy1ysDp7f9wuBXtdzskdZ7MB5Oe6rl0oWLC66+zRpHBcn7Oa jv7/NL1l2XHMX1YXH+8jlAPUx6kFkeGv1w7QDs6kV89mcZYVgGfJI+couF2+x/KN v8abpax/ZzSI2nDVaqLSale2fUbY6ek5r+kxPrStj1vw/J0//drzFaRwGIb3SzAc 9l7V/HGBOte9RjegFOvd =hZGh -END PGP SIGNATURE- Thank you for your contribution to Debian.
Re: openni_1.5.4.0-6_amd64.changes ACCEPTED into unstable, unstable
* Hans-Christoph Steiner h...@eds.org [2013-10-28 13:26]: At long last, we finally did it! openni is officially part of Debian (and soon it'll be automatically included in Ubuntu). Awesome! Also, is openni-sensor-primesense ready for upload? primesense-nite-nonfree is still waiting in the NEW queue, but hopefully it'll be accepted soon since it was just waiting on openni to be accepted. I've just pushed similar licensing patches as you did for Openni, so it's clear to go from me. Cheers Jochen ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: openni_1.5.4.0-6_amd64.changes ACCEPTED into unstable, unstable
On Oct 28, 2013, at 2:05 PM, Jochen Sprickerhof wrote: * Hans-Christoph Steiner h...@eds.org [2013-10-28 13:26]: At long last, we finally did it! openni is officially part of Debian (and soon it'll be automatically included in Ubuntu). Awesome! primesense-nite-nonfree just got accepted too. Also, is openni-sensor-primesense ready for upload? primesense-nite-nonfree is still waiting in the NEW queue, but hopefully it'll be accepted soon since it was just waiting on openni to be accepted. I've just pushed similar licensing patches as you did for Openni, so it's clear to go from me. Cheers Jochen OK, I'll give it one more look and upload it when I have some time. How about openni-sensor-avin2-sensorkinect? Is that still worth having as a separate package? .hc ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: openni_1.5.4.0-6_amd64.changes ACCEPTED into unstable, unstable
* Hans-Christoph Steiner h...@eds.org [2013-10-28 14:53]: OK, I'll give it one more look and upload it when I have some time. How about openni-sensor-avin2-sensorkinect? Is that still worth having as a separate package? It's patches are integrated in openni-sensor-primesense. ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
