[pkg-go] gbp: how to import upstream tarball without tag?

2015-09-02 Thread Dmitry Smirnov
Hi, Alexandre Could you please advise how can I import upstream tarball from remote repo if upstream do not tag their releases? Recently you did it somehow for "golang- gogoprotobuf" so I hope you could share the secret knowledge with me. :) Thank you. -- All the best, Dmitry Smirnov. ---

[pkg-go] Processing of golang-github-jtolds-gls_0.0~git20150401.0.9a4a02d-1_amd64.changes

2015-09-02 Thread Debian FTP Masters
golang-github-jtolds-gls_0.0~git20150401.0.9a4a02d-1_amd64.changes uploaded successfully to localhost along with the files: golang-github-jtolds-gls_0.0~git20150401.0.9a4a02d-1.dsc golang-github-jtolds-gls_0.0~git20150401.0.9a4a02d.orig.tar.bz2

[pkg-go] Processing of golang-gopkg-asn1-ber.v1_1-1_amd64.changes

2015-09-02 Thread Debian FTP Masters
golang-gopkg-asn1-ber.v1_1-1_amd64.changes uploaded successfully to localhost along with the files: golang-gopkg-asn1-ber.v1_1-1.dsc golang-gopkg-asn1-ber.v1_1.orig.tar.gz golang-gopkg-asn1-ber.v1_1-1.debian.tar.xz golang-gopkg-asn1-ber.v1-dev_1-1_all.deb Greetings, Your Debian

[pkg-go] golang-github-jacobsa-ratelimit is marked for autoremoval from testing

2015-09-02 Thread Debian testing autoremoval watch
golang-github-jacobsa-ratelimit 0.0~git20150723.0.2ca5e0c-1 is marked for autoremoval from testing on 2015-09-19 It is affected by these RC bugs: 796400: golang-github-jacobsa-ratelimit: Non-determistically FTBFS due to unreliable timing in tests

[pkg-go] Processing of golang-pault-go-debian_0.4-1_amd64.changes

2015-09-02 Thread Debian FTP Masters
golang-pault-go-debian_0.4-1_amd64.changes uploaded successfully to localhost along with the files: golang-pault-go-debian_0.4-1.dsc golang-pault-go-debian_0.4.orig.tar.gz golang-pault-go-debian_0.4-1.debian.tar.xz golang-pault-go-debian-dev_0.4-1_all.deb Greetings, Your Debian

[pkg-go] golang-pault-go-debian_0.4-1_amd64.changes ACCEPTED into unstable

2015-09-02 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 02 Sep 2015 16:16:31 -0400 Source: golang-pault-go-debian Binary: golang-pault-go-debian-dev Architecture: source all Version: 0.4-1 Distribution: unstable Urgency: medium Maintainer: pkg-go

[pkg-go] Processed: your mail

2015-09-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 793518 0.0~git20150730-1 Bug #793518 [src:golang-github-glacjay-goini] FTBFS: TestString fails: ini_test.go:167: Dict cannot be stringified as expected. Ignoring request to alter fixed versions of bug #793518 to the same values previously

Re: [pkg-go] gbp: how to import upstream tarball without tag?

2015-09-02 Thread Michael Stapelberg
I just use dh-make-golang to produce new upstream tarballs. See also https://github.com/Debian/dh-make-golang/issues/14 On Wed, Sep 2, 2015 at 4:46 AM, Dmitry Smirnov wrote: > On Wednesday 02 September 2015 12:52:56 Martín Ferrari wrote: >> There is a very well documented and

Re: [pkg-go] gbp: how to import upstream tarball without tag?

2015-09-02 Thread Dmitry Smirnov
Thank you for reply, Martín. On Wednesday 02 September 2015 11:22:46 Martín Ferrari wrote: > On 02/09/15 10:54, Dmitry Smirnov wrote: > > Could you please advise how can I import upstream tarball from remote > > repo if upstream do not tag their releases? Recently you did it somehow > > for

Re: [pkg-go] gbp: how to import upstream tarball without tag?

2015-09-02 Thread Dmitry Smirnov
On Wednesday 02 September 2015 04:56:30 Michael Stapelberg wrote: > I just use dh-make-golang to produce new upstream tarballs. See also > https://github.com/Debian/dh-make-golang/issues/14 That's how I generated upstream tarball in the end. :) But it would be much nicer to be able to do that

Re: [pkg-go] Bug#797702: ITP: grafana -- feature rich metrics dashboard and graph editor

2015-09-02 Thread Dmitry Smirnov
Draft packaging is committed to http://anonscm.debian.org/cgit/collab-maint/grafana.git It is already useful but more work is needed to package golang dependencies and document licenses/copyrights of the files in "public" folder. Help is appreciated and welcome. :) -- Regards, Dmitry