[pkg-go] Bug#877146: Bug#877329: Bug#877146: update to runc (1.0.0~rc4) breaks docker
On 10 October 2017 at 12:59, Tianon Gravi <tia...@debian.org> wrote: > I've been working on a "docker-containerd" package today (since that's > going to be useful regardless), and found that there are other > packages needed which depend on > "golang-github-opencontainers-runc-dev", so we're going to have to end > up with either splitting all the deps too, or going with Provides and > hoping for the best compatibility-wise (and perhaps splitting only > if/when there's an actual compatibility divergence for one of the > deps). Alright, I've managed to get everything to a working state. Upload for "docker-runc" is up (with appropriate maintainer), and a "docker-containerd" package should be hitting NEW shortly. Once "docker-containerd" is accepted, then I can upload the fixed "docker.io" package. ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#877146: Bug#877329: Bug#877146: update to runc (1.0.0~rc4) breaks docker
On 3 October 2017 at 15:52, Bálint Réczeywrote: > I think it would be cleaner to go without the Provides: and adding > docker-containerd build-depending on > golang-github-opencontainers-docker-runc-dev, but feel free to go either way. > > I think the most efficient way forward would be if you could adopt the > docker-runc > package for the Docker Team and updating it as you please without > waiting for me - > and I'm perfectly OK with that. I've been working on a "docker-containerd" package today (since that's going to be useful regardless), and found that there are other packages needed which depend on "golang-github-opencontainers-runc-dev", so we're going to have to end up with either splitting all the deps too, or going with Provides and hoping for the best compatibility-wise (and perhaps splitting only if/when there's an actual compatibility divergence for one of the deps). ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#877146: update to runc (1.0.0~rc4) breaks docker
On 30 September 2017 at 08:37, Bálint Réczeywrote: > Tianon, could you please switch to docker-runc in docker.io? > > I have the packaging commits in git for docker-runc but I did not want to > push it to the go packages' area so when I get approved to the Docker > Packaging Team I'll push the repo to their area and happily hand over > the package. Your team application should be approved for creating that "docker-runc" repo and pushing your sources. I went to go try to update "src:docker.io", but I'm having trouble pulling in the "golang-github-opencontainers-docker-runc-dev" dependency (which is oddly named, but past the FTP team so I guess not a big deal). I believe it needs to both "Provides:" and "Conflicts:" of "golang-github-opencontainers-runc-dev" for the sake of "golang-github-docker-containerd-dev" (which is very much intertwined). We might end up needing to _also_ create a "docker-containerd" package to get out of this, which would indirectly unblock https://github.com/containerd/containerd/issues/1508 (updating "containerd" to 1.x, which Docker doesn't support yet). I'll push up my WIP changes now. ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#872807: Bug#872807: Bug#872807: Bug#872807: dh-make-golang: Please find dependencies based on Homepage, too
On 21 August 2017 at 14:11, Michael Hudson-Doylewrote: > On 22 August 2017 at 01:17, Paul R. Tagliamonte wrote: >> Why not use the import path I so lovingly put in the generated control >> file for times like these? > > That's still missing from heaps of packages, isn't it? I know someone who > likes writing scripts to fix lots of golang packages at once... Also, some packages include multiple import paths, usually via a symlink. These are often the result of a rename, or of two imports for the same project (ala, "github.com/foo/bar" and "gopkg.in/foo/bar.vN"), so it might be worth considering making that a list instead of simply a single package path. ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#869242: Bug#869242: CVE-2017-11468
On 21 July 2017 at 15:17, Tianon Gravi <tia...@debian.org> wrote: > https://github.com/docker/distribution/releases/tag/v2.6.2 is the > release which fixes this (and it links to > https://github.com/docker/distribution/commit/29fa466debaabb64f8559116bbffd20a289d523c > as the specific commit which does so). The also updated the 2.5 branch in https://github.com/docker/distribution/releases/tag/v2.5.2, so if we end up cherry-picking the CVE fixing patch instead of bumping, https://github.com/docker/distribution/commit/58d239d723efbc2b2935ddc8816b51d355525989 might apply easier (haven't looked at applying either, just noting it for completeness). ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#869242: Bug#869242: CVE-2017-11468
On 21 July 2017 at 14:35, Moritz Muehlenhoffwrote: > Please see > http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-11468 Thanks for the report! I've started looking into the fix, and will include my notes here: https://github.com/docker/distribution/releases/tag/v2.6.2 is the release which fixes this (and it links to https://github.com/docker/distribution/commit/29fa466debaabb64f8559116bbffd20a289d523c as the specific commit which does so). A plain "dch -v 2.6.2~ds1-1" is _not_ sufficient to get a working build (needs some dependency updates, I think, since we're currently on v2.6.0-rc.1 + a few commits and upstream has obviously made some changes since then). Given that the package is only in unstable, I'll likely commit my WIP bump to 2.6.2 to Git once I'm done looking around at how much it's going to take to update (whether it's building successfully or not). ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
Re: [pkg-go] Self intro and RE: CRI-O in Debian
On 10 May 2017 at 12:29, Lokesh Mandvekarwrote: > I've had off-list conversations with Jonathan about this, and I'll go ahead > with this for now, Jonathan and others are more than welcome to help me out > whenever they get the chance. > > I'm only beginning with debian packaging and I'll most likely need help from > others > on the list, beers will be owed of course :) Welcome to pkg-go! :) Be sure to check out "dh-make-golang" (which will make your life a lot easier; https://github.com/Debian/dh-make-golang), and https://pkg-go.alioth.debian.org/packaging.html. ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
Re: [pkg-go] Replace "tpot-guest" with "tpot" on Golang alioth groups
On 7 March 2017 at 16:50, Potter, Timwrote: > Could someone please add "tpot" to the scm_pkg-go and scm_docker groups? It > might > also be good to remove "tpot-guest" from those groups as well. Done! ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#853866: unblock: runc/0.1.1+dfsg1-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package runc There was a CVE filed against runc recently (CVE-2016-9962), and the patch to fix it was applied in the 0.1.1+dfsg1-2 team upload I just made. The patch is simply setting "runc exec" processes as "non-dumpable" (which according to the CVE text and upstream, closes the vulnerability). unblock runc/0.1.1+dfsg1-2 -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) diff -Nru runc-0.1.1+dfsg1/debian/changelog runc-0.1.1+dfsg1/debian/changelog --- runc-0.1.1+dfsg1/debian/changelog 2016-07-13 06:01:04.0 -0700 +++ runc-0.1.1+dfsg1/debian/changelog 2017-02-01 07:17:54.0 -0800 @@ -1,3 +1,10 @@ +runc (0.1.1+dfsg1-2) unstable; urgency=medium + + * Team upload. + * Backport patch for CVE-2016-9962 (Closes: #850951) + + -- Tianon Gravi <tia...@debian.org> Wed, 01 Feb 2017 07:17:54 -0800 + runc (0.1.1+dfsg1-1) unstable; urgency=medium * New upstream release [June 2016]. diff -Nru runc-0.1.1+dfsg1/debian/control runc-0.1.1+dfsg1/debian/control --- runc-0.1.1+dfsg1/debian/control 2016-07-13 05:58:01.0 -0700 +++ runc-0.1.1+dfsg1/debian/control 2016-11-29 14:18:25.0 -0800 @@ -3,7 +3,8 @@ Priority: extra Maintainer: Debian Go Packaging Team <pkg-go-maintainers@lists.alioth.debian.org> Uploaders: Alexandre Viau <alexan...@alexandreviau.net>, - Dmitry Smirnov <only...@debian.org> + Dmitry Smirnov <only...@debian.org>, + Tim Potter <t...@hpe.com> Build-Depends: debhelper (>= 9), dh-golang, go-md2man, diff -Nru runc-0.1.1+dfsg1/debian/patches/cve-2016-9962.patch runc-0.1.1+dfsg1/debian/patches/cve-2016-9962.patch --- runc-0.1.1+dfsg1/debian/patches/cve-2016-9962.patch 1969-12-31 16:00:00.0 -0800 +++ runc-0.1.1+dfsg1/debian/patches/cve-2016-9962.patch 2017-01-31 20:50:59.0 -0800 @@ -0,0 +1,23 @@ +Description: set "runc exec" processes as non-dumpable (CVE-2016-9962) +Origin: https://github.com/opencontainers/runc/commit/50a19c6ff828c58e5dab13830bd3dacde268afe5 (backported to v0.1.1) +Author: Tianon Gravi <tia...@debian.org> +Forwarded: not-needed +Applied-Upstream: > 1.0.0-rc2 + +diff --git a/libcontainer/nsenter/nsexec.c b/libcontainer/nsenter/nsexec.c +index 8f37d6c..3c74c63 100644 +--- a/libcontainer/nsenter/nsexec.c b/libcontainer/nsenter/nsexec.c +@@ -364,6 +364,12 @@ void nsexec(void) + return; + } + ++ /* make the process non-dumpable */ ++ if (prctl(PR_SET_DUMPABLE, 0, 0, 0, 0) != 0) { ++ pr_perror("Failed to set process as non-dumpable"); ++ exit(1); ++ } ++ + // Retrieve the netlink header + struct nlmsghdr nl_msg_hdr; + int len; diff -Nru runc-0.1.1+dfsg1/debian/patches/series runc-0.1.1+dfsg1/debian/patches/series --- runc-0.1.1+dfsg1/debian/patches/series 2016-07-13 05:08:22.0 -0700 +++ runc-0.1.1+dfsg1/debian/patches/series 2017-01-31 20:48:05.0 -0800 @@ -1 +1,2 @@ disable-failing-tests.patch +cve-2016-9962.patch ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#850951: CVE-2016-9962
On 31 January 2017 at 20:46, Tianon Gravi <tia...@debian.org> wrote: > I'm preparing a patch for the package now, but I'm curious what the > implications of an upload will be so close to the freeze -- do we need > to request a freeze exception or a migration adjustment after the > updated package is up? Should I hold off on uploading? (would rather > not lose "runc" from stretch) CVE fix backported for v0.1.1 is attached (applies cleanly in the current packaging when added to "debian/patches/series"). Happy to do the actual upload if I can get some guidance on how to make sure it's done properly WRT freeze (or just as happy to leave it to someone else). O:) ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 Description: set "runc exec" processes as non-dumpable (CVE-2016-9962) Origin: https://github.com/opencontainers/runc/commit/50a19c6ff828c58e5dab13830bd3dacde268afe5 (backported to v0.1.1) Author: Tianon Gravi <tia...@debian.org> Forwarded: not-needed Applied-Upstream: > 1.0.0-rc2 diff --git a/libcontainer/nsenter/nsexec.c b/libcontainer/nsenter/nsexec.c index 8f37d6c..3c74c63 100644 --- a/libcontainer/nsenter/nsexec.c +++ b/libcontainer/nsenter/nsexec.c @@ -364,6 +364,12 @@ void nsexec(void) return; } + /* make the process non-dumpable */ + if (prctl(PR_SET_DUMPABLE, 0, 0, 0, 0) != 0) { + pr_perror("Failed to set process as non-dumpable"); + exit(1); + } + // Retrieve the netlink header struct nlmsghdr nl_msg_hdr; int len; ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#850951: Bug#850951: Bug#850951: CVE-2016-9962
On 30 January 2017 at 11:31, Salvatore Bonaccorsowrote: > Disclaimer: I'm not too deep into that. I just noticed that > https://bugzilla.novell.com/show_bug.cgi?id=1012568 though seem to > indicate as well 0.1.1 based version are affected. But I cannot tell > more (at the moment). Reading more into the vuln itself, I think ignoring the "stateDirFD" bits of the upstream patch is appropriate (and simply adding the "PR_SET_DUMPABLE" bit for "runc exec" as in "libcontainer/nsenter/nsexec.c"). I'm preparing a patch for the package now, but I'm curious what the implications of an upload will be so close to the freeze -- do we need to request a freeze exception or a migration adjustment after the updated package is up? Should I hold off on uploading? (would rather not lose "runc" from stretch) ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#850951: Bug#850951: CVE-2016-9962
On 11 January 2017 at 07:21, Moritz Muehlenhoffwrote: > Please see: > https://bugzilla.suse.com/show_bug.cgi?id=1012568 > https://github.com/docker/docker/compare/v1.12.5...v1.12.6 > https://github.com/opencontainers/runc/commit/50a19c6ff828c58e5dab13830bd3dacde268afe5 I've been working on backporting this patch to 0.1.1, and I think the CVE actually doesn't apply to 0.1.1 (the version currently in sid/stretch). The file descriptor being closed in this patch isn't being opened at all in 0.1.1 ("stateDirFD" doesn't exist yet). https://github.com/opencontainers/runc/pull/886 is the upstream PR which introduced this file descriptor, and it was not included in a release until 1.0.0-rc2. As a consequence, I think this bug should be closed (and probably the security tracker updated to reflect the fact that this CVE doesn't apply to our older version of runc). ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#841575: Bug#841575: docker-registry: FTBFS: Tests failures
On 20 November 2016 at 20:31, Tianon Gravi <tia...@debian.org> wrote: > I wasn't able to dig into the details yet, but looking at the log I > noticed the following which I believe is the real test failure output: That being said, I currently get the (more severe IMO) failure when trying to build locally: > src/github.com/docker/distribution/registry/registry.go:13:2: cannot find > package "github.com/Sirupsen/logrus/formatters/logstash" in any of: > /<>/obj-x86_64-linux-gnu/src/github.com/docker/distribution/vendor/github.com/Sirupsen/logrus/formatters/logstash > (vendor tree) > /usr/lib/go-1.7/src/github.com/Sirupsen/logrus/formatters/logstash (from > $GOROOT) > /<>/obj-x86_64-linux-gnu/src/github.com/Sirupsen/logrus/formatters/logstash > (from $GOPATH) ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#841575: Bug#841575: docker-registry: FTBFS: Tests failures
On 21 October 2016 at 06:10, Lucas Nussbaumwrote: > During a rebuild of all packages in sid, your package failed to build on > amd64. I wasn't able to dig into the details yet, but looking at the log I noticed the following which I believe is the real test failure output: > === RUN Test > > -- > FAIL: configuration_test.go:167: ConfigSuite.TestMarshalRoundtrip > > configuration_test.go:171: > c.Assert(err, IsNil) > ... value *errors.errorString = {s:"Invalid loglevel Must > be one of [error, warn, info, debug]"} ("Invalid loglevel Must be one of > [error, warn, info, debug]") > > time="2016-10-21T01:11:44Z" level=warning msg="Ignoring unrecognized > environment variable REGISTRY_DUCKS" > time="2016-10-21T01:11:44Z" level=warning msg="Ignoring unrecognized > environment variable REGISTRY_REPORTING_ASDF" > OOPS: 19 passed, 1 FAILED > --- FAIL: Test (0.01s) > FAIL > exit status 1 > FAIL github.com/docker/distribution/configuration 0.015s ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
Re: [pkg-go] update example filelist for website/packaging guide
On 4 October 2016 at 03:53, Jonathan Dowlandwrote: > I seem to lack permission to push to > git+ssh://j...@git.debian.org/git/pkg-go/website.git > directly, but here's a fix to the example package filelist I tried to apply this and got similar permission errors, so I jumped onto git.debian.org to take a look. $ git push Counting objects: 3, done. Delta compression using up to 8 threads. Compressing objects: 100% (3/3), done. Writing objects: 100% (3/3), 459 bytes | 0 bytes/s, done. Total 3 (delta 1), reused 0 (delta 0) remote: error: insufficient permission for adding an object to repository database ./objects remote: fatal: failed to write object error: unpack failed: unpack-objects abnormal exit To ssh://git.debian.org/git/pkg-go/website.git ! [remote rejected] master -> master (unpacker error) error: failed to push some refs to 'ssh://git.debian.org/git/pkg-go/website.git' It appears that the repo is still stapelberg-only. :) tianon@moszumanska:/git/pkg-go/website.git$ ls -l total 32 -rw-r--r-- 1 stapelberg stapelberg 23 Aug 29 2013 HEAD drwxr-xr-x 2 stapelberg stapelberg 4096 Aug 29 2013 branches -rw-r--r-- 1 stapelberg stapelberg 66 Aug 29 2013 config -rw-r--r-- 1 stapelberg stapelberg 73 Aug 29 2013 description -rw-r--r-- 1 stapelberg stapelberg0 Aug 29 2013 git-daemon-export-ok drwxr-xr-x 2 stapelberg stapelberg 4096 Aug 29 2013 hooks drwxr-xr-x 2 stapelberg stapelberg 4096 Aug 29 2013 info drwxr-xr-x 38 stapelberg stapelberg 4096 Apr 15 06:59 objects drwxr-xr-x 4 stapelberg stapelberg 4096 Aug 29 2013 refs ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#830729: Bug#830729: Bug#830729: Bug#830729: golang-github-mitchellh-go-homedir: FTBFS: homedir_test.go:44: "/home/lamby" != "~"
On 31 July 2016 at 20:20, Potter, Tim (HPE Linux Support)wrote: > Patch attached to fix this, but it's a bit icky (and has been replaced by a > shell out to call > getent in a later version. Very nice catch indeed! Given that the code in question is rewritten in newer commits, do you think it'd be worthwhile to instead just bump our snapshot? (since the newer code no longer relies on $USER) ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
Re: [pkg-go] go binary-only package
On 20 July 2016 at 15:53, Potter, Tim (HPE Linux Support)wrote: > I haven't figured out what the best way is to create an upstream source > orig.tar.gz > file that doesn't contain the vendored source though. For packages with > releases > (as opposed to snapshots of the master branch) you can use Files-Excluded > in debian/copyright and then uscan can download and repack the upstream > source. Not sure what the best idea for git snapshot packages is yet. I usually just use "dh-make-golang" again to generate the orig tarball (throwing the rest of the files it generates away, possibly comparing "debian/control" for changes in dependencies) if the package doesn't have explicit versions (and thus "debian/watch" and potentially "Files-Excluded"). ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#830729: Bug#830729: golang-github-mitchellh-go-homedir: FTBFS: homedir_test.go:44: "/home/lamby" != "~"
On 17 July 2016 at 08:22, Chris Lambwrote: > So, I can make the tests pass if I *remove* the "HOME=" bit in > debian/rules. Sorry I can't be more help. It looks like it passes in the reproducible builds framework, but I think I might have a hunch for what's failing on your system. When I build, I build via sbuild, so it builds as my user, but sets HOME to something non-existent, hence without HOME being reset, the tests fail in sbuild (which is what the buildds use too). My _hunch_ is that whatever you're using to build (pbuilder perhaps?) is running as your user ("lamby") but not including "/etc/passwd" from your host (which "sbuild" appears to provide -- at least for the user I currently am), so when the tests try to discover the current user's home directory, it fails in the strange ways we're seeing. I'm hoping we can find an easy way to verify my theory so we can decide whether this might need to instead be an autopkgtest (which I'd rather avoid, but if it's not reasonable to expect our current "build user" to have a valid entry in "/etc/passwd" we don't have much choice). ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#830729: Bug#830729: golang-github-mitchellh-go-homedir: FTBFS: homedir_test.go:44: "/home/lamby" != "~"
On 10 July 2016 at 13:30, Chris Lambwrote: > go install -v github.com/mitchellh/go-homedir > github.com/mitchellh/go-homedir > debian/rules override_dh_auto_test > make[1]: Entering directory > '/home/lamby/temp/cdt.20160710222637.V3OyQr9oAG.golang-github-mitchellh-go-homedir/golang-github-mitchellh-go-homedir-0.0~git20150831.0.df55a15' > # explicitly unset HOME to force tests to shell out > HOME= dh_auto_test > go test -v github.com/mitchellh/go-homedir > === RUN TestDir > --- FAIL: TestDir (0.00s) > homedir_test.go:44: "/home/lamby" != "~" > === RUN TestExpand > --- FAIL: TestExpand (0.00s) > homedir_test.go:97: Input: "~/foo" > > Output: "~/foo" > FAIL > exit status 1 > FAIL github.com/mitchellh/go-homedir 0.005s > dh_auto_test: go test -v github.com/mitchellh/go-homedir returned exit code > 1 > debian/rules:4: recipe for target 'override_dh_auto_test' failed > make[1]: *** [override_dh_auto_test] Error 1 > make[1]: Leaving directory > '/home/lamby/temp/cdt.20160710222637.V3OyQr9oAG.golang-github-mitchellh-go-homedir/golang-github-mitchellh-go-homedir-0.0~git20150831.0.df55a15' I can't seem to reproduce this failure. :( debian/rules override_dh_auto_test make[1]: Entering directory '/<>' # explicitly unset HOME to force tests to shell out HOME= dh_auto_test go test -v -p 1 github.com/mitchellh/go-homedir === RUN TestDir --- PASS: TestDir (0.00s) === RUN TestExpand --- PASS: TestExpand (0.00s) PASS ok github.com/mitchellh/go-homedir 0.010s make[1]: Leaving directory '/<>' fakeroot debian/rules binary dh binary --buildsystem=golang --with=golang dh_testroot -O--buildsystem=golang dh_prep -O--buildsystem=golang dh_auto_install -O--buildsystem=golang ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#830656: Bug#830656: Bug#830656: src:golang-github-docker-libnetwork: FTBFS due to libkv changes
On 9 July 2016 at 16:06, Dmitry Smirnovwrote: > Thank you very much, Tianon. :) > > Would you prefer if I upgrade libnetwork to v0.7.2-rc.1 ? Sure, that'd be great! This patch wasn't backported to 0.7.2 though, was it? (not seeing it in https://github.com/docker/libnetwork/compare/v0.7.0-rc.6...v0.7.2-rc.1) ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#830656: src:golang-github-docker-libnetwork: FTBFS due to libkv changes
Package: src:golang-github-docker-libnetwork Version: 0.7.0~rc.6+dfsg-2 Severity: serious The newest upload of "docker-libkv" changed the API slightly, causing the current libnetwork version to FTBFS. | # github.com/docker/libnetwork/datastore | src/github.com/docker/libnetwork/datastore/cache.go:47: undefined: boltdb.ErrBoltBucketNotFound https://github.com/docker/libnetwork/commit/b6b3642560f59f930d1ecf49d2991d74077d05f9 (https://github.com/docker/libnetwork/pull/1120) from upstream appears to be the appropriate fix. I've done a build test with the attached patch (downloaded via https://github.com/docker/libnetwork/commit/b6b3642560f59f930d1ecf49d2991d74077d05f9.patch and only DEP-3 headers modified), and it appears to resolve the issue. ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 Subject: Remove kvstore deps from datastore package Author: Jana RadhakrishnanApplied-Upstream: https://github.com/docker/libnetwork/commit/b6b3642560f59f930d1ecf49d2991d74077d05f9, https://github.com/docker/libnetwork/pull/1120, v0.8.0-dev.2 diff --git a/bitseq/sequence_test.go b/bitseq/sequence_test.go index d435329..339f592 100644 --- a/bitseq/sequence_test.go +++ b/bitseq/sequence_test.go @@ -8,6 +8,7 @@ import ( "time" "github.com/docker/libkv/store" + "github.com/docker/libkv/store/boltdb" "github.com/docker/libnetwork/datastore" _ "github.com/docker/libnetwork/testutils" ) @@ -16,6 +17,10 @@ const ( defaultPrefix = "/tmp/libnetwork/test/bitseq" ) +func init() { + boltdb.Register() +} + func randomLocalStore() (datastore.DataStore, error) { tmp, err := ioutil.TempFile("", "libnetwork-") if err != nil { diff --git a/datastore/cache.go b/datastore/cache.go index 08c8ac4..2d00038 100644 --- a/datastore/cache.go +++ b/datastore/cache.go @@ -5,7 +5,6 @@ import ( "sync" "github.com/docker/libkv/store" - "github.com/docker/libkv/store/boltdb" ) type kvMap map[string]KVObject @@ -42,9 +41,7 @@ func (c *cache) kmap(kvObject KVObject) (kvMap, error) { kvList, err := c.ds.store.List(keyPrefix) if err != nil { - // In case of BoltDB it may return ErrBoltBucketNotFound when no writes - // have ever happened on the db bucket. So check for both err codes - if err == store.ErrKeyNotFound || err == boltdb.ErrBoltBucketNotFound { + if err == store.ErrKeyNotFound { // If the store doesn't have anything then there is nothing to // populate in the cache. Just bail out. goto out diff --git a/datastore/datastore.go b/datastore/datastore.go index c15cd62..49affc7 100644 --- a/datastore/datastore.go +++ b/datastore/datastore.go @@ -9,10 +9,6 @@ import ( "github.com/docker/libkv" "github.com/docker/libkv/store" - "github.com/docker/libkv/store/boltdb" - "github.com/docker/libkv/store/consul" - "github.com/docker/libkv/store/etcd" - "github.com/docker/libkv/store/zookeeper" "github.com/docker/libnetwork/discoverapi" "github.com/docker/libnetwork/types" ) @@ -148,13 +144,6 @@ func makeDefaultScopes() map[string]*ScopeCfg { var defaultRootChain = []string{"docker", "network", "v1.0"} var rootChain = defaultRootChain -func init() { - consul.Register() - zookeeper.Register() - etcd.Register() - boltdb.Register() -} - // DefaultScopes returns a map of default scopes and it's config for clients to use. func DefaultScopes(dataDir string) map[string]*ScopeCfg { if dataDir != "" { @@ -411,6 +400,9 @@ func (ds *datastore) PutObjectAtomic(kvObject KVObject) error { _, pair, err = ds.store.AtomicPut(Key(kvObject.Key()...), kvObjValue, previous, nil) if err != nil { + if err == store.ErrKeyExists { + return ErrKeyModified + } return err } @@ -571,6 +563,9 @@ func (ds *datastore) DeleteObjectAtomic(kvObject KVObject) error { } if _, err := ds.store.AtomicDelete(Key(kvObject.Key()...), previous); err != nil { + if err == store.ErrKeyExists { + return ErrKeyModified + } return err } diff --git a/drivers/bridge/bridge_store.go b/drivers/bridge/bridge_store.go index eca72bd..de96352 100644 --- a/drivers/bridge/bridge_store.go +++ b/drivers/bridge/bridge_store.go @@ -6,7 +6,6 @@ import ( "net" "github.com/Sirupsen/logrus" - "github.com/docker/libkv/store/boltdb" "github.com/docker/libnetwork/datastore" "github.com/docker/libnetwork/discoverapi" "github.com/docker/libnetwork/netlabel" @@ -35,7 +34,7 @@ func (d *driver) initStore(option map[string]interface{}) error { func (d *driver) populateNetworks() error { kvol, err := d.store.List(datastore.Key(bridgePrefix), {}) - if err != nil && err != datastore.ErrKeyNotFound && err != boltdb.ErrBoltBucketNotFound { + if err != nil && err != datastore.ErrKeyNotFound { return fmt.Errorf("failed to get bridge network configurations from store: %v", err) } diff --git a/drivers/ipvlan/ipvlan_store.go b/drivers/ipvlan/ipvlan_store.go index f6746da..c643083 100644 --- a/drivers/ipvlan/ipvlan_store.go +++ b/drivers/ipvlan/ipvlan_store.go @@ -5,7
[pkg-go] Bug#830519: Bug#830519: docker-swarm: FTBFS: docker/swarm/api/flusher.go:8:2: cannot find package "github.com/docker/docker/pkg/ioutils"
On 8 July 2016 at 14:29, Chris Lambwrote: > src/github.com/docker/swarm/api/flusher.go:8:2: cannot find package > "github.com/docker/docker/pkg/ioutils" in any of: This sounds like another case of #830478, which should've been fixed with src:docker.io 1.11.2~ds1-2 (uploaded this morning). ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
Re: [pkg-go] Two remaining uploads for docker 1.11.0
On 23 May 2016 at 16:09, Potter, Tim (HPE Linux Support)wrote: > * golang-gocapability-dev (new upstream snapshot, various minor packaging > updates) > * golang-github-docker-go (new package, ITP #822219) By my own count, we've got a little bit more than that to get us all the way: | golang-github-docker-libnetwork-dev is version constrainted >= 0.7.0~rc.7~. (???) | golang-github-docker-notary-dev is version constrainted >= 0.2.0~. (???) | golang-gocapability-dev is version constrainted >= 0.0~git20150716~. (https://bugs.debian.org/823464) | golang-google-grpc-dev is version constrainted >= 0.0~git20151216~. (???) (https://people.debian.org/~tianon/todo-docker.txt) ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#823471: Bug#823471: golang-github-miekg-pkcs11: please update to latest upstream snapshot
On 4 May 2016 at 19:00, Potter, Tim (HPE Linux Support)wrote: > I've already packaged this in the repo on alioth. Once you've got a bug number assigned, be sure to update "debian/changelog" to include "(Closes: #xxx)" as appropriate -- I've done so here while reviewing your changes (which I'm preparing to upload shortly), but as a note for the future. :) ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
Re: [pkg-go] DEP-14 and backports for prometheus and docker.io
On 5 May 2016 at 18:12, Potter, Tim (HPE Linux Support)wrote: > I'm not sure whether you want to delete the master branch and set > debian-branch to > debian/sid. I think this is what you have done in some of the other pkg-go > repos you > are maintainer for. Happy to go with whatever you think is right. I like keeping sid == master, since sid is where we do our active "development" (it's our standard target when we don't have anywhere more specific in mind), so I think "master" still fits appropriately (and is still in line with DEP-14). ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#822395: Bug#822395: Bug#822395: Bug#822395: prometheus: FTBFS: cannot find package "golang.org/x/sys/unix"
On 26 April 2016 at 15:46, Michael Hudson-Doylewrote: > Could/should dh_golang provide help for getting this right? It's kinda > similar to the work I did recently to make Built-Using more accurate > -- roughly speaking one needs the -dev package to Depend: on the > Debian packages corresponding to the Go packages reported by go list > -f '{{ .Imports }}' $DH_GOPKG/... I think? > > (I'll try not to break the world so many times implementing the > feature this time :-p) IMO that'd be awesome. :) ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#821832: Bug#821832: golang-github-azure-azure-sdk-for-go: please update Azure SDK
On 20 April 2016 at 13:23, Daniel Stenderwrote: > I hope it's o.k. that I've taken charge with some of your packages ... For sure -- do what's necessary and either report and fix breakage (IMO)! <3 > Yup, it seems a "transition" is needed ... thx for the pointer, great! > I'll check that out. Yeah! "ratt" is a pretty neat tool for at least verifying the downstream effect of a new revision so you can report bugs and/or file patches. :) ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
Re: [pkg-go] [PATCH] Compute Built-Using with go list, not Build-Depends
On 14 April 2016 at 15:50, Michael Hudson-Doylewrote: > Yeah, that's the problem. I was testing with a package that set GOPATH in > rules :-( I sent the same fix to the bug, or at least tried to... Oh yep, you totally did: https://bugs.debian.org/821000#20 (which reminds me that I need to subscribe to dh-golang bugs) ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
Re: [pkg-go] [PATCH] Compute Built-Using with go list, not Build-Depends
On 14 April 2016 at 15:46, Tianon Gravi <admwig...@gmail.com> wrote: > I think this block is why that latest upload is causing everything to > fail to build -- we removed GOPATH from "sub build", but didn't add > "_set_gopath" like we did down in "sub test" to replace it, ala: (and I'm happy to actually commit and upload the fix if sECuRE gives ACK) ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
Re: [pkg-go] [PATCH] Compute Built-Using with go list, not Build-Depends
On 13 April 2016 at 17:43, Michael Hudson-Doylewrote: > @@ -156,7 +161,6 @@ sub get_targets { > sub build { > my $this = shift; > > -$ENV{GOPATH} = $this->{cwd} . '/' . $this->get_builddir(); > if (exists($ENV{DH_GOLANG_GO_GENERATE}) && $ENV{DH_GOLANG_GO_GENERATE} > == 1) { > $this->doit_in_builddir("go", "generate", "-v", @_, get_targets()); > } > @@ -166,7 +170,7 @@ sub build { > sub test { > my $this = shift; > > -$ENV{GOPATH} = $this->{cwd} . '/' . $this->get_builddir(); > +$this->_set_gopath(); > $this->doit_in_builddir("go", "test", "-v", @_, get_targets()); > } I think this block is why that latest upload is causing everything to fail to build -- we removed GOPATH from "sub build", but didn't add "_set_gopath" like we did down in "sub test" to replace it, ala: --- a/lib/Debian/Debhelper/Buildsystem/golang.pm +++ b/lib/Debian/Debhelper/Buildsystem/golang.pm @@ -161,6 +161,7 @@ sub get_targets { sub build { my $this = shift; +$this->_set_gopath(); if (exists($ENV{DH_GOLANG_GO_GENERATE}) && $ENV{DH_GOLANG_GO_GENERATE} == 1) { $this->doit_in_builddir("go", "generate", "-v", @_, get_targets()); } ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
Re: [pkg-go] Security support for packages written in Go
https://sources.debian.net/src/dh-golang/1.12/script/dh_golang/#L121 is where Built-Using is added (generated from the code above that line) https://sources.debian.net/src/dh-golang/1.12/lib/Debian/Debhelper/Buildsystem/golang.pm/#L144 is where dh-golang currently invokes "go list" (on "DH_GOPKG/..." which is set from XS-Go-Import-Path or "DH_GOLANG_BUILDPKG" which is set in d/rules) http://dave.cheney.net/2014/09/14/go-list-your-swiss-army-knife is a good overview of what "go list" is capable of ("Who depends on what?" is the interesting section which talks about -f '{{ .Imports }}' and -f '{{ .Deps }}') ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 On 5 April 2016 at 15:05, Paul Tagliamonte <paul...@debian.org> wrote: > Love this idea, I wonder if the Import-Path XS header could help resolve > packages in a proof of concept > > On Apr 5, 2016 5:54 PM, "Tianon Gravi" <tia...@debian.org> wrote: >> >> On 5 April 2016 at 14:47, Florian Weimer <f...@deneb.enyo.de> wrote: >> > We currently need these intermediate dependencies to discover all the >> > affected applications. So perhaps dh_golang needs to construct the >> > transitive closure, instead of listing just immediate build >> > dependencies. If we don't want to put this information into the >> > Packages file, maybe we can keep it in the separate debuginfo >> > packages. >> >> It _should_ be possible to adjust dh_golang to use "go list" in order >> to determine the exact full set of Go packages which the application >> code depends on, and then use _that_ list to cross-reference the files >> in /usr/share/gocode to get the real list of packages for Built-Using >> ( haven't verified whether it's feasible for dh_golang to do this, but >> it's pretty similar to how it's currently using "go list" to gather >> the list of packages to actually build). >> >> ♥, >> - Tianon >> 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 >> >> ___ >> Pkg-go-maintainers mailing list >> Pkg-go-maintainers@lists.alioth.debian.org >> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
Re: [pkg-go] Security support for packages written in Go
On 5 April 2016 at 14:47, Florian Weimerwrote: > We currently need these intermediate dependencies to discover all the > affected applications. So perhaps dh_golang needs to construct the > transitive closure, instead of listing just immediate build > dependencies. If we don't want to put this information into the > Packages file, maybe we can keep it in the separate debuginfo > packages. It _should_ be possible to adjust dh_golang to use "go list" in order to determine the exact full set of Go packages which the application code depends on, and then use _that_ list to cross-reference the files in /usr/share/gocode to get the real list of packages for Built-Using ( haven't verified whether it's feasible for dh_golang to do this, but it's pretty similar to how it's currently using "go list" to gather the list of packages to actually build). ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#819452: Bug#819452: golang-fsnotify: FTBFS, not working at all in ppc64el
forwarded 819452 https://github.com/fsnotify/fsnotify/issues/130 thanks On 28 March 2016 at 10:30, Martín Ferrariwrote: > As I reported upstream (https://github.com/fsnotify/fsnotify/issues/130), > fsnotify does not seem to work at all in ppc64el. I noticed this when trying > to > solve a FTBFS in prometheus, that can be tracked down to this module not > producing any events in that architecture. Do you think it'd make sense to exclude ppc64el and arm64 from "Architectures" on this package until that upstream bug is resolved? My own expertise in the kernel details of inotify is limited, but I don't see anything in the code of that package that ought to make it particularly unfriendly to these other architectures, so I'm not sure what other options we have. :( ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#818122: docker.io: FTBFS in stretch
On 26 March 2016 at 21:54, Dmitry Smirnovwrote: > However Docker still FTBFS for another reason unrelated to runc as far as I > can tell... It looks like an API change in the new runc (libcontainer bits): .gopath/src/github.com/docker/docker/daemon/execdriver/native/template/default_template.go:40: unknown configs.Cgroup field 'AllowAllDevices' in struct literal .gopath/src/github.com/docker/docker/daemon/execdriver/native/template/default_template.go:41: unknown configs.Cgroup field 'MemorySwappiness' in struct literal Currently digging to figure out whether Docker upstream already has a patch for the change to see how simple it'll be to convert over. ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
Re: [pkg-go] Bug#818122: docker.io: FTBFS in stretch
reassign 818122 golang-github-opencontainers-runc-dev 0.0.8+dfsg-1 retitle 818122 golang-github-opencontainers-runc-dev: missing "golang-github.com-docker-go-units" in Depends thanks On 13 March 2016 at 15:05, Santiago Vilawrote: > /usr/share/gocode/src/github.com/opencontainers/runc/libcontainer/cgroups/utils.go:16:2: > cannot find package "github.com/docker/go-units" in any of: > /usr/lib/go/src/github.com/docker/go-units (from $GOROOT) > /<>/.gopath/src/github.com/docker/go-units (from > $GOPATH) > /usr/share/gocode/src/github.com/docker/go-units > debian/rules:59: recipe for target 'override_dh_auto_build' failed Reassigning to the appropriate -dev package whose recent bump missed a Depends entry. :) ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#818320: Bug#818320: golang-golang-x-tools: FTBFS with go 1.6
On 15 March 2016 at 15:06, Michael Hudson-Doylewrote: > (or you can approve my > request to join pkg-go on alioth :-p) You're long since approved by now! ;) ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
Re: [pkg-go] consul
On 7 March 2016 at 11:50, Dmitry Smirnovwrote: > Thanks. :) I suppose it could be handy when something irrelevant is shipped > in orig.tar. After all "~dfsg" can be changed for "+dfsg" but not the other > way, at least not after upload... Yeah, sorry -- this is my main concern. I agree with Paul that switching "ds" to "dfsg" is a little bit misleading, but I'm OK conceding that one as long as we leave ourselves with some version number breathing room by using ~ instead of + (which is why I was OK with a reject since the version number of the fixed upload would be lower anyhow so would require it regardless). > Though IMHO on this instance there is nothing to fix. > Just Tianon being a bit territorial and me being impatient... :) Well, I do have to admit that I was pretty surprised to have asked for some review/sponsorship and to see that the version numbering scheme was modified without discussion, which is the crux of what felt wrong to me here. Whitespace and versioning are my main pedantic vices. I can definitely understand if you'd rather not spend any more cycles on the package after this, but I know I'd certainly appreciate the help (and my only ask would be that we switch + back to ~). Sorry for the woes! >.< ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
Re: [pkg-go] docker, consul, notary and others
On 6 March 2016 at 14:47, Dmitry Smirnovwrote: > I'm working hard to update dependencies required by new version of docker. > If that's all right with you I'd like to join you as co-maintainer of consul, > notary, docker.io and some other packages. Getting more eyes on the packages sounds reasonable, and should help get deps faster. :) > Consul 0.6.3 is currently waiting for "go-memdb" blocked by another package > in NEW; notary 0.2.0 is waiting for bugsnag blocked by revel/NEW and for > docker-distribution 2.3.0 is OK; libnetwork is almost finished and should be > ready for upload as soon as we introduce consul (can I, can I ;). > > I'm contemplating idea of uploading older version of consul, just to speed > things up. Sounds reasonable to me -- it was basically ready last I looked, just needed review and upload. Is "libnetwork" finally abstract enough that it can be used without "docker/docker" ? I think we've been shipping "src:docker.io" as multi-orig up until now specifically just for this last holdout that was too deeply integrated to package separately, so I'd love to be able to remove that complication! > Also I think we should upload notary with bundled "github.com/docker/docker" > (to avoid circular dependency on docker) and with bundled "github.com/docker/ > go" as the latter does not look like a good candidate to be shipped in its > own package. This is tricky territory, I think. Policy 4.13 is the relevant section we'll need to be careful about (https://www.debian.org/doc/debian-policy/ch-source.html#s-embeddedfiles), which does talk about "unless the included package is explicitly intended to be used in this way" (giving us some kind of leeway here) but in this case I don't think Notary is intended to be the only consumer of this code, is it? Would it be legal/make sense (within the confines of policy and good practice) to split golang-github-docker-docker-dev out from src:docker.io to help resolve these conflicts? (I've added the relevant groups to CC here so that we can hopefully get a bit of further comment on this front, since I'm sure Docker and friends won't be the last Go packages to have this kind of issue.) ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
Re: [pkg-go] Finally built docker.io 1.9.3 from nightly branch!
On 6 March 2016 at 16:08, Dmitry Smirnovwrote: > I'll take care of consul. :) Thanks Dmitry! Would you mind throwing your name on Uploaders too? (or even replacing mine outright if you'd prefer -- I don't mind either way :) ) I'm really curious about why "0.5.2~ds1-1" was switched to "0.5.2+dfsg-1" -- can you elaborate on the reasoning behind the change? ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
Re: [pkg-go] Finally built docker.io 1.9.3 from nightly branch!
On 19 February 2016 at 02:12, Potter, Tim (Converged Cloud)wrote: > Will take a look at all the other things you point out too - thanks for the > feedback. Just a note that I've just updated https://people.debian.org/~tianon/todo-docker.txt with the current state. For example, I'm not sure why src:docker-registry is stuck in the "Uploaded" state (https://buildd.debian.org/status/package.php?p=docker-registry). ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
Re: [pkg-go] golang 1.6... basically ready for upload
On 20 February 2016 at 01:22, Tianon Gravi <tia...@debian.org> wrote: > I've committed a changelog update for 1.6 to Git -- I'm curious what > lintian-overrides changes are necessary, though? (doing an sbuild now, so > I suppose I'll find out soon anyhow) Not seeing anything new show up in ftp-master-rejects: $ lintian --ftp-master-rejects ~/sbuild/golang*.changes N: 41 tags overridden (41 errors) ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
Re: [pkg-go] golang 1.6... basically ready for upload
On 18 February 2016 at 23:25, Hilko Bengenwrote: > I'll need to add some lintian-overrides and do some more testing, but I > think I could have something ready for upload by tomorrow. I've committed a changelog update for 1.6 to Git -- I'm curious what lintian-overrides changes are necessary, though? (doing an sbuild now, so I suppose I'll find out soon anyhow) ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
Re: [pkg-go] golang 1.6... basically ready for upload
On 18 February 2016 at 23:25, Hilko Bengenwrote: > May I go ahead or is someone else (Tianon?) busy on the same thing right > now? As long as you commit to Git, I'm +1! Let's get it up! :D ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
Re: [pkg-go] Finally built docker.io 1.9.3 from nightly branch!
On 18 February 2016 at 22:14, Tianon Gravi <tia...@debian.org> wrote: > On 18 February 2016 at 21:34, Potter, Tim (Converged Cloud) > <timothy.pot...@hpe.com> wrote: >> * golang-github-docker-distribution > > Hah, besides excluding one more directory of tests, it looks like I'm > the author of all the changes here. O:) This one build-depends on a newer version of src:golang-github-ncw-swift, so I've pushed that bump now. ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
Re: [pkg-go] Finally built docker.io 1.9.3 from nightly branch!
On 18 February 2016 at 22:11, Tianon Gravi <tia...@debian.org> wrote: >> * consul > > Changes here look solid! :D Arg, this one will go to NEW, so can't be source-only, and after the snafu that is #812566 I don't trust my local sbuild setup ATM. Any kind DD willing to do a review and sponsor to NEW if all looks well? ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
Re: [pkg-go] Finally built docker.io 1.9.3 from nightly branch!
On 18 February 2016 at 21:34, Potter, Tim (Converged Cloud)wrote: > * consul Changes here look solid! :D ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
Re: [pkg-go] Finally built docker.io 1.9.3 from nightly branch!
On 18 February 2016 at 21:34, Potter, Tim (Converged Cloud)wrote: > Hi everyone. I’ve finally managed to get the nightly docker.io branch > building against sid. Some > light testing was performed at it all seems to work. Hooray! > > I don’t have permission to push to the package repo on alioth, so the patches > I’ve made are > available on my user account, also in the nightly branch: > > git://anonscm.debian.org/users/tpot-guest/docker.io.git You're a modern hero, Tim (in spite of my being horrible). The patches you've added look generally sane, but I'm a little curious how you came by them (since they're somewhat less trivial than the "version bump our deps" patches we've got so far) -- mind adding a bit of DEP-3 to them to explain where they come from? (http://dep.debian.net/deps/dep3/ -- hopefully they're just backported upstream patches?) It also looks like "endophage-gotuf.patch" has a little bit of odd whitespace in it that could use "gofmt". :) Also kind of hoping the subject of this email was a typo, and that you're not somehow testing Docker 1.9.3 (which wasn't ever released). :D ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#796400: Bug#796400: Bug#796400: Bug#796400: golang-github-jacobsa-ratelimit: Non-determistically FTBFS due to unreliable timing in tests
On 18 February 2016 at 15:46, Tianon Gravi <tia...@debian.org> wrote: > Are there any other consumers of this ratelimit package that might warrant > some kind of workaround here? Seems the answer to that is "not currently in the archive, there aren't": ("dak rm -Rn golang-github-jacobsa-ratelimit") Will remove the following packages from unstable: golang-github-jacobsa-ratelimit | 0.0~git20150723.0.2ca5e0c-1 | source golang-github-jacobsa-ratelimit-dev | 0.0~git20150723.0.2ca5e0c-1 | all Maintainer: pkg-go <pkg-go-maintainers@lists.alioth.debian.org> --- Reason --- -- Checking reverse dependencies... No dependency problem found. ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#796400: Bug#796400: Bug#796400: Bug#796400: golang-github-jacobsa-ratelimit: Non-determistically FTBFS due to unreliable timing in tests
On 25 August 2015 at 10:21, Michael Stapelbergwrote: > I don’t think the intention of the test in question is to point out > performance regressions, so while I agree with your general statement > about flakyness in general, I’m not convinced it applies here. Is it worth adding a Debian patch for that test to include a "t.Skip()" for now to at least clear out the RC bug, or are you still considering doing an RM of gcsfuse entirely? Are there any other consumers of this ratelimit package that might warrant some kind of workaround here? ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#803133: Bug#803133: etcd: FTBFS on ppc64
On 12 February 2016 at 00:03, Dmitry Smirnovwrote: > Etcd upstream fixed that by bundling never snapshot of BoltDB. Looks like BoltDB upstream could do with a friendly prod to ask nicely for a new version tag to be released. :) ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
Re: [pkg-go] RFP: github-hub -- hub helps you win at git
On Sun, 13 Dec 2015 16:33:25 -0500 =?utf-8?q?Antoine_Beaupr=C3=A9?= < anar...@debian.org> wrote: > * Package name: github-hub > Version : 2.2.2 > Upstream Author : https://github.com/github/hub/graphs/contributors > * URL : https://hub.github.com/ > * License : MIT > Programming Lang: Go > Description : hub helps you win at git I've started packaging for this in https://anonscm.debian.org/cgit/pkg-go/packages/hub.git/ (cgit hasn't updated yet, but it should show up shortly). I've noted in the changelog which deps I couldn't find in the archive yet that are blocking us from moving forward further: - github.com/howeyc/gopass - github.com/inconshreveable/go-update - github.com/kballard/go-shellquote - github.com/mattn/go-colorable - github.com/octokit/go-octokit/octokit - github.com/ogier/pflag ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
Re: [pkg-go] Fwd: Updating the pkg-go Team Maintenance policy
On 31 January 2016 at 00:01, Dmitry Smirnovwrote: > Though it would be nice if anyone else say "OK" for this proposal. I feel > uncomfortable that nobody supported it and silence can't be interpreted as an > agreement. I had voiced my own +1 on the pkg-golang-devel thread [1]; I should've re-voiced it when the post was moved to a more appropriate list. I'm a member of DPMT (who uses this method) and find that it works very well there. The packages that need a little tighter control have an individual in "Maintainer:" instead of the team, but otherwise "team maintenance" really does apply. [1]: https://lists.alioth.debian.org/pipermail/pkg-golang-devel/Week-of-Mon-20151228/000196.html ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#807002: nmu: golang-golang-x-net-dev_0.0+git20151007.b846920+dfsg-1
Package: release.debian.org User: release.debian@packages.debian.org Usertags: binnmu Severity: normal X-Debbugs-CC: paul...@debian.org, pkg-go-maintainers@lists.alioth.debian.org Hello, Due to a typo of mine while preparing the upload, src:golang-go.crypto 1:0.0~git20151201.0.7b85b09-1 was uploaded and accidentally overwrote the "golang-golang-x-net-dev" binary package from src:golang-golang-x-net-dev. I've pushed a new upload of src:golang-go.crypto fixing the issue there (which is in binNEW now), but in talking with Paul he mentioned that a binNMU _should_ be enough to fix the situation with the binary package of src:golang-golang-x-net-dev, and that I ought to file a bug here with RT to get some help figuring out whether that's really sufficient (or whether we need to also do an FTP team RM or epoch bump the -net package). nmu golang-golang-x-net-dev_0.0+git20151007.b846920+dfsg-1 . all . -m 'Rebuild to bring back the proper binary packages' ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#806175: Bug#806175: Please update golang-golang-x-oauth2 to latest upstream version
On 24 November 2015 at 17:50, Potter, Tim (Converged Cloud)wrote: > This packages needs to be updated to the latest upstream version so that the > golang-google-grpc > package can also be updated to the latest upstream version. I've done a test build of a newer snapshot and it was quite successful; I'd be happy to make this bump as a team upload if you don't mind. :) ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#806179: Bug#806179: Please update golang-google-rpc to latest upstream version
On 24 November 2015 at 18:19, Potter, Tim (Converged Cloud)wrote: > This packages needs to be updated to the latest upstream version so that the > golang-github-docker-notary package can also be updated to the latest upstream > version. I've done a test build of a newer snapshot and it was quite successful; I'd be happy to make this bump as a team upload if you'd rather (pending #806175). :) ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#806481: Bug#806481: Bug#806481: Backport etcd to Jessie
On 28 November 2015 at 12:40, Matthew Dawsonwrote: > To get everything working did require a newer golang (1.4 in my case). Heh, you're in luck; Go 1.5.1 got accepted into jessie-backports just recently. :) ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
Re: [pkg-go] Bug#804187: Please upload golang-github-mattn-go-sqlite3 1.1.0_dfsg1-1
On 18 November 2015 at 12:48, Dmitry Smirnovwrote: > Sorry but I got to it first. ;) :D thanks! ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#805040: Bug#805040: consul-migrate: FTBFS on ppc64: undefined: maxMapSize
On 13 November 2015 at 08:52, Aaron M. Uckowrote: > The consul-migrate build for (big-endian) ppc64 failed: > > # github.com/boltdb/bolt > src/github.com/boltdb/bolt/db.go:85: undefined: maxMapSize > src/github.com/boltdb/bolt/db.go:85: invalid array bound maxMapSize Arg, looks like boltdb upstream doesn't support ppc64 (only ppc64le currently). :( ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#804294: boltdb: upstream version bump: 1.1.0
Awesome, consider it done! (it's uploaded now, should be hitting the archive shortly) Good luck with your exams! ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 On 10 November 2015 at 16:17, Alexandre Viau <alexan...@alexandreviau.net> wrote: > Hello Tianon, > > Feel free to make the upload, as I am currently going trough an exams > period :) > > Let me know if you have any issues, I can always find time to help. > > thank you for your work! > > On 06/11/15 07:52 PM, Tianon Gravi wrote: >> Package: src:golang-github-boltdb-bolt >> Version: 0.0~git20150715.980670a-1 >> X-Debbugs-CC: Alexandre Viau <alexan...@alexandreviau.net> >> >> It'd be really excellent if we could get a bump to the recent 1.1.0 >> release, especially since it adds support for architectures like >> arm64. :) >> >> As usual, willing to do the bump work myself as a team upload if you'd >> prefer! >> >> I've tested the following patch, and it builds successfully. I also >> tested reverse dependencies via ratt and they all build successfully >> too, so I think this is a major win: >> >> diff --git a/debian/changelog b/debian/changelog >> index 13963ae..fd83aec 100644 >> --- a/debian/changelog >> +++ b/debian/changelog >> @@ -1,3 +1,9 @@ >> +golang-github-boltdb-bolt (1.1.0-1) UNRELEASED; urgency=medium >> + >> + * Update to 1.1.0 upstream release. >> + >> + -- Tianon Gravi <tia...@debian.org> Wed, 04 Nov 2015 15:14:31 -0800 >> + >> golang-github-boltdb-bolt (0.0~git20150715.980670a-1) unstable; urgency=low >> >>* Initial release. (Closes: #781321) >> diff --git a/debian/rules b/debian/rules >> index 02f4969..b530be5 100755 >> --- a/debian/rules >> +++ b/debian/rules >> @@ -13,4 +13,4 @@ override_dh_auto_install: >> rm -rf --verbose $(TMP)/*/usr/bin >> >> override_dh_auto_test: >> - dh_auto_test -- -timeout 12000s >> + dh_auto_test -- -short >> diff --git a/debian/watch b/debian/watch >> new file mode 100644 >> index 000..6aad255 >> --- /dev/null >> +++ b/debian/watch >> @@ -0,0 +1,3 @@ >> +version=3 >> +opts=filenamemangle=s/.+\/v?(\d\S*)\.tar\.gz/bolt-$1\.tar\.gz/ \ >> + https://github.com/boltdb/bolt/tags .*/v([\d\.]+)\.tar\.gz >> >> ♥, >> - Tianon >> 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 >> > > -- > Alexandre Viau > alexan...@alexandreviau.net > ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#804294: boltdb: upstream version bump: 1.1.0
Package: src:golang-github-boltdb-bolt Version: 0.0~git20150715.980670a-1 X-Debbugs-CC: Alexandre Viau <alexan...@alexandreviau.net> It'd be really excellent if we could get a bump to the recent 1.1.0 release, especially since it adds support for architectures like arm64. :) As usual, willing to do the bump work myself as a team upload if you'd prefer! I've tested the following patch, and it builds successfully. I also tested reverse dependencies via ratt and they all build successfully too, so I think this is a major win: diff --git a/debian/changelog b/debian/changelog index 13963ae..fd83aec 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,9 @@ +golang-github-boltdb-bolt (1.1.0-1) UNRELEASED; urgency=medium + + * Update to 1.1.0 upstream release. + + -- Tianon Gravi <tia...@debian.org> Wed, 04 Nov 2015 15:14:31 -0800 + golang-github-boltdb-bolt (0.0~git20150715.980670a-1) unstable; urgency=low * Initial release. (Closes: #781321) diff --git a/debian/rules b/debian/rules index 02f4969..b530be5 100755 --- a/debian/rules +++ b/debian/rules @@ -13,4 +13,4 @@ override_dh_auto_install: rm -rf --verbose $(TMP)/*/usr/bin override_dh_auto_test: - dh_auto_test -- -timeout 12000s + dh_auto_test -- -short diff --git a/debian/watch b/debian/watch new file mode 100644 index 000..6aad255 --- /dev/null +++ b/debian/watch @@ -0,0 +1,3 @@ +version=3 +opts=filenamemangle=s/.+\/v?(\d\S*)\.tar\.gz/bolt-$1\.tar\.gz/ \ + https://github.com/boltdb/bolt/tags .*/v([\d\.]+)\.tar\.gz ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#804277: ITP: consul -- Consul is a tool for service discovery, monitoring and configuration
Package: wnpp Severity: wishlist Owner: Tianon Gravi <tia...@debian.org> X-Debbugs-CC: pkg-go-maintainers@lists.alioth.debian.org * Package name: consul Version : 0.5.2-1 Upstream Author : HashiCorp * URL : https://github.com/hashicorp/consul * License : MPL-2.0 Programming Lang: Go Description : Consul is a tool for service discovery, monitoring and configuration. Consul is a tool for service discovery and configuration. Consul is distributed, highly available, and extremely scalable. . Consul provides several key features: . - Service Discovery - Consul makes it simple for services to register themselves and to discover other services via a DNS or HTTP interface. External services such as SaaS providers can be registered as well. . - Health Checking - Health Checking enables Consul to quickly alert operators about any issues in a cluster. The integration with service discovery prevents routing traffic to unhealthy hosts and enables service level circuit breakers. . - Key/Value Storage - A flexible key/value store enables storing dynamic configuration, feature flagging, coordination, leader election and more. The simple HTTP API makes it easy to use anywhere. . - Multi-Datacenter - Consul is built to be datacenter aware, and can support any number of regions without complex configuration. . Consul runs on Linux, Mac OS X, and Windows. It is recommended to run the Consul servers only on Linux, however. This is needed for Docker 1.9.0. ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#804187: go-sqlite3: please package v1.1.0
Package: src:golang-github-mattn-go-sqlite3 Version: 1.0.0~dfsg1-2 It'd be really helpful if we could get a bump to v1.1.0 released on Sep 5th. :) (Needing this for Docker 1.9.0.) As usual, willing to do the bump work myself as a team upload if you'd prefer! ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#803388: Bug#803388: golang-gopkg-mgo.v2-dev: over-aggressive depends
Alexandre, On 29 October 2015 at 12:51, Tianon Gravi <tia...@debian.org> wrote: > On 29 October 2015 at 07:35, Tianon Gravi <tia...@debian.org> wrote: >> Currently, the -dev package depends on both mongodb-server and >> supervisor. I can't see a reason for supervisor to be in any of the >> relations of this package, but mongodb-server really ought to be in >> Suggests instead since it's not necessary for it to be installed for >> the proper user of the -dev package. :) > > I'd also add that I'm happy to make the modification myself if you'd prefer. > :) Mind if I make a fix for this and do a "Team Upload"? Was there a particular reason for these packages to be in Depends instead of just Suggests? Was there a reason for supervisor to be listed at all? I'm having trouble seeing rationale but I don't want to step on toes. :) ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#803321: Bug#803321: [Reproducible-builds] Bug#803321: rawdns: FTBFS: cp: cannot stat 'debian/tmp/debian/tmp/dh-exec.ShSIquIE/etc/rawdns.json': No such file or
On 28 October 2015 at 12:55, Niko Tyniwrote: > Looks like #802034, fixed today in dh-exec_0.22. Indeed! https://reproducible.debian.net/rb-pkg/unstable/amd64/rawdns.html appears happy now, so I'm going to close this. Thanks Chris for the heads up and thanks Niko for the pointer to the dh-exec issue that caused it! ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#803388: golang-gopkg-mgo.v2-dev: over-aggressive depends
Package: golang-gopkg-mgo.v2-dev Version: 2015.06.03-2 Currently, the -dev package depends on both mongodb-server and supervisor. I can't see a reason for supervisor to be in any of the relations of this package, but mongodb-server really ought to be in Suggests instead since it's not necessary for it to be installed for the proper user of the -dev package. :) ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#803388: Bug#803388: golang-gopkg-mgo.v2-dev: over-aggressive depends
On 29 October 2015 at 07:35, Tianon Gravi <tia...@debian.org> wrote: > Currently, the -dev package depends on both mongodb-server and > supervisor. I can't see a reason for supervisor to be in any of the > relations of this package, but mongodb-server really ought to be in > Suggests instead since it's not necessary for it to be installed for > the proper user of the -dev package. :) I'd also add that I'm happy to make the modification myself if you'd prefer. :) ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#803321: Bug#803321: rawdns: FTBFS: cp: cannot stat 'debian/tmp/debian/tmp/dh-exec.ShSIquIE/etc/rawdns.json': No such file or
On 28 October 2015 at 12:08, Chris Lambwrote: > rawdns fails to build from source in unstable/amd64: I just tested this in a fresh sbuild schroot and I can't seem to reproduce the failure (the package builds just fine here). Any ideas for how I could more easily reproduce the failure? ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#803130: Bug#803130: libdevel-cover-perl and golang-golang-x-tools: error when trying to install together
On 27 October 2015 at 01:28, Ralf Treinenwrote: > Here is a list of files that are known to be shared by both packages > (according to the Contents file for sid/amd64, which may be > slightly out of sync): > > /usr/bin/cover Doh -- I'll update golang-golang-x-tools to not build this binary anymore since it's included in "golang-go" now. Thanks for the pointer! ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#802988: golang-golang-x-tools conflict with golang-go
block 802945 802988 thanks Thanks for the reports and patches, Hilko and Russ! I've got the go-ahead from sECuRE to upload a fixed golang-golang-x-tools, so I'm going to take care of this conflict shortly. :) ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#802787: Bug#802787: golang-github-tinylib-msgp: FTBFS: constant 2147483747 overflows int
fixed 802787 golang-github-tinylib-msgp/1.0~alpha-2 thanks On 23 October 2015 at 15:50, Tianon Gravi <admwig...@gmail.com> wrote: > My patch was merged upstream and I've uploaded a new build, but I'm > holding off closing the bug until I see whether the buildds actually > build it successfully. :) Success! Thanks again for the report! :) ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#802787: golang-github-tinylib-msgp: FTBFS: constant 2147483747 overflows int
fowarded 802787 https://github.com/tinylib/msgp/pull/135 thanks Thanks for the report -- I've sent a patch upstream, and will apply a fix to the package as soon as they've merged a fix there. :) ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#802787: Bug#802787: golang-github-tinylib-msgp: FTBFS: constant 2147483747 overflows int
On 23 October 2015 at 08:24, Aaron M. Uckowrote: > Builds of golang-github-tinylib-msgp for 32-bit architectures such as > i386 have been failing: My patch was merged upstream and I've uploaded a new build, but I'm holding off closing the bug until I see whether the buildds actually build it successfully. :) ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#801593: Bug#801593: Bug#801593: ratt does not find all reverse build dependencies
On 14 October 2015 at 22:37, Johannes Schauerwrote: > Extracting all binary packages introduced by your upload is trivial. Just look > at the Binary: field in your .changes file. Just to note, in the case of Paul's interface in "pault.ag/go/debian/control", that'd be changes.Binaries [1]. :) [1]: https://godoc.org/pault.ag/go/debian/control#Changes ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
Re: [pkg-go] Plans for uploading Go 1.5 to unstable?
Sure! :) On the Docker end, the discussion is in https://github.com/docker/docker/pull/15703 (and you're correct that it's Docker doing something "wrong", but isn't it still worth checking so we don't get random FTBFS? or do we just not worry about it and do something about them as they come?) ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 On 15 October 2015 at 11:08, Michael Stapelberg <stapelb...@debian.org> wrote: > Do you have a link with details? I’m curious. > > On Thu, Oct 15, 2015 at 7:45 PM, Tianon Gravi <admwig...@gmail.com> wrote: >> >> On 15 October 2015 at 10:40, Michael Stapelberg <stapelb...@debian.org> >> wrote: >> > FWIW, I don’t think that’s necessary for the compiler itself. Go adheres >> > to >> > its Go 1 stability guarantee, and any package which breaks likely did >> > something wrong in the first place :). If this is the only thing that’s >> > holding back the upload, I’d recommend to just go ahead with the upload. >> >> Right, in theory, that's supposed to be the case. I've seen several >> examples already where that's not the case, including Docker itself. >> >> ♥, >> - Tianon >> 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 > > > > > -- > Best regards, > Michael ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
Re: [pkg-go] Plans for uploading Go 1.5 to unstable?
On 15 October 2015 at 10:40, Michael Stapelbergwrote: > FWIW, I don’t think that’s necessary for the compiler itself. Go adheres to > its Go 1 stability guarantee, and any package which breaks likely did > something wrong in the first place :). If this is the only thing that’s > holding back the upload, I’d recommend to just go ahead with the upload. Right, in theory, that's supposed to be the case. I've seen several examples already where that's not the case, including Docker itself. ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#801595: Bug#801595: Bug#801595: ratt calls sbuild in a way that uses the user's sbuildrc
On 14 October 2015 at 10:06, Michael Stapelbergwrote: > I’m a bit hesitant to do this. If a user specified custom settings in their > ~/.sbuildrc, they are probably there for a reason and should be considered > when using ratt, right? I'm not exactly a long-time user of sbuild, but I'd definitely be very surprised if ratt _didn't_ use my ~/.sbuildrc when invoking sbuild. :) ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#801558: Bug#801558: Bug#801558: golang-codegangsta-cli-dev: fails to upgrade from 'testing' - trying to overwrite /usr/share/gocode/src/github.com/codegangsta/cli/command.go
On 12 October 2015 at 10:20, Tianon Gravi <admwig...@gmail.com> wrote: > | Replaces: golang-codegangsta-cli-dev (<< 0.0~git20150117-1~) > | Breaks: golang-codegangsta-cli-dev (<< 0.0~git20150117-1~) > | Provides: golang-codegangsta-cli-dev > > Are the version numbers wrong or something similarly simple I've overlooked? Doh, that's exactly it -- these should've been "(<< 0.0~git20150117-2~)" (not "-1"). ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#801558: Bug#801558: golang-codegangsta-cli-dev: fails to upgrade from 'testing' - trying to overwrite /usr/share/gocode/src/github.com/codegangsta/cli/command.go
On 11 October 2015 at 21:56, Andreas Beckmannwrote: > It installed fine in 'testing', then the upgrade to 'sid' fails > because it tries to overwrite other packages files without declaring a > Breaks+Replaces relation. Hmm, this seems strange, because "golang-github-codegangsta-cli-dev" does have a Replaces/Breaks/Provides combo: | Replaces: golang-codegangsta-cli-dev (<< 0.0~git20150117-1~) | Breaks: golang-codegangsta-cli-dev (<< 0.0~git20150117-1~) | Provides: golang-codegangsta-cli-dev Are the version numbers wrong or something similarly simple I've overlooked? ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
Re: [pkg-go] golang-github-miekg-pkcs11_0.0~git20150918.0.44a65bd-1_amd64.changes REJECTED
On 11 October 2015 at 09:00, Thorsten Alteholzwrote: > please add the missing license of Researching where these .h files came from was definitely a very interesting history lesson in PKCS #11. O:) Thanks for pointing these out; I've got a new upload up which includes an entry referencing them now. :) ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#798649: Bug#798649: Bug#798649: golang-golang-x-net-dev: new upstream release?
On 13 September 2015 at 11:12, Martín Ferrariwrote: > Sure, I will look into it later today or tomorrow. It's been a bit since this message; mind if I take a stab at bumping it for you? :) ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
Re: [pkg-go] Building the race detector runtime support from source
This is neat! Any particular reason you went straight for an SVN snapshot instead of http://llvm.org/releases/3.7.0/compiler-rt-3.7.0.src.tar.xz ? Just because that's what the Go README does, or was there some kind of incompatibility? Also, does anyone know if there's already a source package consuming the compiler-rt tarball that we could maybe patch to run this script into a new binary package? :) ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 On 8 October 2015 at 00:27, Michael Hudson-Doylewrote: > Hi there, > > It was pointed out during the review of my Go 1.5 package for Ubuntu > that the current go packaging includes files for race detector support > that is not built from source included in the source package, so I > made a package that does build them from source (basically it turns > the instructions from > https://go.googlesource.com/go/+/master/src/runtime/race/README into a > debian/rules file). It seems to me that it would make sense to do this > in Debian too? You can grab the package from here: > > https://launchpad.net/ubuntu/+source/golang-race-detector-runtime/0.0+svn229396-0ubuntu1 > > Cheers, > mwh > > ___ > Pkg-go-maintainers mailing list > Pkg-go-maintainers@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
Re: [pkg-go] Building the race detector runtime support from source
On 8 October 2015 at 06:50, Tianon Gravi <tia...@debian.org> wrote: > Also, does anyone know if there's already a source package consuming > the compiler-rt tarball that we could maybe patch to run this script > into a new binary package? :) Turns out src:llvm-toolchain-3.5 is a multi-orig that includes compiler-rt. O:) ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
Re: [pkg-go] Bug#799907: golang 1.5 does not build under arm64
On 23 September 2015 at 20:45, Potter, Tim (Converged Cloud)wrote: > Hi there. I’ve found and fixed a build bug on arm64 for golang in the > delian-experimental branch, > fixed by the attached patch. According to the GoArm page on the golang wiki > [1] GOARCH needs > to be set to arm64. Nice catch, thanks! > The patch also includes a fix for the “unrecognised build host instruction > set” > error, where the error message displays $BUILD_HOST_ARCH_CPU when the > variable being > checked is DEB_BUILD_ARCH_CPU which I think it not what’s intended. Fantastic! I've pushed this and a few other fixes to this section of the debian/rules file to the branch; mind giving it a try? :) ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
Re: [pkg-go] golang-github-azure-azure-sdk-for-go_1.2~git20150611.0.97d9593-1_amd64.changes REJECTED
On 14 September 2015 at 09:00, Thorsten Alteholzwrote: > Please mention the BSD license in your debian/copyright Jeez, I'm on a roll... Thanks so much for your help catching all these! :) I'll make some changes to my workflow to (hopefully) help me catch these myself sooner. ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
Re: [pkg-go] RFS: golang-github-bitly-simplejson
On 13 September 2015 at 10:07, Paul Tagliamontewrote: > To -alpha or ~alpha? Also, upstream has nice version tags[1], so why are we packaging a snapshot instead of using debian/watch and a direct release version? Is there a package that needs newer commits? If so, have we asked upstream to tag a new version? :) [1]: https://github.com/bitly/go-simplejson/releases ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
Re: [pkg-go] etcd.git
On 9 September 2015 at 00:01, Dmitry Smirnovwrote: > I have no idea how could this happen... I've never touched any files in > etcd.git bare repository other than remotely pushing from my workstation just > like I do with all other repositories all the time... > > I did > > chmod -c -R g+w objects > > so I hope you'll be able to push... Bizarre; thanks for taking a look and fixing it! >> Mind fixing those and/or applying the attached patch? > > Done. Good idea to rename dependencies. Thank you. Excellent, thanks! :) ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
Re: [pkg-go] golang-github-vbatts-tar-split_0.9.7-1_amd64.changes REJECTED
On 8 September 2015 at 12:00, Thorsten Alteholzwrote: > please mention the files that are (C) from go authors and licensed under > BSD in your debian/copyright. Doh. Thanks for the pointer! I'll update d/copyright appropriately and re-upload. :) ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#798422: lintian: please add "go-import-path" to the list of allowed source fields
Package: src:lintian Severity: wishlist Tags: patch X-Debbugs-CC: pkg-go-maintainers@lists.alioth.debian.org This field is used by dh-golang[1][2] to determine the proper location inside /usr/share/gocode for the files of the package, and is useful for other automation too. I've attached the basic patch that adds this, even though the change is pretty trivial. I'd be happy to adapt it if I've done something wrong or could be more helpful. :) [1]: https://sources.debian.net/src/dh-golang/1.12/lib/Debian/Debhelper/Buildsystem/golang.pm/#L27-L36 [2]: https://tracker.debian.org/news/702962 ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 From c64a0e46299cffd7faad3a937106e655d47c5428 Mon Sep 17 00:00:00 2001 From: Tianon Gravi <tia...@debian.org> Date: Tue, 8 Sep 2015 19:48:59 -0700 Subject: [PATCH] d/common/source-fields: Add "go-import-path" field --- data/common/source-fields | 1 + 1 file changed, 1 insertion(+) diff --git a/data/common/source-fields b/data/common/source-fields index 329c3dd..4ef6e4c 100644 --- a/data/common/source-fields +++ b/data/common/source-fields @@ -27,6 +27,7 @@ origin # disappear without notice @if-vendor-is-not debian original-maintainer +go-import-path package-list python-version ruby-versions -- 2.4.6 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] etcd.git
Hey onlyjob, was trying to push a minor update to the Build-Depends for etcd to add | relations for the expanded names of dependencies (especially for #797903), but found that some of the subfolders inside "objects" on git.d.o have broken permissions: tianon@moszumanska:/git/pkg-go/packages/etcd.git/objects$ ls -lAFh total 848K drwxrwsr-x 2 jelmer scm_pkg-go 4.0K Sep 8 06:10 00/ drwxrwsr-x 2 jelmer scm_pkg-go 4.0K Feb 17 2015 01/ drwxrwsr-x 2 jelmer scm_pkg-go 4.0K Sep 8 05:49 02/ drwxr-sr-x 2 onlyjob scm_pkg-go 4.0K Sep 8 05:49 03/ drwxrwsr-x 2 jelmer scm_pkg-go 4.0K Feb 17 2015 04/ drwxrwsr-x 2 jelmer scm_pkg-go 4.0K Sep 8 06:41 05/ Mind fixing those and/or applying the attached patch? Thanks! ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 From 9bafc7e4b328be81c1951246714b745d9197ba96 Mon Sep 17 00:00:00 2001 From: Tianon Gravi <admwig...@gmail.com> Date: Tue, 8 Sep 2015 21:46:39 -0700 Subject: [PATCH] Update a few old-style "golang-" Build-Depends values to use "|" with their new proper names to help with transitioning the dependencies See https://bugs.debian.org/797903#10, for example. --- debian/control | 36 ++-- 1 file changed, 18 insertions(+), 18 deletions(-) diff --git a/debian/control b/debian/control index 38effe4..ecfbb24 100644 --- a/debian/control +++ b/debian/control @@ -7,32 +7,32 @@ Uploaders: Jelmer Vernooij <jel...@debian.org>, Build-Depends: debhelper (>= 9), dh-golang (>= 1.6), dh-systemd, - golang-clockwork-dev, - golang-procfs-dev, - golang-codegangsta-cli-dev, - golang-context-dev, - golang-coreos-log-dev, - golang-etcd-dev, + golang-github-jonboulle-clockwork-dev | golang-clockwork-dev, + golang-github-prometheus-procfs-dev | golang-procfs-dev, + golang-github-codegangsta-cli-dev | golang-codegangsta-cli-dev, + golang-github-gorilla-context-dev | golang-context-dev, + golang-github-coreos-go-log-dev | golang-coreos-log-dev, + golang-github-coreos-go-etcd-dev | golang-etcd-dev, golang-github-bradfitz-http2-dev, golang-github-boltdb-bolt-dev, golang-github-google-btree-dev, golang-github-ugorji-go-codec-dev, - golang-glog-dev, + golang-github-golang-glog-dev | golang-glog-dev, golang-golang-x-net-dev, - golang-go-semver-dev, - golang-prometheus-client-dev, - golang-go.crypto-dev, + golang-github-coreos-go-semver-dev | golang-go-semver-dev, + golang-github-prometheus-client-golang-dev | golang-prometheus-client-dev, + golang-golang-x-go.crypto-dev | golang-go.crypto-dev, golang-golang-x-oauth2-dev, golang-go, golang-go.tools, - golang-gogoprotobuf-dev (>= 0.0~git20150828~), - golang-goprotobuf-dev, - golang-protobuf-extensions-dev, - golang-metrics-dev, - golang-mux-dev, - golang-objx-dev, - golang-testify-dev, - golang-toml-dev, + golang-github-gogo-protobuf-dev (>= 0.0~git20150828~) | golang-gogoprotobuf-dev (>= 0.0~git20150828~), + golang-github-golang-protobuf-dev | golang-goprotobuf-dev, + golang-github-matttproud-golang-protobuf-extensions-dev | golang-protobuf-extensions-dev, + golang-github-rcrowley-go-metrics-dev | golang-metrics-dev, + golang-github-gorilla-mux-dev | golang-mux-dev, + golang-github-stretchr-objx-dev | golang-objx-dev, + golang-github-stretchr-testify-dev | golang-testify-dev, + golang-github-burntsushi-toml-dev | golang-toml-dev, libprotobuf-dev, protobuf-compiler Standards-Version: 3.9.6 -- 2.4.6 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#794454: src:dh-make-golang has incorrect Vcs-*
Package: src:dh-make-golang Version: 0.0~git20150726.0.fc4210a-1 Tags: patch Vcs-Git and Vcs-Browser point to golang-github-debian-dh-make-golang instead of just dh-make-golang. I've attached a simple patch which could be used to correct these. :) ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 From 882bd38e0f324991b0593270ff1151adc94b6e74 Mon Sep 17 00:00:00 2001 From: Tianon Gravi admwig...@gmail.com Date: Mon, 3 Aug 2015 01:25:29 -0700 Subject: [PATCH] Fix Vcs-* headers --- debian/control | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/debian/control b/debian/control index 78fd304..59a4fa0 100644 --- a/debian/control +++ b/debian/control @@ -12,8 +12,8 @@ Build-Depends: debhelper (= 9), git Standards-Version: 3.9.6 Homepage: https://github.com/Debian/dh-make-golang -Vcs-Browser: http://anonscm.debian.org/gitweb/?p=pkg-go/packages/golang-github-debian-dh-make-golang.git;a=summary -Vcs-Git: git://anonscm.debian.org/pkg-go/packages/golang-github-debian-dh-make-golang.git +Vcs-Browser: https://anonscm.debian.org/cgit/pkg-go/packages/dh-make-golang.git +Vcs-Git: git://anonscm.debian.org/pkg-go/packages/dh-make-golang.git Package: dh-make-golang Architecture: any -- 2.4.6 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers