Sweet! On 06/07/2013 08:34 AM, Yaroslav Halchenko wrote:
Thank you for wondering! As you might know, lxc-docker debian package is pretty much ready: http://mentors.debian.net/package/lxc-docker and I've been advocating for inclusion in unstable. Paul Tagliamonte, our awesome DD, and I have been closely working together. We need to rebump the way we generate the package to be more in line with Debian policies.ha cool -- lazy me forgotten to check mentors (usually it is a good practice to send such updates to the corresponding ITP bug so people know where to look)
Good point. CC: is taking care of it now. :) Thanks!
All fair questions! We are following the practice we use for publishing PPA packages, which after installing building dependencies (git debhelper build-essential autotools-dev devscripts golang), boils down to:I see that PPA has some packages (check lintian *.dsc for minor tweeks TODO; also probably there is no reason for duplicate {,src/}github.com/docker; copyright seems to be missing info on ./src/github.com/gorilla/; may be more...) -- but is there anything holding you up really? ;)Yep, those are minor issues. The mayor one is to move the debian/Makefile to debian/rules with new logic, aligned with debian go packaging guidelines. If are you interested in helping out, we will have the debian packaging faster :)oki doki looking at http://mentors.debian.net/debian/pool/main/l/lxc-docker/lxc-docker_0.3.2-1.dsc and trying to $> git clone git://git.debian.org/git/collab-maint/lxc-docker.git Cloning into 'lxc-docker'... fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. so where is the beast? ;) in your stock repo on github I do not see any new 'debian' branch with just 'debian/'... I see only "old" packaging/debian/ only so where/how to look?
git clone git://github.com/dotcloud/docker; cd docker/packaging/debian; make debian
That will take care of generating all packaging files. For the PPA, that's enough. Launchpad builders will take it from there. As you point out, this is not quite the process debian uses. We have already access rights and the next step is creating the proper repo. Upstream is meant to have /packaging/debian as we highly prefer to keep the root level clean and organized ( having /debian will suggest we could have /ubuntu
/redhat /arch. It's much cleaner to have /packaging for packaging stuff :)