Bug#847988: pd-libdir: does not respect current loader path
IOhannes m zmölnig: > On Mon, 12 Dec 2016 23:45:41 +0100 > =?UTF-8?Q?IOhannes_m_zm=c3=b6lnig_=28Debian/GNU=29?= > wrote: >> On 12/12/2016 10:06 PM, IOhannes m zmoelnig wrote: >>> please fix the loader, so it respects the 'path' argument. >> >> >> afaict, this is fixed in the upstream-clone at >>https://github.com/pure-data/libdir >> >> however, the code there needs review. > > do you intend to fix this for stretch? > > dgasndr > IOhannes > I looked at it, seems alright, but I can't really say much because I haven't tracked the changes in Pd in the past couple years. Feel free to upload and make a release. .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
Bug#847988: pd-libdir: does not respect current loader path
yes, I'll happily review your fix. ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#743737: pd-unauthorized: fails to build with clang instead of gcc
Tags: pending This is already fixed in the upstream svn, so the fix will be included in the next release. ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#743738: pd-ggee: fails to build with clang instead of gcc
Tags: pending This is already fixed in the upstream svn, so the fix will be included when 0.27 is released. ___ 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: Cleaning up the team's packages?
On Feb 25, 2014, at 8:55 PM, Felipe Sateler wrote: > On Tue, Feb 25, 2014 at 2:02 PM, Hans-Christoph Steiner wrote: >> I just uploaded a new version of openni, which should fix the open issues >> preventing the openni-sensor-* packages from hitting testing. Thanks to >> Jochen for the update. > > Bug 734768 needs to be closed in a version of > openni-sensor-pointclouds, but was closed in a version of openni. Thus > the bts still thinks it is open. Done (by someone else). .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: Cleaning up the team's packages?
rror: unknown type name > ‘GtkCallbackMarshal’ > testing-migration: Migration: Not in testing for 19 days > > Package: mididings > Binary: python-mididings, mididings, mididings-doc > Uploaders: Alessio Treglia > Version: 0~20120419~ds0-3 > RC-bug: RC bug needs fixing: #733395: mididings: FTBFS: ld: cannot find > -lboost_python-mt > testing-migration: Migration: Not in testing for 24 days > > Package: mplayer > Binary: mplayer-gui, mencoder, mplayer, mplayer-dbg, mplayer-doc > Uploaders: A Mennucc1 , Reinhard Tartler < > siret...@tauware.de>, Andres Mejia > Version: 2:1.0~rc4.dfsg1+svn34540-1 > RC-bug: RC bug needs fixing: #726838: mplayer depends upon old libavutil > under unstable > RC-bug: RC bug needs fixing: #711578: Remove support for svgalib > RC-bug: RC bug needs fixing: #732159: Should this package be removed? > RC-bug: RC bug needs fixing: #708140: FTBFS: error: 'class RTSPClient' has > no member named 'setupMediaSubsession' etc. > testing-migration: Migration: Not in testing for 186 days > > Package: openni-sensor-pointclouds > Binary: libopenni-sensor-pointclouds-dev, libopenni-sensor-pointclouds0 > Uploaders: Debian Multimedia Maintainers < > pkg-multimedia-maintainers@lists.alioth.debian.org>, Hans-Christoph Steiner > > Version: 5.1.0.41.1-1 > RC-bug: RC bug needs fixing: #734768: libopenni-sensor-pointclouds0: > modifies conffiles (policy 10.7.3): /etc/openni/modules.xml > testing-migration: Migration: Not in testing for 4 days > > Package: toonloop > Binary: toonloop > Uploaders: Alexandre Quessy , Jonas Smedegaard < > d...@jones.dk> > Version: 2.2.0-1 > RC-bug: RC bug needs fixing: #721368: toonloop: FTBFS with newer boost. > RC-bug: RC bug needs fixing: #701367: toonloop: ftbfs with GCC-4.8 > testing-migration: Migration: Not in testing for 186 days > missing-build: Missing build on amd64: state Build-Attempted since > 2013-08-31 > missing-build: Missing build on armel: state Build-Attempted since > 2013-09-01 > missing-build: Missing build on armhf: state Failed since 2013-11-20 > missing-build: Missing build on i386: state Build-Attempted since 2013-08-31 > missing-build: Missing build on mips: state Failed since 2013-10-28 > missing-build: Missing build on mipsel: state Failed since 2013-10-30 > missing-build: Missing build on powerpc: state Build-Attempted since > 2014-01-18 > missing-build: Missing build on s390x: state Failed since 2013-10-27 > missing-build: Missing build on sparc: state Build-Attempted since > 2013-08-31 > > Package: tsdecrypt > Binary: tsdecrypt > Uploaders: Alessio Treglia > Version: 10.0-1 > RC-bug: RC bug needs fixing: #730415: tsdecrypt uses inappropriate build > flags including -march=native > testing-migration: Migration: Not in testing for 58 days > > Package: vdpau-video > Binary: vdpau-va-driver > Uploaders: Andres Mejia > Version: 0.7.3-2 > RC-bug: RC bug needs fixing: #713612: vdpau-video: FTBFS: > utils_glx.h:163:5: error: unknown type name 'PFNGLMULTITEXCOORD2FPROC' > testing-migration: Migration: Not in testing for 128 days > > > > > > ___ > pkg-multimedia-maintainers mailing list > pkg-multimedia-maintainers@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers > ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
getting openni-sensor-pointclouds into Debian/testing
Hey Jochen, FYI, this bug is preventing openni-sensor-pointclouds from being accepted from unstable into Debian/testing. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734768 Fixing it should just be a matter of moving modules.xml from /etc to /var and adding it to the postrm script. .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
Bug#734110: doesn't build with patch
When I add the patch as the final patch in the package, it fails to build. It looks like the patch is formatted for applying upstream. If you make your patch a patch to the packaging, and I'll include it in the package. dpkg-source: info: patches are not applied, applying them now dpkg-source: info: applying 0001-do-not-build-mono-samples.patch dpkg-source: info: applying 0002-Add-SONAME-to-libraries.patch dpkg-source: info: applying 0003-Change-path-of-config-files-to-etc-openni.patch dpkg-source: info: applying 0004-Disable-SSE.patch dpkg-source: info: applying 0005-Silence-asserts.patch dpkg-source: info: applying 0006-Use-system-wide-libjpeg.patch dpkg-source: info: applying 0007-Use-system-wide-tinyxml.patch dpkg-source: info: applying 0008-Fix-preprocessor-macro-to-be-C-11-compatible.patch dpkg-source: info: applying 0009-Remove-superfluous-printf.patch dpkg-source: info: applying 0011-do-not-compile-windows-chm-file.patch dpkg-source: info: applying 0012-port-to-powerpc.patch dpkg-source: error: LC_ALL=C patch -t -F 0 -N -p1 -u -V never -g0 -E -b -B .pc/0012-port-to-powerpc.patch/ < openni/debian/patches/0012-port-to-powerpc.patch gave error exit status 1 patching file Platform/Linux/CreateRedist/Redist_OpenNi.py Hunk #1 FAILED at 186. Hunk #2 FAILED at 335. 2 out of 2 hunks FAILED -- saving rejects to file Platform/Linux/CreateRedist/Redist_OpenNi.py.rej patching file Platform/Linux/Build/Common/CommonDefs.mak patching file Platform/Linux/Build/Common/Platform.Powerpc patching file Include/Linux-Powerpc/XnPlatformLinux-Powerpc.h patching file Include/XnOS.h patching file Include/XnPlatform.h patching file Source/OpenNI/XnOpenNI.cpp patching file Samples/NiViewer/NiViewer.cpp patching file Include/XnUSBDevice.h Hunk #1 FAILED at 48. 1 out of 1 hunk FAILED -- saving rejects to file Include/XnUSBDevice.h.rej dpkg-buildpackage: error: dpkg-source -i -I --before-build openni gave error exit status 1 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
Bug#734110: openni: FTBFS: Unknown platform: ppc
Thanks for the patch! This would be a great thing to forward upstream, have you tried that? I think they would accept it. I'm also OK with including it as part of the Debian package regardless. .hc On 01/03/2014 04:44 PM, Roland Stigge wrote: > Source: openni > Version: 1.5.4.0-6 > Severity: important > Tags: patch > User: debian-powerpc...@breakpoint.cc > Usertags: powerpcspe > > Hi, > > on powerpc and powerpcspe, openni FTBFS like this: > > ... > make[1]: Entering directory `/«PKGBUILDDIR»' > cd Platform/Linux/CreateRedist && ./RedistMaker > Unknown platform: ppc > make[1]: *** [override_dh_auto_build] Error 1 > make[1]: Leaving directory `/«PKGBUILDDIR»' > make: *** [build-arch] Error 2 > ... > > The attached patch fixes this. > > Roland > > > -- System Information: > Debian Release: 7.0 > APT prefers unreleased > APT policy: (500, 'unreleased'), (500, 'unstable') > Architecture: powerpcspe (ppc) > > Kernel: Linux 3.9.0-dirty (SMP w/2 CPU cores) > Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: > LC_ALL set to en_GB.UTF-8) > Shell: /bin/sh linked to /bin/dash > > > > ___ > pkg-multimedia-maintainers mailing list > pkg-multimedia-maintainers@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers > 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: becoming a Debian developer...
On 12/19/2013 09:15 AM, Felipe Sateler wrote: > On Thu, Dec 19, 2013 at 8:50 AM, IOhannes m zmoelnig wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA256 >> >> hi fellow packagers, >> >> now that i have become DM, i thought it probably time to do the last >> step and become DD as well. > > Excellent news! > > >> for the process of becoming a DD, i'm currently looking for advocates, >> which is where you come into play :-) >> so if you think me becoming a DD is feasible, it would be great if you >> could drop me a note, so i could proceed on that track. > > Count me as advocate too. > I will advocate too. I can also help with the DD process, since I recently went thru it. Its a pretty long process that involves quite a bit of work. My advice is to start the process whenever you are ready, but don't stress out making it happen fast. Since you're a DM and I think you've been granted upload access to all of the packages you maintain, you already have most of the access you'll use. .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: RFS: updated pd-cyclone
There is a lintian error on this package: E: pd-cyclone source: missing-build-dependency dpkg-dev (>= 1.16.1~) Since I don't really maintain CDBS packages and IOhannes is stepping up on the maintenance, I'm removing myself from Uploaders on this one. I'll grant you upload on it, please handle the lintian error. .hc On 12/09/2013 11:57 AM, IOhannes m zmoelnig wrote: > i've updated the pd-cyclone package, to fix bug #715772. > > while doing so, i also streamlined the packaging a bit, so it now > - uses more features of cdbs > - applies debian-specific build-flags (hardening!) > - has only 1 lintian errors/warning (instead of 162), and this one is > due to an outdated lintian... > - has an updated watch-file > - has me added as uploader > > someone please review and upload the package or comment :-) > > OR grant me upload permissions via dak. > > cheers, > dfasm > IOhannes > > ___ > pkg-multimedia-maintainers mailing list > pkg-multimedia-maintainers@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers > 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: getting openni2 into Debian
On 11/25/2013 06:52 AM, Hauke Wintjen wrote: > >> Hans-Christoph Steiner hat am 23. November 2013 um 18:43 >> geschrieben: >> >> >> >> >> On 11/22/2013 05:55 AM, Jochen Sprickerhof wrote: >>> Hi, >>> >>> * Hauke Wintjen [2013-11-21 09:30]: >>>>> Hans-Christoph Steiner hat am 20. November 2013 um 20:13 >>>>> geschrieben: >>>>> Also, what tool are you building it with? I couldn't get it to build with >>>>> either dpkg-buildpackage or git-buildpackage. >>>> >>>> I have written in the wiki of my fork: >>>> git-buildpackage --git-no-sign-tags --git-ignore-new -us -uc >>>> and it builds packages for me. >>> >>> I think I've found the root of this. Hauke added new upstream tags >>> (2.3.0.14.3). I would propose to reorganize the repo and only build >>> Debian packages based on upstream tags. @Hans-Christoph, did you set up >>> a repo on git.debian.org already, or could you do it, so we can clean >>> this up? >>> >>> Cheers Jochen >> >> Now that alioth is back up and running, I set it up as 'openni2' >> http://anonscm.debian.org/gitweb/?p=pkg-multimedia/openni2.git >> > > Great to hear that! > > >> Read-only is here: >> https://alioth.debian.org/anonscm/git/pkg-multimedia/openni2.git >> >> Read/write is here: >> git+ssh://git.debian.org/git/pkg-multimedia/openni2.git > > Ok, should i push the repo inside that? > >> Things have changed a bit with alioth, its a new server so it might have new >> SSH keys for you. I see the RSA key with the host key fingerprint of: >> d7:0b:26:5c:7a:5d:56:40:a9:e0:5d:f4:e1:70:88:bf > > Ok, i will try to login. > > Created just an account with hcw70-guest on alioth. >> >> I highly recommend using the git-buildpackage layout, and I can help with the >> process of converting the current repo to a git-buildpackage style repo. > > Ok, could you please provide some info on this? I thought this is already > done that way with my repo. Whats missing / wrong? I set up the openni2 repo in pkg-multimedia git-buildpackage style. It should include all of the work in your 2.2.0.33 version of the package. These are two good overviews of this workflow: https://wiki.debian.org/PackagingWithGit https://wiki.debian.org/DebianMultimedia/DevelopPackaging This covers how to include the upstream git history in the package's git repo: http://www.eyrie.org/~eagle/journal/2013-04/001.html Here's a way to set up with the full git-buildpackage style with the upstream git repo included: $ sudo apt-get install git-buildpackage pristine-tar $ gbp-clone git+ssh://git.debian.org/git/pkg-multimedia/openni2.git $ cd openni2 $ git remote add upstream https://github.com/OpenNI/OpenNI2 $ git fetch upstream Now you can build the package using git-buildpackage, and it'll also run all sorts of extra checks on it, like lintian: $ git-buildpackage For including a new release, you can both import the pristine tarball from github, and tie it to the upstream git history: $ wget https://github.com/OpenNI/OpenNI2/archive/7bef8f639e4d6.tar.gz $ cd openni2 $ git tag 2.2.0.33 7bef8f639e4d6 $ git-import-orig --upstream-vcs-tag=2.2.0.33 ../7bef8f639e4d6.tar.gz I didn't add your 'develop' branch, but you can add that as well to this mix as well. In terms of getting it uploaded to Debian, you need to update the debian/copyright with all copyright info for all files included in the git/tarball. checkout the openni package for a good example. There is also a syntax error in your debian/changelog, use the program 'dch' to edit it, and it'll automatically handle the syntax for you. I pushed your package to my OpenNI PPA for anyone to try, let's hope it builds: https://launchpad.net/~eighthave/+archive/openni/+packages .hc >> >> Hauke, were you able to request an account on alioth yet? I forget where that >> stands. > > Yes, see above. > >> >> .hc >> > > > Kind regards > > Hauke > > 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/25/2013 01:49 PM, Jochen Sprickerhof wrote: > * Hans-Christoph Steiner [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 [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
On 11/09/2013 12:36 PM, Jochen Sprickerhof wrote: > * Hans-Christoph Steiner [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: getting openni2 into Debian
On 11/22/2013 05:55 AM, Jochen Sprickerhof wrote: > Hi, > > * Hauke Wintjen [2013-11-21 09:30]: >>> Hans-Christoph Steiner hat am 20. November 2013 um 20:13 >>> geschrieben: >>> Also, what tool are you building it with? I couldn't get it to build with >>> either dpkg-buildpackage or git-buildpackage. >> >> I have written in the wiki of my fork: >> git-buildpackage --git-no-sign-tags --git-ignore-new -us -uc >> and it builds packages for me. > > I think I've found the root of this. Hauke added new upstream tags > (2.3.0.14.3). I would propose to reorganize the repo and only build > Debian packages based on upstream tags. @Hans-Christoph, did you set up > a repo on git.debian.org already, or could you do it, so we can clean > this up? > > Cheers Jochen Now that alioth is back up and running, I set it up as 'openni2' http://anonscm.debian.org/gitweb/?p=pkg-multimedia/openni2.git Read-only is here: https://alioth.debian.org/anonscm/git/pkg-multimedia/openni2.git Read/write is here: git+ssh://git.debian.org/git/pkg-multimedia/openni2.git Things have changed a bit with alioth, its a new server so it might have new SSH keys for you. I see the RSA key with the host key fingerprint of: d7:0b:26:5c:7a:5d:56:40:a9:e0:5d:f4:e1:70:88:bf I highly recommend using the git-buildpackage layout, and I can help with the process of converting the current repo to a git-buildpackage style repo. Hauke, were you able to request an account on alioth yet? I forget where that stands. .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: getting openni2 into Debian
On 11/21/2013 04:41 AM, Jochen Sprickerhof wrote: > * IOhannes m zmoelnig [2013-11-21 10:37]: >> it's always best to follow upstream as closely as possible (as long as >> they make sane assumptions :-)), esp. in picky areas like SONAMEing. >> >> if your package has not been in debian yet (which i think is true), >> you should get rid of any hacks like renaming SONAME, as long as this >> is still easily possible. > > We are not renaming the SONAME but adding one in the first place ;). > > Cheers Jochen Including a description of the issue in the patch would be quite helpful. It looks like the upstream version has a SONAME since it ends in .so.2. To add a desciption just add this at the top of the patch file: Description: renaming file to match our SONAME Upstream doesn't set SONAM blah blah blah... .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: getting openni2 into Debian
The first thing that needs doing is the debian/copyright file. All of the various licenses of the code that are included in the openni source release need to be marked in there, or the Debian ftp-masters will reject the package. So things like in the ThirdParty/ folder. Check out the debian/copyright in 'openni' for an example. Also, your debian/changelog seems to have a syntax issue: parsechangelog/debian: warning: openni2/debian/changelog(l6): badly formatted trailer line LINE: -- Hauke Wintjen Fri, 29 Mar 2013 23:14:11 +010openni2 (2.1.0.4-1ubuntu1~1.gbp2a4158) UNRELEASED; urgency=low The best way to edit debian/changelog is to use the 'dch' utility. Also, what tool are you building it with? I couldn't get it to build with either dpkg-buildpackage or git-buildpackage. Why do you change the SONAME from upstream? That's a pretty unusual thing to do. patches/0001-Add-SONAME-to-libraries.patch .hc On 11/20/2013 11:30 AM, Hauke Wintjen wrote: > Hi Hans-Christoph. > > I already have "readily" debian / ubuntu packages on github, so the > "only" thing missing is reviewing it by some more experienced debian > maintainers and getting it into debian binary packages. > > These packages are also compiling / working on Raspbian(!). > > See https://github.com/hcw70/OpenNI2 > > Regards > > Hauke > > > Am Mittwoch, den 20.11.2013, 11:26 -0500 schrieb Hans-Christoph Steiner: >> They've built up a new machine and have much of it restored, but its still in >> progress. I guess it was a really bad failure. Feel free to work out of >> gitorious.org or github.com in the meantime. Its easy to move git repos. >> >> .hc >> >> On 11/20/2013 03:47 AM, Hauke Wintjen wrote: >>> Hi Hans-Christoph. >>> >>> Still no connection to alioth? Any News on this? >>> >>> Kind regards >>> >>> Hauke >>> >>> >>> Am Dienstag, den 12.11.2013, 14:34 -0500 schrieb Hans-Christoph Steiner: >>>> Glad to hear it! >>>> >>>> Yeah, there was a multiple disk failure on that server, so they have to >>>> restore the whole thing from backups. That's what they're doing now. >>>> >>>> .hc >>>> >>>> On 11/12/2013 06:22 AM, Hauke Wintjen wrote: >>>>> Hi Hans-Christoph. >>>>> >>>>> Now i had found some time for this project again and wanted to register >>>>> at alioth. >>>>> >>>>> But since yesterday the host is down (not only for me). >>>>> >>>>> Kind regards >>>>> >>>>> Hauke >>>>> >>>>> >>>>>> Hans-Christoph Steiner hat am 13. September 2013 um 20:48 >>>>>> geschrieben: >>>>>> >>>>>> >>>>>> >>>>>> Hey Hauke, >>>>>> >>>>>> I'm emailing you as part of the team working on the OpenNI packages for >>>>>> Debian. I'm glad to see you're work on openni2! >>>>>> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707056 >>>>>> >>>>>> In case you haven't seen it, the most up-to-date version of the 'openni' >>>>>> package is here: >>>>>> http://anonscm.debian.org/gitweb/?p=pkg-multimedia/openni.git;a=summary >>>>>> >>>>>> All of the other OpenNI-related packaged are part of the Debian >>>>>> pkg-multimedia >>>>>> project, and the git repos are there: >>>>>> http://anonscm.debian.org/gitweb/?a=project_list&pf=pkg-multimedia&s=openni&btnS=Search >>>>>> >>>>>> It would be great if you could also work out of a git repo hosted by the >>>>>> pkg-multimedia team. I can set up the repo, you just need to create an >>>>>> account on Alioth, the Debian git host: >>>>>> https://alioth.debian.org/account/register.php >>>>>> >>>>>> then request to join the pkg-multimedia project here: >>>>>> http://alioth.debian.org/projects/pkg-multimedia >>>>>> >>>>>> We can then work out the final details and upload openni2 to Debian! >>>>>> >>>>>> .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/04/2013 02:32 PM, Jochen Sprickerhof wrote: > * Hans-Christoph Steiner [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 11/03/2013 01:28 PM, Jochen Sprickerhof wrote: > * Hans-Christoph Steiner [2013-10-31 14:06]: >> 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. > Good idea, I've pushed all patches to [1], so we can name the package > 'openni-sensor-pointclouds'. Can you prepare the Debian package repo? > > [1] https://github.com/PointCloudLibrary/Sensor/tree/stable-pointclouds > > Cheers Jochen Looks good. Next step is tagging a release there, so there is an upstream 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 .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/30/2013 02:30 PM, Jochen Sprickerhof wrote: > * Hans-Christoph Steiner [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 [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
On 10/28/2013 03:24 PM, Jochen Sprickerhof wrote: > (just recent my previous reply, to all, sorry for the spam) > > * Hans-Christoph Steiner [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
On Oct 28, 2013, at 2:05 PM, Jochen Sprickerhof wrote: > * Hans-Christoph Steiner [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
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 > > Changed-By: Hans-Christoph Steiner > 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 > Kxpci04InJ8YYZz7m6f
Re: OpenNI_UserGuide.pdf in original Microsoft Word format?
Hey Ziv, Just had a thought: if PrimeSense wants to see openni2 in Debian and Ubuntu sooner rather than later, it would be possible to do this as a consulting job. I am available for such work, and I imagine others are as well. I'd defer to Jochen on it since he's done the most work recently. .hc On Oct 2, 2013, at 3:10 AM, Ziv Hendel wrote: > Excellent! > Thank you for all your work, > Zivo. > > -Original Message----- > From: Hans-Christoph Steiner [mailto:h...@eds.org] > Sent: Wednesday, October 02, 2013 4:21 AM > To: Ziv Hendel > Cc: Jochen Sprickerhof; Nobuhiro Iwamatsu; Debian Multimedia Maintainers > Subject: Re: OpenNI_UserGuide.pdf in original Microsoft Word format? > > > This is perfect, no problems. I just added the .docx to the openni packaging > for openni 1.x, then for openni2, we can get it from the next release. > > .hc > > On 10/01/2013 09:54 AM, Ziv Hendel wrote: >> Yes it's exactly the same license. All of OpenNI is Apache v2. >> >> I've already checked it into our internal git, but I don't think we have any >> plans to sync it with the public openni1 git anytime soon since we only work >> on openni2. >> >> If we do update it again, it will get checked it... Is this a problem? >> (If it is I'm sure we can figure something out) >> >> Zivo. >> >> -Original Message- >> From: Hans-Christoph Steiner [mailto:h...@eds.org] >> Sent: Tuesday, October 01, 2013 4:45 PM >> To: Ziv Hendel >> Cc: Jochen Sprickerhof; Nobuhiro Iwamatsu; Debian Multimedia >> Maintainers >> Subject: Re: OpenNI_UserGuide.pdf in original Microsoft Word format? >> >> >> Excellent! The Debian gatekeepers will be happy. Two quick questions: >> >> - is the license on this file the same as the PDF and the rest of the source >> code in the OpenNI package? >> >> - can this docx file be checked into the OpenNI git alongside the PDF? >> >> .hc >> >> On Oct 1, 2013, at 3:18 AM, Ziv Hendel wrote: >> >>> Hi Hans! >>> >>> I was finally able to find the original doc file :) >>> >>> Here it is... >>> >>> Is there anything else that's missing? >>> >>> Zivo. >>> >>> -Original Message- >>> From: Hans-Christoph Steiner [mailto:h...@eds.org] >>> Sent: Wednesday, September 18, 2013 3:57 AM >>> To: Ziv Hendel >>> Subject: Re: OpenNI_UserGuide.pdf in original Microsoft Word format? >>> >>> >>> Thanks! The openni2 package is already in the works :) >>> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707056 >>> >>> .hc >>> >>> On 09/17/2013 05:00 PM, Ziv Hendel wrote: >>>> I'll try to find out who has this file :-) >>>> >>>> Are you also going to make a package for OpenNI 2? >>>> OpenNI1 is already pretty outdated... >>>> >>>> Zivo. >>>> >>>> -Original Message- >>>> From: Hans-Christoph Steiner [mailto:h...@eds.org] >>>> Sent: Friday, September 13, 2013 9:21 PM >>>> To: Ziv Hendel; z...@openni.org; Einat Kinamon; Debbie Gold Hadar >>>> Cc: Jochen Sprickerhof; Nobuhiro Iwamatsu; >>>> pkg-multimedia-maintainers@lists.alioth.debian.org >>>> Subject: OpenNI_UserGuide.pdf in original Microsoft Word format? >>>> >>>> >>>> Hey, >>>> >>>> I have a small request: would it be possible to include the original >>>> Microsoft Word document that >>>> OpenNI/Documentation/OpenNI_UserGuide.pdf is generated from? It >>>> would be useful for people used to that format rather than PDFs, and >>>> also the original format is a better source for converting to other >>>> formats >>>> >>>> Lastly, the last blocker issue preventing openni from being officially >>>> accepted into Debian and Ubuntu is the missing source file to >>>> OpenNI_UserGuide.pdf. >>>> >>>> The authors of the original are listed as Einat Kinamon and Debbie Gold >>>> Hadar. >>>> >>>> Thanks in advance! >>>> >>>> .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: updating OpenNI Debian packages
On 06/18/2013 09:56 PM, Thomas Moulard wrote: > On Wed, May 22, 2013 at 5:03 AM, Hans-Christoph Steiner wrote: >> On 05/20/2013 03:18 PM, Jochen Sprickerhof wrote: >> I just updated primesense-nite-nonfree to the latest version and updated the >> packaging. I'm out of time on this sprint. It would be great if people >> could test it and then also contribute any relevant things from the [1] >> above repo to it. Its part of pkg-multimedia, so y'all should have commit >> access to it. >> >> http://git.debian.org/?p=pkg-multimedia/primesense-nite-nonfree.git > Dear Hans-Christoph, > it just occurred to me than primesense-nite-nonfree is depending on > libopenni-dev [1] > > "Depends: debconf | debconf-2.0, dpkg-dev, devscripts, wget, unzip, > gnupg, libopenni-dev, openni-utils" > > Should someone upload openni too? Is the package ready for inclusion? > > [1] http://ftp-master.debian.org/new/primesense-nite-nonfree_0.1.html > > Best, I'm about to upload another attempt, after correcting some things. Hopefully it finally gets thru... .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_UserGuide.pdf in original Microsoft Word format?
This is perfect, no problems. I just added the .docx to the openni packaging for openni 1.x, then for openni2, we can get it from the next release. .hc On 10/01/2013 09:54 AM, Ziv Hendel wrote: > Yes it's exactly the same license. All of OpenNI is Apache v2. > > I've already checked it into our internal git, but I don't think we have any > plans to sync it with the public openni1 git anytime soon since we only work > on openni2. > > If we do update it again, it will get checked it... Is this a problem? > (If it is I'm sure we can figure something out) > > Zivo. > > -Original Message- > From: Hans-Christoph Steiner [mailto:h...@eds.org] > Sent: Tuesday, October 01, 2013 4:45 PM > To: Ziv Hendel > Cc: Jochen Sprickerhof; Nobuhiro Iwamatsu; Debian Multimedia Maintainers > Subject: Re: OpenNI_UserGuide.pdf in original Microsoft Word format? > > > Excellent! The Debian gatekeepers will be happy. Two quick questions: > > - is the license on this file the same as the PDF and the rest of the source > code in the OpenNI package? > > - can this docx file be checked into the OpenNI git alongside the PDF? > > .hc > > On Oct 1, 2013, at 3:18 AM, Ziv Hendel wrote: > >> Hi Hans! >> >> I was finally able to find the original doc file :) >> >> Here it is... >> >> Is there anything else that's missing? >> >> Zivo. >> >> -Original Message- >> From: Hans-Christoph Steiner [mailto:h...@eds.org] >> Sent: Wednesday, September 18, 2013 3:57 AM >> To: Ziv Hendel >> Subject: Re: OpenNI_UserGuide.pdf in original Microsoft Word format? >> >> >> Thanks! The openni2 package is already in the works :) >> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707056 >> >> .hc >> >> On 09/17/2013 05:00 PM, Ziv Hendel wrote: >>> I'll try to find out who has this file :-) >>> >>> Are you also going to make a package for OpenNI 2? >>> OpenNI1 is already pretty outdated... >>> >>> Zivo. >>> >>> -Original Message- >>> From: Hans-Christoph Steiner [mailto:h...@eds.org] >>> Sent: Friday, September 13, 2013 9:21 PM >>> To: Ziv Hendel; z...@openni.org; Einat Kinamon; Debbie Gold Hadar >>> Cc: Jochen Sprickerhof; Nobuhiro Iwamatsu; >>> pkg-multimedia-maintainers@lists.alioth.debian.org >>> Subject: OpenNI_UserGuide.pdf in original Microsoft Word format? >>> >>> >>> Hey, >>> >>> I have a small request: would it be possible to include the original >>> Microsoft Word document that OpenNI/Documentation/OpenNI_UserGuide.pdf is >>> generated from? It would be useful for people used to that format rather >>> than PDFs, and also the original format is a better source for converting >>> to other formats >>> >>> Lastly, the last blocker issue preventing openni from being officially >>> accepted into Debian and Ubuntu is the missing source file to >>> OpenNI_UserGuide.pdf. >>> >>> The authors of the original are listed as Einat Kinamon and Debbie Gold >>> Hadar. >>> >>> Thanks in advance! >>> >>> .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_UserGuide.pdf in original Microsoft Word format?
Excellent! The Debian gatekeepers will be happy. Two quick questions: - is the license on this file the same as the PDF and the rest of the source code in the OpenNI package? - can this docx file be checked into the OpenNI git alongside the PDF? .hc On Oct 1, 2013, at 3:18 AM, Ziv Hendel wrote: > Hi Hans! > > I was finally able to find the original doc file :) > > Here it is... > > Is there anything else that's missing? > > Zivo. > > -----Original Message- > From: Hans-Christoph Steiner [mailto:h...@eds.org] > Sent: Wednesday, September 18, 2013 3:57 AM > To: Ziv Hendel > Subject: Re: OpenNI_UserGuide.pdf in original Microsoft Word format? > > > Thanks! The openni2 package is already in the works :) > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707056 > > .hc > > On 09/17/2013 05:00 PM, Ziv Hendel wrote: >> I'll try to find out who has this file :-) >> >> Are you also going to make a package for OpenNI 2? >> OpenNI1 is already pretty outdated... >> >> Zivo. >> >> -Original Message- >> From: Hans-Christoph Steiner [mailto:h...@eds.org] >> Sent: Friday, September 13, 2013 9:21 PM >> To: Ziv Hendel; z...@openni.org; Einat Kinamon; Debbie Gold Hadar >> Cc: Jochen Sprickerhof; Nobuhiro Iwamatsu; >> pkg-multimedia-maintainers@lists.alioth.debian.org >> Subject: OpenNI_UserGuide.pdf in original Microsoft Word format? >> >> >> Hey, >> >> I have a small request: would it be possible to include the original >> Microsoft Word document that OpenNI/Documentation/OpenNI_UserGuide.pdf is >> generated from? It would be useful for people used to that format rather >> than PDFs, and also the original format is a better source for converting to >> other formats >> >> Lastly, the last blocker issue preventing openni from being officially >> accepted into Debian and Ubuntu is the missing source file to >> OpenNI_UserGuide.pdf. >> >> The authors of the original are listed as Einat Kinamon and Debbie Gold >> Hadar. >> >> Thanks in advance! >> >> .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
OpenNI_UserGuide.pdf in original Microsoft Word format?
Hey, I have a small request: would it be possible to include the original Microsoft Word document that OpenNI/Documentation/OpenNI_UserGuide.pdf is generated from? It would be useful for people used to that format rather than PDFs, and also the original format is a better source for converting to other formats Lastly, the last blocker issue preventing openni from being officially accepted into Debian and Ubuntu is the missing source file to OpenNI_UserGuide.pdf. The authors of the original are listed as Einat Kinamon and Debbie Gold Hadar. Thanks in advance! .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-7_amd64.changes REJECTED
On 07/27/2013 09:00 AM, Luca Falavigna wrote: > > Hi, > > * files under External are licensed under different terms than those listed in > copyright file. > * libopenni0 recommends libopenni-sensor-primesense0, which is not available > in the archive These are all fixed. > * Documentation/OpenNI_UserGuide.pdf has no accompanying source code: > $ pdfinfo OpenNI_UserGuide.pdf > Title: Contents > Author: Einat Kinamon;Debbie Gold Hadar > Creator:Microsoft® Office Word 2007 > Producer: Microsoft® Office Word 2007 Is the source required to be there in order for it to be included? A PDF is a binary format generated from other files, but it is also a file format that can be read and edited by many free programs. .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
getting openni2 into Debian
Hey Hauke, I'm emailing you as part of the team working on the OpenNI packages for Debian. I'm glad to see you're work on openni2! http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707056 In case you haven't seen it, the most up-to-date version of the 'openni' package is here: http://anonscm.debian.org/gitweb/?p=pkg-multimedia/openni.git;a=summary All of the other OpenNI-related packaged are part of the Debian pkg-multimedia project, and the git repos are there: http://anonscm.debian.org/gitweb/?a=project_list&pf=pkg-multimedia&s=openni&btnS=Search It would be great if you could also work out of a git repo hosted by the pkg-multimedia team. I can set up the repo, you just need to create an account on Alioth, the Debian git host: https://alioth.debian.org/account/register.php then request to join the pkg-multimedia project here: http://alioth.debian.org/projects/pkg-multimedia We can then work out the final details and upload openni2 to Debian! .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: updating OpenNI Debian packages
On 06/18/2013 09:56 PM, Thomas Moulard wrote: > On Wed, May 22, 2013 at 5:03 AM, Hans-Christoph Steiner wrote: >> On 05/20/2013 03:18 PM, Jochen Sprickerhof wrote: >> I just updated primesense-nite-nonfree to the latest version and updated the >> packaging. I'm out of time on this sprint. It would be great if people >> could test it and then also contribute any relevant things from the [1] >> above repo to it. Its part of pkg-multimedia, so y'all should have commit >> access to it. >> >> http://git.debian.org/?p=pkg-multimedia/primesense-nite-nonfree.git > Dear Hans-Christoph, > it just occurred to me than primesense-nite-nonfree is depending on > libopenni-dev [1] > > "Depends: debconf | debconf-2.0, dpkg-dev, devscripts, wget, unzip, > gnupg, libopenni-dev, openni-utils" > > Should someone upload openni too? Is the package ready for inclusion? > > [1] http://ftp-master.debian.org/new/primesense-nite-nonfree_0.1.html > > Best, The dependencies were uploaded and rejected. Jochen has fixed the issues, and I just need to find the time to upload the new versions. .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: updating OpenNI Debian packages
On 05/20/2013 03:18 PM, Jochen Sprickerhof wrote: > * Hans-Christoph Steiner [2013-05-20 14:44]: >> Ok, I uploaded openni-sensor-primesense and osceleton to Debian just now. > Awesome, thanks! > >> What about primesense-nite-nonfree? Is there an updated version of that? Is >> that still needed? > I don't use it, so I haven't looked into packaging it. Still it would be > great to have as it's used in ROS, for example. The sources to that > version is at [1], but I guess the version in the Debian git is superior > already. Would be great if someone could finish it. > > Cheers Jochen > > [1] http://kforge.ros.org/openni/drivers I just updated primesense-nite-nonfree to the latest version and updated the packaging. I'm out of time on this sprint. It would be great if people could test it and then also contribute any relevant things from the [1] above repo to it. Its part of pkg-multimedia, so y'all should have commit access to it. http://git.debian.org/?p=pkg-multimedia/primesense-nite-nonfree.git .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: updating OpenNI Debian packages
On 05/21/2013 09:13 AM, Jochen Sprickerhof wrote: > * Hans-Christoph Steiner [2013-05-20 16:06]: >> How about openni-sensor-avin2-sensorkinect? Is that still relevant? > > No, it's all integrated into openni-sensor-primesense, so it's working > with the original Primesense and the Kinect. > >> Have any of these patches been submitted upstream? Things like >> 0013-Add-SONAME-to-libraries.patch should really be included upstream. > > I've send a mail to Ziv Hendel who seems to be responsible for the > software. Not sure if he will include it, as the last release is a year > old and there is OpenNI2 on the way. Btw. Hauke Wintjen is working on > Debian packages of that one [1]. I briefly talked with them in the past, and outlined the SONAME stuff that they needed to include. I guess it never happened. It'd save the packagers a lot of work if this stuff can be included upstream, so its worth revisiting in openni2 > I've just seen that I did it wrong with the openni-sensor-primesense. > 5.1.2.1-2 is still broken, so could you probably move it back to > 5.1.0.41? I'm really sorry for the trouble. I've run out of time in this sprint, but don't fret. We'll wait and see if this goes thru, and take it from there. .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: updating OpenNI Debian packages
On 05/20/2013 03:18 PM, Jochen Sprickerhof wrote: > * Hans-Christoph Steiner [2013-05-20 14:44]: >> Ok, I uploaded openni-sensor-primesense and osceleton to Debian just now. > Awesome, thanks! > >> What about primesense-nite-nonfree? Is there an updated version of that? Is >> that still needed? > I don't use it, so I haven't looked into packaging it. Still it would be > great to have as it's used in ROS, for example. The sources to that > version is at [1], but I guess the version in the Debian git is superior > already. Would be great if someone could finish it. > > Cheers Jochen > > [1] http://kforge.ros.org/openni/drivers How about openni-sensor-avin2-sensorkinect? Is that still relevant? Have any of these patches been submitted upstream? Things like 0013-Add-SONAME-to-libraries.patch should really be included upstream. .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: updating OpenNI Debian packages
On 05/20/2013 12:51 PM, Jochen Sprickerhof wrote: > * Hans-Christoph Steiner [2013-05-20 12:49]: >> I just built openni-sensor-primesense and I got this lintian warning: >> >> W: libopenni-sensor-primesense1: package-name-doesnt-match-sonames libXnCore1 >> libXnDDK1 libXnDeviceFile1 libXnDeviceSensorV2-1 libXnFormats1 >> >> I want to add a lintian override for this, so I want to document the >> rationale. Are those libraries basically just serving like plugins to >> openni? > Right, they are registered in libopenni-sensor-primesense0.postinst and > get loaded through dlopen. Ok, I uploaded openni-sensor-primesense and osceleton to Debian just now. What about primesense-nite-nonfree? Is there an updated version of that? Is that still needed? .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: git-packaging workflows
On 04/06/2013 03:32 AM, Reinhard Tartler wrote: > Hi, > > Recently, Russ' blog post was echoed on http://planet.debian.org: > > http://www.eyrie.org/~eagle/journal/2013-04/001.html > > In that post, he describes how to combine both the "import tarball" > and the "have upstream history" available in the upstream packaging > branch. AFAIUI, the heavy work is implemented in git-buildpackage's > --upstream-vcs-tag option. > > While that option is news to me, I wonder if maybe anyone else already > experiments with this? Does the team feel that making it mandatory for > our package would be beneficial and appropriate? > It sounds very promising, but I think its too soon to mandate it. I think people should all try it and then report back on experience with it. If no one hits major hurdles, then mandate it. I'm going to try my first package in this style: http://anonscm.debian.org/gitweb/?p=collab-maint/python-qrcode.git .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: updating OpenNI Debian packages
On 07/02/2012 10:43 AM, Hans-Christoph Steiner wrote: > On Jul 2, 2012, at 8:37 AM, Jochen Sprickerhof wrote: > >> * Hans-Christoph Steiner [2012-06-29 11:58]: >>> Hey, >> Hi Hans-Christoph, >> >>> This is great news! I'm also CCing the others who have contributed to the >>> current packages. I have little time to work on the OpenNI stuff these >>> days, but I can support you working on it as much as possible. And I'm a >>> Debian Developer, so I can sponsor and upload it once its ready. >> Great, I've been mailing with Stephen already to get this one into >> Debian finally. According to [1] there are still some things to sort >> out: >> - Did anyone mail upstream regarding the soname already? > I did email with them on the openni-dev list and they said they'd look into > it, but I haven't checked back. Here's my emails: > > https://groups.google.com/forum/#!msg/openni-dev/GPwUZEueIPA/SoUCATOmVbQJ > > http://openni-discussions.979934.n3.nabble.com/OpenNI-dev-packages-for-Mac-OS-X-Fink-and-Debian-Ubuntu-Mint-td3673546.html > >> - I really like your way for fink to package both sensor drivers with >> proper names. At the moment we have avin2 imported as >> primesense-kinect-sensor should we change that? > Sounds good to me. > > >> [1] >> http://lists.alioth.debian.org/pipermail/pkg-multimedia-maintainers/2011-June/019178.html >> >>> As for getting access to the git, I think the best route for now is if you >>> clone those repos and then post your work to sourceforge, github, or >>> whatever public git host. Then I can review the stuff there and include it >>> into the official repo. >> Could you import the new upstream versions into the Debian git, so >> Stephen and me only have to provide small patches? >> >> Cheers Jochen > Yes, will do. Ok, I renamed the avin2 package and added the official sensor package: http://anonscm.debian.org/gitweb/?p=pkg-multimedia/openni-sensor-avin2-sensorkinect.git http://anonscm.debian.org/gitweb/?p=pkg-multimedia/openni-sensor-primesense.git I updated the 'pristine-tar' and 'upstream' branches on openni: http://anonscm.debian.org/gitweb/?p=pkg-multimedia/openni.git I left primesense-nite-nonfree as is because as far as I know it doesn't have an 'upstream' branch since it downloads the binary tarball. Should be ready for people to hack on, let me know if I missed something. .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: updating OpenNI Debian packages
On Jul 2, 2012, at 8:37 AM, Jochen Sprickerhof wrote: > * Hans-Christoph Steiner [2012-06-29 11:58]: >> Hey, > > Hi Hans-Christoph, > >> This is great news! I'm also CCing the others who have contributed to the >> current packages. I have little time to work on the OpenNI stuff these >> days, but I can support you working on it as much as possible. And I'm a >> Debian Developer, so I can sponsor and upload it once its ready. > > Great, I've been mailing with Stephen already to get this one into > Debian finally. According to [1] there are still some things to sort > out: > - Did anyone mail upstream regarding the soname already? I did email with them on the openni-dev list and they said they'd look into it, but I haven't checked back. Here's my emails: https://groups.google.com/forum/#!msg/openni-dev/GPwUZEueIPA/SoUCATOmVbQJ http://openni-discussions.979934.n3.nabble.com/OpenNI-dev-packages-for-Mac-OS-X-Fink-and-Debian-Ubuntu-Mint-td3673546.html > - I really like your way for fink to package both sensor drivers with > proper names. At the moment we have avin2 imported as > primesense-kinect-sensor should we change that? Sounds good to me. > [1] > http://lists.alioth.debian.org/pipermail/pkg-multimedia-maintainers/2011-June/019178.html > >> As for getting access to the git, I think the best route for now is if you >> clone those repos and then post your work to sourceforge, github, or >> whatever public git host. Then I can review the stuff there and include it >> into the official repo. > > Could you import the new upstream versions into the Debian git, so > Stephen and me only have to provide small patches? > > Cheers Jochen Yes, will do. .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
new DD on the team
Hey all, I'm now officially a DD with upload privileges! I just tried them out, uploading two simple packages that I had sitting around ready to go. Thanks all for your help getting me there. I have a little bit of time to do some uploads if there is anything urgent that needs to make it into Wheezy before the freeze. .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: debian-multimedia.org considered harmful - redux
On May 3, 2012, at 9:24 AM, Stefano Zacchiroli wrote:
> On Thu, Apr 12, 2012 at 02:26:27PM +0200, Stefano Zacchiroli wrote:
>> I've drafted a message that I'd like to send to Christian publicly
>> Cc:-ing this list. It is attached to this mail for review by the
>> pkg-multimedia team. (Yes, I know this is a public list and Christian
>> will likely read it before the review, but I don't particularly mind: it
>> will just anticipate a public discussion we'd like to have anyhow.)
>>
>> I'd appreciate your feedback on it.
>
> I've now patched my first draft trying to take into account your
> feedback without changing the substance of the message I think we should
> send through. The new draft is attached.
>
> You're feedback is, again, very welcome.
> If you have no further changes to suggest or objections, I can send it
> this week-end.
>
> Either way, please let me know,
> Cheers.
> --
> Stefano Zacchiroli zack@{upsilon.cc,pps.jussieu.fr,debian.org} . o .
> Maître de conférences .. http://upsilon.cc/zack .. . . o
> Debian Project Leader... @zack on identi.ca ...o o o
> « the first rule of tautology club is the first rule of tautology club »
>
> From: Stefano Zacchiroli
> Date: May 3, 2012 9:22:49 AM EDT
> To: Christian Marillat , maril...@free.fr
> Cc: pkg-multimedia-maintainers@lists.alioth.debian.org
> Bcc: lea...@debian.org
> Subject: on package duplication between Debian and debian-multimedia
>
>
> Dear Christian,
> as you probably are aware of, there are recurring discussions on the
> package duplication between the official Debian archive and the
> debian-multimedia.org ("d-m.o" from now on) that you maintain.
>
> AFAIK, the Debian team in charge of maintaining multimedia packages
> (that I'm Cc:-ing) is not happy about the duplication and has approached
> you about that [1], providing some evidence of the troubles that it
> causes to them and to Debian users that also happen to use d-m.o. OTOH
> I'm sure you are maintaining d-m.o to provide a useful service to Debian
> users, when some of the packages you distribute are not available in
> Debian proper.
>
> [1]
> http://lists.alioth.debian.org/pipermail/pkg-multimedia-maintainers/2012-March/025498.html
>
> Personally, I think that principle is fine, but I'm worried about the
> duplication part. Not only due to the troubles that it might cause to
> users, but also for the apparent waste of maintenance energies. Energies
> that could be put into better use if you and the pkg-multimedia team
> could find a way to collaborate, and to do so contributing to the
> *official* Debian packaging of the concerned software.
>
> I have no specific opinion on the technical claims that d-m.o causes
> trouble to official Debian packages. That might be true or not. Ditto
> for your allegations of conflict of interest in the maintenance of
> ffmpeg or libav in Debian. But I observe that *in* Debian we do have
> mechanisms to solve that kind of issues, if and when they arise. As long
> as you keep on doing your work outside Debian instead of raising your
> concerns within Debian, we'll have to keep on assuming that what is
> being done in Debian is fine and is entitled to the official status that
> come with the name "Debian".
>
> Thinking about it, I think we should choose one of the two possible way
> forward:
>
> 1) You and the pkg-multimedia team reach an agreement on
> which-packages-belong-where. One way to settle would be that for
> every package that exist in the official Debian archive, the same
> package should not exist in d-m.o, unless it has a version that does
> not interfere with the official packages in "standard" Debian
> installations. Another way would be to rename packages and sonames.
>
> I understand that such agreements would give a sort of "advantage" to
> the pkg-multimedia people over d-m.o, but that seems to be warranted
> by the fact that they are doing the official packaging, while you're
> not. If, as I hope, you could start doing your packaging work
> (wherever possible) within Debian as well, things would be different
> and we could consider solving potential technical conflicts in the
> usual Debian way.
>
> 2) You stop using "debian" as part of the domain name of your
> repository, which is confusing for users (e.g. [2,3]). That would
> allow each part to keep on doing what they want in terms of
> packaging, but at least would remove any of the existings doubts
> about the official status of d-m.o.
>
> [2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=660924#20
> [3] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668308#47
>
> I can imagine that would be a painful step for you to take, given the
> well established domain name. But it seems fair to ask you to do so
> if we couldn't manage to find an agreement between you and the
> official Debian packaging initiative of software you're maintaining
> in an unofficial repositor
Re: Helping with Maintenance of Packages in Debian
On Apr 28, 2012, at 3:25 AM, Reinhard Tartler wrote: > On Sat, Apr 28, 2012 at 3:08 AM, Hans-Christoph Steiner wrote: >> >> On Apr 26, 2012, at 3:31 PM, Reinhard Tartler wrote: >> >>> On Thu, Apr 26, 2012 at 6:18 PM, Hans-Christoph Steiner >>> wrote: >>>> ffmpeg provides many things that >>>> libav does not. For example, I have written an audio redaction plugin for >>>> ffmpeg. Such a plugin is not possible in libav. >>> >>> Please elaborate. What makes this impossible. Maybe you can point to >>> your plugin? >> >> From what I can tell, they improved the audio plugin API in ffmpeg 0.9 quite >> a bit. When I was programming my plugin, I looked at both libav and ffmpeg. >> It wasn't until I looked at ffmpeg 0.9 that it seemed feasible. I attached >> my plugin source code: > > Oh, you're talking about libavfilter. Well, so far there is not a > single application in debian that uses it, so it clearly wasn't a > priority for me. It is true that lavfi has more functionality in > ffmpeg, espc. since stefano has implemented his audio filtering work > only after the split. On the libav side, I'd suggest talking to anton > about this. He is very open and helpful, so why don't you try to catch > him on irc, show him the plugin source code and see if he can port it > to libav's libavfilter? There is indeed at least one application that does use libavfilter, and that is the ffmpeg command line tool. I think that's how most people use the functions in libavfilter. There are going to be differences between ffmpeg and there are going to solid reasons to use one or the other. So it seems futile to me to ask the devs to make them the same thing when the devs just split up over that very issue. I should add, since this came up in the discussion related to debian-multimedia.org, that this discussion about ffmpeg and libav should not be taken to mean that I am arguing against the proposals related to debian-multimedia.org. I have also been burned by debian-multimedia.org package conflicts, and at the same time I think that the debian-multimedia.org packages are a valuable resource. I think it is a good idea to make debian-multimedia.org more distinct from Debian itself, and also, it is a good idea to try to get as much of the debian-multimedia.org packages into Debian as possible. So I support the DPL's statement on that specific topic. .hc "[T]he greatest purveyor of violence in the world today [is] my own government." - Martin Luther King, Jr. ___ 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: Helping with Maintenance of Packages in Debian
On Apr 27, 2012, at 7:21 AM, Fabian Greffrath wrote: > Am 26.04.2012 18:18, schrieb Hans-Christoph Steiner: >> When I read statements like "Uploading ffmpeg would be a bad idea", it >> seems to me that the Debian-multimedia team has taken sides on the >> ffmpeg-libav fork dispute. That is not a position that a Debian team >> should take. Both ffmpeg and libav remain valuable free software that >> people want to use. And if someone is willing to do the work, Debian >> and Debian Multimedia should welcome both ffmpeg and libav. > > I disagree and second Andres' statement that uploading ffmpeg into Debian > *now* in its current state is a bad idea. This is not because ffmpeg is bad > per se - it isn't - it's just that we decided to go the libav route. This > switch is not irrevocable, but so far no general problems have occured with > libav and I think it fits better to Debian's release model. There is simply > no pressing reason to switch back. We do not disagree at all on this point. I'm not saying that we should just upload ffmpeg as is, obviously it would be stupid to upload ffmpeg if it broke things. But we should welcome anyone who wants to do the work to make it possible to install libav and ffmpeg at the same time, or any other reasonable solution. And since this is a very political issue, we do need to speak carefully and clearly. That's why I object to the statement "Uploading ffmpeg would be a bad idea". It is very broad, and wrong from some legitimate Debian-specific points of view. > Furthermore, currently libav and ffmpeg share the same library name space > without being binary compatible - they are just not drop-in replacements for > each other. This is also the reason for most of the bug reports we receive > from users, who mixed up Debian packages built against libav with ffmpeg > libraries from d-m.o. >From what I know, this really seems to me a question for libav itself. IMHO, >it is a version of the code with a new name, so that seems that the burden >falls on libav to do it. And for the record, I have zero interest in getting >involved in the politics, and I don't even want to know what happened to cause >the libav fork. I am just offering a Debian user's perspective on two pieces >of valuable software that have some technical conflicts. > If we would re-introduce ffmpeg into Debian now, alongside libav, we'd have > two choices. Either we get ffmpeg and libav binary-compatible and sustain > this compatibility for all subsequent releases. Or we can live with the > incompatibility, but then we sould have to rename the libraries of one of the > projects and have to build each and every depending package twice, once > against libav and once against ffmpeg - with appropriate package dependency > declarations and migration plans. > > Do you think any of these alternatives is worth the effort? I don't! I'm specifically interested in the ffmpeg command line util, I don't really need all the libraries. That wouldn't be hard to package. As for libraries, how about putting the ffmpeg versions into /usr/include/ffmpeg and /usr/lib/ffmpeg? Then if someone wants to build against them, they can add -I/usr/include/ffmpeg and -L/usr/lib/ffmpeg. For most projects that use the libav* libraries, there probably wouldn't be any difference between using the ffmpeg or libav versions, so it would be silly to make all packages for both. And of course, I'm not telling anyone that they should do the work here. I am saying we should welcome anyone who wants to do it. Oops, I guess I already said that ;) .hc All mankind is of one author, and is one volume; when one man dies, one chapter is not torn out of the book, but translated into a better language; and every chapter must be so translated -John Donne ___ 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: Helping with Maintenance of Packages in Debian
On Apr 26, 2012, at 3:31 PM, Reinhard Tartler wrote: > On Thu, Apr 26, 2012 at 6:18 PM, Hans-Christoph Steiner wrote: >> ffmpeg provides many things that >> libav does not. For example, I have written an audio redaction plugin for >> ffmpeg. Such a plugin is not possible in libav. > > Please elaborate. What makes this impossible. Maybe you can point to > your plugin? From what I can tell, they improved the audio plugin API in ffmpeg 0.9 quite a bit. When I was programming my plugin, I looked at both libav and ffmpeg. It wasn't until I looked at ffmpeg 0.9 that it seemed feasible. I attached my plugin source code: af_aredact.c Description: Binary data .hc “We must become the change we want to see. - Mahatma Gandhi ___ 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: Helping with Maintenance of Packages in Debian
On Mar 28, 2012, at 1:09 PM, Andres Mejia wrote: > On Mar 28, 2012 2:14 AM, "Christian Marillat" wrote: > > > > Andres Mejia writes: > > > > > Hi Christian, > > > So I'll ask one more time and if the answer is no (or you don't > > > respond), I won't bother you anymore. For the packages in DMO that can > > > now be uploaded to Debian, will you be willing to help upload and > > > maintain those packages in Debian? > > > > I can upload ffmpeg in Debian ? > > > > Christian > > > > Uploading ffmpeg would be a bad idea. Aside from the package name conflicts, > libav and ffmpeg are incompatible with each other. Trying to keep them > abi/api compatible would be a lot of work, more than what I have time for at > least. If you want to upload ffmpeg and still have them compatible, feel free > to submit your patches to libav/ffmpeg. Another alternative is to have the > libraries renamed, of which case you will still need to submit patches > upstream > Since this whole ffmpeg-libav thing is a sensitive issue, I think we need to treat lightly, and be extra clear. I strongly disagree that uploading ffmpeg into Debian is a bad idea. It may be difficult to handle both ffmpeg and libav, but that is a separate question. ffmpeg provides many things that libav does not. For example, I have written an audio redaction plugin for ffmpeg. Such a plugin is not possible in libav. When I read statements like "Uploading ffmpeg would be a bad idea", it seems to me that the Debian-multimedia team has taken sides on the ffmpeg-libav fork dispute. That is not a position that a Debian team should take. Both ffmpeg and libav remain valuable free software that people want to use. And if someone is willing to do the work, Debian and Debian Multimedia should welcome both ffmpeg and libav. .hc Access to computers should be unlimited and total. - the hacker ethic ___ 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 debian package updates?
Ok, I've just had to dive deep into this stuff again, but sadly this time on Mac OS X. The good news is that almost all of this experience will be easy to apply to the Debian packages. Indeed, I was packaging for Fink which uses a lot of Debian tools and even .deb packages. Here are the sources: http://fink.cvs.sourceforge.net/fink/dists/10.4/stable/main/finkinfo/libs/openni.info?view=markup http://fink.cvs.sourceforge.net/fink/dists/10.4/stable/main/finkinfo/libs/openni-sensor-primesense.info?view=markup http://fink.cvs.sourceforge.net/fink/dists/10.4/stable/main/finkinfo/libs/openni-sensor-avin2-sensorkinect.info?view=markup http://fink.cvs.sourceforge.net/fink/dists/10.4/stable/main/finkinfo/libs/primesense-nite.info?view=markup One thing I did to is change the 'sensor' package names, I propose using these names: openni-sensor-primesense.info (for OpenNI PrimeSense Sensor driver) openni-sensor-avin2-sensorkinect (for avin2's SensorKinect fork) If anyone can take on applying this stuff to the Debian packaging, I'll help out where I can. If not, I'll try to get to it when I can. .hc On Dec 9, 2011, at 1:55 PM, Dan wrote: > hi hans, > > I have had the latest unstable NITE middleware and openni working with avin2 > sensor on kinect by hacking your packges but have not yet had a chance to > investigate howto automate the download process with the new website layout. > > They have also changed some of the paths and bits in the build process. Linux > vs linux-x86 paths etc. Not sure if anything i have is very useful atm. > > Maybe ill find a spare moment to investigate getting the midleware without a > browser at some point over the weekend and get it working. > > - Original message - >> >> I was just looking into the OpenNI/PrimeSense updates. There are new >> source releases, and they've changed the URL and the binary layout of >> the NITE middleware. Has anyone got this stuff working or made any >> recent updates on this? It would be great if we could get the packages >> working again with the newest releases. >> >> .hc >> >> >> >> >> ¡El pueblo unido jamás será vencido! >> >> > > > ___ > pkg-multimedia-maintainers mailing list > pkg-multimedia-maintainers@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers Programs should be written for people to read, and only incidentally for machines to execute. - from Structure and Interpretation of Computer Programs ___ 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: advocate for becoming DD
Woo hoo! Back on the road to becoming a DD, thanks Felipe! .hc On Jan 15, 2012, at 2:48 PM, Felipe Sateler wrote: > I have just advocated you. > > > Cheers > > On Thu, Jan 12, 2012 at 16:54, Hans-Christoph Steiner wrote: >> >> A month later and resounding silence, either everyone thinks I'm unworthy of >> becoming a DD or ...? Even a negative response would be better than silence >> :) I also asked on Debian-NYC, the crew that I worked with to put on >> Debconf-NYC, and got the same silence, so I'm not really sure what to do >> next. >> >> .hc >> >> On Dec 9, 2011, at 1:50 PM, Hans-Christoph Steiner wrote: >> >>> >>> Hey all, >>> >>> Now that I've been a DM for at over 6 months, I'm thinking I'm ready to >>> take the final step and become a full DD. Then not only will I no longer >>> need to bother y'all with my upload requests, but then I can also handle >>> the upload requests of others! Here are the 34 packages I am one of the >>> maintainers on, plus the 9 that are in the works: >>> >>> http://qa.debian.org/developer.php?login=hans%40eds.org >>> >>> My name is registered in the system if you are ready to advocate: >>> https://nm.debian.org/nmadvocate.php?email=hans%40eds.org >>> >>> .hc >>> >>> >>> >>> "[W]e have invented the technology to eliminate scarcity, but we are >>> deliberately throwing it away to benefit those who profit from scarcity." >>> -John Gilmore >>> >>> >> >> >> >> >> >> If nature has made any one thing less susceptible than all others of >> exclusive property, it is the action of the thinking power called an idea, >> which an individual may exclusively possess as long as he keeps it to >> himself; but the moment it is divulged, it forces itself into the possession >> of everyone, and the receiver cannot dispossess himself of it.- >> Thomas Jefferson >> >> >> >> ___ >> pkg-multimedia-maintainers mailing list >> pkg-multimedia-maintainers@lists.alioth.debian.org >> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers > > > > -- > > Saludos, > Felipe Sateler I spent 33 years and four months in active military service and during that period I spent most of my time as a high class muscle man for Big Business, for Wall Street and the bankers. - General Smedley Butler ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#649891: how does it work in 64-bit?
Thanks for the bug report and patch, I'm also upstream on this, so I can get it in there. One question: I noticed that epsilon is 1e-9 as a float. We're in the process of porting all Pd libraries to support a 64-bit t_float and t_sample. The 'vbap' library is not there yet, but we hope to get it there. Does the value of epsilon need to be different when t_float is 64-bit double precision? Is it possible to make eplison work for both t_float/t_sample as single and double precision? ___ 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: advocate for becoming DD
A month later and resounding silence, either everyone thinks I'm unworthy of becoming a DD or ...? Even a negative response would be better than silence :) I also asked on Debian-NYC, the crew that I worked with to put on Debconf-NYC, and got the same silence, so I'm not really sure what to do next. .hc On Dec 9, 2011, at 1:50 PM, Hans-Christoph Steiner wrote: > > Hey all, > > Now that I've been a DM for at over 6 months, I'm thinking I'm ready to take > the final step and become a full DD. Then not only will I no longer need to > bother y'all with my upload requests, but then I can also handle the upload > requests of others! Here are the 34 packages I am one of the maintainers on, > plus the 9 that are in the works: > > http://qa.debian.org/developer.php?login=hans%40eds.org > > My name is registered in the system if you are ready to advocate: > https://nm.debian.org/nmadvocate.php?email=hans%40eds.org > > .hc > > > > "[W]e have invented the technology to eliminate scarcity, but we are > deliberately throwing it away to benefit those who profit from scarcity." >-John Gilmore > > If nature has made any one thing less susceptible than all others of exclusive property, it is the action of the thinking power called an idea, which an individual may exclusively possess as long as he keeps it to himself; but the moment it is divulged, it forces itself into the possession of everyone, and the receiver cannot dispossess himself of it.- Thomas Jefferson ___ 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: Bug#654984: libav: Please use a less confusing package name
On Jan 10, 2012, at 7:19 PM, Carl Eugen Hoyos wrote: > Reinhard Tartler gmail.com> writes: > >> I'm not really convinced by 'avtools' and 'avutils', as both seem >> pretty generic to me. 'libav' was chosen to follow the name change of >> the project 'ffmpeg'->'libav'. > > To clarify: > There was no name change, the FFmpeg project is active with no name change at > http://ffmpeg.org > libav is just one of several FFmpeg forks, all forks share several security > issues and many known bugs and regressions not present in FFmpeg, see the > FFmpeg > bug tracker for details > > Carl Eugen How about we keep this fight out of Debian? It seems clear that the place for libav bug reports would be the libav bug tracker. It also seems clear libav is an ffmpeg fork, and ffmpeg is also alive as a project. Its certainly not the first time such a thing has happened in the world of free software. I think there should also be room for someone to package ffmpeg for Debian if they wanted to since it provides different things than libav. I see no reason for Debian policy to dictate that ffmpeg not be allowed in Debian, please illuminate me if you believe otherwise. I do fear that useful software (ffmpeg in this case) will be prevented from inclusion in Debian. .hc "A cellphone to me is just an opportunity to be irritated wherever you are." - Linus Torvalds ___ 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: upload request: pd-mapping
I should add, this was all bundled up for uploading, and I even dput'ed it, but it was rejected since DM-Upload-Allowed isn't set already. I had tagged the release in git, but have deleted the tag for whomever might upload it. Or I can tag it once its uploaded. .hc On Dec 30, 2011, at 9:52 AM, Hans-Christoph Steiner wrote: > > I am trying to get pd-hid into Debian/testing and also Ubuntu by getting > it in before the Ubuntu Debian Import deadline. This update of > pd-mapping (0.2-2) is the last step, but I don't yet had upload > priviledges for it. Its all ready for upload, hopefully someone can > upload it in the next day or two so it makes it into testing in time. > > .hc "We have nothing to fear from love and commitment." - New York Senator Diane Savino, trying to convince the NY Senate to pass a gay marriage bill ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
upload request: pd-mapping
I am trying to get pd-hid into Debian/testing and also Ubuntu by getting it in before the Ubuntu Debian Import deadline. This update of pd-mapping (0.2-2) is the last step, but I don't yet had upload priviledges for it. Its all ready for upload, hopefully someone can upload it in the next day or two so it makes it into testing in time. .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
advocate for becoming DD
Hey all, Now that I've been a DM for at over 6 months, I'm thinking I'm ready to take the final step and become a full DD. Then not only will I no longer need to bother y'all with my upload requests, but then I can also handle the upload requests of others! Here are the 34 packages I am one of the maintainers on, plus the 9 that are in the works: http://qa.debian.org/developer.php?login=hans%40eds.org My name is registered in the system if you are ready to advocate: https://nm.debian.org/nmadvocate.php?email=hans%40eds.org .hc "[W]e have invented the technology to eliminate scarcity, but we are deliberately throwing it away to benefit those who profit from scarcity." -John Gilmore ___ 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 debian package updates?
I was just looking into the OpenNI/PrimeSense updates. There are new source releases, and they've changed the URL and the binary layout of the NITE middleware. Has anyone got this stuff working or made any recent updates on this? It would be great if we could get the packages working again with the newest releases. .hc ¡El pueblo unido jamás será vencido! ___ 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: request sponsor for / upload of pd-pdstring
On Nov 29, 2011, at 6:00 PM, Felipe Sateler wrote: > On Fri, Nov 11, 2011 at 04:53, Roman Haefeli wrote: >> >> If time allows, > > Finally some time... :/ > >> could you also have a look at pd-pdstring? It's been >> waiting for some time and I have ironed out all issues that were >> discussed on this list. > > As discussed in another thread, the autotools stuff need not be > documented in the copyright file, and is just unnecessary noise. > > > BTW, I still find it weird that we need to issue weird commands in pd > to load distro-provided externals. Can someone please explain to me > the rationale for such a requirement? Most programming languages do this: Java: import java.io.File Python: import sys C: #include and so many more. .hc Access to computers should be unlimited and total. - the hacker ethic ___ 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 packages in eighthave repo
Hmm, that's a new development. I wonder if this package should blacklist that kernel module... .hc On Oct 21, 2011, at 12:45 PM, Daniel Squires wrote: The version that the original package built is not available for download on the openni.org site anymore so i will have to make the builder work for the later release. Will let you know if i manage that. I found the reason for the kinect not working is the gspca_kinect kernel module! Unload that and it works as expected. On Thursday 20 October 2011 12:52:55 you wrote: If you can post a fix to this, I'll include it in the git repo and post some updated packages on launchpad. .hc On Oct 20, 2011, at 12:22 PM, Daniel Squires wrote: Oops, Eleanor is my wife,I replied using her old email profile, sorry about that. I got it installing ok, now trying to work out why client apps wont work, just gives me an error something like "initfromxml failed" and something to do with usb. I don't have exact error to hand right now. Thanks Dan On Thursday 20 October 2011 12:01:51 you wrote: Daniel, Looks like Eleanor found the answer. So the thing to do is change the download URL in the script in that package. .hc On Oct 20, 2011, at 11:47 AM, Eleanor Blackmore wrote: Looks like the real problem is that the download site has been changed, so wget is retrieving a html doc. I still had the 1.3.1.5 Nite Binary knocking about and hacked the update- primesense-nite-nonfree script to use it instead, then it built a .deb which i can install :) On Wednesday 19 October 2011 12:17:03 you wrote: That .deb is generated by the installing of openni-module- primesense- nite-nonfree, it downloads the non-free binaries and makes a deb out of it. I'm on a 32-bit system, it works for me. But I think the author of that package is on 64-bit. I cc'ed the pkg-multimedia team to see if anyone can help on 64- bit. Can you post the whole log of your apt-get install session somewhere? .hc On Oct 19, 2011, at 5:50 AM, Daniel Squires wrote: Hi, I am trying to use the packages from your eighthave repo on Ubuntu oneiric, I found the wiki at @ http://wiki.debian.org/PrimeSenseNite#Installation But the .deb it refers to ( /var/cache/primesense-nite-nonfree/ openni- module-primesense-nite-nonfree_1.3.1.5-1_i386.deb) does not exist on my system. It is an amd64 install and wonder if this is why? The only file that does exist there is /var/cache/primesense-nite- nonfree/primesense-nite.tar.gz which actually just seems to be an html doc of the openni homepage! indeed dpkg -L openni-module-primesense-nite-nonfree makes no mention of the .deb file. Any help much appreciated. Thanks Dan -- -- All mankind is of one author, and is one volume; when one man dies, one chapter is not torn out of the book, but translated into a better language; and every chapter must be so translated -John Donne -- -- All mankind is of one author, and is one volume; when one man dies, one chapter is not torn out of the book, but translated into a better language; and every chapter must be so translated -John Donne The arc of history bends towards justice. - Dr. Martin Luther King, Jr. "[T]he greatest purveyor of violence in the world today [is] my own government." - Martin Luther King, Jr. ___ 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 packages in eighthave repo
If you can post a fix to this, I'll include it in the git repo and post some updated packages on launchpad. .hc On Oct 20, 2011, at 12:22 PM, Daniel Squires wrote: Oops, Eleanor is my wife,I replied using her old email profile, sorry about that. I got it installing ok, now trying to work out why client apps wont work, just gives me an error something like "initfromxml failed" and something to do with usb. I don't have exact error to hand right now. Thanks Dan On Thursday 20 October 2011 12:01:51 you wrote: Daniel, Looks like Eleanor found the answer. So the thing to do is change the download URL in the script in that package. .hc On Oct 20, 2011, at 11:47 AM, Eleanor Blackmore wrote: Looks like the real problem is that the download site has been changed, so wget is retrieving a html doc. I still had the 1.3.1.5 Nite Binary knocking about and hacked the update- primesense-nite-nonfree script to use it instead, then it built a .deb which i can install :) On Wednesday 19 October 2011 12:17:03 you wrote: That .deb is generated by the installing of openni-module- primesense- nite-nonfree, it downloads the non-free binaries and makes a deb out of it. I'm on a 32-bit system, it works for me. But I think the author of that package is on 64-bit. I cc'ed the pkg-multimedia team to see if anyone can help on 64- bit. Can you post the whole log of your apt-get install session somewhere? .hc On Oct 19, 2011, at 5:50 AM, Daniel Squires wrote: Hi, I am trying to use the packages from your eighthave repo on Ubuntu oneiric, I found the wiki at @ http://wiki.debian.org/PrimeSenseNite#Installation But the .deb it refers to ( /var/cache/primesense-nite-nonfree/ openni- module-primesense-nite-nonfree_1.3.1.5-1_i386.deb) does not exist on my system. It is an amd64 install and wonder if this is why? The only file that does exist there is /var/cache/primesense-nite- nonfree/primesense-nite.tar.gz which actually just seems to be an html doc of the openni homepage! indeed dpkg -L openni-module-primesense-nite-nonfree makes no mention of the .deb file. Any help much appreciated. Thanks Dan -- -- All mankind is of one author, and is one volume; when one man dies, one chapter is not torn out of the book, but translated into a better language; and every chapter must be so translated -John Donne All mankind is of one author, and is one volume; when one man dies, one chapter is not torn out of the book, but translated into a better language; and every chapter must be so translated -John Donne The arc of history bends towards justice. - Dr. Martin Luther King, Jr. ___ 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 packages in eighthave repo
Daniel, Looks like Eleanor found the answer. So the thing to do is change the download URL in the script in that package. .hc On Oct 20, 2011, at 11:47 AM, Eleanor Blackmore wrote: Looks like the real problem is that the download site has been changed, so wget is retrieving a html doc. I still had the 1.3.1.5 Nite Binary knocking about and hacked the update- primesense-nite-nonfree script to use it instead, then it built a .deb which i can install :) On Wednesday 19 October 2011 12:17:03 you wrote: That .deb is generated by the installing of openni-module-primesense- nite-nonfree, it downloads the non-free binaries and makes a deb out of it. I'm on a 32-bit system, it works for me. But I think the author of that package is on 64-bit. I cc'ed the pkg-multimedia team to see if anyone can help on 64-bit. Can you post the whole log of your apt-get install session somewhere? .hc On Oct 19, 2011, at 5:50 AM, Daniel Squires wrote: Hi, I am trying to use the packages from your eighthave repo on Ubuntu oneiric, I found the wiki at @ http://wiki.debian.org/PrimeSenseNite#Installation But the .deb it refers to ( /var/cache/primesense-nite-nonfree/ openni- module-primesense-nite-nonfree_1.3.1.5-1_i386.deb) does not exist on my system. It is an amd64 install and wonder if this is why? The only file that does exist there is /var/cache/primesense-nite- nonfree/primesense-nite.tar.gz which actually just seems to be an html doc of the openni homepage! indeed dpkg -L openni-module-primesense-nite-nonfree makes no mention of the .deb file. Any help much appreciated. Thanks Dan All mankind is of one author, and is one volume; when one man dies, one chapter is not torn out of the book, but translated into a better language; and every chapter must be so translated -John Donne All mankind is of one author, and is one volume; when one man dies, one chapter is not torn out of the book, but translated into a better language; and every chapter must be so translated -John Donne ___ 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 packages in eighthave repo
That .deb is generated by the installing of openni-module-primesense- nite-nonfree, it downloads the non-free binaries and makes a deb out of it. I'm on a 32-bit system, it works for me. But I think the author of that package is on 64-bit. I cc'ed the pkg-multimedia team to see if anyone can help on 64-bit. Can you post the whole log of your apt-get install session somewhere? .hc On Oct 19, 2011, at 5:50 AM, Daniel Squires wrote: Hi, I am trying to use the packages from your eighthave repo on Ubuntu oneiric, I found the wiki at @ http://wiki.debian.org/PrimeSenseNite#Installation But the .deb it refers to ( /var/cache/primesense-nite-nonfree/openni- module-primesense-nite-nonfree_1.3.1.5-1_i386.deb) does not exist on my system. It is an amd64 install and wonder if this is why? The only file that does exist there is /var/cache/primesense-nite- nonfree/primesense-nite.tar.gz which actually just seems to be an html doc of the openni homepage! indeed dpkg -L openni-module-primesense-nite-nonfree makes no mention of the .deb file. Any help much appreciated. Thanks Dan -- This message was sent from Launchpad by Daniel Squires (https://launchpad.net/~mango-5) using the "Contact this user" link on your profile page (https://launchpad.net/~eighthave). For more information see https://help.launchpad.net/YourAccount/ContactingPeople All mankind is of one author, and is one volume; when one man dies, one chapter is not torn out of the book, but translated into a better language; and every chapter must be so translated -John Donne ___ 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: pd-hid caught in unstable, but why?
FYI, here's the answer from debian-release: On Mon, 2011-10-10 at 22:01 +0100, Adam D. Barratt wrote: > On Mon, 2011-10-10 at 16:43 -0400, Hans-Christoph Steiner wrote: > > I was just checking in on my packages, it seems that pd-hid is caught in > > unstable for 75 days, but I can't figure out what the issue is. The > > error message is "Adding pd-hid makes 1 non-depending packages > > uninstallable on kfreebsd-amd64: pd-hid " > > > > http://release.debian.org/migration/testing.pl?package=pd-hid;expand=1 > > > > But what is that 1 non-depending package? Is it 'puredata (<<0.43)'? > > No, it's pd-hid, as the message you quoted indicates. > > > Other packages with that same Build-Depends are already in testing. > > Also, buildd seems to show it as installed on kFreeBSD: > > That only indicates it builds, not that it's installable. > > edos-debcheck is one method of demonstrating the issue: > > $ edos-debcheck -explain -checkonly pd-hid < Packages_kfreebsd-amd64 > Completing conflicts...* 100.0% > Conflicts and dependencies... * 100.0% > Solving* 100.0% > pd-hid (= 0.7-1): FAILED > pd-hid (= 0.7-1) depends on one of: > - pd-mapping (= 0.2-1) > > $ edos-debcheck -explain -checkonly pd-mapping < Packages_kfreebsd-amd64 > Completing conflicts...* 100.0% > Conflicts and dependencies... * 100.0% > Solving* 100.0% > pd-mapping (= 0.2-1): FAILED > pd-mapping (= 0.2-1) depends on missing: > - pd-cyclone > > $ dak ls pd-cyclone > pd-cyclone | 0.1~alpha55-3 | testing | source, amd64, armel, i386, > ia64, mips, mipsel, powerpc, s390, sparc > pd-cyclone | 0.1~alpha55-3 | unstable | source, amd64, armel, i386, > ia64, mips, mipsel, powerpc, s390, sparc > > Regards, > > Adam > > ___ 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: pd-hid caught in unstable, but why?
On Oct 10, 2011, at 4:23 PM, Felipe Sateler wrote: On Fri, Oct 7, 2011 at 12:00, Hans-Christoph Steiner wrote: I was just checking in on my packages, it seems that pd-hid is caught in unstable for 75 days, but I can't figure out what the issue is. The error message is "Adding pd-hid makes 1 non-depending packages uninstallable on kfreebsd-amd64: pd-hid " http://release.debian.org/migration/testing.pl?package=pd- hid;expand=1 But what is that 1 non-depending package? Is it 'puredata (<<0.43)'? Other packages with that same Build-Depends are already in testing. This looks fishy. You might want to ask on debian-release. Yeah, it does. pd-hid should only depend on Linux's input.h, libc, and puredata. All of those are in kFreeBSD. Thanks, I'll ask there. .hc All mankind is of one author, and is one volume; when one man dies, one chapter is not torn out of the book, but translated into a better language; and every chapter must be so translated -John Donne ___ 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: pd-hid caught in unstable, but why?
On Oct 8, 2011, at 1:15 AM, Simon Wise wrote: On 08/10/11 12:54, Hans-Christoph Steiner wrote: On Oct 7, 2011, at 11:48 PM, Simon Wise wrote: On 07/10/11 23:00, Hans-Christoph Steiner wrote: I was just checking in on my packages, it seems that pd-hid is caught in unstable for 75 days, but I can't figure out what the issue is. The error message is "Adding pd-hid makes 1 non-depending packages uninstallable on kfreebsd-amd64: pd-hid " http://release.debian.org/migration/testing.pl?package=pd-hid;expand=1 But what is that 1 non-depending package? Is it 'puredata (<<0.43)'? Other packages with that same Build-Depends are already in testing. The package is listed as pd-hid itself ... apparently it is not installable on kfreebsd-amd64, that is what is keeping it out of testing That's odd, because buildd seems to show it as installed on kFreeBSD: https://buildd.debian.org/status/package.php?p=pd-hid It says that moving pd-hid to testing prevents pd-hid from installing on testing in kfreebsd-amd64 [and maybe more architectures, only the first found is listed]. Since it IS installed on sid, is there something missing from testing, but present in sid, that pd-hid needs before it can be installed? something that is not listed as a dependency, but should be? Simon pd-hid was written in 2004-2005 and uses the Linux input.h. It's had bug fixes since then, but no major changes. I can't imagine what pd- hid would need that wouldn't be in oldstable, or sarge even. Any ideas on how I can find details on what the issue is? .hc The arc of history bends towards justice. - Dr. Martin Luther King, Jr. ___ 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: pd-hid caught in unstable, but why?
On Oct 7, 2011, at 11:48 PM, Simon Wise wrote: On 07/10/11 23:00, Hans-Christoph Steiner wrote: I was just checking in on my packages, it seems that pd-hid is caught in unstable for 75 days, but I can't figure out what the issue is. The error message is "Adding pd-hid makes 1 non-depending packages uninstallable on kfreebsd-amd64: pd-hid " http://release.debian.org/migration/testing.pl?package=pd- hid;expand=1 But what is that 1 non-depending package? Is it 'puredata (<<0.43)'? Other packages with that same Build-Depends are already in testing. The package is listed as pd-hid itself ... apparently it is not installable on kfreebsd-amd64, that is what is keeping it out of testing That's odd, because buildd seems to show it as installed on kFreeBSD: https://buildd.debian.org/status/package.php?p=pd-hid .hc The arc of history bends towards justice. - Dr. Martin Luther King, Jr. ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
pd-hid caught in unstable, but why?
I was just checking in on my packages, it seems that pd-hid is caught in unstable for 75 days, but I can't figure out what the issue is. The error message is "Adding pd-hid makes 1 non-depending packages uninstallable on kfreebsd-amd64: pd-hid " http://release.debian.org/migration/testing.pl?package=pd-hid;expand=1 But what is that 1 non-depending package? Is it 'puredata (<<0.43)'? Other packages with that same Build-Depends are already in testing. .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: where is Pd's "-stdlib"? (was Re: request sponsor/upload for pd-pdstring)
On Oct 4, 2011, at 5:19 AM, Roman Haefeli wrote: On Mon, 2011-10-03 at 13:06 -0400, Hans-Christoph Steiner wrote: On Oct 3, 2011, at 3:54 AM, IOhannes m zmoelnig wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 @pd-dev: in the course of making packages for debian, we discovered another slight problem with the "-stdpath" and "-stdlib" flags for declare (and probably this also expands to the "-nostdpath" startup flag). following is an excerpt of the discussion in the debian packaging team: On 2011-10-01 14:11, Roman Haefeli wrote: On Fri, 2011-09-30 at 17:02 +0200, IOhannes m zmölnig wrote: i'm not entirely sure though (given the nastiness of [declare]) if you think that it is a bug in "puredata-core", please file a bugreport. Yeah, that is indeed the case. Before filing a bug report, I'd like to clear up the meanings of the different paths. /usr/lib/pd/extra Am I right in assuming that this path is supposed to be searched by all flavors of Pd (all packages that provide the virtual package pd)? This also the path where usually external libraries are installed to because from there they can be loaded from any flavor of pd? /usr/lib/puredata/extra is only searched by puredata / pd from the puredata package? This is where libraries are installed that only are suitable for the pd provided by the puredata package? /usr/lib/pd-extended/extra is only searched by pdextended / pd from the pd-extended package? Libs that are only useful with pdextended go there? If that is the case, then there is definitely a bug in the puredata- core package as it is ignoring /usr/lib/pd/extra. it might as well be a bug in puredata upstream (that's why i want to discuss it; probably a more appropriate place for discussion is the pd-dev mailinglist which i include in the recipients) imho, the issue boils down to the question "what are stdpaths?" (and i assume that "stdlibs" are std because they live in "stdpaths"). for the sake of simplicity, i will only talk about the "linux" version of Pd (and with Pd i mean Pd-vanilla) before Pd-0.43 (vanilla!), there was only a single "stdpath", which was the path were the Pd binaries lived in. this usually was /usr/local/lib/pd/ or /usr/lib/pd/ since 0.43, a few more paths have been added, namely: /usr/local/lib/pd-externals and ~/pd-externals on Debian and derivatives, yet another path is added: since Pd is installed into /usr/lib/puredata/ (in order to allow pd-extended live side by side with puredata), the path "/usr/lib/pd" is also added as a "common system-managed search path". now all these paths are handled separately from the user defined search-paths; e.g. they do not show up in the path dialog, and they can be disabled with the "-nostdpaths" flag. otoh, [declare] has not adapted to these changes. if you add "-stdpath extra/foo", it will only search in /usr/local/lib/pd/extra/foo (given that pd is installed in /usr/local/lib/pd), but it will not search in /usr/local/lib/pd-externals/extra/foo nor in ~/pd-externals/extra/ foo. (the same applies for the additional Debian-specific search path /usr/lib/pd/extra/foo). hence i do think that the problem is general problem with Pd-vanilla (and not specific to Debian; it only shows here) My guess is that [declare] should be adapted to consider as stdpath the same stuff that -nostdpaths does. I agree. I think that the various standard paths shouldn't be treated differently. As a patch creator I don't care whether I installed the foo library in ~/pd-externals or /usr/local/lib/pd/extra, in either case I want to load a library the same way. I believe it makes sense to distinguish only two different scopes here: * system environment _all_ standard paths belong to it and the '-stdpath' and '-stdlib' flags of [declare] should expand all those paths, respectively try to load libraries from those paths. * patch / local environment paths relative to the patch's location. The '-lib' and '-path' flags of [declare] cover those. I can't come up with another meaningful scope. But if there is any, probably new flags for [declare] would be necessary. This also means, that currently all Pd libraries in unstable that install to /usr/lib/pd/extra (most of them do) are currently broken, as there is no proper way to actually load them in pd (you still can specify the absolute path to the library, which renders your patch unportable to other OS'). you could also simply start Pd with "-lib foo" and it will just work. so i wouldn't consider "all broken". obviously, we lack the possibility to express a library dependency within the patch, which is a shame (but which is also due to the current broken implementation of [declare] in general). anyhow, wha
Re: where is Pd's "-stdlib"? (was Re: request sponsor/upload for pd-pdstring)
On Oct 3, 2011, at 3:54 AM, IOhannes m zmoelnig wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 @pd-dev: in the course of making packages for debian, we discovered another slight problem with the "-stdpath" and "-stdlib" flags for declare (and probably this also expands to the "-nostdpath" startup flag). following is an excerpt of the discussion in the debian packaging team: On 2011-10-01 14:11, Roman Haefeli wrote: On Fri, 2011-09-30 at 17:02 +0200, IOhannes m zmölnig wrote: i'm not entirely sure though (given the nastiness of [declare]) if you think that it is a bug in "puredata-core", please file a bugreport. Yeah, that is indeed the case. Before filing a bug report, I'd like to clear up the meanings of the different paths. /usr/lib/pd/extra Am I right in assuming that this path is supposed to be searched by all flavors of Pd (all packages that provide the virtual package pd)? This also the path where usually external libraries are installed to because from there they can be loaded from any flavor of pd? /usr/lib/puredata/extra is only searched by puredata / pd from the puredata package? This is where libraries are installed that only are suitable for the pd provided by the puredata package? /usr/lib/pd-extended/extra is only searched by pdextended / pd from the pd-extended package? Libs that are only useful with pdextended go there? If that is the case, then there is definitely a bug in the puredata- core package as it is ignoring /usr/lib/pd/extra. it might as well be a bug in puredata upstream (that's why i want to discuss it; probably a more appropriate place for discussion is the pd-dev mailinglist which i include in the recipients) imho, the issue boils down to the question "what are stdpaths?" (and i assume that "stdlibs" are std because they live in "stdpaths"). for the sake of simplicity, i will only talk about the "linux" version of Pd (and with Pd i mean Pd-vanilla) before Pd-0.43 (vanilla!), there was only a single "stdpath", which was the path were the Pd binaries lived in. this usually was /usr/local/lib/pd/ or /usr/lib/pd/ since 0.43, a few more paths have been added, namely: /usr/local/lib/pd-externals and ~/pd-externals on Debian and derivatives, yet another path is added: since Pd is installed into /usr/lib/puredata/ (in order to allow pd-extended live side by side with puredata), the path "/usr/lib/pd" is also added as a "common system-managed search path". now all these paths are handled separately from the user defined search-paths; e.g. they do not show up in the path dialog, and they can be disabled with the "-nostdpaths" flag. otoh, [declare] has not adapted to these changes. if you add "-stdpath extra/foo", it will only search in /usr/local/lib/pd/extra/foo (given that pd is installed in /usr/local/lib/pd), but it will not search in /usr/local/lib/pd-externals/extra/foo nor in ~/pd-externals/extra/foo. (the same applies for the additional Debian-specific search path /usr/lib/pd/extra/foo). hence i do think that the problem is general problem with Pd-vanilla (and not specific to Debian; it only shows here) My guess is that [declare] should be adapted to consider as stdpath the same stuff that -nostdpaths does. This also means, that currently all Pd libraries in unstable that install to /usr/lib/pd/extra (most of them do) are currently broken, as there is no proper way to actually load them in pd (you still can specify the absolute path to the library, which renders your patch unportable to other OS'). you could also simply start Pd with "-lib foo" and it will just work. so i wouldn't consider "all broken". obviously, we lack the possibility to express a library dependency within the patch, which is a shame (but which is also due to the current broken implementation of [declare] in general). anyhow, what i'm mainly asking is, whether "std" prefixed declare options and the "std" prefixed cmdline flags are supposed to work on the same "standard". if so, does this mean to be exclusive (e.g. only have the Pd install path) or inclusive (additionally have /usr/local/lib/pd-externals/ and ~/pd-externals/ (and on debian the additional /usr/lib/pd/extra/) i generally tend towards an inclusive solution, though i'm not 100% sure whether this is the user expectancy with regards to ~/pd-externals/ [import foo] will load libraries from all paths, I think. Or at least it should. I never understood [declare]'s -stdpath and -stdlib, that lead to me writing [import]. .hc Terrorism is not an enemy. It cannot be defeated. It's a tactic. It's about as sensible to say we declare war on night attacks and expect we're going to win that war. We're not going to win the war on terrorism.- retired U.S. Army general, William Odom ___ pkg-multimedia-maintainers mailing list
Re: request sponsor/upload for pd-pdstring
I find that Launchpad is a good place to test new packages. I think you have a launchpad account already, so it should be easy. I always upload my packages to my launchpad before submitting them for upload to Debian. So far, I haven't remembered how to use cowbuilder or pbuilder... an uploading to launchpad has stuck. .hc On Oct 1, 2011, at 8:11 AM, Roman Haefeli wrote: Hi again There was some confusion on my part, since I seem to have tested it only in Debian stable where everything works as expected. The puredata package in Debian unstable is quite different from previous versions and also is its behavior. On Fri, 2011-09-30 at 17:02 +0200, IOhannes m zmölnig wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/30/2011 04:19 PM, Roman Haefeli wrote: On Fri, 2011-09-30 at 13:24 +0200, IOhannes m zmölnig wrote: debian/control: any reason why you are so picky about the debhelper version? I'm using short-form dh with dh overrides. Lintian tells me that those features are only available since 7.0.50. I read the thread about thanks for the explanation. debian/README.Debian quite a long line :-) more important, i cannot load pdstring following your advice in README.Debian: [declare -stdlib extra/pdstring] will do nothing (on reload), only [declare -lib pdstring] helps How did you test? The '-lib' flag searches relative to your patch, whereas '-stdlib' searches relative to pd. You only can correctly test it by effectively installing the package and run pd (/usr/bin/pd). my test is to open the attached abstraction with $ puredata -noprefs pdstring-test.pd which gives me: any2string error: ... couldn't create puredata (the 0.43.0-4) finds neither the library nor the abstraction of the name "any2string". the former can be a bug in your documentation (i have to admit that i'm not so familiar with [declare]), as it would look for a library "extra/pdstring" where the pdstring.pd_linux file really is extra/pdstring/pdstring.pd_linux, so it should probably read "-stdlib extra/pdstring/pdstring". '-stdlib extra/pdstring/pdstring' is supposed to work as well but should not be necessary at all. Pd normally checks also folders with the lib name for libs. When specifying mylib, both extra/mylib.pd_linux and extra/mylib/mylib.pd_linux are searched. However, it turned out, that the advice was not complete, since the library also contains abstractions, which are not found with only '-stdlib extra/pdstring'. The full and correct declaration is: [declare -stdlib extra/pdstring -stdpath extra/pdstring] Yeah, that's a lot for loading only a library, but unfortunately that is how it currently works in Pd. after closer inspection it seems like this _might_ be a bug in the "puredata" package, which seems only to consider "/usr/lib/ puredata/" as a stdpath, and it won't search "extra/pdstring" in "/usr/lib/pd". i'm not entirely sure though (given the nastiness of [declare]) if you think that it is a bug in "puredata-core", please file a bugreport. Yeah, that is indeed the case. Before filing a bug report, I'd like to clear up the meanings of the different paths. /usr/lib/pd/extra Am I right in assuming that this path is supposed to be searched by all flavors of Pd (all packages that provide the virtual package pd)? This also the path where usually external libraries are installed to because from there they can be loaded from any flavor of pd? /usr/lib/puredata/extra is only searched by puredata / pd from the puredata package? This is where libraries are installed that only are suitable for the pd provided by the puredata package? /usr/lib/pd-extended/extra is only searched by pdextended / pd from the pd-extended package? Libs that are only useful with pdextended go there? If that is the case, then there is definitely a bug in the puredata- core package as it is ignoring /usr/lib/pd/extra. This also means, that currently all Pd libraries in unstable that install to /usr/lib/pd/extra (most of them do) are currently broken, as there is no proper way to actually load them in pd (you still can specify the absolute path to the library, which renders your patch unportable to other OS'). Roman ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers I spent 33 years and four months in active military service and during that period I spent most of my time as a high class muscle man for Big Business, for Wall Street and the bankers. - General Smedley Butler ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#638239: pd-mjlib: FTBFS on hurd & kfreebsd
This is fixed upstream already in most of these, and will be soon in the rest. Its less than half of the pd-* packages that are effected, according to buildd. The list of affected packages is: pd-bsaylor pd-cxc pd-cyclone pd-ekext pd-ext13 pd-ggee pd-hcs pd- markex pd-maxlib pd-mjlib pd-moonlib pd-pddp pd-sigpack pd-smlib pd- windowing ___ 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: please upload pd-osc
One important upstream detail is that the lib is called 'osc', the folder in SVN is called 'osc', the package is called 'pd-osc', therefore the OSC-meta.pd needs to be osc-meta.pd to match the library and package name. That change is already in the upstream SVN. Also, it'd be good to get a release signed-off by Martin Peach, the upstream author, and to make the release tarball that you posted also match the other names, i.e. osc-0.1.tar.gz rather than OSC-0.1.tar.gz. .hc On Aug 4, 2011, at 10:21 AM, IOhannes m zmoelnig wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 dear fellow pkgers, after debconf i finally found the time to package one of my longstanding ITPs (before it finally expires!): pd-osc pd-osc is a puredata library adding Open Sound Control (OSC) capabilities (at the application layer (OSI-7)) to Pd. It "allows one to construct and parse OSC messages within Pd. It includes support for ordinary OSC-messages, typetags, timetags and bundles. These objects are transport-agnostic, so you can use them to transmit OSC over UDP, TCP/IP, serial port, or in fact whatever you want. However, you will have to install additional libraries that will handle the transport layer (like pd-iemnet or pd-comport)." [1] the package can be found at: git+ssh://git.debian.org/pkg-multimedia/pd-osc http://git.debian.org/?p=pkg-multimedia/pd-osc.git it appears to be lintian clean (there is a single Pedantic warning, about a missing upstream changelog). it builds cleanly in my pbuilder environment. this package uses CDBS (ping jonas!) i would be glad if somebody could review the package and throw some comments at me. if there is somebody willing to upload the package, that would be even nicer :-) @jonas: i shamelessly copied a README.source written by you, which i found in the "scenic" package. it has no built-in copyright notice, so i assumed it is GPL-3+; could you please confirm that? fmgasdr IOhannes [1] that's what it says in debian/control -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk46quYACgkQkX2Xpv6ydvRzyACfRObaaOtt4u/ZqaNki9hhwgdp Ih0AoKcJDquNbzNe/Nl5HEBaOFsFekFV =j3Xp -END PGP 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 'You people have such restrictive dress for women,’ she said, hobbling away in three inch heels and panty hose to finish out another pink- collar temp pool day. - “Hijab Scene #2", by Mohja Kahf ___ 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: lame_3.98.4+repack2-1_amd64.changes ACCEPTED into unstable
On Jul 29, 2011, at 9:25 AM, Romain Beauxis wrote: 2011/7/29 Debian FTP Masters : Accepted: lame-doc_3.98.4+repack2-1_all.deb to main/l/lame/lame-doc_3.98.4+repack2-1_all.deb (...) Guys, I am impressed, really impressed... Thanks you all! Romain Yay! Good work! I'm going to package a pd lib that depends on LAME now :) .hc If nature has made any one thing less susceptible than all others of exclusive property, it is the action of the thinking power called an idea, which an individual may exclusively possess as long as he keeps it to himself; but the moment it is divulged, it forces itself into the possession of everyone, and the receiver cannot dispossess himself of it.- Thomas Jefferson ___ 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: pd-pmpd bugfix: request for upload
On Jul 26, 2011, at 8:38 PM, Felipe Sateler wrote: On Tue, Jul 26, 2011 at 16:16, Hans-Christoph Steiner wrote: There is one more package with the same "fatal error: m_pd.h: No such file or directory (missing B-D on puredata-dev)" bug that needs uploading: pd-pmpd. The changes are all in git and its ready to go. Uploaded. Hans, please fix the dependencies on pd and explicitly state the preferred provider (on this and the other pd-* packages). In the near future, I plan on packaging pdextended, which will also provide pd. If I put the Depends: as 'puredata | pd', and pdextended is already installed, won't apt try to install puredata also? That's what I want to avoid. People should be able to choose puredata or pdextended, then all of the pd-* packages that Depend: on pd should be happy with either. .hc Terrorism is not an enemy. It cannot be defeated. It's a tactic. It's about as sensible to say we declare war on night attacks and expect we're going to win that war. We're not going to win the war on terrorism.- retired U.S. Army general, William Odom ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
pd-pmpd bugfix: request for upload
There is one more package with the same "fatal error: m_pd.h: No such file or directory (missing B-D on puredata-dev)" bug that needs uploading: pd-pmpd. The changes are all in git and its ready to go. .hc "Free software means you control what your computer does. Non-free software means someone else controls that, and to some extent controls you." - Richard M. Stallman ___ 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: request for sponsorship for pd-hid
On Jul 20, 2011, at 11:07 PM, Felipe Sateler wrote: On Sun, Jun 19, 2011 at 23:50, Hans-Christoph Steiner wrote: On Jun 14, 2011, at 12:31 PM, Hans-Christoph Steiner wrote: On Jun 13, 2011, at 8:01 PM, Felipe Sateler wrote: On Mon, Jun 13, 2011 at 14:43, Hans-Christoph Steiner > wrote: On Jun 12, 2011, at 10:53 PM, Felipe Sateler wrote: On Sat, Jun 11, 2011 at 22:15, Hans-Christoph Steiner > wrote: On Sat, 2011-06-11 at 19:30 +, Felipe Sateler wrote: On Sat, Jun 11, 2011 at 02:45, Hans-Christoph Steiner > wrote: On Wed, 09 Feb 2011 17:41 -0300, "Felipe Sateler" wrote: On Mon, Jan 31, 2011 at 21:55, Felipe Sateler > wrote: On Fri, Jan 21, 2011 at 19:08, Felipe Sateler wrote: On Fri, Jan 21, 2011 at 03:37, Hans-Christoph Steiner wrote: On Fri, 24 Dec 2010 15:37 -0800, "Hans-Christoph Steiner" wrote: On Dec 24, 2010, at 9:19 AM, Felipe Sateler wrote: On Wed, Dec 22, 2010 at 21:13, Hans-Christoph Steiner wrote: Just ITPed, packaged and uploaded pd-hid to git.debian.org. It is an object for Pure Data that allows you to use USB HID devices in Pd. The build system is similar in structure to pd-plugin and pd-freeverb, plus it includes the kFreeBSD and Hurd updates, so it should build on all platforms. It depends on pd-mapping and recommends pd-pddp, which are both in NEW. http://git.debian.org/?p=pkg-multimedia/pd-hid.git;a=summary There is some code that is not yours, please add Jan Truetzschler Falkenstein to the debian/copyright file (ftpmaster may reject the package for this missing information). Thanks for spotting that, I pushed the fix. Ping. Anyone willing to sponsor this one? Sorry, I lost track of this. I will try to get to this (and your other packages) during the weekend. I clearly didn't do this when promised, and this week I couldn't either. I've been extremely busy. I'm sorry about that. If someone else can look into these packages, please upload them, since I'm not likely to get any debian time anytime soon. I will, if nobody else gets to these packages, still review them as time permits. It seems that this package never got uploaded. It needs its git-dch done and the changelog finalized and then uploaded. I can finalize the changelog if that makes it easier. It seems some people want to do it themselves when uploading. I believe this package needs to be fixed for puredata >= 0.43 As far as I can tell it has already. For me, it builds on Debian/testing using puredata-dev and no puredata, and squeeze using puredata 0.42.6. Indeed, it seems to work. I have a licensing question though. The package is distributed as GPLv3+. However, Supercollider (where some code was borrowed) is GPLv2+. I think debian/copyright should document that fact. Code from 2004 cannot possibly be under GPLv3+ unless relicensed. The GPLv2+ license has that built into it. In the context of this project, the code from SuperCollider is so intermingled, there is no easily recognizable chunk that could be labeled GPLv2+. Since the project is GPLv3+, I think it would be misleading to try to say that a file is available under GPLv2+. If people want the GPLv2+ file, they should go to the original SuperCollider source. Here's the text from the GPL: "Each version is given a distinguishing version number. If the Program specifies that a certain numbered version of the GNU General Public License "or any later version" applies to it, you have the option of following the terms and conditions either of that numbered version or of any later version published by the Free Software Foundation. " Indeed, I'm not questioning that. My point is that the objective of debian/copyright is documenting, not relicensing, even if it is permissible. From what I've seen, debian/copyright is not finer grained than files. The GPLv2+ code is mixed into two different files that are mostly GPLv3+. So if looking on a per-file basis, all of the files are GPLv3+. .hc Hey Felipe, Any chance of getting this one uploaded in the next week? I'd love to make the Ubuntu/oneiric import deadline. .hc Sorry I'm late. Uploaded. All that matters is that it got done, thanks :) .hc All mankind is of one author, and is one volume; when one man dies, one chapter is not torn out of the book, but translated into a better language; and every chapter must be so translated -John Donne ___ 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: primesense-nite-nonfree should install resulting package?
On Jun 21, 2011, at 5:58 AM, Cosimo Alfarano wrote: On 20/06/11 23:40, Hans-Christoph Steiner wrote: With the primesense-nite-nonfree, it downloads the binary and generates the openni-module-primesense-nite-nonfree_1.3.1.5-1_i386.deb package but it doesn't install it afterwards. It seems to me that it should install it automatically, since that's the only purpose of installing primesense-nite-nonfree. How does that sound? I didn't do it in the beginning to avoid problems with the licence, just in case (out of ignorance and lack of time to check :). Feel free to add it. What the package actually needs is a sort of sha256 checksum like flashplugin does, but yeah installing the new package is only a line :) Do you mean to checksum the file that it downloads from openni.org? That should be pretty straightforward. .hc There is no way to peace, peace is the way. -A.J. Muste ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
primesense-nite-nonfree should install resulting package?
With the primesense-nite-nonfree, it downloads the binary and generates the openni-module-primesense-nite-nonfree_1.3.1.5-1_i386.deb package but it doesn't install it afterwards. It seems to me that it should install it automatically, since that's the only purpose of installing primesense-nite-nonfree. How does that sound? .hc There is no way to peace, peace is the way. -A.J. Muste ___ 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: please upload pd-moonlib
A gentle ping looking for an upload. I'd love to make the Ubuntu/ oneiric import deadline. .hc On Jun 10, 2011, at 1:16 PM, Hans-Christoph Steiner wrote: pd-moonlib was uploaded before, but was rejected by the ftpmasters because the LGPL-covered files were not documented distinct from the over-arching GPL of the project. That's fixed, as well as other recent issues that have come up, and pd-moonlib is ready for upload! http://git.debian.org/?p=pkg-multimedia/pd-moonlib.git .hc Man has survived hitherto because he was too ignorant to know how to realize his wishes. Now that he can realize them, he must either change them, or perish.-William Carlos Williams ___ 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: request for sponsorship for pd-hid
On Jun 14, 2011, at 12:31 PM, Hans-Christoph Steiner wrote: On Jun 13, 2011, at 8:01 PM, Felipe Sateler wrote: On Mon, Jun 13, 2011 at 14:43, Hans-Christoph Steiner wrote: On Jun 12, 2011, at 10:53 PM, Felipe Sateler wrote: On Sat, Jun 11, 2011 at 22:15, Hans-Christoph Steiner > wrote: On Sat, 2011-06-11 at 19:30 +, Felipe Sateler wrote: On Sat, Jun 11, 2011 at 02:45, Hans-Christoph Steiner > wrote: On Wed, 09 Feb 2011 17:41 -0300, "Felipe Sateler" > wrote: On Mon, Jan 31, 2011 at 21:55, Felipe Sateler > wrote: On Fri, Jan 21, 2011 at 19:08, Felipe Sateler > wrote: On Fri, Jan 21, 2011 at 03:37, Hans-Christoph Steiner wrote: On Fri, 24 Dec 2010 15:37 -0800, "Hans-Christoph Steiner" wrote: On Dec 24, 2010, at 9:19 AM, Felipe Sateler wrote: On Wed, Dec 22, 2010 at 21:13, Hans-Christoph Steiner wrote: Just ITPed, packaged and uploaded pd-hid to git.debian.org. It is an object for Pure Data that allows you to use USB HID devices in Pd. The build system is similar in structure to pd-plugin and pd-freeverb, plus it includes the kFreeBSD and Hurd updates, so it should build on all platforms. It depends on pd-mapping and recommends pd- pddp, which are both in NEW. http://git.debian.org/?p=pkg-multimedia/pd-hid.git;a=summary There is some code that is not yours, please add Jan Truetzschler Falkenstein to the debian/copyright file (ftpmaster may reject the package for this missing information). Thanks for spotting that, I pushed the fix. Ping. Anyone willing to sponsor this one? Sorry, I lost track of this. I will try to get to this (and your other packages) during the weekend. I clearly didn't do this when promised, and this week I couldn't either. I've been extremely busy. I'm sorry about that. If someone else can look into these packages, please upload them, since I'm not likely to get any debian time anytime soon. I will, if nobody else gets to these packages, still review them as time permits. It seems that this package never got uploaded. It needs its git-dch done and the changelog finalized and then uploaded. I can finalize the changelog if that makes it easier. It seems some people want to do it themselves when uploading. I believe this package needs to be fixed for puredata >= 0.43 As far as I can tell it has already. For me, it builds on Debian/testing using puredata-dev and no puredata, and squeeze using puredata 0.42.6. Indeed, it seems to work. I have a licensing question though. The package is distributed as GPLv3+. However, Supercollider (where some code was borrowed) is GPLv2+. I think debian/copyright should document that fact. Code from 2004 cannot possibly be under GPLv3+ unless relicensed. The GPLv2+ license has that built into it. In the context of this project, the code from SuperCollider is so intermingled, there is no easily recognizable chunk that could be labeled GPLv2+. Since the project is GPLv3+, I think it would be misleading to try to say that a file is available under GPLv2+. If people want the GPLv2+ file, they should go to the original SuperCollider source. Here's the text from the GPL: "Each version is given a distinguishing version number. If the Program specifies that a certain numbered version of the GNU General Public License "or any later version" applies to it, you have the option of following the terms and conditions either of that numbered version or of any later version published by the Free Software Foundation. " Indeed, I'm not questioning that. My point is that the objective of debian/copyright is documenting, not relicensing, even if it is permissible. From what I've seen, debian/copyright is not finer grained than files. The GPLv2+ code is mixed into two different files that are mostly GPLv3+. So if looking on a per-file basis, all of the files are GPLv3+. .hc Hey Felipe, Any chance of getting this one uploaded in the next week? I'd love to make the Ubuntu/oneiric import deadline. .hc If nature has made any one thing less susceptible than all others of exclusive property, it is the action of the thinking power called an idea, which an individual may exclusively possess as long as he keeps it to himself; but the moment it is divulged, it forces itself into the possession of everyone, and the receiver cannot dispossess himself of it.- Thomas Jefferson ___ 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 package for Debian
On Jun 1, 2011, at 6:57 AM, Cosimo Alfarano wrote: On 31/05/11 03:49, Hans-Christoph Steiner wrote: Ah, cool, so we have an uploader :) I'm just a DM. I'm not sure about Cosimo. I'm a DD. BTW, update to the pkgs status: I tried yesterday the three repos, they worked. I just pushed a couple of patches to fix small (but necessary) things. I just realized that we need to fix the .ini file for Kinect, I had to change "InputFormat=1" which was commented, to make it work. Also, udev rules, does anybody know if we need OWNER="root" or it can be "xxx" as set by upstream? Next steps: - Enable Mono in openni so that it can be re-enabled in NITE. - the Makefile for NITE & OpenNI relies on the presence of the mono exec to compile mono, which means that in a chroot env it compiles without problems, but when build outside in an env which has mono installed it will fail. The reason of the failure is that the upstream install.sh script do not detach the build from the (post) installation process. As per my mono understanding (noob) we need to compile GAC in postinst, while create the DLL at build time. Until we split this behaviour (should be easy) we cannot build mono package and both openni and NITE are inherently broken. It would be nice to have the Mono stuff working, but I don't think it should be a blocker on getting the package uploaded. So far, most of the useful stuff I've seen done with openni has not involved Mono/.NET/ C#. - Re-enable quilt, so that we can patch the Samples to be able to find their XML in a different location than "../../../../Data", and package it as openni-samples, the same for nite and kinect IIRC. - Fix all the lintian complaints and the .ini :) I fixed the man page complaints, tho the man pages I just made could definitely improved a lot. .hc - Fix the SONAME and .so versioning issue, it depends on the email I still have to send to upstream about their build system :) So far this is not a real problem, until we'll have more than one version we need to be able to link at the same time. After that we might be able to consider an upload to unstable, IMHO. cheers, C. ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers If nature has made any one thing less susceptible than all others of exclusive property, it is the action of the thinking power called an idea, which an individual may exclusively possess as long as he keeps it to himself; but the moment it is divulged, it forces itself into the possession of everyone, and the receiver cannot dispossess himself of it.- Thomas Jefferson ___ 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 in Debian
On Jun 19, 2011, at 3:05 AM, Jochen Sprickerhof wrote: * Hans-Christoph Steiner [2011-06-19 00:07]: On Wed, 08 Jun 2011 03:07 +0200, "Jochen Sprickerhof" wrote: * Hans-Christoph Steiner [2011-06-07 18:47]: On Jun 7, 2011, at 6:44 PM, Jochen Sprickerhof wrote: * Hans-Christoph Steiner [2011-06-06 13:05]: I have not been in contact with avin. Is Bayer images support something that is in the original from PrimeSense, or something that you want added? If the idea is to maintain new features in the package, I think that should probably be done in a separate git repo to keep the development and the packaging separately. If you want to maintain a fork of the primesense/sensor repo, we could base the package off of that for now. it's something we have added. Should we put it on github and merge it with the avin2 branch? That works for me. Here it is: https://github.com/ros-pkg-git/Sensor/tree/master. It's not based on the avin2 branch (as they are not really based to the official OpenNI once), let me know if you that's ok for you. By the way, why is the Debian git not connected to the github one? I mean this one: http://anonscm.debian.org/gitweb/?p=pkg-multimedia/primesense-kinect-sensor.git These packages are packaged using standard Debian git-buildpackage style. That means that the upstream code is imported from release tarballs, and the git master branch is all about the debian packaging. That's why this repo is not a fork of the upstream repo. According to the git-buildpackage documentation [1] the upstream- branch can either be imported or a branch you can pull from. So generating tarballs from a git and then importing them into git again seems to be superfluous and makes the upstream branch hard to track. But if it works for you, I'm fine with it. So if we decide to make primesense-kinect-sensor based off of your git fork, then a release tarball would need to be imported using git-import-orig. I'm thinking perhaps its a better idea if you make a separate package of your fork. I used the avin2 fork rather than the offical repo for this package because it seems that the official sources don't fully work. It should be really easy to create a ros package since the code is so close. It could be something like primesense-kinect-sensor-ros or whatever. This has nothing to do with ROS (apart from that it's living in their repository. I'm one of the authors of PCL [2] where we use the features of my version. As there is a ITP [3] for it, it would be nice if the package would include it, so the OpenNI part of PCL would work as well, once it's packages. Regarding the base for the package I'm fine with the avin2 fork, as long as we can put the Bayer patches from my branch inside debian/patches, but for me it would almost make more sense to base it of the OpenNI branch (as this is the official version) and put the avin2 patches in debian/patches as well. [1] /usr/share/doc/git-buildpackage/manual-html/ gbp.intro.html#GBP.REPOSITORY [2] http://pointclouds.org [3] http://bugs.debian.org/624178 Sounds to me like you are much deeper in this code than I am, so I would defer to you on that topic :) I'm mostly am thinking of the long term policy for this package, and what makes sense for the code that's out there. So I don't have strong opinions on how it shaped for the most part. My guess is that the package should try to stick to the primesense code as much as possible, as long as they are accepting patches so that their codebase is usable for Debian. So yes, all changes as patches in debian/patches makes sense to me. I've mostly achieved my goal, which was making it really easy to use skeleton tracking with other media software, but I'm happy to stay involved as much as I am useful. I'm about to have a baby, so I'll probably be not around for a while, so don't worry about waiting on me to get stuff done. Speaking of it, did you see the Fedora patches over there [4]? [4] https://github.com/OpenNI/OpenNI/pull/10] That looks very useful, I hope they accept it. .hc "It is convenient to imagine a power beyond us because that means we don't have to examine our own lives.", from "The Idols of Environmentalism", by Curtis White ___ 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 in Debian
On Jun 19, 2011, at 4:00 AM, Reinhard Tartler wrote: On Sun, Jun 19, 2011 at 09:05:46 (CEST), Jochen Sprickerhof wrote: According to the git-buildpackage documentation [1] the upstream- branch can either be imported or a branch you can pull from. So generating tarballs from a git and then importing them into git again seems to be superfluous and makes the upstream branch hard to track. But if it works for you, I'm fine with it. That's the price of the overhead of team work. As a team, we want to use the same workflow on all packages. Since not all upstreams maintain the sources in git, we need to come down to the lowest common denominator, which boils down to importing tarballs. The other side of it is that the upstream git repos are a mess. The PrimeSense repo is not used for development, and has a quite unusual structure. It looks like to me they are just importing releases and not doing any development out of that git, plus they are using the two branches as separate repos, one called 'master' which is the stable releases, and the other called 'unstable'. As code is pushed to the stable releases, it is not merged from the 'unstable' branch into master. Then it looks like the avin2 fork is a new reconstruction of the git repo to be more git-like, but then that doesn't follow the original git. But I think if I was avin2, I'd do the same. .hc "Making boring techno music is really easy with modern tools, but with live coding, boring techno is much harder." - Chris McCormick ___ 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 in Debian
On Wed, 08 Jun 2011 03:07 +0200, "Jochen Sprickerhof" wrote: > * Hans-Christoph Steiner [2011-06-07 18:47]: > > > > On Jun 7, 2011, at 6:44 PM, Jochen Sprickerhof wrote: > > > > >* Hans-Christoph Steiner [2011-06-06 13:05]: > > >> > > >>I have not been in contact with avin. Is Bayer images support > > >>something that is in the original from PrimeSense, or something that > > >>you want added? If the idea is to maintain new features in the > > >>package, I think that should probably be done in a separate git repo > > >>to keep the development and the packaging separately. If you want > > >>to maintain a fork of the primesense/sensor repo, we could base the > > >>package off of that for now. > > > > > >it's something we have added. Should we put it on github and merge it > > >with the avin2 branch? > > > > > > That works for me. > > Here it is: https://github.com/ros-pkg-git/Sensor/tree/master. It's not > based on the avin2 branch (as they are not really based to the official > OpenNI once), let me know if you that's ok for you. By the way, why is > the Debian git not connected to the github one? I mean this one: > http://anonscm.debian.org/gitweb/?p=pkg-multimedia/primesense-kinect-sensor.git These packages are packaged using standard Debian git-buildpackage style. That means that the upstream code is imported from release tarballs, and the git master branch is all about the debian packaging. That's why this repo is not a fork of the upstream repo. So if we decide to make primesense-kinect-sensor based off of your git fork, then a release tarball would need to be imported using git-import-orig. I'm thinking perhaps its a better idea if you make a separate package of your fork. I used the avin2 fork rather than the offical repo for this package because it seems that the official sources don't fully work. It should be really easy to create a ros package since the code is so close. It could be something like primesense-kinect-sensor-ros or whatever. .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
handling udev for primesense-kinect-sensor
I was just looking at the udev stuff in primesense-kinect-sensor. It seems to me that we should probably ignore their 55-primesense-usb.rules file and do it the proper Debian way. Nobuhiro, I see you are a maintainer on bluez, which installs udev rules. Do you think you could set up the proper Debian style udev handling in primesense-kinect-sensor? I've never packaged udev stuff before. But basically, there .rules file is simple, uses deprecated contructs, and has the user set as 'xxx', and the perms set as 666. So there isn't much there to build on, it seems it should just be replaced. I guess the proper way to do this is to have a standard group that is used to give permissions to read/write to the sensor device, then use that. You can find the upstream file in the source here: Platform/Linux-x86/Install/55-primesense-usb.rules .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: please upload: puredata-import
On Tue, 2011-06-14 at 13:30 -0400, Hans-Christoph Steiner wrote: > On Jun 13, 2011, at 8:24 PM, Felipe Sateler wrote: > > > On Mon, Jun 13, 2011 at 15:06, Hans-Christoph Steiner > > wrote: > >> > >> On Jun 12, 2011, at 10:40 PM, Felipe Sateler wrote: > >> > >>> On Sat, Jun 11, 2011 at 22:05, Hans-Christoph Steiner > >>> > >>> wrote: > >>>> > >>>> On Sat, 2011-06-11 at 19:18 +, Felipe Sateler wrote: > >>>>> > >>>>> I'm confused. You make a change for puredata >= 0.43. Does this > >>>>> break > >>>>> puredata <0.43? The Depends field suggests that (puredata-core > >>>>> is non > >>>>> existent until 0.43). If so, the build-depends on puredata << > >>>>> 0.43 is > >>>>> wrong. > >>>> > >>>> puredata << 0.43 provides everything, headers, app, gui, doc, > >>>> etc. With > >>>> 0.43, the headers are in puredata-dev and puredata is a meta > >>>> package > >>>> that installs everything. I wanted to avoid having the package > >>>> Build-Depend on the whole suite of packages, that's why I added the > >>>> 0.43. Plus in the future, puredata might no longer also install > >>>> puredata-dev. > >>>> > >>>>> Also, doesn't 0.43 bring in the required headers? I think the > >>>>> add_required_headers patch can be removed. > >>>> > >>>> Yes, the puredata-dev 0.43 package does provide those headers, > >>>> but I > >>>> wanted to leave in the patch for now to aid backporting and let > >>>> the dust > >>>> settle on the big changes that happened with the puredata package > >>>> being > >>>> split into puredata-gui, puredata-dev, puredata-core, etc. > >>> > >>> The package won't work unmodified anyways, since it Depends on > >>> puredata-core, which doesn't exist until 0.43. So strictly speaking > >>> the aid for backporting is incomplete (also, it installs into a > >>> different dir, so that would need to be changed too). > >>> > >>> I suggest just dropping the << 0.43 option, since it misleads into > >>> thinking it could actually work unchanged with 0.42. > >>> > >>> > >>> Please update the changelog. I have reviewed this and will upload > >>> tomorrow afternoon (GMT-4, so probably past midnight in europe). > >> > >> > >> Ok, makes sense, I removed the << 0.43 and pushed. > > > > Offering puredata as an option is wrong too (it still allows 0.42) > > > Yes, good point. I also now realized that a backport would also mean > changing the installed folder, since the puredata 0.43 package suite > installs into /usr/lib/puredata now, while puredata 0.42 installed > into /usr/lib/pd I should add: I pushed the changes. .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: please upload: puredata-import
On Jun 13, 2011, at 8:24 PM, Felipe Sateler wrote: On Mon, Jun 13, 2011 at 15:06, Hans-Christoph Steiner wrote: On Jun 12, 2011, at 10:40 PM, Felipe Sateler wrote: On Sat, Jun 11, 2011 at 22:05, Hans-Christoph Steiner wrote: On Sat, 2011-06-11 at 19:18 +, Felipe Sateler wrote: I'm confused. You make a change for puredata >= 0.43. Does this break puredata <0.43? The Depends field suggests that (puredata-core is non existent until 0.43). If so, the build-depends on puredata << 0.43 is wrong. puredata << 0.43 provides everything, headers, app, gui, doc, etc. With 0.43, the headers are in puredata-dev and puredata is a meta package that installs everything. I wanted to avoid having the package Build-Depend on the whole suite of packages, that's why I added the 0.43. Plus in the future, puredata might no longer also install puredata-dev. Also, doesn't 0.43 bring in the required headers? I think the add_required_headers patch can be removed. Yes, the puredata-dev 0.43 package does provide those headers, but I wanted to leave in the patch for now to aid backporting and let the dust settle on the big changes that happened with the puredata package being split into puredata-gui, puredata-dev, puredata-core, etc. The package won't work unmodified anyways, since it Depends on puredata-core, which doesn't exist until 0.43. So strictly speaking the aid for backporting is incomplete (also, it installs into a different dir, so that would need to be changed too). I suggest just dropping the << 0.43 option, since it misleads into thinking it could actually work unchanged with 0.42. Please update the changelog. I have reviewed this and will upload tomorrow afternoon (GMT-4, so probably past midnight in europe). Ok, makes sense, I removed the << 0.43 and pushed. Offering puredata as an option is wrong too (it still allows 0.42) Yes, good point. I also now realized that a backport would also mean changing the installed folder, since the puredata 0.43 package suite installs into /usr/lib/puredata now, while puredata 0.42 installed into /usr/lib/pd .hc "[W]e have invented the technology to eliminate scarcity, but we are deliberately throwing it away to benefit those who profit from scarcity."-John Gilmore ___ 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: please upload pd-bassemu, pd-beatpipe, pd-boids, pd-cyclone, pd-earplug, pd-ext13, d-ggee, pd-hcs, pd-libdir, pd-motex, pd-pddp, pd-vbap
On Jun 13, 2011, at 8:51 PM, Felipe Sateler wrote: On Mon, Jun 13, 2011 at 15:20, Hans-Christoph Steiner wrote: Here are my lowest priority uploads, but I hope to get them uploaded in time to be included in Ubuntu/oneiric. An easier fix to all these RC bugs would be to get someone to upload the 'puredata' package from collab-maint/puredata.git. IOhannes and I have been asking the maintainers to upload for weeks, but they are unresponsive. So perhaps an NMU would be appropriate. What are the changes in puredata? Is there a bug filed? I'm speaking on behalf of the work of IOhannes here, so it might not be entirely correct. IOhannes did the work to split puredata into many packages, including puredata-dev. For a transition plan, the new puredata was supposed to depend on puredata-dev, so that the old Build- Depends would work. That didn't happen, so now all of the existing packages don't build, since the headers are no longer installed when you install puredata. The bugs were then files against the packages that no longer build. I've fixed all of my packages to work with "Build-Depends: puredata- dev | puredata (<< 0.43)" http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=629700 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=629702 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=629705 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=629706 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=629708 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=629710 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=629711 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=629791 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=629718 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=629796 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=629799 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=629802 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=629779 .hc The arc of history bends towards justice. - Dr. Martin Luther King, Jr. ___ 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: request for sponsorship for pd-hid
On Jun 13, 2011, at 8:01 PM, Felipe Sateler wrote: On Mon, Jun 13, 2011 at 14:43, Hans-Christoph Steiner wrote: On Jun 12, 2011, at 10:53 PM, Felipe Sateler wrote: On Sat, Jun 11, 2011 at 22:15, Hans-Christoph Steiner wrote: On Sat, 2011-06-11 at 19:30 +, Felipe Sateler wrote: On Sat, Jun 11, 2011 at 02:45, Hans-Christoph Steiner > wrote: On Wed, 09 Feb 2011 17:41 -0300, "Felipe Sateler" > wrote: On Mon, Jan 31, 2011 at 21:55, Felipe Sateler > wrote: On Fri, Jan 21, 2011 at 19:08, Felipe Sateler > wrote: On Fri, Jan 21, 2011 at 03:37, Hans-Christoph Steiner wrote: On Fri, 24 Dec 2010 15:37 -0800, "Hans-Christoph Steiner" wrote: On Dec 24, 2010, at 9:19 AM, Felipe Sateler wrote: On Wed, Dec 22, 2010 at 21:13, Hans-Christoph Steiner wrote: Just ITPed, packaged and uploaded pd-hid to git.debian.org. It is an object for Pure Data that allows you to use USB HID devices in Pd. The build system is similar in structure to pd-plugin and pd-freeverb, plus it includes the kFreeBSD and Hurd updates, so it should build on all platforms. It depends on pd-mapping and recommends pd- pddp, which are both in NEW. http://git.debian.org/?p=pkg-multimedia/pd-hid.git;a=summary There is some code that is not yours, please add Jan Truetzschler Falkenstein to the debian/copyright file (ftpmaster may reject the package for this missing information). Thanks for spotting that, I pushed the fix. Ping. Anyone willing to sponsor this one? Sorry, I lost track of this. I will try to get to this (and your other packages) during the weekend. I clearly didn't do this when promised, and this week I couldn't either. I've been extremely busy. I'm sorry about that. If someone else can look into these packages, please upload them, since I'm not likely to get any debian time anytime soon. I will, if nobody else gets to these packages, still review them as time permits. It seems that this package never got uploaded. It needs its git-dch done and the changelog finalized and then uploaded. I can finalize the changelog if that makes it easier. It seems some people want to do it themselves when uploading. I believe this package needs to be fixed for puredata >= 0.43 As far as I can tell it has already. For me, it builds on Debian/testing using puredata-dev and no puredata, and squeeze using puredata 0.42.6. Indeed, it seems to work. I have a licensing question though. The package is distributed as GPLv3+. However, Supercollider (where some code was borrowed) is GPLv2+. I think debian/copyright should document that fact. Code from 2004 cannot possibly be under GPLv3+ unless relicensed. The GPLv2+ license has that built into it. In the context of this project, the code from SuperCollider is so intermingled, there is no easily recognizable chunk that could be labeled GPLv2+. Since the project is GPLv3+, I think it would be misleading to try to say that a file is available under GPLv2+. If people want the GPLv2+ file, they should go to the original SuperCollider source. Here's the text from the GPL: "Each version is given a distinguishing version number. If the Program specifies that a certain numbered version of the GNU General Public License "or any later version" applies to it, you have the option of following the terms and conditions either of that numbered version or of any later version published by the Free Software Foundation. " Indeed, I'm not questioning that. My point is that the objective of debian/copyright is documenting, not relicensing, even if it is permissible. From what I've seen, debian/copyright is not finer grained than files. The GPLv2+ code is mixed into two different files that are mostly GPLv3+. So if looking on a per-file basis, all of the files are GPLv3+. .hc Man has survived hitherto because he was too ignorant to know how to realize his wishes. Now that he can realize them, he must either change them, or perish.-William Carlos Williams ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
please upload pd-bassemu, pd-beatpipe, pd-boids, pd-cyclone, pd-earplug, pd-ext13, d-ggee, pd-hcs, pd-libdir, pd-motex, pd-pddp, pd-vbap
Here are my lowest priority uploads, but I hope to get them uploaded in time to be included in Ubuntu/oneiric. An easier fix to all these RC bugs would be to get someone to upload the 'puredata' package from collab-maint/puredata.git. IOhannes and I have been asking the maintainers to upload for weeks, but they are unresponsive. So perhaps an NMU would be appropriate. pd-bassemu pd-beatpipe pd-boids pd-cyclone pd-earplug pd-ext13 pd-ggee pd-hcs pd-libdir pd-motex pd-pddp pd-vbap I can post individual emails for each, if anyone wants me to. I just figured this is a long list all on the same topic, all with the same fix (adding 'puredata-dev | puredata' as the Build-Depends). .hc 'You people have such restrictive dress for women,’ she said, hobbling away in three inch heels and panty hose to finish out another pink- collar temp pool day. - “Hijab Scene #2", by Mohja Kahf ___ 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: please upload pd-cxc, pd-ekext, pd-bsaylor, pd-markex, pd-maxlib, pd-mjlib, pd-sigpack, pd-smlib, pd-windowing, and pd-pdogg
On Jun 13, 2011, at 12:20 AM, Felipe Sateler wrote: On Sat, Jun 11, 2011 at 22:20, Hans-Christoph Steiner wrote: Just to reiterate, the plan is to drop those patches now that puredata-dev provides all the needed headers. But first, I just want to fix the current bug that prevents these packages from building at all, and let the dust settle on the very new reorg of 'puredata' into 'puredata-dev', 'puredata-core', 'puredata-gui', etc. Thanks for following up on this, good luck with the update :) Cool, I just saw that you uploaded a bunch, thanks. Now I have DM upload rights, so I don't need to burden you with them :) Not uploaded: pd-maxlib (pd-libdir moved from Depends to Suggests and not documented reason on changelog), Thanks for catching that, I meant to revert that change since pd- maxlib needs pd-libdir in order for it to load as a library in the standard pd ways (i.e. pd -lib maxlib, etc). pd-pdogg (has pristine-tar data in the master branch, an accidental merge?). Uploaded the rest. Ok, I pushed a "revert merge" commit. Next time, please do not manually tag the releases (pd-ekext), most likely the person uploading forgot to push the git tags. First ask why the tag is not there. Yes, good point, I should have asked. I think I pushed the tags on a couple of other packages. Sorry about that. It'll be easier for me to keep track of the details now that I can dput myself :). .hc Terrorism is not an enemy. It cannot be defeated. It's a tactic. It's about as sensible to say we declare war on night attacks and expect we're going to win that war. We're not going to win the war on terrorism.- retired U.S. Army general, William Odom ___ 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: please upload: puredata-import
On Jun 12, 2011, at 10:40 PM, Felipe Sateler wrote: On Sat, Jun 11, 2011 at 22:05, Hans-Christoph Steiner wrote: On Sat, 2011-06-11 at 19:18 +, Felipe Sateler wrote: I'm confused. You make a change for puredata >= 0.43. Does this break puredata <0.43? The Depends field suggests that (puredata-core is non existent until 0.43). If so, the build-depends on puredata << 0.43 is wrong. puredata << 0.43 provides everything, headers, app, gui, doc, etc. With 0.43, the headers are in puredata-dev and puredata is a meta package that installs everything. I wanted to avoid having the package Build-Depend on the whole suite of packages, that's why I added the 0.43. Plus in the future, puredata might no longer also install puredata-dev. Also, doesn't 0.43 bring in the required headers? I think the add_required_headers patch can be removed. Yes, the puredata-dev 0.43 package does provide those headers, but I wanted to leave in the patch for now to aid backporting and let the dust settle on the big changes that happened with the puredata package being split into puredata-gui, puredata-dev, puredata-core, etc. The package won't work unmodified anyways, since it Depends on puredata-core, which doesn't exist until 0.43. So strictly speaking the aid for backporting is incomplete (also, it installs into a different dir, so that would need to be changed too). I suggest just dropping the << 0.43 option, since it misleads into thinking it could actually work unchanged with 0.42. Please update the changelog. I have reviewed this and will upload tomorrow afternoon (GMT-4, so probably past midnight in europe). Ok, makes sense, I removed the << 0.43 and pushed. .hc ¡El pueblo unido jamás será vencido! ___ 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: request for sponsorship for pd-hid
On Jun 12, 2011, at 10:53 PM, Felipe Sateler wrote: On Sat, Jun 11, 2011 at 22:15, Hans-Christoph Steiner wrote: On Sat, 2011-06-11 at 19:30 +, Felipe Sateler wrote: On Sat, Jun 11, 2011 at 02:45, Hans-Christoph Steiner wrote: On Wed, 09 Feb 2011 17:41 -0300, "Felipe Sateler" > wrote: On Mon, Jan 31, 2011 at 21:55, Felipe Sateler wrote: On Fri, Jan 21, 2011 at 19:08, Felipe Sateler > wrote: On Fri, Jan 21, 2011 at 03:37, Hans-Christoph Steiner > wrote: On Fri, 24 Dec 2010 15:37 -0800, "Hans-Christoph Steiner" wrote: On Dec 24, 2010, at 9:19 AM, Felipe Sateler wrote: On Wed, Dec 22, 2010 at 21:13, Hans-Christoph Steiner wrote: Just ITPed, packaged and uploaded pd-hid to git.debian.org. It is an object for Pure Data that allows you to use USB HID devices in Pd. The build system is similar in structure to pd-plugin and pd- freeverb, plus it includes the kFreeBSD and Hurd updates, so it should build on all platforms. It depends on pd-mapping and recommends pd- pddp, which are both in NEW. http://git.debian.org/?p=pkg-multimedia/pd-hid.git;a=summary There is some code that is not yours, please add Jan Truetzschler Falkenstein to the debian/copyright file (ftpmaster may reject the package for this missing information). Thanks for spotting that, I pushed the fix. Ping. Anyone willing to sponsor this one? Sorry, I lost track of this. I will try to get to this (and your other packages) during the weekend. I clearly didn't do this when promised, and this week I couldn't either. I've been extremely busy. I'm sorry about that. If someone else can look into these packages, please upload them, since I'm not likely to get any debian time anytime soon. I will, if nobody else gets to these packages, still review them as time permits. It seems that this package never got uploaded. It needs its git- dch done and the changelog finalized and then uploaded. I can finalize the changelog if that makes it easier. It seems some people want to do it themselves when uploading. I believe this package needs to be fixed for puredata >= 0.43 As far as I can tell it has already. For me, it builds on Debian/testing using puredata-dev and no puredata, and squeeze using puredata 0.42.6. Indeed, it seems to work. I have a licensing question though. The package is distributed as GPLv3+. However, Supercollider (where some code was borrowed) is GPLv2+. I think debian/copyright should document that fact. Code from 2004 cannot possibly be under GPLv3+ unless relicensed. The GPLv2+ license has that built into it. In the context of this project, the code from SuperCollider is so intermingled, there is no easily recognizable chunk that could be labeled GPLv2+. Since the project is GPLv3+, I think it would be misleading to try to say that a file is available under GPLv2+. If people want the GPLv2+ file, they should go to the original SuperCollider source. Here's the text from the GPL: "Each version is given a distinguishing version number. If the Program specifies that a certain numbered version of the GNU General Public License "or any later version" applies to it, you have the option of following the terms and conditions either of that numbered version or of any later version published by the Free Software Foundation. " .hc kill your television ___ 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: please upload pd-cxc, pd-ekext, pd-bsaylor, pd-markex, pd-maxlib, pd-mjlib, pd-sigpack, pd-smlib, pd-windowing, and pd-pdogg
Just to reiterate, the plan is to drop those patches now that puredata-dev provides all the needed headers. But first, I just want to fix the current bug that prevents these packages from building at all, and let the dust settle on the very new reorg of 'puredata' into 'puredata-dev', 'puredata-core', 'puredata-gui', etc. Thanks for following up on this, good luck with the update :) .hc On Sat, 2011-06-11 at 19:40 +, Felipe Sateler wrote: > All these packages seem to build-depend on puredata-dev | puredata (<< > 0.43). While for some this is harmless, I believe there is no reason > to keep the patch that adds the required headers. I would suggest just > dropping support for older puredatas. > > > Sorry for taking so long, I've been extra busy. Alas, I can't upload > right now, my internet is a bit slow and updating my system and > chroots is taking a while. Please someone take a look and upload some > of these packages, the changes relatively few (the diffs against the > previous version in debian are very short). > > I'll try to check again when my systems have finished updating > (aptitude is telling me I should wait 2-4 hours, depending on the > current internet speed). > > On Tue, Jun 7, 2011 at 17:30, Hans-Christoph Steiner wrote: > > > > And a gentle ping on these packages... but for me puredata-import is a > > higher prioity for uploading. > > > > Thanks in advance! > > > > .hc > > > > On May 25, 2011, at 11:07 AM, Hans-Christoph Steiner wrote: > > > >> > >> After the 'hold', these have all been reviewed and are just awaiting > >> upload. They all include bug fixes so they build on kFreeBSD and Hurd. > >> There is an extra bonus in that I'm now a DM, so I'm setting DM-Upload: > >> yes, then they won't need sponsored uploads any more :) > >> > >> IOhannes sent an email per package originally, I'm now just pinging > >> again on these packages so they get uploaded. > >> > >> pd-cxc, pd-ekext, pd-bsaylor, pd-markex, pd-maxlib, pd-mjlib, > >> pd-sigpack, pd-smlib, pd-windowing, and pd-pdogg > >> > >> .hc > > > > > > > > > > "A cellphone to me is just an opportunity to be irritated wherever you are." > > - Linus Torvalds > > > > > > ___ > > pkg-multimedia-maintainers mailing list > > pkg-multimedia-maintainers@lists.alioth.debian.org > > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers > > > > > > -- > > Saludos, > Felipe Sateler > > ___ > pkg-multimedia-maintainers mailing list > pkg-multimedia-maintainers@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers ___ 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: request for sponsorship for pd-hid
On Sat, 2011-06-11 at 19:30 +, Felipe Sateler wrote: > On Sat, Jun 11, 2011 at 02:45, Hans-Christoph Steiner wrote: > > > > On Wed, 09 Feb 2011 17:41 -0300, "Felipe Sateler" > > wrote: > >> On Mon, Jan 31, 2011 at 21:55, Felipe Sateler > >> wrote: > >> > On Fri, Jan 21, 2011 at 19:08, Felipe Sateler > >> > wrote: > >> >> On Fri, Jan 21, 2011 at 03:37, Hans-Christoph Steiner > >> >> wrote: > >> >>> > >> >>> On Fri, 24 Dec 2010 15:37 -0800, "Hans-Christoph Steiner" > >> >>> wrote: > >> >>>> > >> >>>> On Dec 24, 2010, at 9:19 AM, Felipe Sateler wrote: > >> >>>> > >> >>>> > On Wed, Dec 22, 2010 at 21:13, Hans-Christoph Steiner > >> >>>> > wrote: > >> >>>> >> > >> >>>> >> Just ITPed, packaged and uploaded pd-hid to git.debian.org. It is > >> >>>> >> an > >> >>>> >> object for Pure Data that allows you to use USB HID devices in Pd. > >> >>>> >> The > >> >>>> >> build system is similar in structure to pd-plugin and pd-freeverb, > >> >>>> >> plus > >> >>>> >> it includes the kFreeBSD and Hurd updates, so it should build on > >> >>>> >> all > >> >>>> >> platforms. It depends on pd-mapping and recommends pd-pddp, which > >> >>>> >> are > >> >>>> >> both in NEW. > >> >>>> >> > >> >>>> >> http://git.debian.org/?p=pkg-multimedia/pd-hid.git;a=summary > >> >>>> > > >> >>>> > There is some code that is not yours, please add Jan Truetzschler > >> >>>> > Falkenstein to the debian/copyright file (ftpmaster may reject the > >> >>>> > package for this missing information). > >> >>>> > >> >>>> > >> >>>> Thanks for spotting that, I pushed the fix. > >> >>> > >> >>> Ping. Anyone willing to sponsor this one? > >> >> > >> >> Sorry, I lost track of this. I will try to get to this (and your other > >> >> packages) during the weekend. > >> > > >> > I clearly didn't do this when promised, and this week I couldn't > >> > either. I've been extremely busy. I'm sorry about that. If someone > >> > else can look into these packages, please upload them, since I'm not > >> > likely to get any debian time anytime soon. > >> > > >> > I will, if nobody else gets to these packages, still review them as > >> > time permits. > > > > It seems that this package never got uploaded. It needs its git-dch > > done and the changelog finalized and then uploaded. I can finalize the > > changelog if that makes it easier. It seems some people want to do it > > themselves when uploading. > > I believe this package needs to be fixed for puredata >= 0.43 As far as I can tell it has already. For me, it builds on Debian/testing using puredata-dev and no puredata, and squeeze using puredata 0.42.6. .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: please upload: puredata-import
On Sat, 2011-06-11 at 19:18 +, Felipe Sateler wrote: > I'm confused. You make a change for puredata >= 0.43. Does this break > puredata <0.43? The Depends field suggests that (puredata-core is non > existent until 0.43). If so, the build-depends on puredata << 0.43 is > wrong. puredata << 0.43 provides everything, headers, app, gui, doc, etc. With 0.43, the headers are in puredata-dev and puredata is a meta package that installs everything. I wanted to avoid having the package Build-Depend on the whole suite of packages, that's why I added the 0.43. Plus in the future, puredata might no longer also install puredata-dev. > Also, doesn't 0.43 bring in the required headers? I think the > add_required_headers patch can be removed. Yes, the puredata-dev 0.43 package does provide those headers, but I wanted to leave in the patch for now to aid backporting and let the dust settle on the big changes that happened with the puredata package being split into puredata-gui, puredata-dev, puredata-core, etc. .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: request for sponsorship for pd-hid
On Wed, 09 Feb 2011 17:41 -0300, "Felipe Sateler" wrote: > On Mon, Jan 31, 2011 at 21:55, Felipe Sateler > wrote: > > On Fri, Jan 21, 2011 at 19:08, Felipe Sateler wrote: > >> On Fri, Jan 21, 2011 at 03:37, Hans-Christoph Steiner > >> wrote: > >>> > >>> On Fri, 24 Dec 2010 15:37 -0800, "Hans-Christoph Steiner" > >>> wrote: > >>>> > >>>> On Dec 24, 2010, at 9:19 AM, Felipe Sateler wrote: > >>>> > >>>> > On Wed, Dec 22, 2010 at 21:13, Hans-Christoph Steiner > >>>> > wrote: > >>>> >> > >>>> >> Just ITPed, packaged and uploaded pd-hid to git.debian.org. It is an > >>>> >> object for Pure Data that allows you to use USB HID devices in Pd. > >>>> >> The > >>>> >> build system is similar in structure to pd-plugin and pd-freeverb, > >>>> >> plus > >>>> >> it includes the kFreeBSD and Hurd updates, so it should build on all > >>>> >> platforms. It depends on pd-mapping and recommends pd-pddp, which > >>>> >> are > >>>> >> both in NEW. > >>>> >> > >>>> >> http://git.debian.org/?p=pkg-multimedia/pd-hid.git;a=summary > >>>> > > >>>> > There is some code that is not yours, please add Jan Truetzschler > >>>> > Falkenstein to the debian/copyright file (ftpmaster may reject the > >>>> > package for this missing information). > >>>> > >>>> > >>>> Thanks for spotting that, I pushed the fix. > >>> > >>> Ping. Anyone willing to sponsor this one? > >> > >> Sorry, I lost track of this. I will try to get to this (and your other > >> packages) during the weekend. > > > > I clearly didn't do this when promised, and this week I couldn't > > either. I've been extremely busy. I'm sorry about that. If someone > > else can look into these packages, please upload them, since I'm not > > likely to get any debian time anytime soon. > > > > I will, if nobody else gets to these packages, still review them as > > time permits. It seems that this package never got uploaded. It needs its git-dch done and the changelog finalized and then uploaded. I can finalize the changelog if that makes it easier. It seems some people want to do it themselves when uploading. .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
Bug#629803: pd-windowing: FTBFS: bartlett~.c:22:18: fatal error: m_pd.h: No such file or directory (missing B-D on puredata-dev)
Tags: wheezy sid pending help I am the packager and lead maintainer on this package. I have fixed this bug and pushed the fixes to the git.debian.org repo listed in the Vcs-* lines. The package is ready for upload, but I am a DM without upload permissions on this package. I have been looking for a sponsor on pkg-multimedia for a few weeks now, so I'd appreciate it if anyone could upload this package, either NMU or from pkg-multimedia. .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
Bug#629802: pd-vbap: FTBFS: vbap.h:5:24: fatal error: m_pd.h: No such file or directory (missing B-D on puredata-dev)
Tags: wheezy sid pending help I am the packager and lead maintainer on this package. I have fixed this bug and pushed the fixes to the git.debian.org repo listed in the Vcs-* lines. The package is ready for upload, but I am a DM without upload permissions on this package. I have been looking for a sponsor on pkg-multimedia for a few weeks now, so I'd appreciate it if anyone could upload this package, either NMU or from pkg-multimedia. .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
Bug#629801: pd-smlib: FTBFS: defines.h:1:18: fatal error: m_pd.h: No such file or directory (missing B-D on puredata-dev)
Tags: wheezy sid pending help I am the packager and lead maintainer on this package. I have fixed this bug and pushed the fixes to the git.debian.org repo listed in the Vcs-* lines. The package is ready for upload, but I am a DM without upload permissions on this package. I have been looking for a sponsor on pkg-multimedia for a few weeks now, so I'd appreciate it if anyone could upload this package, either NMU or from pkg-multimedia. .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
Bug#629800: pd-sigpack: FTBFS: chop~.c:6:18: fatal error: m_pd.h: No such file or directory (missing B-D on puredata-dev)
Tags: wheezy sid pending help I am the packager and lead maintainer on this package. I have fixed this bug and pushed the fixes to the git.debian.org repo listed in the Vcs-* lines. The package is ready for upload, but I am a DM without upload permissions on this package. I have been looking for a sponsor on pkg-multimedia for a few weeks now, so I'd appreciate it if anyone could upload this package, either NMU or from pkg-multimedia. .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
Bug#629799: pd-pmpd: FTBFS: iAmbient2D.c:1:18: fatal error: m_pd.h: No such file or directory (missing B-D on puredata-dev)
Tags: wheezy sid pending help I am the packager and lead maintainer on this package. I have fixed this bug and pushed the fixes to the git.debian.org repo listed in the Vcs-* lines. The package is ready for upload, but I am a DM without upload permissions on this package. I have been looking for a sponsor on pkg-multimedia for a few weeks now, so I'd appreciate it if anyone could upload this package, either NMU or from pkg-multimedia. .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
