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: getting openni2 into Debian
> 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? > > Hauke, were you able to request an account on alioth yet? I forget where that > stands. Yes, see above. > > .hc > Kind regards Hauke ___ 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
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 ___ 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
* 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 ___ 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
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2013-11-21 09:30, Hauke Wintjen wrote: >>> Why do you change the SONAME from upstream? That's a pretty >>> unusual thing to do. >>> patches/0001-Add-SONAME-to-libraries.patch > > Because upstream does not add a SONAME and jsprickerhoff had it in > its openni package (from which i started) and suggested to me to > add this patch also. > > Then for the debian-develop branch (2.3.x) they changed one api > incompatible so i incremented it from the debian-master branch > (2.0.x - 2.2.x). 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. fgamsdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.15 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iQIcBAEBCAAGBQJSjdRvAAoJELZQGcR/ejb4DboP/i2Ek8PiwPvSLdtYQdOP4bwY +5q9hV6zA1+cne8pf4tMjNmh8hefHRVa068DZNXesQcIVFyb3wluZUykNAcC+Tfx MpySJvuFrCl7JOlrY7TbqI9EhgD8rxqIsdqqpziAHHfq8War+J88Su1fcOny/sFn nqVpZ/73z8QC7OlbwAC8IPWq/A74khcjwNjmxutKxHhYxTyRG2kvewVA6xJF0bfL H0NEigjcyqk8kGqrDLPtqU4i4YAngIty/XvcdT1Jkg9wCcDu+wotkOukZMuIOSDq B83jtlTeYyfOmttqknvkgGMiW3ml/XBmCrActXsIjPPo+SPBbFqI9ik9OBd9Sc/A lWDAXLe2IZp+n/OL9cQ3Gaum9G6VzQHSu0TVZiSwjJ2IZUExDjWPft95kRraQEqx dlRA2qsjaQu+rxrn2zxHYy8TcT3YLN1m+GWWhADlzh6db84IIFdA4b1g7qdp6anh V58WLyxmUcuDOVWrlpZAqgcBHIZXegMjmkjYQCw9PsfFGn7K1+Ebp8jPIeVwn3Xc +EAe4/6hjy/SEbIBWpPI3xKpa6+s89eMURv9gNt7pLRRPV38JBXXPDzBd8KNXL1Q rbKJit2Xa85fbUzUWVgAoFTeOery5jXk9r3Z/ikDNOuiXoQ9RhbChm7gRWLGR98c Zqo5v8jQxgUamUCr5Y6c =LhRW -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
Re: getting openni2 into Debian
Hi. > Hans-Christoph Steiner hat am 20. November 2013 um 20:13 > geschrieben: > > > > 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. Ok, i will check that. > > 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. I tried to use git-dch but (since my first debian package) are somewhat clueless about the various tools. I will fix that. Actually i took this package from jsprickerhoff. > > 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. > > Why do you change the SONAME from upstream? That's a pretty unusual thing to > do. > patches/0001-Add-SONAME-to-libraries.patch Because upstream does not add a SONAME and jsprickerhoff had it in its openni package (from which i started) and suggested to me to add this patch also. Then for the debian-develop branch (2.3.x) they changed one api incompatible so i incremented it from the debian-master branch (2.0.x - 2.2.x). I think he discussed with upstream to add the soname version id but without success. > > > .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 > >> > > >>> > >>> > >> > > > > >___ 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
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
