On 11/25/2013 06:52 AM, Hauke Wintjen wrote: > >> Hans-Christoph Steiner <h...@eds.org> hat am 23. November 2013 um 18:43 >> geschrieben: >> >> >> >> >> On 11/22/2013 05:55 AM, Jochen Sprickerhof wrote: >>> Hi, >>> >>> * Hauke Wintjen <hwint...@rimpl-consulting.de> [2013-11-21 09:30]: >>>>> Hans-Christoph Steiner <h...@eds.org> 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
