<div dir="ltr">Dmitry, note that the pkg-go team policy states that packages must be buildable using git-buildpackage: <a href="https://pkg-go.alioth.debian.org/packaging.html">https://pkg-go.alioth.debian.org/packaging.html</a><div><br></div><div>So, even if you prefer not to use git-buildpackage, please at least verify before pushing your repository that it can successfully be built using git-buildpackage (without having to specify any options).</div><div><br></div><div>Thanks.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Oct 19, 2015 at 6:11 AM, Dmitry Smirnov <span dir="ltr"><<a href="mailto:onlyjob@debian.org" target="_blank">onlyjob@debian.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Sunday 18 October 2015 23:39:35 Matthew Dawson wrote:<br>
> > Why? Etcd is as a statically linked binary so you do not need to re-build<br>
> > it for Jessie. Just use the package from "testing" as is. You can use<br>
> > Apt- Pinning technique to allow list of certain packages to be installed<br>
> > from "testing".<br>
><br>
> I generally avoid this method only because eventually I find packages that<br>
> start requiring newer versions of core packages that I don't want to pull<br>
> and keep up to date constantly. In the past I usually got away with what<br>
> was available in Wheezy, but this time I have a huge dependency list.<br>
><br>
> If etcd (and Kubernetes in the future) can keep its runtime dependencies<br>
> Jessie friendly, I wouldn't have an issue doing as you suggest.<br>
<br>
</span>So you are building your own private backports... :)<br>
<br>
I'm not sure which core packages you are concerned about but in general since<br>
both Etcd and Kubernetes are still fairly young they are adding new<br>
dependencies all the time. Docker does the same...<br>
<span class=""><br>
<br>
> If not, you could consider this a start on a backports effort :)<br>
<br>
</span>Maybe if this effort would be sponsored financially...<br>
<br>
I agree that backports could be useful even for statically linked Golang<br>
software as protection from sudden changes in "testing".<br>
<span class=""><br>
<br>
> I'm happy to help in any way I can. I haven't dug into Debian packaging<br>
> before, so I figured I'd start on etcd and move on to Kubernetes after. Is<br>
> there any specific method you'd want me to follow to work on those<br>
> packages?<br>
<br>
</span>I'd use dh-make-golang (-type="library") with passing -git_revision whenever<br>
upstream do formal releases. Also I add "debian/watch" file even if upstream<br>
do not tag yet -- it helped me more than twice already when tags appeared...<br>
<span class=""><br>
<br>
> I was going to start with one of the other Go packages as a<br>
> template, so if you can point me at a good example I can try starting from<br>
> there. I do want to finish dealing with etcd first, so that I can start<br>
> Kubernetes once its ready.<br>
<br>
</span>Although Kubernetes packaging is not published yet it is not too bad and will<br>
probably need only little work. But packaging all dependencies is a pain...<br>
<span class=""><br>
<br>
<br>
> I tried adding that, but it didn't seem to help. It seems gbp doesn't like<br>
> this repository format by default, as it assume the upstream files are<br>
> available. Making it use git-pbuilder does fix it, as it builds<br>
> everything from the tar archive. Google doesn't seem to talk much about<br>
> this.<br>
><br>
> I'll keep poking at this, but any other suggestions would be appreciated.<br>
<br>
</span>Sorry, then I think it must be the following:<br>
<br>
~~~~<br>
[DEFAULT]<br>
builder = pdebuild --debbuildopts "-i\.git -I.git $*"<br>
~~~~<br>
<span class=""><br>
<br>
> Ok, for reference what do you run to build from the git repository? That<br>
> might help me get this going.<br>
<br>
</span>I just extract tarball obtained with `uscan` or `origtargz`, add "debian"<br>
directory and invoke `pbuilder` (or `debuild). IMHO this procedure is simple<br>
enough and avoids GBP which I see as unnecessary complex and demanding...<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
All the best,<br>
Dmitry Smirnov.<br>
</font></span><br>_______________________________________________<br>
Pkg-go-maintainers mailing list<br>
<a href="mailto:Pkg-go-maintainers@lists.alioth.debian.org">Pkg-go-maintainers@lists.alioth.debian.org</a><br>
<a href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers" rel="noreferrer" target="_blank">http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers</a><br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">Best regards,<br>Michael</div>
</div>