[pkg-go] Bug#890501: Bug#890501: prometheus startup fails due to racey PID file implementation in prometheus

[Martín Ferrari]

fixed 890501 2.2.0+ds-1
thanks

Due to some mistake in my workflow, a couple of changelog entries went
missing in 2.2.0+ds-1, and so this bug was never closed. I added the
entries retrospectively, and closing manually the bug now..

-- 
Martín Ferrari (Tincho)

___
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] pkg-go will migrate to salsa.debian.org on 2018-04-02

[Martín Ferrari]

On 27/03/18 22:24, Alexandre Viau wrote:

> === After the migration ===

> - You may point your git working directories to the new remote address
> with this oneliner:
>  ``git remote set-url origin g...@salsa.debian.org:go-team/$(git
> config --get remote.origin.url | tr "/" "\n" | tail -n 1)``


Today I am finally updating my local repos, but this script is not good
for me, as I usually call my debian remote "debian". So I used this
instead (to fix all the repos in one directory):

for i in */; do test -d $i/.git || continue; git --git-dir=$i/.git
config --get-regexp '^remote\.[^.]*\.url$' | while read key value; do
newval=$(echo $value | sed
's#.*/git/pkg-go/packages/\([^/]*\.git\)/\?$#g...@salsa.debian.org:go-team/packages/\1#');
test "$value" != "$newval" || continue ; remote=$(echo $key | sed
's/^remote\.\([^.]*\)\.url$/\1/'); git --git-dir=$i/.git remote set-url
$remote $newval;  done; done



-- 
Martín Ferrari (Tincho)

___
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] DebConf18 - Anyone planning to go?

[Martín Ferrari]

On 05/04/18 15:31, Michael Stapelberg wrote:
> I’ll not be able to attend in person.
> 
> I’d be happy to review any material you come up with for the talk,
> though :).
> 
> In case there’ll be another BoF like last year, I’d like to participate
> online as timezones permit.

Same from me, on the three items :)


-- 
Martín Ferrari (Tincho)

___
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] pkg-go will migrate to salsa.debian.org on 2018-04-02

[Martín Ferrari]

On 03/04/18 05:16, Alexandre Viau wrote:

> The migration was completed.

Thank you for all your work!!


-- 
Martín Ferrari (Tincho)

___
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] Accepted prometheus 2.2.1+ds-2 (source) into unstable

[Martín Ferrari]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 29 Mar 2018 09:17:37 +
Source: prometheus
Binary: prometheus
Architecture: source
Version: 2.2.1+ds-2
Distribution: unstable
Urgency: high
Maintainer: Debian Go Packaging Team 
<pkg-go-maintainers@lists.alioth.debian.org>
Changed-By: Martín Ferrari <tin...@debian.org>
Description:
 prometheus - Monitoring system and time series database
Changes:
 prometheus (2.2.1+ds-2) unstable; urgency=high
 .
   * debian/control: Require latest TSDB version, that solves serious bugs
 in the DB.
Checksums-Sha1:
 2e1c0261044e2e507235e4889026fc724971ecbe 3319 prometheus_2.2.1+ds-2.dsc
 525dd54129c1c4703e579ad1ab6af5c5a1428d47 26664 
prometheus_2.2.1+ds-2.debian.tar.xz
 9e87429fd4dd626e683c8aa2ed437415beeae845 11480 
prometheus_2.2.1+ds-2_amd64.buildinfo
Checksums-Sha256:
 bef3b7299dabd99efabaa6873bbc50b6e8dc92533248774160a421f6280db42d 3319 
prometheus_2.2.1+ds-2.dsc
 070e368991670a3233dfe9dd69c4bf1bd556e4a42cc3425959ca2ca818193d0d 26664 
prometheus_2.2.1+ds-2.debian.tar.xz
 5db17ed119b2cd002f7c1628af7229d4859370be7a087da8971b4f00a402aa0c 11480 
prometheus_2.2.1+ds-2_amd64.buildinfo
Files:
 adc03761b383ad5676fee7df1b42f524 3319 net optional prometheus_2.2.1+ds-2.dsc
 bf7660f99986faf54705f9f1613a5d83 26664 net optional 
prometheus_2.2.1+ds-2.debian.tar.xz
 ab8c164d62232dea28e32608311b73b5 11480 net optional 
prometheus_2.2.1+ds-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEETe94h3mvRsa9AoOeXdjgv5Gj09oFAlq8r9gACgkQXdjgv5Gj
09qs4xAAynLzVx2aUX8YYlmhf1mGNv4Jz353Oe8cr2Ec16sTWp2yAe/1bD/jmXDk
qJrWkC174lDZNfdLyDe+DngHVcC39z6Iz4Vh9RCpIkX+1cthIf1uaJmsjpeE5pLO
2wBIyvpjmM5gy82p48afjQDFCritD6ksnE//9rgPEyoYQ1m4N7duol5cqSkZzVIv
VTLPRhIpIdmLwWzsCfUSrLhbE/uwdY8lR8ffcVOkEV2TnsTSoFlI8bt0gbmh2Lqv
JYOG/9AhQRHCm3yEolvpekwWNPZqSMLyPiObJ23CKX16+mW86md3QuLuojg/jJEl
tOjRjo2n13bkJM4VfgZglu3nrzKkyLmZ+/WtrJcUSTD1h/+5fsRKHJTw1p3U+n3t
aMy2Vac44TwFw90b4kK1nw6QycS+fDgNog6CpYJhwc5mOo0RcLEvVhSW36j+LOXp
0WARynCYIn5Pf1fIvcSdJGU9zqYrNiRVf/z0+TB/EkC+5DXdimVJZ8zofhOwpjHj
FWi4OCws8503tCIUCL6i+zrlorVvov3JMEoYoyMz1ALSX2oql5vrkuivKsSC1BuA
jLoj4rR/Jnewy9h4A+P3l8jeCx2ejUDRxTm2TrZ65aeevXdlC93S+UMKcDzW2N5d
J8GcK0Svh++XYfSbXeqM0Nj8mfGLbG9pK3UhoEziXsGsSlazhsw=
=UnqL
-END PGP SIGNATURE-


___
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] Accepted golang-github-prometheus-tsdb 0.0~git20180314.659ed64-1 (source) into unstable

[Martín Ferrari]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 29 Mar 2018 09:10:38 +
Source: golang-github-prometheus-tsdb
Binary: golang-github-prometheus-tsdb-dev
Architecture: source
Version: 0.0~git20180314.659ed64-1
Distribution: unstable
Urgency: high
Maintainer: Debian Go Packaging Team 
<pkg-go-maintainers@lists.alioth.debian.org>
Changed-By: Martín Ferrari <tin...@debian.org>
Description:
 golang-github-prometheus-tsdb-dev - Prometheus storage layer library
Changes:
 golang-github-prometheus-tsdb (0.0~git20180314.659ed64-1) unstable; 
urgency=high
 .
   * New upstream snapshot, fixes serious bugs.
Checksums-Sha1:
 7c25105d1e1db4d345abd0c4d2becb18b516e2cd 2723 
golang-github-prometheus-tsdb_0.0~git20180314.659ed64-1.dsc
 8ad4c22af5f03312a9b7bb607cda1f85ab7d2767 2407377 
golang-github-prometheus-tsdb_0.0~git20180314.659ed64.orig.tar.gz
 4f9b788dc3ac8b6f2afbda675781fb750a311fdd 3496 
golang-github-prometheus-tsdb_0.0~git20180314.659ed64-1.debian.tar.xz
 dbed33ed915c8d63aaf869edebae2a0110972de9 8314 
golang-github-prometheus-tsdb_0.0~git20180314.659ed64-1_amd64.buildinfo
Checksums-Sha256:
 077933cd301ba2ec4fa5df83191ca5ec2c188c818c5b48dc75b68a255e1df7f1 2723 
golang-github-prometheus-tsdb_0.0~git20180314.659ed64-1.dsc
 93af7cd81867ed70380c405730529e936dc033ababa44e86e0b24531b4bb8d9c 2407377 
golang-github-prometheus-tsdb_0.0~git20180314.659ed64.orig.tar.gz
 9cced21230ee0ed84b025d46b2235b13aa465db0b3b8ca83a9fb54c20b8442eb 3496 
golang-github-prometheus-tsdb_0.0~git20180314.659ed64-1.debian.tar.xz
 f28a7739c81480035231b914e9aa940baea07f8e7dd9ff3c87b62e9dbb37be90 8314 
golang-github-prometheus-tsdb_0.0~git20180314.659ed64-1_amd64.buildinfo
Files:
 cfad26bfa94d4b7888063980703383e4 2723 devel optional 
golang-github-prometheus-tsdb_0.0~git20180314.659ed64-1.dsc
 556529cb9f54cb87d7f0207fc1150d70 2407377 devel optional 
golang-github-prometheus-tsdb_0.0~git20180314.659ed64.orig.tar.gz
 a0af173d23cc2dd17c84837feef92c43 3496 devel optional 
golang-github-prometheus-tsdb_0.0~git20180314.659ed64-1.debian.tar.xz
 a93b040d1153a1ad8bc28301f67d3afd 8314 devel optional 
golang-github-prometheus-tsdb_0.0~git20180314.659ed64-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEETe94h3mvRsa9AoOeXdjgv5Gj09oFAlq8rmsACgkQXdjgv5Gj
09oFOA/+OysAju8qPqjVpU4LcWzkDGUuH/l8rLELOpofXAqouOjSw6ofpenDaqTw
YNvqPNGt3Vec8JsqsybJCFMSXvrUQNYjdiDU/Po1JqRaLS4/RgLXEd2zP0A5mk0f
bpM1l85VWPJxb5XMnE3C9Sh0IHcACz5Of4N3G8mIFs89gIAC2XNcm7l7HCGIqIiO
g3ILbRTJl3Ud1mWKaA2l/9FF46loDmZ1KzfWwIhB31CpYVq0yvgSWC50XVR4V0pe
F4T+PT+mfKUOuxLodmCatnMJ1WOVAsPuFqRBiup9ysc2pGmGqkoxQ9/vMXbpx5Vy
gwva9PsjgT90CSitkuWMyU32guxRVhBiDME48wlBb9IEcOKtNV7ocMaxTzVxB1CN
itGRdYxzovS+feKmDg86BrMPsw+5EWO8JrFPGdiGDLkt1DYyNKCjZNDg1wFMo68E
x1Dy62dyemvEZfCUZyh+tW3oYwpM4COFDsepbKJ5JNHCwQJ236HXXHA+Qxa+Ho4q
AiDeHx/nMmQfqwvYZ16taHdsHQ//YRp4If3lj2uGGgZoi73gMPt/4BW1aAv6iYam
Vffrr6lLehuWfHQ5pNiJggG+K+x3vvRAxjGHNBAzDbJOasrFni+Py3nVHQsdSvrK
ZSGMJMqzfEIpvsQEcaCzSmulNxZiBGCFNCzZG7S8XbUSXoNPLLI=
=iIW9
-END PGP SIGNATURE-


___
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#894131: Bug#894131: prometheus-alertmanager: New upstream release 0.14.0 available. Please package and backport to stretch.

[Martín Ferrari]

On 27/03/18 14:35, Pirate Praveen wrote:

> We had this debate with handlebars templates and I'm happy to share good
> news about handlebars now. I know you moved to mustache based templates,
> handlebars is in main now.

Ah, well, back in 2016 I convinced upstream to just use mustache, which
is simpler and has support for many languages, and was in Debian already :)

-- 
Martín Ferrari (Tincho)

___
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#894131: Bug#894131: prometheus-alertmanager: New upstream release 0.14.0 available. Please package and backport to stretch.

[Martín Ferrari]

Daniel,

On 27/03/18 09:06, Daniel Swarbrick wrote:

> Debian currently has Haskell Platform 2014.2.0.0 (GHC 7.8.3), so to
> build the version of Elm used by Alertmanager, Debian would most likely
> first have to update their Haskell. And so it continues...

Ah, nice..

> I think you idea of stripping away the UI and replacing it with
> something non-standard is not a good idea, because Debian will become
> known as "that distro" which has non-standard Prometheus packages.
> People will either use a different distro, or run it in Docker, or
> something else - in any case, your work will have been for nothing.

Well, I don't really care about being not standard in that sense. The
standard is to run docker packages downloaded from untrusted sources,
fwiw. My objective is to provide sysadmins that align with the Debian
worldview with a working Prometheus stack. I have had already to deviate
from the standard in a few things, for example: kubernetes support was
removed from the prometheus Debian package because it is unmaintainable,
until the k8s people get their act together.

> What exactly in Debian policy is preventing us shipping Alertmanager
> built as intended by upstream?

I don't remember which section in the Policy that is. But those
generated files are not source code, and therefore there is a
requirement to (re)build them from source. It is the same as i was
shipping a pre-compiled .so file.

> Would it be an option to _decompress_ the gzipped & hex-encoded blobs
> from Alertmanager's ui/bindata.go back to their sources and package
> those? Looking at the file, that would produce these files:

This is not really a problem, I am not shipping the binary blob (because
I want to reuse libraries already present in debian). The problem is the
generated code, which is not source code (preferred form of modification).

-- 
Martín Ferrari (Tincho)

___
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] Accepted prometheus-mysqld-exporter 0.10.0+git20180201.a71f4bb+ds-2 (source) into unstable

[Martín Ferrari]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 27 Mar 2018 00:49:40 +
Source: prometheus-mysqld-exporter
Binary: prometheus-mysqld-exporter
Architecture: source
Version: 0.10.0+git20180201.a71f4bb+ds-2
Distribution: unstable
Urgency: high
Maintainer: Debian Go Packaging Team 
<pkg-go-maintainers@lists.alioth.debian.org>
Changed-By: Martín Ferrari <tin...@debian.org>
Description:
 prometheus-mysqld-exporter - Prometheus exporter for MySQL server.
Closes: 893051
Changes:
 prometheus-mysqld-exporter (0.10.0+git20180201.a71f4bb+ds-2) unstable; 
urgency=high
 .
   * Use non-recursive chown.
   * Fix FTBFS in 32bits arches. Closes: #893051
   * debian/control: Add myself to Uploaders.
Checksums-Sha1:
 c8d1cf35c2ed16bad9821498ddbf3edf2b8bb4d0 2887 
prometheus-mysqld-exporter_0.10.0+git20180201.a71f4bb+ds-2.dsc
 867008168ba4ddb1c775063b858f775fc9dff5cd 5896 
prometheus-mysqld-exporter_0.10.0+git20180201.a71f4bb+ds-2.debian.tar.xz
 4a9731064210a2af2bedfc4155c84ade52cf2d9a 8635 
prometheus-mysqld-exporter_0.10.0+git20180201.a71f4bb+ds-2_amd64.buildinfo
Checksums-Sha256:
 fe3ed5f1c2a479c5d8f18215815a60c5c1bae27eca832207c500fa592ad76611 2887 
prometheus-mysqld-exporter_0.10.0+git20180201.a71f4bb+ds-2.dsc
 0a9ffb0019be687dd43097cdb00a8843a27d982b59f8a3c3dcc975ea011ad986 5896 
prometheus-mysqld-exporter_0.10.0+git20180201.a71f4bb+ds-2.debian.tar.xz
 318654b42de06df84a2e1bcdecd325256a91b48efc112f983c676381a5e0b2d6 8635 
prometheus-mysqld-exporter_0.10.0+git20180201.a71f4bb+ds-2_amd64.buildinfo
Files:
 2aac26526bed8882b2d2415188a94876 2887 net optional 
prometheus-mysqld-exporter_0.10.0+git20180201.a71f4bb+ds-2.dsc
 08eeec55a4b325b7e6a514cb43512311 5896 net optional 
prometheus-mysqld-exporter_0.10.0+git20180201.a71f4bb+ds-2.debian.tar.xz
 e5915b216f372cd3117159ca54017b17 8635 net optional 
prometheus-mysqld-exporter_0.10.0+git20180201.a71f4bb+ds-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEETe94h3mvRsa9AoOeXdjgv5Gj09oFAlq5lWAACgkQXdjgv5Gj
09oRHxAAwLagYCWXWmo2t9c9UGZ+dZgXsrq8fya93AXpNGHb/PNw+ZLEqnbEPPUi
YpLn67n7xRa4YC4VDlXqDItBMbnAf7wqmsUB6XKw/IsREfUTaegZ3/oUptzGCEQx
KlP/7cOxUYjkDXZEwrCYqK0V762yZMgFnNiD1p/SMvcCrn+XbvN5eIS8tUD0+Iyr
gFujKbSGK9WSopcfayl9Frz5UEWO2IWiW3ik8b98lso/51u+/+QcK8xkIo9RK5I/
3YgoaaCYEo/Zfn+O07hwRHia7zDDNeEYeEKgnqvAFd4jqJywYl61s5/VuDU9DSYB
m4cEyzBX1jMFwWSsXAgY5bNR6zCJ9cMVzcedWaQd7NgQqR3FYdiRTlAljOZIhoiL
AQ0Nyq9tYWqhm4iM0U6MAq3m5fejVonlrAWPyVZ4PF+JkLpBDRJrPnZZQON1EyYb
Xw+QnWxHmBLWOz4yGALZ85IQzVSAkpOkxngHBZwG+wUYhHoluWPzAhUujgVE5qR8
rTMb9plIYL6LDakT1iZ/FW76jf2TyYy8B/dWUlD0Lx8QUAbqU+yo4fRZJ1g7r1A0
RyLeyjjIxgeGhTv3bNQLZQSs3NUFzRxSAvjvQiUxtN97DVd9y5mzfO74m22KIwxZ
JhRlCYOznJx+oDiqLpju1Vw7Gu16rloRbxpY3u0/5t8fUpigfeQ=
=+51I
-END PGP SIGNATURE-


___
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] Accepted golang-golang-x-sys 0.0~git20180308.349b81f-1~bpo9+1 (source all) into stretch-backports

[Martín Ferrari]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 26 Mar 2018 23:38:09 +
Source: golang-golang-x-sys
Binary: golang-golang-x-sys-dev
Architecture: source all
Version: 0.0~git20180308.349b81f-1~bpo9+1
Distribution: stretch-backports
Urgency: medium
Maintainer: Debian Go Packaging Team 
<pkg-go-maintainers@lists.alioth.debian.org>
Changed-By: Martín Ferrari <tin...@debian.org>
Description:
 golang-golang-x-sys-dev - Low-level interaction with the operating system
Closes: 891894
Changes:
 golang-golang-x-sys (0.0~git20180308.349b81f-1~bpo9+1) stretch-backports; 
urgency=medium
 .
   * Rebuild for stretch-backports.
 .
 golang-golang-x-sys (0.0~git20180308.349b81f-1) unstable; urgency=medium
 .
   * New upstream bugfix version:
 - unix: skip SchedAffinity test on single CPU system
   (by Michael Hudson-Doyle, fixes e.g. Ubuntu Autopkgtest on ARM64)
 - unix: fix nil pointer dereference in Select on linux/{arm64,mips64x}
   (by Tobias Klauser)
 .
 golang-golang-x-sys (0.0~git20180224.f6cff07-1) unstable; urgency=medium
 .
   * New upstream version, which has gccgo redeclared *SyscallNoError
 functions moved to a separate file and avoids build error with gccgo-8.
 Many thanks to Shengjing Zhu for the detailed report. (Closes: #891894)
 .
 golang-golang-x-sys (0.0~git20180126.0.ff2a66f-1) unstable; urgency=medium
 .
   [ Felix Lechner ]
   * New upstream version
   * Set Build-Depends: debhelper (>= 11)
   * Set compat to 11
   * Set Standards-Version: 4.1.3
Checksums-Sha1:
 bfa199ecdc3d1ef9ae5528d87c146f7477f87c31 2379 
golang-golang-x-sys_0.0~git20180308.349b81f-1~bpo9+1.dsc
 6ac74a2c5963370570d22ed8c48b57dbd4beb426 4524 
golang-golang-x-sys_0.0~git20180308.349b81f-1~bpo9+1.debian.tar.xz
 3eca95fa7f7f4674585c1027b9b36c6b05c1afb4 228520 
golang-golang-x-sys-dev_0.0~git20180308.349b81f-1~bpo9+1_all.deb
 7322293f79ca7c4035332ba5eb0afd78098b2f78 5815 
golang-golang-x-sys_0.0~git20180308.349b81f-1~bpo9+1_amd64.buildinfo
Checksums-Sha256:
 607fc2e7a46bee1007887bb4caf9297db28fc97cf0205581874c92440295e639 2379 
golang-golang-x-sys_0.0~git20180308.349b81f-1~bpo9+1.dsc
 d35f06b838ed2fcc4c261725cca3a608d150a2f58b738e59327b39e42973851c 4524 
golang-golang-x-sys_0.0~git20180308.349b81f-1~bpo9+1.debian.tar.xz
 2917eb38a70fcaebb09ca735735e40aa23b39c1f7eca455bc3a1b36feef39abe 228520 
golang-golang-x-sys-dev_0.0~git20180308.349b81f-1~bpo9+1_all.deb
 b38e4a09b563fac121778fc47bc33ecc2d5e46644352a68549526119d2d1da1f 5815 
golang-golang-x-sys_0.0~git20180308.349b81f-1~bpo9+1_amd64.buildinfo
Files:
 600afe4fde1ab1828a30a3d1cd4cc71d 2379 devel optional 
golang-golang-x-sys_0.0~git20180308.349b81f-1~bpo9+1.dsc
 0cb7ca714224fcdca910fd1e1a050e69 4524 devel optional 
golang-golang-x-sys_0.0~git20180308.349b81f-1~bpo9+1.debian.tar.xz
 f6c70f391fd56548fd04854333b5a412 228520 devel optional 
golang-golang-x-sys-dev_0.0~git20180308.349b81f-1~bpo9+1_all.deb
 3af62b84373441fa2f3bf843197d2292 5815 devel optional 
golang-golang-x-sys_0.0~git20180308.349b81f-1~bpo9+1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEETe94h3mvRsa9AoOeXdjgv5Gj09oFAlq5hRsACgkQXdjgv5Gj
09ralg//RQPlQqAtR92kEejZnTkZtPw1KKlKmQaUs7A5X4dlFuBFdp3yXPHgXz9X
XqVsTp7OywsWAMxAmh0xSLxsWzJ6qVG3o+i4iXDs5/JH7520hcIOIERviuELJW3X
UM3IabC8JOpIuw+PspLQyWICzJsrjNTyr4nmcbIk3MlO+0vHZweQjJYjaPWlDC6A
M/zV+YR9YLvgpeJpujaMKEPUC+7D+Lb4735P+VwSZHgEDVlY0jgkqAPtwItESy7k
ueBlPNtOoClUnNH8AAQXXgJexqm9wFyMHTQhs5J8YyteOvVOG+F97bBf6YyyhBls
KEcov14kkVj1OATpEGU66J1D3Vvp6XPFSjxD53SBlI6JI+L+q+xFFG6t69jcNDPt
2cyuMTMiQyeFznAAEZGfA4UiUjBvl1kmgdFoyo0dg07qB3YpQLOF+NxM9gbrGdce
H9jRkNhIit+dMiE8rn2rXCvbHAi3mjV5j5t6wVti1E2csw/JahAN7FeoRaUtp05W
afbbHJgaKwG/CWOAW8/q9k+8rlx71ZekBKULZSxMI11zt3Qt+V+p/ICweDRT+RFJ
E6qe2eolsuLOHuhhhKWAgAyGG7GgXx9FrCgyj47KLYB04AnPsRnQDsaHF/b9eBeC
j5A7p2Nq4q2sbbQO+hUjGVNmsGhWBXLjeW33B/ghFCZzbjdsZ4o=
=ia24
-END PGP SIGNATURE-


___
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] Accepted golang-github-grpc-ecosystem-grpc-gateway 1.3.0-1~bpo9+1 (source all amd64) into stretch-backports

[Martín Ferrari]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 26 Mar 2018 23:01:03 +
Source: golang-github-grpc-ecosystem-grpc-gateway
Binary: golang-github-grpc-ecosystem-grpc-gateway-dev golang-grpc-gateway
Architecture: source all amd64
Version: 1.3.0-1~bpo9+1
Distribution: stretch-backports
Urgency: medium
Maintainer: Debian Go Packaging Team 
<pkg-go-maintainers@lists.alioth.debian.org>
Changed-By: Martín Ferrari <tin...@debian.org>
Description:
 golang-github-grpc-ecosystem-grpc-gateway-dev - gRPC to JSON proxy generator 
for Golang -- sources
 golang-grpc-gateway - gRPC to JSON proxy generator for Golang -- binaries
Changes:
 golang-github-grpc-ecosystem-grpc-gateway (1.3.0-1~bpo9+1) stretch-backports; 
urgency=medium
 .
   * Rebuild for stretch-backports.
   * debian/control: Add missing dependency on genproto.
Checksums-Sha1:
 1a48228aa2298e798a371a76be8f284f84f8c7a0 2775 
golang-github-grpc-ecosystem-grpc-gateway_1.3.0-1~bpo9+1.dsc
 7ac66e377ed35368d37a979aa855bd42f3f01f48 3132 
golang-github-grpc-ecosystem-grpc-gateway_1.3.0-1~bpo9+1.debian.tar.xz
 77bdb0d1c2ef14cf1f7f8ef1460bccafb335ee5a 154656 
golang-github-grpc-ecosystem-grpc-gateway-dev_1.3.0-1~bpo9+1_all.deb
 df3adc76f452dad4e2eee71b9acae288059416cd 7607 
golang-github-grpc-ecosystem-grpc-gateway_1.3.0-1~bpo9+1_amd64.buildinfo
 c11d22ddaf51355f6bdef9f1418213ca9ed36761 1171694 
golang-grpc-gateway_1.3.0-1~bpo9+1_amd64.deb
Checksums-Sha256:
 2100901b06d3516b6a4ed742ad85841071d6fe03f1af15bc592f80b2bcaf30b9 2775 
golang-github-grpc-ecosystem-grpc-gateway_1.3.0-1~bpo9+1.dsc
 589d426e10d9d5e19dbdf724d170270ad2633c091d08ce524ba5c12468cb9a20 3132 
golang-github-grpc-ecosystem-grpc-gateway_1.3.0-1~bpo9+1.debian.tar.xz
 744fdae0f4a5c3bdee3c40214132611f5df7fcba888f8640d596e33b60f03b64 154656 
golang-github-grpc-ecosystem-grpc-gateway-dev_1.3.0-1~bpo9+1_all.deb
 beb4844009d1c6129d98978b37479551790411e56f1047b7bbc9983db51c4f5b 7607 
golang-github-grpc-ecosystem-grpc-gateway_1.3.0-1~bpo9+1_amd64.buildinfo
 2429bfa4b4ea45ede9438a1939fe23dae3581851a97f6474d50fa477a07358de 1171694 
golang-grpc-gateway_1.3.0-1~bpo9+1_amd64.deb
Files:
 3f4d7e778db2f11a2a570c7bb231b367 2775 devel optional 
golang-github-grpc-ecosystem-grpc-gateway_1.3.0-1~bpo9+1.dsc
 c324084bda242eda475e371ea6c3a8f6 3132 devel optional 
golang-github-grpc-ecosystem-grpc-gateway_1.3.0-1~bpo9+1.debian.tar.xz
 1c78900a8d2d723025cb8a0a5a5985f9 154656 devel optional 
golang-github-grpc-ecosystem-grpc-gateway-dev_1.3.0-1~bpo9+1_all.deb
 31f6e7a2c4eea1f6d4d78b9ac6274b38 7607 devel optional 
golang-github-grpc-ecosystem-grpc-gateway_1.3.0-1~bpo9+1_amd64.buildinfo
 bbda4e6803b4b9408e1068855992600d 1171694 devel optional 
golang-grpc-gateway_1.3.0-1~bpo9+1_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEETe94h3mvRsa9AoOeXdjgv5Gj09oFAlq5gdwACgkQXdjgv5Gj
09r/KBAAufI9cPRYBocM1XitxgTFLNQiY0K07xvBOqb6V+FWL4wqT2dqJl06KBDL
0J07Bn2O3qkQ9FS8xm7yc8l4pSVoTPDl1NatzZo8GokZGVu1ShyubuvFl68xHMxf
qWK2noYCQVxUDMGBFgTxjrQd951XcTf1wUY/sRcQEB2CVGPJF6c53GmSQuJoJxtN
6k27X7QS/6BAfIFxT7ZoBfe8ItzGMiwsrYGdBW06QCJ3XK8EaRMmfLyyKLpHajya
AbskRV8SobbAuT+m/cYDr2Zr0XUmiIztiNm9eOqd/m5PUZRGT93xgXVeYx0slIr8
MWyCdqtjVs/mF/C2ko63kRIwe95Sotf/ibESwLiVkmfQkbM1T4MQO8dssf6VuBDO
9E61qAepfPFXAf79YKzsYUeWFSF91RyN/MIfYuHx7OQuWMs53FOqslnARroQe6Kv
Oem0DkDJiW8pac3koA/ihuCdheK3ymtjdeASCJSihjxsEE8mJvNzj+wY8uVFpZdh
i2G2Ay73ec9FuSBue+xlpB3cM1kAw94/2Lnwf7/WS9oM/3AUhsP9hOv9UBe4yTOL
lv2gfaUN4y/D1PHid02GfwAkp9XPwJxYex2raoXb3gWt4tIeFmFsmkU1SnFTdtdZ
Yjsu5DkZt4zxQav2Ql3+vihvReE9O+r8mrNIs1WQhB1IqRLa1h0=
=20eJ
-END PGP SIGNATURE-


___
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] Accepted prometheus-blackbox-exporter 0.12.0+ds-1 (source) into unstable

[Martín Ferrari]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 26 Mar 2018 22:14:14 +
Source: prometheus-blackbox-exporter
Binary: prometheus-blackbox-exporter
Architecture: source
Version: 0.12.0+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 
<pkg-go-maintainers@lists.alioth.debian.org>
Changed-By: Martín Ferrari <tin...@debian.org>
Description:
 prometheus-blackbox-exporter - Blackbox prober for Prometheus
Closes: 894130
Changes:
 prometheus-blackbox-exporter (0.12.0+ds-1) unstable; urgency=medium
 .
   * New upstream release. Closes: #894130
   * debian/control: Update dependency version.
   * debian/copyright: Add Files-Excluded header.
   * debian/{postinst,init}: Use non-recursive chown.
   * Update debhelper compat to 11.
Checksums-Sha1:
 575e7c0c42f5dbc4c4c00159f969ef46c47f686e 2602 
prometheus-blackbox-exporter_0.12.0+ds-1.dsc
 aba2951239498eb324b53b124a233f6c5ba56cda 36105 
prometheus-blackbox-exporter_0.12.0+ds.orig.tar.gz
 09f67410433ca4ff59eb15808fe8dcc0bfbdd140 4788 
prometheus-blackbox-exporter_0.12.0+ds-1.debian.tar.xz
 2c7d54137c7a1f39e4e0125dba36aadb41c7122a 8065 
prometheus-blackbox-exporter_0.12.0+ds-1_amd64.buildinfo
Checksums-Sha256:
 e6d6c77ad8776e9a6b9bfd6a9f686c9722803e5b1a9c90f61c2ec5d215274eae 2602 
prometheus-blackbox-exporter_0.12.0+ds-1.dsc
 cae7781d4a80011c7f574a797dbdb097fd639eb95d2d95f44da8bdecd4b396d4 36105 
prometheus-blackbox-exporter_0.12.0+ds.orig.tar.gz
 fe0c4aee4aabb5b92dadc80da3911afb057f83df42120dd739b38f2eccc5313f 4788 
prometheus-blackbox-exporter_0.12.0+ds-1.debian.tar.xz
 1134789ebeda64dee7bf41036f2199e712240151df2c379f233122098a48 8065 
prometheus-blackbox-exporter_0.12.0+ds-1_amd64.buildinfo
Files:
 ec7d096d558a86e5878f74971deea2a1 2602 devel optional 
prometheus-blackbox-exporter_0.12.0+ds-1.dsc
 39325ba63d8439c8dfe76c7da19c647a 36105 devel optional 
prometheus-blackbox-exporter_0.12.0+ds.orig.tar.gz
 6bd386ca01efcd42de76d6a21c5c2786 4788 devel optional 
prometheus-blackbox-exporter_0.12.0+ds-1.debian.tar.xz
 f23fec2fa86341fa29ae2db7de46aa7f 8065 devel optional 
prometheus-blackbox-exporter_0.12.0+ds-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEETe94h3mvRsa9AoOeXdjgv5Gj09oFAlq5cPcACgkQXdjgv5Gj
09q3CA//UMFhwVJ3jTNeQDeIHUjEYFdREStucwMMzq9MwJPLFbXYIkwCgYtMDhIa
JwI1laed5VrIOv5qa637cBttlKKYGGrniSEXhvS2ECzFrl6NFHhxxIxE3DRxn4Uq
urMzX2JQ0Ch9c0il5mxX2A3m3pqeVZlZfY7Y/DI9dtf1dhysKRD7dTGAVaqMRY4U
+pPKLH+z+Ae50RZHLE3mFEKEgzIuxm7gI9cZQ82LUraTp81higWl6ljoIOwXAjlQ
9IjMSYrWA1v8IMX5na6ORXw60C2qzfXGGjTrDWRyuwNl59tnj6zACJgH/yZi0xPd
fMmcRcOw0yAOd5XOG0CH1b9wnHDLy2A/QjNcArET+jOjSvoKIks9lkHvOdju6/zf
Fqr6lkAgfpNBNo/0c742sxHMurl9Ct0+aj7bggEdKF0soXiojcaP5t6jganlTc21
kqsjZhHsedOp0ijD8ryACn+pJU9kxoFRlwG666Hr4DD4Ax+sFAavzsD2OFOl13dk
ujmElZjKJsTuc0XysS6tWIBVgVqe+rr00GejvMOz623s/1dfEbhxGrTufrr8aJjM
YDDvFoUinQ2XFNVMlQz8evCIQWqs9dWsURBuLGoJfWXUyJWvQ9jS/KfB/5z436q0
m+wUV2mk1aTukSGJKNyc18cElggF94Wdb0CVsgTjaQBFvay69go=
=IUXu
-END PGP SIGNATURE-


___
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] Accepted golang-github-miekg-dns 1.0.4+ds-1 (source) into unstable

[Martín Ferrari]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 26 Mar 2018 21:25:00 +
Source: golang-github-miekg-dns
Binary: golang-github-miekg-dns-dev golang-dns-dev
Architecture: source
Version: 1.0.4+ds-1
Distribution: unstable
Urgency: medium
Maintainer: pkg-go <pkg-go-maintainers@lists.alioth.debian.org>
Changed-By: Martín Ferrari <tin...@debian.org>
Description:
 golang-dns-dev - transitional package for golang-github-miekg-dns-dev
 golang-github-miekg-dns-dev - DNS protocol library for Go
Changes:
 golang-github-miekg-dns (1.0.4+ds-1) unstable; urgency=medium
 .
   * New upstream release.
   * Drop pristine tar, get back to upstream git history, use DEP14.
   * Add watch file, now that there are releases.
   * Remove patch merged upstream.
   * New dependencies, removed from vendoring.
   * Update copyright info.
   * Various packaging improvements.
Checksums-Sha1:
 63e4b4c4a8d595487de2bc0f6a4b496c1b33f444 2399 
golang-github-miekg-dns_1.0.4+ds-1.dsc
 1376562fcb1ae6802abaef90586b7adefd76cc70 152494 
golang-github-miekg-dns_1.0.4+ds.orig.tar.gz
 03fa33f7db3ff8334e4197a5a84daaa13a721974 4280 
golang-github-miekg-dns_1.0.4+ds-1.debian.tar.xz
 b91fcc842cdf0f8ca9a8aa7f4205c44991a671cb 6263 
golang-github-miekg-dns_1.0.4+ds-1_amd64.buildinfo
Checksums-Sha256:
 3f0956133c7393b428ca62be984286941d27e858d3120f618e37e30f17418045 2399 
golang-github-miekg-dns_1.0.4+ds-1.dsc
 f58d47f1e1a69f0338d361f0ba5132aaf326dbbb0b94ce4fda446e9e30c2031e 152494 
golang-github-miekg-dns_1.0.4+ds.orig.tar.gz
 0213b2694a3b6ef8f0d2138836a88c34b2eaac3c6ea2e21568c3bd51ef164c52 4280 
golang-github-miekg-dns_1.0.4+ds-1.debian.tar.xz
 d130f471b37f978921ef64a757c6fd458a132e0222e3fa2486328b41d7c0a5bb 6263 
golang-github-miekg-dns_1.0.4+ds-1_amd64.buildinfo
Files:
 22661efcdf6ce6ee3348465e2f0fcd1d 2399 devel optional 
golang-github-miekg-dns_1.0.4+ds-1.dsc
 b8c73d77cc9645a19c6e681cb477c60a 152494 devel optional 
golang-github-miekg-dns_1.0.4+ds.orig.tar.gz
 3579c9d201375766ee7972597b7136c2 4280 devel optional 
golang-github-miekg-dns_1.0.4+ds-1.debian.tar.xz
 d0a9a5f0c495a84a0a7ba8fbd944ef8d 6263 devel optional 
golang-github-miekg-dns_1.0.4+ds-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEETe94h3mvRsa9AoOeXdjgv5Gj09oFAlq5ZWgACgkQXdjgv5Gj
09rkGw//RiZjD5kZ0DRjUtD1ifnsW3RJwAWfvqPv2h3U7e565Nzl4O8QReKuDF2P
RTiP9Du/6nB7yJw7nXlr4gMphyTOgx643IMuFC/sj362LIcI18/zHLVo8CWdXECn
Ve4jJUHalAvxtJObOqh+IvlqrcjISvccgB8FwYxw6/cpS6jr2BbN9Rl+wAEfWzP2
kBQzMGJlHIChpKadqlLcSrdrkqEdjuiezJ9Ci1HpkRJ47QtXuVTCZv68u9YDKRvf
wNfE1c3QaEaXYs4UMnr1zz01sQ4OkirjnU61cDqifzf28p1WUmgu8OuwOG+kxpQb
RF2T6zarT/Mwl5aNpvgXuWv/gGN4xH/texExVlVHCErz8UqionenFRk4paxAoM89
IiqrcfqGpsL0d2xDJhKEZJrnbeZ3gdjmn2rjNAb2/CrXeSbQ17LDHwWhV0qKL7a9
njDGPIM5mQpj57WaT7Jhm0sEi15sTL7gDEYYBoVuvPrPJwpod8kRW/65Wp253ZVP
+Zn8BTH0wQKz270ZSRaCOP6WphYt635H3KUF3pLAv/vt6dsEONsB1uMpzC0wBlgf
zqspbgd0ZHXFhSw7bX6REdUm7n9Ve3EY9QNvNvCwuvq8EA3s6f+Y1fXD4kCR6yZS
ej1+Ox0H7bwwlnQ6k5yIcARPnuvLqAh5WD96PzRfzJBD136br/g=
=5b2t
-END PGP SIGNATURE-


___
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#894129: Bug#894129: prometheus: Please backport Prometheus 2.2.1 to stretch.

[Martín Ferrari]

On 26/03/18 17:24, Daniel Swarbrick wrote:

> Please backport Prometheus 2.2.1 to stretch.

It is in my plans, but it has to reach testing first :-)

-- 
Martín Ferrari (Tincho)

___
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#894131: Bug#894131: prometheus-alertmanager: New upstream release 0.14.0 available. Please package and backport to stretch.

[Martín Ferrari]

Hi Daniel,

On 26/03/18 20:34, Daniel Swarbrick wrote:

> I was a bit too hasty in my previous reply. It appears that Alertmanager
> compresses and encodes all the web UI assets a Go "blob"
> (https://github.com/prometheus/alertmanager/blob/master/ui/bindata.go).
> Elm libraries are only needed if you intend to hack / develop the web UI.

Exactly. Prometheus itself does the same thing.

The approach I took was to remove the blob and patch the web serving
code to read the files directly from disk, and then to do al the JS
processing at build time from source.

I would do the same for alertmanager, but for that I need a working Elm
stack to generate the JS from source, otherwise it is a serious
violation of Debian policy.

> I just built a fully functional alertmanager binary from a git clone,
> with no Elm or Haskell or Node.js anywhere to be seen on my system. This
> is why I mistakenly thought that the aforementioned RPMs had stripped
> the UI completely, when in fact it is simply compiled into the
> alertmanager binary.
> 
> Does this simplify things somewhat? I suppose it just leaves the
> vendored Go libs as a possible sticking point.

Vendoring Go libs would not be a direct violation of policy, but it is
something we try hard to avoid as it becomes a maintenance problem.
Vendoring pre-generated pre-minified code, on the other hand, is not
possible in Debian, and that's how we ended in the current situation :-)

It is because of this that I thought of stripping the UI away, and
replacing it with something bare-bones. This would not be that difficult
to do, it is just a matter of writing some html and JS.

If you could help me with that, I would take care of integrating the
replacement UI, and I could get a new release out of the door pretty
quickly.


-- 
Martín Ferrari (Tincho)

___
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#894131: Bug#894131: prometheus-alertmanager: New upstream release 0.14.0 available. Please package and backport to stretch.

[Martín Ferrari]

Daniel,

On 26/03/18 17:31, Daniel Swarbrick wrote:

> Current Debian packages for prometheus-alertmanager are extremely out of
> date. The web UI and (undocumented / unstable) API has changed
> considerably in the ten versions that have been released since 0.6.2,
> along with many bugfixes.

I know, this is a pretty sad state. The problem is that upgrading the
alertmanager requires packaging and uploading many new packages, as they
started using the Elm system for the UI, and no part of it is in Debian.

The alternative to this is to develop a patch that will provide an
barebones UI without the dynamic JS generated with Elm.

I am maintaining most of the prometheus ecosystem by myself, so I have
not been able to do any of this. If you have the resources to help, you
would be most welcomed!


-- 
Martín Ferrari (Tincho)

___
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] Accepted prometheus 2.2.1+ds-1 (source) into unstable

[Martín Ferrari]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 26 Mar 2018 04:34:44 +
Source: prometheus
Binary: prometheus
Architecture: source
Version: 2.2.1+ds-1
Distribution: unstable
Urgency: high
Maintainer: Debian Go Packaging Team 
<pkg-go-maintainers@lists.alioth.debian.org>
Changed-By: Martín Ferrari <tin...@debian.org>
Description:
 prometheus - Monitoring system and time series database
Changes:
 prometheus (2.2.1+ds-1) unstable; urgency=high
 .
   * New upstream release, with critical fixes.
   * Ignore fsnotify on mips64el, rely only on timeouts for file discovery on
 that platform, and disable the tests.
 https://github.com/fsnotify/fsnotify/issues/241
Checksums-Sha1:
 9219c2f479536f104a0976d8e9b5f016ce7ada3a 3319 prometheus_2.2.1+ds-1.dsc
 8a8ebc700b6852d1f9b856a3aed5dd921dd873b9 1028225 
prometheus_2.2.1+ds.orig.tar.gz
 d63694237d5a7e1b701cffe2960b54f31d16241f 26608 
prometheus_2.2.1+ds-1.debian.tar.xz
 0dc4baa9c951207270d44fdc8c93bb7b0166a8b8 11519 
prometheus_2.2.1+ds-1_amd64.buildinfo
Checksums-Sha256:
 ae6e68e24da9f085dd2387e6767e9f5f2e60e30e4ec7b6eea7b88a608c5d73e7 3319 
prometheus_2.2.1+ds-1.dsc
 d652f7303c555ee03f8f6f9b34b76ee4f32115085ed85c4ea155cbeae0bf7ee8 1028225 
prometheus_2.2.1+ds.orig.tar.gz
 07171a6a0bc541530875d9548e513d0ea4f7e4d35c9ed6d34ee7800b23e9c9d0 26608 
prometheus_2.2.1+ds-1.debian.tar.xz
 6f0515f269eaa3240b803c077412f6aed5f071c701ac27508dc26ca765ecef63 11519 
prometheus_2.2.1+ds-1_amd64.buildinfo
Files:
 dd6ad24d8fda7e37cf58fee3f59711ed 3319 net optional prometheus_2.2.1+ds-1.dsc
 aa1ba2c7482260cf317899fc61fb2e19 1028225 net optional 
prometheus_2.2.1+ds.orig.tar.gz
 a559cfccf4785686796221e77be7f13d 26608 net optional 
prometheus_2.2.1+ds-1.debian.tar.xz
 197ec90e0451d56ac4c8d36400f96a91 11519 net optional 
prometheus_2.2.1+ds-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEETe94h3mvRsa9AoOeXdjgv5Gj09oFAlq4ePwACgkQXdjgv5Gj
09o+fA/9HGabPWdI5vA15zlU8FR5hM+nRG8YY5dtJleAXorsZNY6eL1B2jKxIc/z
GgufNo5n/UQo6ZFGlCWaQesrfbI6jp4EFTM8MP8JTdIfQRI9JDvoERNHdHXgSFwK
yxWbRQRJcM8la5NYvdE2zO9Jmfr6aLEEkUchlycbQncKqLSJd2MDDbHXEGb7tn3j
NhRAxKuFCI4zyDavMDJbwYOId1gbwtLzxq0+hhKUidJx5v6ViIUTZTDIcfmvmGBj
rJk+AZya+BD4hj0Pflkz9a3QLGfbbEW0FPltEADfO0RgT4C0zZ0qL7muK7cYa/++
94EedDv9ri1u1GmesBAGhQM4AZI8MSrOPaEUhQs8acqxe5Fju6RuO5nT5URw3Nsg
vo85uS8gBZ3b/z6QOtMy26WHFpEQVXKIWONEXCFoOg7DVpPa7WL5fheaRYzn5QMT
fwkkWCMT6vKaEbiCsABXrps0vS2CKJKI6khiuYdviq68aMVQV7PANg94lo502jj+
k5571SqPjZyaUrqvJxz4sGPmDJ3wvFYiX9LAiKQTr25dLx9gU13X5qyJAvAp4ydK
9aYrDEpXQUdqJzKHdqB8rdWzBobQtAXj1ybH6iwI/LvUBVEZA66hL/tx5LYS6sGv
1ZpddjI0xmq2aXecDQDNNXh+JPjv4c5P2vn9LaV6c766Mup7s00=
=+8wc
-END PGP SIGNATURE-


___
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] Guidance for packaging Docker for Debian

[Martín Ferrari]

On 15/03/18 09:22, Arnaud Rebillout wrote:

> So I made a beginner mistake, but I'm learning, and hopefully I'm on the
> right track !

Don't worry, we've all been there.. the go ecosystem is a mess.

> I don't know what's the best way to deal with this situation, so if
> anyone from the team can provide some advice, that would be super welcome !

I sometimes have kept small dependencies vendored in for convenience..
But keeping the whole containerd seems wrong to me. Specially
considering that it is something that can have security implications.
Vendoring means nobody knows that version is there, so no audits; and
the problem of patching separate copies, with different versions, when
there is some patch to urgently apply..

In an ideal world, we should try to convince the docker people to use
stable APIs (that means using only released non-alpha versions!), or at
least to fix the incompatibilities with 1.0.2. I think it is at least
worth a try.

The other way, which we have done many times, is to patch the software
ourselves. I have no idea why docker does not build with that version,
but sometimes it is not that difficult to fix.

my 2¢
-- 
Martín Ferrari (Tincho)

___
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] Accepted prometheus-mysqld-exporter 0.10.0+git20180201.a71f4bb+ds-1 (source) into unstable

[Martín Ferrari]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 15 Mar 2018 03:07:26 +
Source: prometheus-mysqld-exporter
Binary: prometheus-mysqld-exporter
Architecture: source
Version: 0.10.0+git20180201.a71f4bb+ds-1
Distribution: unstable
Urgency: high
Maintainer: Debian Go Packaging Team 
<pkg-go-maintainers@lists.alioth.debian.org>
Changed-By: Martín Ferrari <tin...@debian.org>
Description:
 prometheus-mysqld-exporter - Prometheus exporter for MySQL server.
Closes: 848481 884542
Changes:
 prometheus-mysqld-exporter (0.10.0+git20180201.a71f4bb+ds-1) unstable; 
urgency=high
 .
   * Team upload.
 .
   [ Filippo Giunchedi ]
   * Suggest default-mysql-server | virtual-mysql-server (Closes: #848481)
 .
   [ Martín Ferrari ]
   * debian/control: Update package name for client-golang.
   * debian/control: Update Standards-Version (no changes).
   * debian/control: Fix Vcs-* fields.
   * debian/control: Replace golang-go with golang-any in Build-Depends.
   * debian/control: Mark package as autopkgtest-able.
   * debian/rules: Replace DH_GOPKG with XS-Go-Import-Path.
   * debian/rules: Replace dpkg-parsechangelog with /usr/share/dpkg/pkg-info.mk
 and simplify.
   * New upstream release/git snapshot. Closes: #884542.
   * debian/control: Require latest go-sqlmock, as tests fail otherwise.
   * debian/rules: Fix dh_auto_install parameters.
   * debian/control: Automated cme fixes.
   * debian/control: Update debhelper compat.
   * debian/copyright: Add Files-Excluded to match repackaging.
   * Remove unneeded lintian override.
   * debian/doc: Refresh.
Checksums-Sha1:
 06d28a408934cf0e9be182c7183a08d09e2b4411 2850 
prometheus-mysqld-exporter_0.10.0+git20180201.a71f4bb+ds-1.dsc
 7b3573bf9f893f8e7f121112de8777bce705e79b 48085 
prometheus-mysqld-exporter_0.10.0+git20180201.a71f4bb+ds.orig.tar.gz
 83a41b33ef8371fe0d65a0e0f62e4a2a77a74123 5460 
prometheus-mysqld-exporter_0.10.0+git20180201.a71f4bb+ds-1.debian.tar.xz
 8ec83d474815ac2de875b6c18be34ce1b2b87ffa 8640 
prometheus-mysqld-exporter_0.10.0+git20180201.a71f4bb+ds-1_amd64.buildinfo
Checksums-Sha256:
 c599d99fc720ea3e7936d43716400b01ece97e2d078f144d6b129306a42b79a7 2850 
prometheus-mysqld-exporter_0.10.0+git20180201.a71f4bb+ds-1.dsc
 6b648efbc580fe0b3232d6e8e0cb9f96a9157737e574344b6ef6c0614794500b 48085 
prometheus-mysqld-exporter_0.10.0+git20180201.a71f4bb+ds.orig.tar.gz
 8adf24d774594d72041a1ed33af85d4831d9dc00823d02aec8372f6ea3b839a8 5460 
prometheus-mysqld-exporter_0.10.0+git20180201.a71f4bb+ds-1.debian.tar.xz
 d63b8f58eef89b40899374160b13b3996205c86c8b183144f07b265581957249 8640 
prometheus-mysqld-exporter_0.10.0+git20180201.a71f4bb+ds-1_amd64.buildinfo
Files:
 608d6013d1ba570d4dfceb689aa22399 2850 net optional 
prometheus-mysqld-exporter_0.10.0+git20180201.a71f4bb+ds-1.dsc
 cd0df0ab84013531e20b538571dba9ed 48085 net optional 
prometheus-mysqld-exporter_0.10.0+git20180201.a71f4bb+ds.orig.tar.gz
 0d5b9dde3eed8a819838704f20b6b91d 5460 net optional 
prometheus-mysqld-exporter_0.10.0+git20180201.a71f4bb+ds-1.debian.tar.xz
 450bb2ab41e31d7708a96005310ae58b 8640 net optional 
prometheus-mysqld-exporter_0.10.0+git20180201.a71f4bb+ds-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEETe94h3mvRsa9AoOeXdjgv5Gj09oFAlqp46sACgkQXdjgv5Gj
09qD9g/+KJJxryQpejSvS/hN0LTqw+DkcNUIsiq1aiulHyED5knNaK17Z9UC80Rg
jIl3prkulocMyzKF2e0PCWuAFP/SkI0toEIFwe6IIjDaQUcA5LVSmpmWdWm81/3v
cfT4ViGwQ2gCr/QSKz4JjIVQsnqd/EhxJn08IfDF73Z1gM1Qe6TxUsn0hvSIV64S
H7xEQ6Il+bBxZvA0jeY8rqJW3WvAcfdUsgPezHpqnydthlq+RzTt7ZpnDejNVauG
f7xGmMnt3A623LN35RhPABA6o5yGOELvc9wkF52omqmPJxVEgQGySahiw6eJF4w7
264ds3D/0tWnrJ+9YLwr2Uyi5mCEGfB0BKY942g11vBPGWhHC0P9SMk1Rz/puxJ/
1KP3uyQao2Zao8sf3tuh01tVFIZ4jk/Cp3zh7uzy8oh8KJVoJToh+HUQj41nru/D
xQI+vgorUw7RQtUBg7TOCZw/FdVHj7s8MSlYuBW8W+HG96ixM87v02O75s21co0B
xqSZXbnhCByISd0hcTkEdL8dHGXU1qBqdIQUhaG0XKyaLZchdB8J0sa52APmBb0c
V4rdWeodC+JoWFNI/o3VQvhnZju7uKJexbiFbzKu7vjj18RZjA5b+y2khEzF4u6I
nbLeJ9nUyWxaPbSrjwk5CUTAO6S/je6+EmhuR3qORjOYWsWHvJg=
=GX5I
-END PGP SIGNATURE-


___
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] Accepted golang-github-data-dog-go-sqlmock 1.3.0-1 (source) into unstable

[Martín Ferrari]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 15 Mar 2018 02:45:37 +
Source: golang-github-data-dog-go-sqlmock
Binary: golang-github-data-dog-go-sqlmock-dev
Architecture: source
Version: 1.3.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 
<pkg-go-maintainers@lists.alioth.debian.org>
Changed-By: Martín Ferrari <tin...@debian.org>
Description:
 golang-github-data-dog-go-sqlmock-dev - Sql mock driver for golang to test 
database interactions
Changes:
 golang-github-data-dog-go-sqlmock (1.3.0-1) unstable; urgency=medium
 .
   [ Paul Tagliamonte ]
   * Team upload.
   * Use a secure transport for the Vcs-Git and Vcs-Browser URL
 .
   [ Martín Ferrari ]
   * New upstream release.
   * Automated cme fixes.
   * Update debhelper version.
   * Add examples.
   * Stop using pristine-tar.
Checksums-Sha1:
 8221b9836b622289af3fc0c194b82b8f231b72cb 2352 
golang-github-data-dog-go-sqlmock_1.3.0-1.dsc
 f24fc06138350c9ddb62ed8962f4d119ff44e110 23019 
golang-github-data-dog-go-sqlmock_1.3.0.orig.tar.gz
 1e606ecc43e6924898877a0552135e40d2622967 2348 
golang-github-data-dog-go-sqlmock_1.3.0-1.debian.tar.xz
 9d807badc53cfa4e2b42539088579b3960f88cb1 5794 
golang-github-data-dog-go-sqlmock_1.3.0-1_amd64.buildinfo
Checksums-Sha256:
 370148d771d48b2f0aa8281ec6640e96894aa0f5dc88f317f65a215de3218937 2352 
golang-github-data-dog-go-sqlmock_1.3.0-1.dsc
 d8a1ebccfcc6b158c0084de476c8d30c3e7963929ecccbd57316e7c7a32b941b 23019 
golang-github-data-dog-go-sqlmock_1.3.0.orig.tar.gz
 7f0588d4327a6794ddbdfdb74ff9ed5719a443391d6aa5125d961f350d8ee1b7 2348 
golang-github-data-dog-go-sqlmock_1.3.0-1.debian.tar.xz
 0594ed4eb8d78c51badf298063bce17849be961ea85f6cea250c40a0271b1ee5 5794 
golang-github-data-dog-go-sqlmock_1.3.0-1_amd64.buildinfo
Files:
 591707639c731d657df81134a5c02921 2352 devel optional 
golang-github-data-dog-go-sqlmock_1.3.0-1.dsc
 5d3e9c690dcba104304286abe3aef4d7 23019 devel optional 
golang-github-data-dog-go-sqlmock_1.3.0.orig.tar.gz
 99059fc2d9573bdd9abc7520d74ef1ba 2348 devel optional 
golang-github-data-dog-go-sqlmock_1.3.0-1.debian.tar.xz
 97e01b50fc4979fffe25445c5e5769aa 5794 devel optional 
golang-github-data-dog-go-sqlmock_1.3.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEETe94h3mvRsa9AoOeXdjgv5Gj09oFAlqp3oIACgkQXdjgv5Gj
09r/OxAAw/7OOplBBuf2p3Ns+bOQwSB5rXj43iBMb7Z0pknzYkmSf4//pKgWLCx3
uxqGyKXIg/r6H6JCWmC2wyy9F8cnOUAGcNcE6KGzEU+MMMn6IQM5IK1Nki/oDFgD
EEhYNMSH8pf3BkVg6WeD4Rhu5DH96n78NGmRkVe70zCGjgTI/wOkPtNU8e2D/52K
xmsEX5U9vB2cHpKpZcUUN3qt9rKh6yVlcueb/nOOJHThAMKhOL/8CxUgWS54+t2b
BhMq/pJ3GmTaPCSqqduGjjM4bRuEdaq15ezq4P4RguD5KcFpLqNnlPNYVVEdv1+V
hshNmBoPDEN1jehkmCRAKkVGt+LIAeaQN47J8EJcLXp+VpsfrC6aKiNQ+YgB/DHb
WD2eCPGfPMx1PElFEpkMtLJxSnJe9BTtqYFQInwkfcyPdAWXXcFSkh/Rf3JMPTH0
sSCu39IERcdarKzDBpZTno9PuMK+V8w90Cf0J4pDxQV4QStPJgyjwSfPEpFdSNq+
DsyP1VhAWZtARDuoE7Imm9ZMiztbPTfbm2ZtVV6+iW3Fa5LtOKIt+MD/A1swDpDF
Wqz0h33UMjbUT7yGjLuYAhVDlagOCaGmgiJL4g6mK6lEghQ7qsUwd1L87+bVdVPt
wMmiClpl9EcN7D9s0RSc6nfx9HsOwOaAhxXPncmaql+6g6lYZN8=
=VuXA
-END PGP SIGNATURE-


___
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] Accepted prometheus 2.2.0+ds-1 (source) into unstable

[Martín Ferrari]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 14 Mar 2018 18:18:37 +
Source: prometheus
Binary: prometheus
Architecture: source
Version: 2.2.0+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 
<pkg-go-maintainers@lists.alioth.debian.org>
Changed-By: Martín Ferrari <tin...@debian.org>
Description:
 prometheus - Monitoring system and time series database
Closes: 888153
Changes:
 prometheus (2.2.0+ds-1) unstable; urgency=medium
 .
   * New upstream release. Closes: #888153.
   * Add notice about DB changes.
   * Update TSDB version.
   * Refresh patches.
   * Update Azure patch for new breakage.
   * Inline unreleased method from the golang client lib.
Checksums-Sha1:
 3b5cfc1337c75ed664c126b34a60ca03b1bd169a 3319 prometheus_2.2.0+ds-1.dsc
 d6ccaa7bd6ef4cf8fc51c7f941d7fc4188eb341b 1028048 
prometheus_2.2.0+ds.orig.tar.gz
 68a0c75380659b9ca0d4af12367be5309f607036 26376 
prometheus_2.2.0+ds-1.debian.tar.xz
 736527fb6b5dfff61220f3e3e6a7390077d9d9f3 11519 
prometheus_2.2.0+ds-1_amd64.buildinfo
Checksums-Sha256:
 c94de16918725034e0f7e0fac281488917a11de9034aa7e199e7f646390045c4 3319 
prometheus_2.2.0+ds-1.dsc
 ef9a88451fb28f0696844fd26f83ce07fcf54dcf94fb8bae37044045b40276ca 1028048 
prometheus_2.2.0+ds.orig.tar.gz
 d450ea7f3f46e36074021aa99fe361493a57f419a1fcf1445dbac101368efa2f 26376 
prometheus_2.2.0+ds-1.debian.tar.xz
 382dcee2dd5072fb8a6dcf1b96eb30b216fabef6dedcef255a283b2e8e18fc5b 11519 
prometheus_2.2.0+ds-1_amd64.buildinfo
Files:
 db21a645236d03023b168e4c44d2dba7 3319 net optional prometheus_2.2.0+ds-1.dsc
 639fc5f3dd3faf6d9178437fbda61be5 1028048 net optional 
prometheus_2.2.0+ds.orig.tar.gz
 da6d01bcc5aa186ef794145af9ed0ac9 26376 net optional 
prometheus_2.2.0+ds-1.debian.tar.xz
 5ee67f656e7c9341c43535ba2aa34eeb 11519 net optional 
prometheus_2.2.0+ds-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEETe94h3mvRsa9AoOeXdjgv5Gj09oFAlqpaAoACgkQXdjgv5Gj
09rs2A//fFua269dmGDa2OnB903TZr1qu1BfEIVEgKJYJ2CmB7bv5kfhSxPRqRiT
q7nBitsvhfy6f3voEoUdR+KmRAeraxHF2npwRVZt8pVoLp3SsAZbiDX0uUT8GRYv
3C4zmkvuQYIZA6MDmrQjg6UyzeH4N8UA/Sk5sohf9HyuBSFoXb+3UJ2Ut2pf+ZUV
h2zqExLQHrW0sOGaiAN/15ic94+2Q+XmbyVIoEi7fOc241/VjR6vZgLAlM81ha0R
1Mdgwzpd7jc9fzXUkKfe0633xSCdkiDfL1h8PoScL28SbTs1Ot4OWnnfD85O4/n1
1vIWPI/h3dh/jBpcoFTfZwwH+aec0NRDsJOn6BvMEEstLd2tQFW4zhWMUurk47h6
sGp3TuVPFryrG/U1xPfNJqGBMFK3oj3qx3wu9WuPxhQ2B5kQtQIfOw0+9Vg83Hj0
kzSNjVe5Sbha6Mht1Yyv2ymvXp16mFu87kp2kdJYGHLHcIHVVoif0y61R6h/1N74
LxZDqueeQ06dp+CZlIamDdIXCfnNMmeOZTPoWAxKvCBWV8p1sdQimw9YhqWfUlzZ
bmjvnPw+cO8MElA2duRGUibkytqjaQNPEBKy3KUsWbJ5w7RQNgeS2VWv+93XXXh+
5ZsIyCqGGl9iaCpMIFBJqUm/HuAMvED+oM1InNMvrAd5AKW1xNM=
=tcUm
-END PGP SIGNATURE-


___
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] Accepted golang-github-prometheus-tsdb 0.0~git20180302.16b2bf1-1 (source) into unstable

[Martín Ferrari]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 14 Mar 2018 14:13:48 +
Source: golang-github-prometheus-tsdb
Binary: golang-github-prometheus-tsdb-dev
Architecture: source
Version: 0.0~git20180302.16b2bf1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 
<pkg-go-maintainers@lists.alioth.debian.org>
Changed-By: Martín Ferrari <tin...@debian.org>
Description:
 golang-github-prometheus-tsdb-dev - Prometheus storage layer library
Changes:
 golang-github-prometheus-tsdb (0.0~git20180302.16b2bf1-1) unstable; 
urgency=medium
 .
   * New upstream snapshot, for prometheus 2.2.0.
Checksums-Sha1:
 a3cb743fcec4201bc7ef842d933fabe78dfcb2c2 2723 
golang-github-prometheus-tsdb_0.0~git20180302.16b2bf1-1.dsc
 6ea9601df5501a5ee71265d5012dedd5855ce839 2407272 
golang-github-prometheus-tsdb_0.0~git20180302.16b2bf1.orig.tar.gz
 2dcdad814a89069d1197cfbce5b56d5f1b218d3d 3456 
golang-github-prometheus-tsdb_0.0~git20180302.16b2bf1-1.debian.tar.xz
 8ed132a4463a17cebc1fa55f641b2bd5dd036586 8310 
golang-github-prometheus-tsdb_0.0~git20180302.16b2bf1-1_amd64.buildinfo
Checksums-Sha256:
 3d6a0c88a284e3dbe27da37a631d92410b4187a0f84b66f6753632f515aefc75 2723 
golang-github-prometheus-tsdb_0.0~git20180302.16b2bf1-1.dsc
 a2736b53a97c7393a9f54df0cc4033002e2395b5fc9cda0b16d02c60cbfc0e96 2407272 
golang-github-prometheus-tsdb_0.0~git20180302.16b2bf1.orig.tar.gz
 ab8c19b29caa614a839abe6dc53f8137195ece4c218c8627ed82efb3387398ee 3456 
golang-github-prometheus-tsdb_0.0~git20180302.16b2bf1-1.debian.tar.xz
 a0aaa425208e588dcb988ddd4cfd94f6a80ab8591bca8cad59b7a9f357c4ecc5 8310 
golang-github-prometheus-tsdb_0.0~git20180302.16b2bf1-1_amd64.buildinfo
Files:
 f9cf86c335278bb1ebf2586445e2fe40 2723 devel optional 
golang-github-prometheus-tsdb_0.0~git20180302.16b2bf1-1.dsc
 fdaee806e89c83e9bac5bc203991dc8f 2407272 devel optional 
golang-github-prometheus-tsdb_0.0~git20180302.16b2bf1.orig.tar.gz
 8517765f37c490513495ed6dafbaea6b 3456 devel optional 
golang-github-prometheus-tsdb_0.0~git20180302.16b2bf1-1.debian.tar.xz
 31ecdb57e2fdc05d06772b5e7cc7bcfd 8310 devel optional 
golang-github-prometheus-tsdb_0.0~git20180302.16b2bf1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEETe94h3mvRsa9AoOeXdjgv5Gj09oFAlqpLrMACgkQXdjgv5Gj
09rM9BAAsciaRbvTMZFxrJNIneyNkgTNUvXnVojpEa9nP3YhD5PBZvNhqfQjf83k
pxMC2i1x2HR5G0YJVcUIvpWKrAlDAnXQ+Y76jcQwY1ghNCv2/7AcbJx0DdIqCEeo
mDdSP+c653/5JDsciWHeW8DNcrnbsmIHbZsTREs5LN0CI28ei6x1aWHwX5F6Wydl
bZigW2gWqyrxDtheAtWlUWtuVRyopkq4WytmHTkrT0jrZHC/nJDHuTnaKoRombq0
2Z2DYMYZjgTiJLfC4KaYxW/JbPCJgWdnohaKm0yQHDTOhXhzy4Ei5aI2/VEyuQCc
5wnjtlZWMY1qCsIGcLXW/sWMmFWdvMUQ1Yc1DCdm5DXl3vIZdZHiK3xrqzhluCWF
MSJPuiIJQ5d8LYoW9VQ03gEZ9etF7V8B+lMNJI46KjWH7X4pj2DOp/7k9M7Ttv5R
5u471ZxPee3EXZ/nZb7Cxy7BXyPgbK7bA50tJqZnzEav0f6Ha6ztbnmMA6QyVPRb
wW3oSZPLtponHiDanNT/W/A32hKi3f5GOWMVQsP1T42Xgrrupi8WbYjAzwMU8pS1
++0fy9XnbTAAJih0LE75vTU5U1j9wi4KOp1A3n+vis+7hMZ3EFve6IDLQXFI1yto
v+IGL9/ku27worWZRx5GSEdskDkbEzbY3twLpWuvgfJpRmxJyOY=
=bXLs
-END PGP SIGNATURE-


___
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] GitLab CI: git-buildpackage and ratt

[Martín Ferrari]

On 04/03/18 21:39, Michael Stapelberg wrote:
> Ah! Runs will automatically be triggered as soon as a gitlab-ci.yml file
> is found. You can retry any run with the “retry” button next at the top
> right. See for
> example https://salsa.debian.org/go-team/packages/ethflux/-/jobs/8312
> 
> Does that answer your question?
Ah, that's perfect. Thanks!

-- 
Martín Ferrari (Tincho)

___
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] GitLab CI: git-buildpackage and ratt

[Martín Ferrari]

Hi,

Thanks for all the info, now it is a lot more clear!


On 04/03/18 08:48, Michael Stapelberg wrote:
> * What kind of control do we have over it?

> Not sure I follow. Can you make this question more specific?

Wondering about if it is posible to manually trigger runs, re-tries, etc.


-- 
Martín Ferrari (Tincho)

___
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] moving to salsa.debian.org

[Martín Ferrari]

On 01/03/18 08:18, Michael Stapelberg wrote:


> I agree with mwhudson’s reply — go-team as group name is what we settled
> on (see my thread on the subject, which had a long feedback time
> window). I’m okay with the compiler team being a subgroup.

Sounds good to me, just wanted to make sure that we agreed on it before
doing changes :)

> Can you explain why the maintainer address needs to be changed in the
> same step as the repository move?

It is true, it does not need to be at the same time. But if we are going
to upload about a thousand packages with the repo changes, we should
probably avoid doing twice :)

> As far as I’m concerned, we can leave it as-is for the time being. The
> mailing list will be migrated, and there will be a separate turn-down
> cycle for that in a few years.

OK, if that is possible, I have no objections.

-- 
Martín Ferrari (Tincho)

___
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] GitLab CI: git-buildpackage and ratt

[Martín Ferrari]

On 01/03/18 07:58, Michael Stapelberg wrote:
> I’m assuming you have read https://pkg-go.alioth.debian.org/ci.html
> already. If not, start there.

I had read it, but it was good to read it again.

> Instead of sharing the knowledge only on mailing list posts, I would
> strongly prefer to extend ci.html such that it makes sense to everyone
> and is easily discoverable.
> 
> Could you pose a few specific questions, which I’ll try to answer
> through updates of ci.html? Thanks!

I think the problem is that I don't know anything about Gitlab and its
CI infrastructure.. My main questions would be:

* Where does all this run?
* How does it communicate with gitlab?
* What kind of control do we have over it?

Sorry for the very basic questions..

-- 
Martín Ferrari (Tincho)

___
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] Accepted prometheus-alertmanager 0.6.2+ds-3~bpo9+1 (source amd64) into stretch-backports, stretch-backports

[Martín Ferrari]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 24 Feb 2018 12:26:30 +
Source: prometheus-alertmanager
Binary: prometheus-alertmanager golang-github-prometheus-alertmanager-dev
Architecture: source amd64
Version: 0.6.2+ds-3~bpo9+1
Distribution: stretch-backports
Urgency: medium
Maintainer: Debian Go Packaging Team 
<pkg-go-maintainers@lists.alioth.debian.org>
Changed-By: Martín Ferrari <tin...@debian.org>
Description:
 golang-github-prometheus-alertmanager-dev - Handle and deliver alerts created 
by Prometheus -- source
 prometheus-alertmanager - Handle and deliver alerts created by Prometheus
Closes: 862007 871330
Changes:
 prometheus-alertmanager (0.6.2+ds-3~bpo9+1) stretch-backports; urgency=medium
 .
   * Rebuild for stretch-backports.
   * Tighten dependency versions.
   * Fix acceptance tests (log.level flag does not exist anymore).
 .
 prometheus-alertmanager (0.6.2+ds-3) unstable; urgency=medium
 .
   [ Martín Ferrari ]
   * Team upload.
   * debian/control: Update Standards-Version (no changes).
   * Automatic fixes to control and copyright from cme.
   * Replace dpkg-parsechangelog with /usr/share/dpkg/pkg-info.mk
   * debian/control: Update package name for client-golang.
 .
   [ Michael Stapelberg ]
   * gbp.conf: set debian-branch
 .
 prometheus-alertmanager (0.6.2+ds-2) unstable; urgency=medium
 .
   * Fix compilation on gccgo/mips*.
 .
 prometheus-alertmanager (0.6.2+ds-1) unstable; urgency=medium
 .
   * New upstream release. Closes: 871330, 862007..
   * Fix installation path for source files.
   * Refresh patches.
   * Add gbp.conf.
   * debian/copyright: Document new vendored dependency.
   * debian/control:
 - Update Standards-Version (no changes).
 - Fix Vcs-* fields.
 - Mark package as autopkgtest-able.
 - Require latest version of the common library.
 - Add new dependencies.
   * debian/default: Update options.
   * Fix /var/lib permissions.
Checksums-Sha1:
 a41d624f920992d03f7956ef8375ce3ae79bbf21 2890 
prometheus-alertmanager_0.6.2+ds-3~bpo9+1.dsc
 e680ea4cf461132a895b2c01c45158a59b64e412 11204 
prometheus-alertmanager_0.6.2+ds-3~bpo9+1.debian.tar.xz
 f2602da21b5b34fe439aecc0e3602c0d3dac8262 91198 
golang-github-prometheus-alertmanager-dev_0.6.2+ds-3~bpo9+1_amd64.deb
 00973c59ba77556d09eaa99c41da5e784690bd74 12991 
prometheus-alertmanager_0.6.2+ds-3~bpo9+1_amd64.buildinfo
 3bff62d275b91668328118297e829fdad5f712ad 2328462 
prometheus-alertmanager_0.6.2+ds-3~bpo9+1_amd64.deb
Checksums-Sha256:
 4f830e11a64b6a5ee75dfe56421256ef99ef8f8a1f30d9335d7a2e4769280a8b 2890 
prometheus-alertmanager_0.6.2+ds-3~bpo9+1.dsc
 3a35aace82381681abd0c06875e19426c53c7bc9f38371bed87a37fc90c30082 11204 
prometheus-alertmanager_0.6.2+ds-3~bpo9+1.debian.tar.xz
 19d7393d065bfb08884325bf61009d35bded15329eae4d499e4e7ec0626aa680 91198 
golang-github-prometheus-alertmanager-dev_0.6.2+ds-3~bpo9+1_amd64.deb
 402ef3d9bcb7522db7ea156a778f5673dac8bddc68a1346da51230f2ea067fd3 12991 
prometheus-alertmanager_0.6.2+ds-3~bpo9+1_amd64.buildinfo
 441e13827a1d1cdfaba46fe1a4f6899a73ab5ac6b1291f7a6337324a4933b9b6 2328462 
prometheus-alertmanager_0.6.2+ds-3~bpo9+1_amd64.deb
Files:
 a780dfd6ae82efeff9227b278684ee0a 2890 net extra 
prometheus-alertmanager_0.6.2+ds-3~bpo9+1.dsc
 569b96c28266e12e21c67b826cc29f5b 11204 net extra 
prometheus-alertmanager_0.6.2+ds-3~bpo9+1.debian.tar.xz
 bd57b337f9d8e2d3d1e7c8be7c84d994 91198 net extra 
golang-github-prometheus-alertmanager-dev_0.6.2+ds-3~bpo9+1_amd64.deb
 8d81532089557f9b5d61f018c5e73750 12991 net extra 
prometheus-alertmanager_0.6.2+ds-3~bpo9+1_amd64.buildinfo
 cdc81bf3b655480858c43540b8307b83 2328462 net extra 
prometheus-alertmanager_0.6.2+ds-3~bpo9+1_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEETe94h3mvRsa9AoOeXdjgv5Gj09oFAlqRW/0ACgkQXdjgv5Gj
09r+khAAyW2xC7ZOReaBgvokMZ0qRa0RsjODUx3IGpU/lviPz1B0vnivin8AA+VS
NfEOTSyc04s7gLrPfeqEm7Wls508+nxOTZNQ5WvnpRVq9ctmJmytoXii4HwswjM4
cLEIreejhxj4z3nVLfKwVFzqwIkHaREeI7hMHd6zGOo31fIrvj856pHNDFrqF6J4
BIG/5ECSQXdruYIJE5ubt7huaWGmlb0ZfVyymXlny+5Is+ofYyJxONAd+wMhh3Xd
g0ljoJY3XMrz1zMk050FLhAD97qkLh9meLDQrYHoTGX+gHq13q+LsRmcdX0eyfvB
QQwBemYiDN2Z9rKKp2sZcC4zqTLpV7xgABLdb1kYETtNp2DFF08aQsgvpaO+ZTuN
/aZRxifeopYrypb9FU83D8TpXslLL2tGDhAy8i8dQOqkUd+ZZnCH45qntrbHGxsO
P7cnm4F034OJbcvg91eRiKsr6VsxEW43fes21ISsvsbA2qC7fafBa94L12CX1p88
MdksJB8126UBd75KLl8f+rWCZVXbvQzkHkTif+M1pyQOWSb1WnhNbSvzCWFeiOQE
370Lh8632yjLnYiTFf2DC83lZ8P+cTRwKjyoXtJDXn2z63m7X1Yl5qR1khPRtnMP
Di02P2pemH3K8Qo45RUguWxPBhj2iNZew8BC4rmmVy7v0o77Rak=
=9KnZ
-END PGP SIGNATURE-


___
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] moving to salsa.debian.org

[Martín Ferrari]

On 28/02/18 23:28, Michael Hudson-Doyle wrote:

> The salsa group is now called "go-team" and I thought that's the one we
> were going to stick with?

I was not sure if that was already agreed, same with the names for the
submodules, in particular where the packages are stored.

> The go compiler stuff should be a subgroup of the go-team group,
> although I don't think anything about that should block the package
> migration.

True.

-- 
Martín Ferrari (Tincho)

___
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] moving to salsa.debian.org

[Martín Ferrari]

Hi Michael,

Thanks for moving this forward!

On 27/02/18 21:10, Michael Stapelberg wrote:

> dh-make-golang’s create-salsa-project subcommand now calls this logic
> via an HTTP request, so that we can update the logic independent of the
> version of dh-make-golang that users are running (we’ve seen people run
> very old versions). See

I was going to say that my version of the tool does not have it, but
then I realised it is there, but the help or the man say nothing about
it.. Is there a reference somewhere?

> Tincho, aviau, can you confirm that we’re good to go?
> aviau, are you still up for coordinating and doing the next steps
> (sending the announcement, migrating the repositories)?

I have some things in mind that I think have not been resolved yet:

* Have we decided on a naming scheme, including group name? What about
the go compiler stuff? (I think it will make sense to join everytihng
under one group)
* What about mailing list and maintainer address? I know the perl people
solved this somehow, but I don't understand how :)

These two are important, because we should define them before changing
all repos and mass-committing hundreds of changes.

-- 
Martín Ferrari (Tincho)

___
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] GitLab CI: git-buildpackage and ratt

[Martín Ferrari]

Michael,

On 25/02/18 22:43, Michael Stapelberg wrote:

> I ran this yesterday and had it do a CI run for all of our repositories.
> There were 3 failures, all of which because the repository in question
> has a debian/changelog entry whose version git-buildpackage cannot find
> as a tag:

This all looks great, thanks a lot!

Now, I am still a bit confused as to how this all works :-) Could you
share a basic intro?

-- 
Martín Ferrari (Tincho)

___
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] Accepted golang-google-cloud 0.9.0-5 (source) into unstable

[Martín Ferrari]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 26 Feb 2018 13:30:54 +
Source: golang-google-cloud
Binary: golang-google-cloud-dev golang-google-cloud-compute-metadata-dev
Architecture: source
Version: 0.9.0-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 
<pkg-go-maintainers@lists.alioth.debian.org>
Changed-By: Martín Ferrari <tin...@debian.org>
Description:
 golang-google-cloud-compute-metadata-dev - Google Cloud Platform APIs (only 
cloud/compute/metadata)
 golang-google-cloud-dev - Google Cloud Platform APIs
Closes: 891356
Changes:
 golang-google-cloud (0.9.0-5) unstable; urgency=medium
 .
   * debian/patches: Fix typo.
   * Fix racy spanner test. Closes: #891356
Checksums-Sha1:
 6fe1216fc79855fcc09eed537525b33d7e538b7b 2709 golang-google-cloud_0.9.0-5.dsc
 3f9007091021a3c6436ae2c661cab50ee47d4d09 7104 
golang-google-cloud_0.9.0-5.debian.tar.xz
 0b0f31f4339037ef26a0c81a64a110d17974e6a6 7025 
golang-google-cloud_0.9.0-5_amd64.buildinfo
Checksums-Sha256:
 959ac87853f3f42c24b15046f3e5dc6d72286a69f4f6ea8733606a21f140ee5f 2709 
golang-google-cloud_0.9.0-5.dsc
 de5155c8aacf65b6d19f08b3023a9fb83159422c54c7867e4724c2995923c230 7104 
golang-google-cloud_0.9.0-5.debian.tar.xz
 ee3f138869c4db110204e0d0ce8fe81627c1425166a466235cf529b9ae0016d7 7025 
golang-google-cloud_0.9.0-5_amd64.buildinfo
Files:
 117914e219fc6747002a1d988e26c8e5 2709 devel optional 
golang-google-cloud_0.9.0-5.dsc
 f3d742edc9f45a084e61b42c39a28dad 7104 devel optional 
golang-google-cloud_0.9.0-5.debian.tar.xz
 57302eee2092a76fe5073734c0b47b1e 7025 devel optional 
golang-google-cloud_0.9.0-5_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEETe94h3mvRsa9AoOeXdjgv5Gj09oFAlqUDMUACgkQXdjgv5Gj
09rR0w//Z9eRRnOZT5+pFTuLBBMXJ1PyhGw11HUuwzSt4W37S1zYFAb4fNqqYISO
NuJN7rNoQKxU7YnKYF3SWQbZkzJ4DIlg8g2yIuB3/fQ8t4KbEVVbATuMIxZlhdan
/Pnp4dUU5TUoOgSoFnBpOEkn6/Ab6FOg4kHVKlklRngSHaWNpLimW3brbr21Y79T
9lKSRP0H1P4PKf9wkTVwLJx0sZdKenSJ1zv9AdxPQIfzkBgV5mb4Zyf6YQ4rWWL1
xTBgstJpdlZ931iOqCyx3kWYO35MyLeLgJlSxvR3udE45cic02ook4nti2A4+MNX
0NfCP0TGdN43Irr0CU71NoK5RLemG6+wA8wZTjXigtVrvDv8yNmtRT8b9rVBdaCN
rXrxYRc76O3M7JaRnxaNjch37AMQoXbTipJIv9WL04b+6MBVvVLBWsO34d1rnAnr
9OTT0E0KEnXBqIgWi+WNj2R5EGaqDxMH8crN5RRcCvoHOja3tDS+CeoRXFc6ulPl
F145Ra01UoGTGwAxoIBgqevhmHT4Op8hGcXWdQMDM52P4FqFKVRv7wwc+LOmZemh
Ksm7q3FoU9huuBXql3BOt3mQIJgRr2rJbXSp8M36sFwdUEpvqdKw8kopD7On+4cI
yLumHCXLBa+XReEvst6wJvYjlBWaRNwclmp4vA5dsVrG/piD6Aw=
=ipVB
-END PGP SIGNATURE-


___
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#891356: Bug#891356: golang-google-cloud FTBFS: FAIL google.golang.org/cloud/spanner

[Martín Ferrari]

On 24/02/18 21:14, Adrian Bunk wrote:
> Source: golang-google-cloud
> Version: 0.9.0-4
> Severity: serious

Another flaky test. Actually, I think it only worked by chance (because
goroutines will take a while to start), but it still required a busy
CPU, 19 niceness, and a while loop to reproduce..

I have a fix and it seems I can't reproduce the problem any more.

-- 
Martín Ferrari (Tincho)

___
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] Accepted golang-golang-x-tools 1:0.0~git20180222.0.f8f2f88+ds-1 (source all amd64) into unstable

[Martín Ferrari]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 24 Feb 2018 12:07:14 +
Source: golang-golang-x-tools
Binary: golang-golang-x-tools golang-go.tools golang-golang-x-tools-dev 
golang-go.tools-dev
Architecture: source all amd64
Version: 1:0.0~git20180222.0.f8f2f88+ds-1
Distribution: unstable
Urgency: high
Maintainer: pkg-go <pkg-go-maintainers@lists.alioth.debian.org>
Changed-By: Martín Ferrari <tin...@debian.org>
Description:
 golang-go.tools - Transitional package for golang-golang-x-tools
 golang-go.tools-dev - Transitional package for golang-golang-x-tools-dev
 golang-golang-x-tools - supplementary Go tools
 golang-golang-x-tools-dev - supplementary Go tools (development files)
Closes: 890927
Changes:
 golang-golang-x-tools (1:0.0~git20180222.0.f8f2f88+ds-1) unstable; urgency=high
 .
   * New upstream snapshot. Closes: #890927.
   * Refresh patches.
   * Add new lintian overrides.
   * Fix gccgo build by disabling a couple of tests.
   * Stop manually copying testdata.
Checksums-Sha1:
 b4cc12a8905f82db008ac17130f91a3c327c7248 2717 
golang-golang-x-tools_0.0~git20180222.0.f8f2f88+ds-1.dsc
 47e4d5f593aabd2a6ab227c8b91961f9fc49a4a1 1173094 
golang-golang-x-tools_0.0~git20180222.0.f8f2f88+ds.orig.tar.gz
 e76e885a0be8f9792ef69aab97412b6ec85a68e6 24440 
golang-golang-x-tools_0.0~git20180222.0.f8f2f88+ds-1.debian.tar.xz
 49c8bf276bf354dcf644188b81981d239fc8fe78 12036 
golang-go.tools-dev_0.0~git20180222.0.f8f2f88+ds-1_all.deb
 50e52a95bd63cf4681cc2cf92a7df6e5b49f8c04 12028 
golang-go.tools_0.0~git20180222.0.f8f2f88+ds-1_amd64.deb
 4ed200c920990053e5e5e593e2d98ff799321938 952980 
golang-golang-x-tools-dev_0.0~git20180222.0.f8f2f88+ds-1_all.deb
 511394b8af996faba2519ac149b1c94271848385 7215 
golang-golang-x-tools_0.0~git20180222.0.f8f2f88+ds-1_amd64.buildinfo
 4e66b6a7f2ac181e944894c2b27ccff54a8bd8cd 16087324 
golang-golang-x-tools_0.0~git20180222.0.f8f2f88+ds-1_amd64.deb
Checksums-Sha256:
 7c98dbf9123a258af76ac29d0fed25eb17996647339ea3816f59c47b4964f452 2717 
golang-golang-x-tools_0.0~git20180222.0.f8f2f88+ds-1.dsc
 b149357a0cb2d6e92fd24c92efc08a5254bce24ec5e24fc84a13dd0f225c7f06 1173094 
golang-golang-x-tools_0.0~git20180222.0.f8f2f88+ds.orig.tar.gz
 883645e7c9ec497d4570e46f7bab2679491cc959aabd340c854b05a6a5111475 24440 
golang-golang-x-tools_0.0~git20180222.0.f8f2f88+ds-1.debian.tar.xz
 e0b0b58ddbda308cd3d8f85fa463fe787e9dfeb85b47af3ad2db3f84a1fc6f11 12036 
golang-go.tools-dev_0.0~git20180222.0.f8f2f88+ds-1_all.deb
 d2803bd6c096b3fcd1c9c868c6342c6634344ff0fd0a448828f825e4ef997716 12028 
golang-go.tools_0.0~git20180222.0.f8f2f88+ds-1_amd64.deb
 43c98ba7d41f0ccf30a9f534968288f0832fd8e1561c2297f25a2af7013cbf94 952980 
golang-golang-x-tools-dev_0.0~git20180222.0.f8f2f88+ds-1_all.deb
 9be6d8d7e6436fd2ea9cfe69923d0421773e4bdb4d2b307b2c3d7bbbf0bad5ed 7215 
golang-golang-x-tools_0.0~git20180222.0.f8f2f88+ds-1_amd64.buildinfo
 0c298ac839a4a5688fdafb5e58fd12e9a65fcbd597df1bdd181d34f06dcf5c60 16087324 
golang-golang-x-tools_0.0~git20180222.0.f8f2f88+ds-1_amd64.deb
Files:
 1be98663cc5ab3baf7eab5f6b992892a 2717 devel optional 
golang-golang-x-tools_0.0~git20180222.0.f8f2f88+ds-1.dsc
 a76f5f9c158a6a824f2db643ee8ec84c 1173094 devel optional 
golang-golang-x-tools_0.0~git20180222.0.f8f2f88+ds.orig.tar.gz
 9be58461ddd6c3928e220727ef6bf035 24440 devel optional 
golang-golang-x-tools_0.0~git20180222.0.f8f2f88+ds-1.debian.tar.xz
 69a14ff4929d496a2487824b9ec05862 12036 oldlibs optional 
golang-go.tools-dev_0.0~git20180222.0.f8f2f88+ds-1_all.deb
 4cdced265680eda44f626634fb3395ec 12028 oldlibs optional 
golang-go.tools_0.0~git20180222.0.f8f2f88+ds-1_amd64.deb
 ca0569019aa386b0292164bd280f2cde 952980 devel optional 
golang-golang-x-tools-dev_0.0~git20180222.0.f8f2f88+ds-1_all.deb
 63d91012a103a6badf0bacea37e9dbfd 7215 devel optional 
golang-golang-x-tools_0.0~git20180222.0.f8f2f88+ds-1_amd64.buildinfo
 22bff20879937ff6f062c7be9401cf54 16087324 devel optional 
golang-golang-x-tools_0.0~git20180222.0.f8f2f88+ds-1_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEETe94h3mvRsa9AoOeXdjgv5Gj09oFAlqRVoEACgkQXdjgv5Gj
09oeFhAAwhMZu1u/DsFMIew66W8Uy/sF75vAc37hhrLjPo7HOS1Mkm9v0OSxUNnC
EBB/ovwR4vyMdW5Xprd7LBWBTIO/883XsmLywQ27KQlfkytYXyBrQJgTHLKKICq+
k/mHdinRjzSHImjk8RPkvQDRZTVes6CIFggIURLA8OIgFksvgPn10VBFHANBoZ0m
9Y1DBePEk3hmQZ/jIFKVhpoxWQUXlf7lFAtZvDLy2tenbJbvW12v2xJ9SF76crZX
u+XJn3QM+LWjQsjgQyzVQhQwuRJH+huhnMTPf9zdO2V66bWTlKtf30pqgV/c1Aap
+ybrqnIK0AAsnmyJ3xvL5OlnmFvtHlhwXsAdJuDUARFxSGLoAhy4gJBgEEXgRBXN
C0VuPDDXiZnQtc5W6iluFdhirpiRGbr62mYXfpRV3523ervHfblfYJpjWkd52N5L
ikFPRTd3ApYhGW1Nn5Uw/o97Ul7kd/UVGYy4fq8PxYpiZJT07/aW7LpMSGz3hWEj
vRPlM0p/q9F3RPd3x816e4bn3CVp17mrMlGsTQo1AgYkjLbwu6WytooRKXoE0WaL
NpQK5frMKjctqIgqG3f+eBOljRqjRtj6UYVaqXWECpjGbcCcJ4rlTUGR0rbt4W1g
Q7O7r5JJMGwMH5qVNVvB8fMLCSB26a/gua5xrLZ6GXuvskfvf2g=
=RbnP
-END PGP SIGNATURE-


___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian

[pkg-go] Accepted golang-google-cloud 0.9.0-4 (source) into unstable

[Martín Ferrari]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 24 Feb 2018 11:02:49 +
Source: golang-google-cloud
Binary: golang-google-cloud-dev golang-google-cloud-compute-metadata-dev
Architecture: source
Version: 0.9.0-4
Distribution: unstable
Urgency: high
Maintainer: Debian Go Packaging Team 
<pkg-go-maintainers@lists.alioth.debian.org>
Changed-By: Martín Ferrari <tin...@debian.org>
Description:
 golang-google-cloud-compute-metadata-dev - Google Cloud Platform APIs (only 
cloud/compute/metadata)
 golang-google-cloud-dev - Google Cloud Platform APIs
Closes: 890938
Changes:
 golang-google-cloud (0.9.0-4) unstable; urgency=high
 .
   * Fix FTBFS with golang 1.10. Closes: #890938.
   * Bump Standards-Vesion with no changes.
Checksums-Sha1:
 fe1198090f1b082396969faf5add984d509021aa 2709 golang-google-cloud_0.9.0-4.dsc
 857bebbdf95a3d49ba23bec407c0c62db9b36c22 6836 
golang-google-cloud_0.9.0-4.debian.tar.xz
 bb66a36b1f9594c2c1bfdcd7c7007232d8562e55 7010 
golang-google-cloud_0.9.0-4_amd64.buildinfo
Checksums-Sha256:
 1b63929fa4ee764eb982dd1f4761014840a50ad311683d81328407e97df658e0 2709 
golang-google-cloud_0.9.0-4.dsc
 e2c43d7a3d905d45414d0856dcb46e943f736ff2f8cea8b829ec493888f8bc91 6836 
golang-google-cloud_0.9.0-4.debian.tar.xz
 a1051f298a1747b46dea26535ce0e35090e9811a90409886b92f16c817f054cf 7010 
golang-google-cloud_0.9.0-4_amd64.buildinfo
Files:
 a51b94e83780c3583b6ac4bfe0db151d 2709 devel optional 
golang-google-cloud_0.9.0-4.dsc
 c23c47a82d3ed16efd3732f523a59f96 6836 devel optional 
golang-google-cloud_0.9.0-4.debian.tar.xz
 e978339fca75cba042b98d1086677bc6 7010 devel optional 
golang-google-cloud_0.9.0-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEETe94h3mvRsa9AoOeXdjgv5Gj09oFAlqRRx4ACgkQXdjgv5Gj
09qTxw//du1892xn5hiFx/3aNXM9QVv9I1lJvjQ2oXoaPYSxZG1SBDBavKSOzClO
zDlV1HXBiZfjt/bl4sONX8Cfo4TfiJLoz/ueJrBPWmlYqfDmwbeaIsH1X25AaW2i
Pepz2sK0f8qLavAcJlnuhyEOhrwMy+NlIKarb69hqFRA3Cq8eL3n6AxlG7yeoAZw
BKNPR3XBKoGkrOd+YPVNIQsIHwGrFjD5bXpllsovZVkUwR0XqdbqL7NCmjTiKF4Y
PSOlFRXFCuSYckOoscxoOW0P8o7q908UplJGgdf9mQofeh7NBoKzLWaEoDBzyRas
Mni2fe1C3T2IxwTU8KsdvURiuVw8zmaJAem8u/6gfVUp3TftGDjwC9zAFnBj6nKw
qwxUQKyiLYSCr6SBbiQcgqLAviyZqkvlwtLzBWvE5ZXHGl7afmjp1qbXdyeZuIbd
E7/JbZT0QLeyT+nX7SBRQ5qaptdJj1xSx7GQh9srCLA1RdG1/EpvKtD9UATcuu57
yEA/XcTZgTzld+jfbyhwgcWChguD69ChPhltk7wpK/AkXeWXBDHjFeT5GSd18Fqu
NMkzBEzJI68eC9I4jolaJj8J7/qHBA41GiFgu3gmyf9NC0O5W1XhkcnRNsdGtKX8
gmakEwAe7qJ8aaRYdMDQnBYA3/I4r+4DmHzCAVUIDtP9UVyFuvg=
=cshC
-END PGP SIGNATURE-


___
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#890927: Bug#890927: golang-golang-x-tools: FTBFS and Debci failure with golang-1.10-go

[Martín Ferrari]

On 20/02/18 19:17, Adrian Bunk wrote:
> Source: golang-golang-x-tools
> Version: 1:0.0~git20170707.0.bce9606b+ds-1
> Severity: serious

Thanks for the report. It seems this is one of the packages that broke
with the swtich to golang 1.10. I will take a look into it.

-- 
Martín Ferrari (Tincho)

___
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#891202: Bug#891202: prometheus-alertmanager: False owner/group for /var/lib/prometheus

[Martín Ferrari]

Hi,

On 23/02/18 12:17, tuxcoder wrote:

> The service trys to `mkdir /var/lib/prometheus/alertmanager` on startup,
> but the dir `/var/lib/prometheus` is owned by root.
> 
> If the package `prometheus` is installed first this is not the case.
Uhm, I think you are mistaken, or I missed something.

The directory is created when unpacking the deb file:

$ dpkg -L prometheus-alertmanager | grep /var/lib/
/var/lib/prometheus
/var/lib/prometheus/alertmanager

Then the post-installation script does this:

chown -R prometheus:prometheus /var/lib/prometheus/alertmanager || true
chown -R prometheus:prometheus /var/log/prometheus || true

And the initsciprt does this (as root):

mkdir -p `dirname $PIDFILE` || true
chown -R $USER: `dirname $LOGFILE`
chown -R $USER: `dirname $PIDFILE`

So, I don't know where you saw that mkdir, nor where it could be a problem.

-- 
Martín Ferrari (Tincho)

___
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#891202: Bug#891202: prometheus-alertmanager: False owner/group for /var/lib/prometheus

[Martín Ferrari]

Ah, sorry, now I see that you are reporting against the version in
stable. There is not much I can do to fix that, the version in testing
does not have this issue.

What I can do (and I had forgotten to do before), is to backport that
version to stretch.

On 23/02/18 14:48, Martín Ferrari wrote:
> Hi,
> 
> On 23/02/18 12:17, tuxcoder wrote:
> 
>> The service trys to `mkdir /var/lib/prometheus/alertmanager` on startup,
>> but the dir `/var/lib/prometheus` is owned by root.
>>
>> If the package `prometheus` is installed first this is not the case.
> Uhm, I think you are mistaken, or I missed something.
> 
> The directory is created when unpacking the deb file:
> 
> $ dpkg -L prometheus-alertmanager | grep /var/lib/
> /var/lib/prometheus
> /var/lib/prometheus/alertmanager
> 
> Then the post-installation script does this:
> 
> chown -R prometheus:prometheus /var/lib/prometheus/alertmanager || true
> chown -R prometheus:prometheus /var/log/prometheus || true
> 
> And the initsciprt does this (as root):
> 
> mkdir -p `dirname $PIDFILE` || true
> chown -R $USER: `dirname $LOGFILE`
> chown -R $USER: `dirname $PIDFILE`
> 
> So, I don't know where you saw that mkdir, nor where it could be a problem.
> 


-- 
Martín Ferrari (Tincho)

___
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] Call for review - containerd and dependencies

[Martín Ferrari]

On 23/02/18 11:10, Michael Stapelberg wrote:

> Which file specifically is affected? The Files-Excluded directive in
> debian/copyright is a good way to exclude files.

Not anymore.. If you are not using import-orig and the like, that is
effectively ignored.

-- 
Martín Ferrari (Tincho)

___
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] GitLab CI: git-buildpackage and ratt

[Martín Ferrari]

On 20/02/18 12:20, Michael Stapelberg wrote:

> I’m only aware of one package (jacobsa/crypto) which has a
> Debian-specific patch that requires the use of an architecture-specific
> build tag. My proposed solution for this is to either specify the
> architectures (as opposed to custom pointer size build tags) in the
> files (they change rarely enough), or at least add the amd64 architecture.
> 
> Are you aware of other packages which use the same technique? If so, it
> might be good to write up a little bit of documentation, and perhaps
> even make this a feature of dh-golang.

the ones I have in mind would work for amd64 without the tags. Others
could be patched. The one that is not going to be easy without a lot of
medding is x/sys.

> This particular example is moot since dh-golang 1.31’s
> install-testdata-by-default change :).

Cool

> I understand your concern. I suggest we try my suggested approach and
> re-evaluate at some point down the road (a quarter? a year?) whether
> keeping it up is feasible and worthwhile. We can always course-correct,
> there’s no lock-in here.

Sounds good to me.

-- 
Martín Ferrari (Tincho)

___
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] GitLab CI: git-buildpackage and ratt

[Martín Ferrari]

Hi,

On 19/02/18 17:13, Michael Stapelberg wrote:

> I see the role of the CI setup as complementary: I expect that people
> will still build packages locally as they work on the packages. That
> path will continue to cover the debian/* part of the package. The
> remainder (fit into the archive) will be covered by the CI. In the worst
> case, the issue will be caught on the buildds (provided one uses
> source-only uploads).

OK, good point.

> Regarding the amount of work required to make packages buildable
> directly with the Go tool, have a look at the examples I listed at the
> bottom of the document. I don’t expect to spend more than 15 minutes per
> package, and I can volunteer to do the initial fixes. We need to be on
> the same page regarding the longer-term strategy, though, otherwise
> packages will degrade quickly.
> 
> Does that address your concern?

More or less, there are things that would be very clumsy to do without a
Makefile. For example, arch-specific build tags, if you don't evaluate
the complete makefile you won't get those. Granted, if you are only
using amd64 this would be a non-issue most of the time, although you
have things like this that will still require evaluating properly
debian/rules:

export DH_GOLANG_INSTALL_EXTRA := godoc/static \
$(wildcard */*/testdata) $(wildcard */*/*/testdata)

Dunno, seems it could work as you propose it, but at the same time I am
a bit worried that we will need to be careful not to break the system,
and that it will not be obvious when building locally.

-- 
Martín Ferrari (Tincho)

___
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] GitLab CI: git-buildpackage and ratt

[Martín Ferrari]

Michael,

On 19/02/18 09:25, Michael Stapelberg wrote:
> I have spent the last two weeks on a different approach to our CI setup,
> published the current version of the tools just now and added a document
> to our website (not linked from the main page yet until I have some
> feedback).
This is a great initiative, thanks!

Now, my main objection is to using the go tool directly and skipping the
debian build system. I understand this is faster, but it also means that
we could be missing problems in the debian files themselves, and that
some packages will either fail or require a lot of work to avoid having
any customisation in debian/rules.


-- 
Martín Ferrari (Tincho)

___
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#890501: Bug#890501: prometheus startup fails due to racey PID file implementation in prometheus

[Martín Ferrari]

Hi Tim,

On 15/02/18 12:09, Tim Small wrote:

> Due to https://github.com/prometheus/prometheus/issues/2689 Prometheus
> may fail to start (most commonly after a reboot), since the lock file
> checking implementation it uses is naive (just "is there a pid running
> with the same pid number that I wrote to the pid file").
> 
> The recommended (by upstream) workaround is to disable the lock file
> checking by using the --storage.tsdb.no-lockfile commandline argument
> when starting prometheus from the systemd unit file etc.

Thanks for your bug report. I had no idea there was now a tsdb lockfile,
and I agree that it makes sense to disable it, since we have that
functionality implemented in the init/service files.


-- 
Martín Ferrari (Tincho)

___
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] Circular dependency in a test file

[Martín Ferrari]

Hi Arnaud,

On 13/02/18 12:37, Arnaud wrote:

> The fact that it breaks dh-make-dolang is not the blocker here, as I can
> workaround and create the packaging files manually. However, what should
> I do with this `marshal_test.go` file ? Should I exclude it from the
> package ? Or should I patch it ?

You could either add an exclusion during build/test, or you can patch it
so it is ignored with '// +build ignore'. If you go with the exclusion,
you should probably add the dependency in the package dependencies (not
in the build-deps), but unless it is a very important test, maybe it is
better to just disable it.

> And more generally: I've noticed that a lot of go packages have test
> files named `*_test.go` Is it good policy to remove them from the
> package when they get in the way like this ? Or are they needed in some
> way that I don't expect ?

We usually keep them in the package, so tests can be run from the
installed package, including in ci.debian.net.

-- 
Martín Ferrari (Tincho)

___
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] Accepted chasquid 0.04-1 (source) into unstable

[Martín Ferrari]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 12 Feb 2018 11:10:36 +
Source: chasquid
Binary: chasquid
Architecture: source
Version: 0.04-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 
<pkg-go-maintainers@lists.alioth.debian.org>
Changed-By: Martín Ferrari <tin...@debian.org>
Description:
 chasquid   - simple SMTP (email) server written in go
Changes:
 chasquid (0.04-1) unstable; urgency=medium
 .
   [ Alberto Bertogli ]
   * New upstream release.
   * Ignore dovecot-auth-cli (internal binary not useful for production).
   * Add new dependencies for the packages that were split off.
   * Standards-Version: 4.1.3 (no adjustments needed).
   * Update compat and debhelper (to 11)
   * gbp.conf: No longer generate pristine-tar
   * debian/rules: Use pkg-info.mk
   * debian/control: Use "optional" priority
   * debian/postint: Do not use recursive chown
   * debian/patches: Add description to 0001-Use_chasquid_user.patch
   * debian/rules: Use dh_installsystemd
   * debian/rules: UPGRADING.md as upstream changelog
   * Add a debian/watch file
Checksums-Sha1:
 ec741d70ec5d50efa6acc1716cc982c319858d3f 2300 chasquid_0.04-1.dsc
 ccf6347076448e8ffbec8891b7f110ec7e35795c 104689 chasquid_0.04.orig.tar.gz
 d6b0acea3a89a19ee76fec52a17d07208497be02 5780 chasquid_0.04-1.debian.tar.xz
 526ccbe14464b6cc3d4d2aa73f18d34fbe720114 6250 chasquid_0.04-1_amd64.buildinfo
Checksums-Sha256:
 7386f1227e08f137349bbf39a64f4304ed1c5a6fd978d5bc98dfd8049321cc0e 2300 
chasquid_0.04-1.dsc
 17574df4eb00f28ed8218b4757a2d06de843559682a17fc49008bdcb275d591e 104689 
chasquid_0.04.orig.tar.gz
 0d08115176258906cf4243200d5713574f451aa44b9b1fcccd6d7e4b6472eeb8 5780 
chasquid_0.04-1.debian.tar.xz
 2e7143a04b6ef7c2eaa9397fb54d32cee3b1ab125610052ed1e6d66b3c6a7cd6 6250 
chasquid_0.04-1_amd64.buildinfo
Files:
 65485b26950d76810b29b75d4e62f98c 2300 mail optional chasquid_0.04-1.dsc
 fead108372688de7436bee5e412d47e0 104689 mail optional chasquid_0.04.orig.tar.gz
 4f642f8bdfc9d58bfb0c38182cbff5bb 5780 mail optional 
chasquid_0.04-1.debian.tar.xz
 f86e86cf0d37396854cf8e9ffb8b0888 6250 mail optional 
chasquid_0.04-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEETe94h3mvRsa9AoOeXdjgv5Gj09oFAlqBdm4ACgkQXdjgv5Gj
09rJNA//e04X7283AI14a5hjFW/xDF3UiJMPXeMTLOcM5dNPen+YfBrzSL2oepFY
hnlJ386rJwntWVnZHwbZfo5G8ae5+5OwtP2NiYD9OnMFdjuDa5z0sVrO6VUgsr8P
GD5UGQt2128iAtG3UZES9WQEZT3y/9hQf8xZkqStH9dk5pn0QR1UpWAPOSD0FRai
72YbmSCNbCa/7/1TVgyXPw16RPY4LEa8ruMDLjEV8lhmVzyBVjtDwmLdghTJd2JJ
TSd8SJzcrsRqfwbpxLI0dXML1cuALkFqy9NJ0p/WWkWN1Dtp8fbUTDdh2D9UK78c
VDuzJLUiRTAgnTOgJDctQp0D0avPGFtMJv+EYa41pdCLIReFmRTLzA99drStWnDr
CUZuWCVfmsUPcjDV2LM2mVB6QqCtfLWLS0kR2YaTZ+/nJ5TZp07ttlVGstvEqR64
lLma5E3it3NrFxDmv3UGV76SlIILp8/oy1gJzp1W6iKK8DzPPc4NEmA5I6EHjZ1s
ggiBbe6PSp01aFzMyl43x+t/B/SxqOuenS7hyGoxPy53DzL+N3QrDHFeWgDR7PoB
8jXTCOitKi8gvT+DC/zrgInccYt7s87MjKSwiMAtHdFuLNWzXK8WSpZrYt633+4o
xuJizih/Ezw/ahT56we1f5Yg2St6Z3QPTJDKKN768Ap3q5cCdrM=
=oqW6
-END PGP SIGNATURE-


___
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-mtpfs_0.0~git20150917.0.bc7c0f7-2_source.changes ACCEPTED into unstable

[Martín Ferrari]

On 09/02/18 10:24, Julian Gilbey wrote:

> I'm happy to make that change.  But because I hadn't been thinking in
> terms of team maintainance until now, I would have been entirely
> unaware that this change had been made until I tried to push some

Please bear in mind that if there is a package in the pkg-go git tree,
the assumption is that it must follow the team policy and that it is
team maintained. You can not assume nobody else has touched it,
otherwise, there is not much point in having it under the pkg-go umbrella.


-- 
Martín Ferrari (Tincho)

___
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] moving to salsa.debian.org

[Martín Ferrari]

Sorry for my late reply, life was pretty busy the last few days..

On 27/01/18 16:29, Alexandre Viau wrote:
> I don't think the advantages are worth renaming. It could create confusion.
> 
> I don't mind doing it, but please also consider that I would have to
> rename the team in the 150 packages that I already migrated.
While I won't suggest a change for the sake of it, I think the fact that
some packages were migrated before we had this discussion should not be
a determining factor. This is why I complained when you started doing it.

Now, on to the name itself, I think it'd be wise to try to have a
similar scheme to other teams. Dunno if there is any consensus yet, but
for example the perl team has gone for perl-team.

-- 
Martín Ferrari (Tincho)

___
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-gopkg-lxc-go-lxc.v2

[Martín Ferrari]

On 03/02/18 16:23, Clément Hermann wrote:

> The last missing dependency for LXD should be ready to upload,
> hopefully. If a DD could have a look at it and upload it that would be
> awesome.
> 
> Martín, maybe preferably you since you already had a first look at it ?

The package looks good. I only made a couple of minor corrections, and
uploaded it :)

-- 
Martín Ferrari (Tincho)

___
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] Accepted golang-github-dgrijalva-jwt-go 3.0.0.1+REALLY.2.6.0-3 (source) into unstable

[Martín Ferrari]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 08 Feb 2018 15:35:58 +
Source: golang-github-dgrijalva-jwt-go
Binary: golang-github-dgrijalva-jwt-go-dev
Architecture: source
Version: 3.0.0.1+REALLY.2.6.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 
<pkg-go-maintainers@lists.alioth.debian.org>
Changed-By: Martín Ferrari <tin...@debian.org>
Description:
 golang-github-dgrijalva-jwt-go-dev - Golang implementation of JSON Web Tokens 
(JWT)
Closes: 889875
Changes:
 golang-github-dgrijalva-jwt-go (3.0.0.1+REALLY.2.6.0-3) unstable; 
urgency=medium
 .
   * Team upload.
   * Automated cme updates.
   * Fix golang dependencies. Closes: #889875.
Checksums-Sha1:
 71351348c62078c3c13e33eb25cf3d5589297c5a 2384 
golang-github-dgrijalva-jwt-go_3.0.0.1+REALLY.2.6.0-3.dsc
 f802a448c0dce7ed24a15b406f2c2f6d92de1933 2580 
golang-github-dgrijalva-jwt-go_3.0.0.1+REALLY.2.6.0-3.debian.tar.xz
 679866ca8550ae652e7b0a52f01f18eeae94cba7 5786 
golang-github-dgrijalva-jwt-go_3.0.0.1+REALLY.2.6.0-3_amd64.buildinfo
Checksums-Sha256:
 a74b7d5d7ba507ada193ee54de3fb31a1e33c96958209b4ce0a203f17860ad05 2384 
golang-github-dgrijalva-jwt-go_3.0.0.1+REALLY.2.6.0-3.dsc
 403d7042227caf4797f9a15ceb9390862043c7e1ba143e95091a70d420297dc0 2580 
golang-github-dgrijalva-jwt-go_3.0.0.1+REALLY.2.6.0-3.debian.tar.xz
 c59e8f06bf08110c95c467877c288d467d4ee70f4b016396be5e4a780787673e 5786 
golang-github-dgrijalva-jwt-go_3.0.0.1+REALLY.2.6.0-3_amd64.buildinfo
Files:
 0c84ed5c682bb0cadae26aa0fc223d2f 2384 devel optional 
golang-github-dgrijalva-jwt-go_3.0.0.1+REALLY.2.6.0-3.dsc
 69280d12558b05e30cb3cf7341fcc1ae 2580 devel optional 
golang-github-dgrijalva-jwt-go_3.0.0.1+REALLY.2.6.0-3.debian.tar.xz
 5d0728da3196c6e26d278f5a0db3fb60 5786 devel optional 
golang-github-dgrijalva-jwt-go_3.0.0.1+REALLY.2.6.0-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEETe94h3mvRsa9AoOeXdjgv5Gj09oFAlp8bocACgkQXdjgv5Gj
09oxqw//VNllXNMvXLBj2DmALODDIgZcXCN7iNtBJxLlSKDOPVE1Y5lyYiSv6tRP
tPSa3S6dZ2Y+t88x3uEy1b36aNpZO+BE+3Dx0lsdl9ZnhQvATquSORYukLM+7Pst
XlJBKB47XeL8tjnh7y3GP4QYnFxt+qBa32MAMUB2Y98qrTF9ouPc1H0nvCv8rk37
tE2WKlD/+vecFOVoI1NRpfkIkkBhWC7hE5KyxuRWcpi2hWLGjI8KkdDX9+ibIxS5
VZNjISn/gOXGX8jH9CH5+KY6zgr58UI+b3Tkcf+Y03hxUIOCJj8nzPFOMZA+RAY7
ulpIFg4iOEsgt4NQE7pXbpVwciYMRLF2iQ11pSvyJfm1pRD3cYYdj7eyziCI9Iwu
DOTjplBpjoDy2ttnnAJscKOHWNO1E5lmORSSowttF3feV1G8v5wEUV7lQs29q+l5
ppo2O/31b/0CaReykdbvgkEf/XZg2T8q5Z12a1RLWDSrgZ03o9wQ6c6VUlbEHJ0K
HQtcCtu74dHd46qayuDsjQ0kXMrxbg7b+IV3bnfVzOTwL3mnJLBM0Ipo63xDETAQ
uElkeD9V1z3hkKrGC3hqyiuiTZAt6+7OZl6/vo3gubejEmzDOa3iobnC+Kbq2J/h
I1SrPt7x0LP+EDx+LbFrrOlMb+NlC437dQir4Hu4N4FUg6DltEc=
=tWRL
-END PGP SIGNATURE-


___
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] Minutes for the DebConf17 BoF

[Martín Ferrari]

On 24/01/18 21:45, Michael Stapelberg wrote:
> I filed a wishlist bug for the remote configuration:
> https://bugs.debian.org/888313

Thanks!

> To import it, AIUI, I should tag the latest upstream branch commit
> (7cafcd837844e784b526369c9bce262804aebc60) with tag
> upstream/0.0_git20160503.7cafcd8, then merge the upstream branch into
> the master branch with the merge strategy “theirs”.

What I do, is to first merge upstream at the point of the current
version (with --allow-unrelated-histories), which "should" be identical
to the current upstream, and after that merges are automatic.

> However, I can’t find a git-buildpackage command to take care of this.
> How do you do it? Manually?

Yup :)

-- 
Martín Ferrari (Tincho)

___
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] Minutes for the DebConf17 BoF

[Martín Ferrari]

On 23/01/18 21:48, Michael Stapelberg wrote:
> Status update: I now have tooling to perform the “delete existing

Yay!

> Also, I’m wondering how we can accomplish automated git remote
> configuration, i.e. how do people obtain an upstream branch which tracks
> the correct upstream remote branch? AFAICT, git-buildpackage has no
> solution for this (yet?). Does anyone know by chance?

For us, 99% of the time, the homepage field in d/control is what we
need. But it would be nicer to have something proper.

-- 
Martín Ferrari (Tincho)

___
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] [RFC] honoring DH_GOLANG_EXCLUDES for sources ?

[Martín Ferrari]

On 22/01/18 16:57, Michael Stapelberg wrote:

> We should exclude examples from being installed as binaries (which the
> example below does), but it’s not clear to me why we would exclude them
> from being included in the sources.

My rationale for that is that we ought to include them as examples (i.e.
in /usr/share/doc), and that many times, they do not build out of the
box, usually because of extra dependencies.

> The advantage to having them installed is that they could be compiled
> when testing packages for an updated package version, and thereby
> pinpointing an issue more quickly. E.g., assume I’m updating golang-foo
> 2.2 to 2.3, which is used by golang-bar, which in turn is used by
> cooltool. If golang-bar comes with an example program, I might catch the
> issue which golang-foo 2.3 introduces as a failure in the golang-bar
> compilation, not only in the cooltool compilation.

If they work, leaving them in the source and not excluding from
compilation/tests can be a good idea. And autopkgtest will pick them up
too. But I fear this will be a minority of cases.

> > I thought I did. But indeed, I misread the man page [1], which plainly
> > states that this is about excluding _targets_.

> By “this”, you refer to DH_GOLANG_EXCLUDES, I assume.

The main issue that we discussed with Clément is that DH_GOLANG_EXCLUDES
excludes packages from compilation, but not from installation. And I
feel that is not the best outcome.


-- 
Martín Ferrari (Tincho)

___
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] moving to salsa.debian.org

[Martín Ferrari]

On 19/01/18 15:25, Alexandre Viau wrote:

>> Salsa is not ready yet, people (including me) are working on fixing the
>> warts, but there are still many things to do.
> 
> The rationale is that Alioth will be deprecated.

Yes, but even formorer acknowledges this will take a few months.

> Everything I need/use is ready.
> 
> I don't mind waiting, do you have another date to suggest? Or will you
> let us know when your needs are fulfilled?

Will do, sure.

I think it would be best if we discuss as a team the migration. Get all
the tools we use now changed or replaced, and set a time table.

My list of things I would like to fix before migrating:

* Team website
* Repo setup tool: /home/groups/pkg-go/meta/setup-repository
* KGB
* Automatic tagging of pending fixes
* PET, hopefully, but that might not be feasible in time.

One thing that I think has not been discussed is the repo layout: now it
seems we are using a flat layout, whereas before we had a packages tree,
separate from other things like meta, website, and even a users/
subtree. What are we going to do with those?


-- 
Martín Ferrari (Tincho)

___
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#884542: Bug#884542: prometheus-mysqld-exporter FTBFS: FAIL: TestScrapeInnodbMetrics

[Martín Ferrari]

Status update: still waiting for upstream's fix.

On 18/12/17 04:55, Martín Ferrari wrote:
> Adrian,
> 
> Thanks for the report. I presume this error is due to the change in the
> Prometheus' common library. I am already preparing a new upstream
> release, but that is waiting on an upstream bug:
> https://github.com/prometheus/mysqld_exporter/issues/251
> 
> 
> On 16/12/17 12:03, Adrian Bunk wrote:
>> Source: prometheus-mysqld-exporter
>> Version: 0.9.0+ds-3
>> Severity: serious
>> Tags: buster sid
>>
>> Some recent change in unstable makes prometheus-mysqld-exporter FTBFS:
>>
>> https://tests.reproducible-builds.org/debian/history/prometheus-mysqld-exporter.html
>> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/prometheus-mysqld-exporter.html
>>
>> ...
>> === RUN   TestScrapeInnodbMetrics
>> --- FAIL: TestScrapeInnodbMetrics (0.00s)
>>  info_schema_innodb_metrics_test.go:17: no such flag -log.level
> 
> 
> 


-- 
Martín Ferrari (Tincho)

___
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: golang-github-hashicorp-raft_1.0.0+git20171204.0919aa6-1_source.changes ACCEPTED into unstable

[Martín Ferrari]

On 04/01/18 19:31, Alexandre Viau wrote:

> KGB will be very easy to rewrite for the gitlab API.

I have started working on that.

> I am sure we can also adapt PET. In the meantime, maybe just use the QA
> page?
>  -
> https://qa.debian.org/developer.php?login=pkg-go-maintainers@lists.alioth.debian.org

PET will take a lot of effort to migrate, if that ever happens.

> If you don't want to maintain the anonscm links, Alexander Wirt is
> working on a solution and you will still be able to use anonscm links:
>  - https://salsa.debian.org/salsa/AliothRewriter

But now we are introducing inconsistencies in the group packages, while
there was no need to change the links if we have waited.

> However I think maintaining this map and a link will be even more
> complicated.

But that means re-uploading every one of our 891 packages.

>> Honestly, it feels very demotivating that you did this change :(
> 
> You don't have to switch your packages now if you don't want to spend
> the time. I am sure Alioth will remain usable for a while. You can do it
> as you upload them, there is no rush.
> 
> You can also automate it.
> 
> For my packages, I automated the repository creation on salsa and the
> removal from Alioth.

Well, this is part of the problem. These are not "your packages" or "my
packages". We have a team where we decided that mainteinance is
collaborative and that nobody owns the packages.

What you are saying here goes against all that, and reverses efforts put
into making pkg-go collaborative and welcoming.

To make this more evident, I noticed this happened because I wanted to
work on a package that you moved. That package is a dependency of
prometheus, so I *need* to keep it healthy in order to ship prometheus
in Debian. If you look at the changelog of raft, you will see that the
last two uploads were done by me.

-- 
Martín Ferrari (Tincho)

___
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#884406: Bug#884406: golang-google-cloud FTBFS and Debci failure: *MockCloudSpanner does not implement spanner.SpannerServer

[Martín Ferrari]

It seems that updating to v0.16.0 fixes this issue but that pulls new
dependencies, so I am just going to backport the fix for this.

On 04/01/18 11:49, Martín Ferrari wrote:
> On 14/12/17 22:48, Adrian Bunk wrote:
> 
>> # cloud.google.com/go/spanner/internal/testutil
>> src/cloud.google.com/go/spanner/internal/testutil/mockserver.go:238:30: 
>> cannot use m (type *MockCloudSpanner) as type spanner.SpannerServer in 
>> argument to spanner.RegisterSpannerServer:
>>  *MockCloudSpanner does not implement spanner.SpannerServer (missing 
>> ListSessions method)
>> ...
> 
> It seems the latest upload to golang-google-genproto broke the API. Will
> have to investigate...
> 
> 


-- 
Martín Ferrari (Tincho)

___
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#884406: Bug#884406: golang-google-cloud FTBFS and Debci failure: *MockCloudSpanner does not implement spanner.SpannerServer

[Martín Ferrari]

On 14/12/17 22:48, Adrian Bunk wrote:

> # cloud.google.com/go/spanner/internal/testutil
> src/cloud.google.com/go/spanner/internal/testutil/mockserver.go:238:30: 
> cannot use m (type *MockCloudSpanner) as type spanner.SpannerServer in 
> argument to spanner.RegisterSpannerServer:
>   *MockCloudSpanner does not implement spanner.SpannerServer (missing 
> ListSessions method)
> ...

It seems the latest upload to golang-google-genproto broke the API. Will
have to investigate...


-- 
Martín Ferrari (Tincho)

___
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: golang-github-hashicorp-raft_1.0.0+git20171204.0919aa6-1_source.changes ACCEPTED into unstable

[Martín Ferrari]

On 31/12/17 15:10, Alexandre Viau wrote:

>>  and it already breaks all tooling.
> 
> What tooling? We should fix it. I can help.

KGB, PET, automatic marking of pending bugs, anonscm links.


Plus, all already cloned repos need to be adjusted manually, and you
uploaded with the new salsa URLs in the Vcs links, but now it seems we
get to maintain the anonscm links.

Honestly, it feels very demotivating that you did this change :(


-- 
Martín Ferrari (Tincho)

___
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: golang-github-hashicorp-raft_1.0.0+git20171204.0919aa6-1_source.changes ACCEPTED into unstable

[Martín Ferrari]

Hi Alexandre,

On 30/12/17 19:10, Alexandre Viau wrote:

> Everything that I have moved to salsa was removed from Alioth to avoid
> confusion.

UHm. That's better than having two copies, but I am not sure it is a
good idea. Salsa is still in beta, and I fear there might be downtime or
lost data, and it already breaks all tooling.

-- 
Martín Ferrari (Tincho)

___
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#885726: Bug#885726: golang-github-hashicorp-go-sockaddr: Source includes "cmd/sockaddr/vendor/vendor.json" listed in Files-Excluded header

[Martín Ferrari]

On 30/12/17 13:06, Chris Lamb wrote:

>> Also, how can it be a DFSG violation?

> It was just an entirely-generic list of possible problems, don't
> worry.

Ah, OK.

>> I really don't see much the point of removing it, or making a very 
>> complicated
>> files-excluded field.
> 
> Mmm. I have a rough plan to make this an autoreject Lintian tag, so that
> would be problematic here. :)
> 
> Would something like (untested) "cmd/sockaddr/vendor/*/*" not work, ooi?

I guess.. Also, we should probably remove that field from most packages,
since we have decided to use upstream git history, and repack on git, so
there is no real usage for it --except documentation.


-- 
Martín Ferrari (Tincho)

___
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] Fwd: golang-github-hashicorp-raft_1.0.0+git20171204.0919aa6-1_source.changes ACCEPTED into unstable

[Martín Ferrari]

Hi Alexandre,

I see you have been pretty busy uploading stuff :-) But can you please
push to git all these changes? We risk getting out of sync.


 Forwarded Message 
Subject: [pkg-go]
golang-github-hashicorp-raft_1.0.0+git20171204.0919aa6-1_source.changes
ACCEPTED into unstable
Date: Sat, 30 Dec 2017 08:51:07 +
From: Debian FTP Masters 
To: Alexandre Viau , Debian Go Packaging Team




Accepted:

Format: 1.8
Date: Sat, 30 Dec 2017 03:34:20 -0500
Source: golang-github-hashicorp-raft
Binary: golang-github-hashicorp-raft-dev
Architecture: source
Version: 1.0.0+git20171204.0919aa6-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team

Changed-By: Alexandre Viau 
Description:
 golang-github-hashicorp-raft-dev - implementation of the Raft consensus
protocol
Changes:
 golang-github-hashicorp-raft (1.0.0+git20171204.0919aa6-1) unstable;
urgency=medium
 .
   * Move to salsa.debian.org.
   * Priority extra -> optional.
   * Change my email to @debian.org.
   * New upstream snapshot.
Checksums-Sha1:
 60762bc4e4541b4b07f80ec36f7ee61db418b824 2494
golang-github-hashicorp-raft_1.0.0+git20171204.0919aa6-1.dsc
 f439306e749d398aa8ffa090557f77568c5dae89 86544
golang-github-hashicorp-raft_1.0.0+git20171204.0919aa6.orig.tar.xz
 8e3db27d6317991b0da2be5b0e5d3cb12b5530ce 7364
golang-github-hashicorp-raft_1.0.0+git20171204.0919aa6-1.debian.tar.xz
 26216ccc61baea221083eb24db928700df67ba91 7568
golang-github-hashicorp-raft_1.0.0+git20171204.0919aa6-1_source.buildinfo
Checksums-Sha256:
 768177ff432a8bc326f2e9948179a62fff8e98b13a71924fa86527bfd171fd80 2494
golang-github-hashicorp-raft_1.0.0+git20171204.0919aa6-1.dsc
 6330eafcc6b9102e5ca06954be3ba0aadc308bf6bf81b8dd8ca34ad21aa8fa37 86544
golang-github-hashicorp-raft_1.0.0+git20171204.0919aa6.orig.tar.xz
 cc62b80bc37781c19d6a8d624f81243cb2bc3e2ba071566261ead2fbc6ef0c8f 7364
golang-github-hashicorp-raft_1.0.0+git20171204.0919aa6-1.debian.tar.xz
 4dbd3995e732d8f645a6ee537532a1475c771e7c787af2c517ac10c9d42d443c 7568
golang-github-hashicorp-raft_1.0.0+git20171204.0919aa6-1_source.buildinfo
Files:
 ef8250130360b72c7ba7df37eaa25ef2 2494 devel optional
golang-github-hashicorp-raft_1.0.0+git20171204.0919aa6-1.dsc
 3646e149582d1e14a66111ec5b55128a 86544 devel optional
golang-github-hashicorp-raft_1.0.0+git20171204.0919aa6.orig.tar.xz
 f26c8abc62a6390d5bb280702af616ee 7364 devel optional
golang-github-hashicorp-raft_1.0.0+git20171204.0919aa6-1.debian.tar.xz
 4d4c8569805df3d25390e217ada1ceb1 7568 devel optional
golang-github-hashicorp-raft_1.0.0+git20171204.0919aa6-1_source.buildinfo



Thank you for your contribution to Debian.

___
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

[pkg-go] Bug#885726: Bug#885726: golang-github-hashicorp-go-sockaddr: Source includes "cmd/sockaddr/vendor/vendor.json" listed in Files-Excluded header

[Martín Ferrari]

On 29/12/17 16:28, Chris Lamb wrote:

> golang-github-hashicorp-go-sockaddr lists "cmd/sockaddr/vendor/*" in the 
> Files-Excluded field
> in debian/copyright but the source tree contains 
> cmd/sockaddr/vendor/vendor.json.
> 
> This might be a DFSG violation, the referenced files are probably not
> attributed in debian/copyright or the upstream tarball was simply not
> repacked as intended. Alternatively, the field is simply out of date.

The vendor.json is an autogenerated file that keeps versions (commit
hashes and dates) of every vendored dependency. I usually keep it around
for reference, as it is very useful when things break. I really don't
see much the point of removing it, or making a very complicated
files-excluded field. Also, how can it be a DFSG violation?


-- 
Martín Ferrari (Tincho)

___
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] Minutes for the DebConf17 BoF

[Martín Ferrari]

On 09/11/17 04:24, Michael Stapelberg wrote:

> At least for our transition period, we’ll have to use origtargz.

Yes, but only for -2 and up releases. For -1, origtargz would do the
same as gbp (AFAIK).

> I’m happy to pro-actively add compression algorithm/level options and
> evaluate at a later time whether that worked. I think just testing
> across different machines is a good start, but we should also pass the
> test of time — perhaps we can easily simulate that by testing on
> stable/oldstable.
Not sure if we need to devote a lot of time to this, after all, the
worst that can happen is a rejected upload because of checksum mismatches.

-- 
Martín Ferrari (Tincho)

___
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] Minutes for the DebConf17 BoF

[Martín Ferrari]

On 08/11/17 21:01, Martín Ferrari wrote:
> The best test would be to use gbp to create the tarballs under different
> conditions (machine, user name, path, manually touch()ing files locally)
> and see if they are really reproducible.

For one data point, I just tried this on two different machines (same
arch, though), on different paths, one a fresh clone, other my usual
work dir, and after some random touch() of files, I get always the same tar.

$ gbp buildpackage --git-force-create --git-no-pristine-tar
--git-compression=gzip --git-compression-level=9

$ sha256sum ../build-area/prometheus_1.8.1+ds.orig.tar.gz
726f7c392f99b48b63a85bc8f873fbdecbf6fabbb167a2dd7be312bdcf56d60c
../build-area/prometheus_1.8.1+ds.orig.tar.gz


Which, notably, does not match what's on the archive. It seems I had
different default values for the compression level on different
machines, so I had to pass the parameters explicitly.

If I use compression level 6, I get that exact SHA:

$ sha256sum ../build-area/prometheus_1.8.1+ds.orig.tar.gz
726f7c392f99b48b63a85bc8f873fbdecbf6fabbb167a2dd7be312bdcf56d60c
../build-area/prometheus_1.8.1+ds.orig.tar.gz

I think if we mandate some fixed parameters (by policy or inclusion in
debian/gbp.conf), this approach would be feasible.

-- 
Martín Ferrari (Tincho)

___
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] Minutes for the DebConf17 BoF

[Martín Ferrari]

On 08/11/17 17:55, Michael Stapelberg wrote:

> Quote from the commit message
> (https://anonscm.debian.org/git/pkg-go/website.git/commit/?id=866810cfeea8086dbdfc0176b148f7a063e3ac0b):
One comment on this:

+NOTE: Using `--git-upstream-tree=TAG` (the default) is not sufficient
to obtain
+a byte-for-byte equal orig .tar.gz file. In stapelberg’s tests, only 5% of
+pkg-go’s git repositories would match the orig .tar.gz in the archive.

I think this test is not useful, because probably that 95% of packages
matches those whose tars were not created by gbp, but by upstream or by
pristine-tar.

If you are using gbp, the tars are meant to be reproducible, but not
necesarily equal to pristine-tar. I think it uses last commit time to
set the mtime of each file, and that could surely be different in a
tarball created by upstream.

The best test would be to use gbp to create the tarballs under different
conditions (machine, user name, path, manually touch()ing files locally)
and see if they are really reproducible.

-- 
Martín Ferrari (Tincho)

___
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] Minutes for the DebConf17 BoF

[Martín Ferrari]

On 08/11/17 17:55, Michael Stapelberg wrote:
> I started a document describing the changes we agreed on, the
> rationale behind them, the old/new workflows and the migration
> strategy.

Thanks!! I am very glad we are moving forward with this!

> I hope I can make some progress on this in the next few days. Any help
> is welcome.

I will try to squeeze some contributions.

-- 
Martín Ferrari (Tincho)

___
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] Minutes for the DebConf17 BoF

[Martín Ferrari]

On 06/11/17 15:04, Martín Ferrari wrote:

> I have added something that I think it is widely accepted, but was not
> explicitly discussed, and that I would like to be set on policy: should
> we mandate merging of upstream code in debian branch?

Just to clarify: I don't think this new point should delay the rest of
the decisions. I think the other points had enough time by now to be
considered settled.


-- 
Martín Ferrari (Tincho)

___
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] Minutes for the DebConf17 BoF

[Martín Ferrari]

On 06/11/17 04:04, Michael Stapelberg wrote:
> Reminder: The deadline is approaching in a few hours. Please have a final 
> look.

Thanks!

I have added something that I think it is widely accepted, but was not
explicitly discussed, and that I would like to be set on policy: should
we mandate merging of upstream code in debian branch?

-- 
Martín Ferrari (Tincho)

___
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: golang-github-hashicorp-memberlist_0.1.0-2_amd64.changes is NEW

[Martín Ferrari]

Hi Andreas,

On 01/11/17 17:46, Andreas Beckmann wrote:

> * package golang-github-hashicorp-memberlist-dev in version 
> 0.0~git20160329.0.88ac4de-2 is no longer built from source

> --- Reason ---
> [auto-cruft] obsolete source package
> --

> And since the package built fine locally (also the arch-indep-only build)
> this removal was just unfortunate timing, so I just uploaded my no-change
> rebuild instead of trying to figure out where to report a bug.
> 
> golang-github-ugorji-go-codec-dev OTOH shares the fate, but FTBFS (#879483).
> 
> There is #825398 about premature removal of arch:all package while the new
> source is still queued for building. Which is one factor contributing to
> putting too many packages (temporarily) into obsolete-source state.

So what happened is that because of the source-only upload, it was
considered obsolete and removed? I had no idea about this problem, I
will stop doing source-only uploads then..


Thanks for the info, and the upload!


-- 
Martín Ferrari (Tincho)

___
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: golang-github-hashicorp-memberlist_0.1.0-2_amd64.changes is NEW

[Martín Ferrari]

Andreas?

On 29/10/17 16:03, Martín Ferrari wrote:
> According to the changelog in the NEW page, it seems this package was
> removed by mistake. Andreas, can you share some details? I did not see
> the RM mail, nor I can find the new upload in the git repo.
> 
> 
>  Forwarded Message 
> Subject: [pkg-go]
> golang-github-hashicorp-memberlist_0.1.0-2_amd64.changes is NEW
> Date: Sat, 28 Oct 2017 11:48:55 +
> From: Debian FTP Masters <ftpmas...@ftp-master.debian.org>
> To: Andreas Beckmann <a...@debian.org>, Debian Go Packaging Team
> <pkg-go-maintainers@lists.alioth.debian.org>
> 
> source:golang-github-hashicorp-memberlist is NEW.
> 
> Your package has been put into the NEW queue, which requires manual action
> from the ftpteam to process. The upload was otherwise valid (it had a good
> OpenPGP signature and file hashes are valid), so please be patient.
> 
> Packages are routinely processed through to the archive, and do feel
> free to browse the NEW queue[1].
> 
> If there is an issue with the upload, you will receive an email from a
> member of the ftpteam.
> 
> If you have any questions, you may reply to this email.
> 
> [1]: https://ftp-master.debian.org/new.html
>  or https://ftp-master.debian.org/backports-new.html for *-backports
> 
> ___
> 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
> 


-- 
Martín Ferrari (Tincho)

___
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] Minutes for the DebConf17 BoF

[Martín Ferrari]

On 21/10/17 17:10, Michael Stapelberg wrote:

> Please give it a look at
> https://oasis.sandstorm.io/shared/l4YsLYdwUgnhzzwmKS_TGwWyVQ9Ol8EKiMR8qhpHaS2
> and add any remaining discussion points you would like to bring up
> within the next 14 days, i.e. no later than 2017-11-04.

I added my comments, and updated my preferences (mainly, that since
albertito pointed me to gbp's ability to create reproducible tarballs, I
have stopped using pristine-tar).

What I feel is not too clear there is that many discussion points depend
on others; the most important one being to follow upstream git history
or not.

In any case, it is important that other people check it out and comment.
So far, I only see edits my Michael and me. Having a clear policy is
very important to make the team more productive and easy to work with!

-- 
Martín Ferrari (Tincho)

___
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#876697: Bug#876697: golang-github-golang-mock FTBFS on mips: test failure

[Martín Ferrari]

Adrian,

On 25/09/17 01:22, Adrian Bunk wrote:

> go build github.com/golang/mock/gomock_test: /usr/bin/mips-linux-gnu-gccgo-7: 
> waitid: bad address

It seems that this issue is affecting all packages that use waitid in
mips, and that the problem is either in the kernel or in gccgo (but I've
heard it is actually a kernel problem).

I think it does not make much sense to open more RC bugs against these
packages that cannot really be fixed until the root cause is addressed.

-- 
Martín Ferrari (Tincho)

___
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#832834: Bug#832834: golang-github-boltdb-bolt: FTBFS: Tests failures

[Martín Ferrari]

On 22/09/17 16:55, Santiago Vila wrote:

> Hmm. Why would a test suite have to test the disk speed at all?
> 
> A test suite in a program is supposed to test the program,
> not the underlying hardware.
> 
> IMHO; I don't think such kind of tests are really useful.
> I would just disable the test completely.

It is not testing the hardware, it is testing that the write completes,
and developers many times assume everybody has fast hardware, and then
you get these bugs. We could argue about disabling this test (which is
noted as hacky by upstream), but those are not the reasons.

-- 
Martín Ferrari (Tincho)

___
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#854687: Bug#854687: Bug#854687: Bug#854687: golang-github-prometheus-client-golang: FTBFS randomly (failing tests)

[Martín Ferrari]

On 14/07/17 12:59, Martín Ferrari wrote:
> On 14/07/17 11:21, Santiago Vila wrote:
> 
>> It could also be a race condition which happens more
>> likely on low memory systems. Feel free to recategorize.
> 
> Honestly, without a way to reproduce it, I am more inclined to close :)

Actually, upstream says it is a known issue, and that it is disabled
under -short for this reason. So I will just disable the test.


-- 
Martín Ferrari (Tincho)

___
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#872402: Bug#872402: golang-golang-x-tools-dev: Does not work on mips*

[Martín Ferrari]

On 24/08/17 19:11, Shengjing Zhu wrote:
> Control: severity -1 normal
> 
> On Thu, Aug 24, 2017 at 10:37 PM, Martín Ferrari <tin...@debian.org> wrote:
>> Yes, sorry, I was confused with x/tools, which has disabled tests. This
>> one does not get built in other arches, so the relevant tests are not
>> executed.. Maybe we should make it arch:any...?

> I think the CI like ci.d.n should run on more archs instead...

Yeah, that'd be ideal :)

> ok, so I read the issue on https://github.com/golang/go/issues/18031
> 
> I don't have mips env to verify comments by foka. But what foka said
> in that issue is,
> gccgo reports mipsel and mips both as `mipso32`. So we need pass
> another `-tags` to distinguish the two archs.
> Unless gccgo has corrent build tip, we can only manually add `-tags
> mips` or `-tags mipsel`.

I have just tested that, with eller for mips(64)el and minkus for mips.
And sadly, that is true:

eller (mipsel):
$ go env
GOARCH="mipso32"

eller (mips64el):
$ go env
GOARCH="mipsn64"

minkus (mips):
$ go env
GOARCH="mipso32"

The bug referenced above says this might be already fixed in gccgo, and
looking at the commit history, it does seem to be true:
https://go.googlesource.com/gofrontend/+/3f713ddb2a9a2a736f3a12d71c56cb7fd444afba%5E%21/

This harmonizes the arch names with gc, and as a side effect, fixes the
missing little-endian marker.

The problem is that gcc and friends make my head hurt, and I don't
really understand if this made it into the 7.2 release or not. Seeing
that eller has libgo 7.2, I assume it did not.. Does anybody understand
all this?

> BTW, let me down grade this bug's severity first since I think we have
> workaround for that :)

OK.

-- 
Martín Ferrari (Tincho)

___
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#873514: golang-google-cloud: FTBFS due to changes in dependency

[Martín Ferrari]

Source: golang-google-cloud
Version: 0.5.0-2
Severity: serious
Justification: fails to build from source

Since the latest update to golang-google-genproto-dev, this package FTBFS.

The fix for this is in release 0.7.0, but that requires also updating
golang-github-googleapis-gax-go-dev, and I am not sure about the effect on
other rdeps like kubernetes, docker, and cadvisor.

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 
'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_IE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

___
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] lintian: Please add autopkgtest-pkg-elpa as a valid value for Testsuite

[Martín Ferrari]

On 28/08/17 11:07, Chris Lamb wrote:

>> Can you add pkg-go to the list of valid testsuites?
> 
> This was fixed by Niels in:
> 
>   
> https://anonscm.debian.org/git/lintian/lintian.git/commit/?id=2a279596289a9e7b4f31fc5aba48f2c6c9a18ebc
> 
> I've added the sole remaining value ("autopkgtest-pkg-elpa") in:
> 
>   
> https://anonscm.debian.org/git/lintian/lintian.git/commit/?id=d5f0c0115ef46eb98d1b68f7113aa63d93f72211
> 
> … and renaming this bug to match :)

Cool, we just need to wait for the next release then. Thanks!


-- 
Martín Ferrari (Tincho)

___
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#873458: lintian: Please add autopkgtest-pkg-go as valid value for Testsuite

[Martín Ferrari]

Package: lintian
Version: 2.5.52
Severity: normal

Hi,

Currently, lintian complains about the pkg-go testsuite, but autodep8 has
support for it since 0.9.

source: unknown-testsuite autopkgtest-pkg-go

Can you add pkg-go to the list of valid testsuites?

Moreover, autodep8 already supports a few other automatic test suites, so those
should be added too:

dkms
elpa
go
nodejs
perl
python
r
ruby

Thanks.

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 
'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_IE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages lintian depends on:
ii  binutils  2.29-7
ii  bzip2 1.0.6-8.1
ii  diffstat  1.61-1+b1
ii  dpkg  1.18.24
ii  file  1:5.31-1
ii  gettext   0.19.8.1-4
ii  intltool-debian   0.35.0+20060710.4
ii  libapt-pkg-perl   0.1.33
ii  libarchive-zip-perl   1.59-1
ii  libclass-accessor-perl0.34-1
ii  libclone-perl 0.38-2+b2
ii  libdpkg-perl  1.18.24
ii  libemail-valid-perl   1.202-1
ii  libfile-basedir-perl  0.07-1
ii  libipc-run-perl   0.96-1
ii  liblist-moreutils-perl0.416-1+b3
ii  libparse-debianchangelog-perl 1.2.0-12
ii  libperl5.26 [libdigest-sha-perl]  5.26.0-5
ii  libtext-levenshtein-perl  0.13-1
ii  libtimedate-perl  2.3000-2
ii  liburi-perl   1.72-1
ii  libxml-simple-perl2.24-1
ii  libyaml-libyaml-perl  0.63-2+b2
ii  man-db2.7.6.1-2
ii  patchutils0.3.4-2
ii  perl  5.26.0-5
ii  t1utils   1.40-2
ii  xz-utils  5.2.2-1.3

Versions of packages lintian recommends:
ii  libperlio-gzip-perl  0.19-1+b4

Versions of packages lintian suggests:
pn  binutils-multiarch 
ii  dpkg-dev   1.18.24
ii  libhtml-parser-perl3.72-3+b2
ii  libtext-template-perl  1.46-1

-- no debconf information

___
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#872402: golang-golang-x-tools-dev: Does not work on mips*

[Martín Ferrari]

On 24/08/17 16:31, Shengjing Zhu wrote:

> Hi Martín,
> So what's the prolem of this x/sys? I didn't see this package has
> disabled tests.

Yes, sorry, I was confused with x/tools, which has disabled tests. This
one does not get built in other arches, so the relevant tests are not
executed.. Maybe we should make it arch:any...?

> Which package ftbfs because of x/sys?

Prometheus and friends were failing. I understood now what you are doing
here (it took me a while), and by passing tags I managed to get them
building again, but that's not a reasonable solution.. The packages
should build out of the box. Can't you add the correct build
restrictions for gccgo so we don't need the tags?

-- 
Martín Ferrari (Tincho)

___
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] Minutes for the DebConf17 BoF

[Martín Ferrari]

On 20/08/17 19:21, Michael Stapelberg wrote:

>> Gccgo has many quirks. One is that it does not use the vendor directory
>> (I need to check if this is true with the latest version), so you might
>> need to copy vendor into the builddirectory.
> 
> …hopefully only temporarily, though, right? Ideally, we wouldn’t have
> any vendored source in our packages.

Gah! Another thing I forgot to talk about! go packaging is hard.. :)

Yes, most of the time I kill all vendoring, but there have been some
exceptions: 1) small, useless libraries that I see no point in packaging
separately; and 2) self-contained parts of a library, that avoid
dragging 100s of dependencies.

The latter happened to me recently with prometheus: I had removed the
vendoring of the consul API, but when I tried to backport that, I
realised I'd need to backport consul, docker, and way too many dependencies.

Sadly, even if the client API is in a different package, the source
packages have long dependency chains. I am starting to think that for
some of these packages, having a separate source package with client
APIs would make sense.


>> BUILDFLAGS := -ldflags \
>>   " -X $(METAPKG)/version.Version=$(VERSION)\
>> -X $(METAPKG)/version.Revision=$(REV)\
>> -X $(METAPKG)/version.Branch=$(BRANCH)\
>> -X $(METAPKG)/version.BuildUser=$(USER)\
>> -X $(METAPKG)/version.BuildDate=$(BUILD_DATE)\
>> -X $(METAPKG)/version.GoVersion=$(GO_VERSION)"
> 
> What does METAPKG resolve to? We should consider centralizing these
> definitions somewhere.

Ah, this is prometheus-specific. All the meta info is stored in the
prometheus/common namespace, so I defined that earlier in the rules file.


-- 
Martín Ferrari (Tincho)

___
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] Minutes for the DebConf17 BoF

[Martín Ferrari]

On 20/08/17 17:35, Martín Ferrari wrote:
> So, my turn to describe workflows.

Some things I forgot in my previous email:

* I am not married to the idea of dch + debcommit, specially when I have
merge conflicts. I understand the merits of git commit + gbp dch.
* The export=WC option in gbp.conf is to make sure my uncommitted
changes are taken into account when building, which allows me to
experiment and test before committing.

Some notes not about workflow, but about packaging strategies:

1. debian/control

I wrap and sort all multi-entry fields, with a trailing comma at every
line (to minimise diffs). I always did this by hand (or with my
pkg-go-common-fixes script), but a friend just recommended the
wrap-and-sort script from devscripts, and I think we should all use that
with the same options.

Even if this does not match what I am currently doing (indent after
colon), I think it makes more sense:

$ wrap-and-sort -st

Add myself as Uploader for any package where I do some non-trivial
amount of work. Although I think this usage of Uploaders is being
challenged project-wise.

Add Testsuite: autopkgtest-pkg-go to every package.

2. debian/rules

Keep it as minimal as possible.

To add extra needed files (for tests and the such) use
DH_GOLANG_INSTALL_EXTRA, no manual copying and no DH_GOLANG_INSTALL_ALL.

To avoid compilation and testing of some packages use DH_GOLANG_EXCLUDES.

If I need to do something in the build directory, pass --builddirectory
to dh, so it is a known location (as opposed to getting the weird path
from debhelper)

Gccgo has many quirks. One is that it does not use the vendor directory
(I need to check if this is true with the latest version), so you might
need to copy vendor into the builddirectory.

For detecting gccgo, and doing special things:

GCCGO  := $(strip $(shell go version | grep gccgo))
ifneq ($(GCCGO),)
..
endif

Many programs include versions, build info, date, etc, through linker
variables. To make it consistent and reproducible I use this:

DEBVERS?= $(shell dpkg-parsechangelog -SVersion)
VERSION?= $(shell echo '$(DEBVERS)' | sed 's/^[[:digit:]]*://;
s/[-].*//')
DEBDATE?= $(shell dpkg-parsechangelog -SDate)
REV:= $(DEBVERS)
BRANCH := debian/sid
USER   := pkg-go-maintainers@lists.alioth.debian.org
HOSTNAME   := debian
BUILD_DATE := $(shell date --utc --date='$(DEBDATE)' +%Y%m%d-%H:%M:%S)
GO_VERSION := $(shell go version | sed 's/go version \(\S*\).*/\1/')
BUILDFLAGS := -ldflags \
  " -X $(METAPKG)/version.Version=$(VERSION)\
-X $(METAPKG)/version.Revision=$(REV)\
-X $(METAPKG)/version.Branch=$(BRANCH)\
-X $(METAPKG)/version.BuildUser=$(USER)\
-X $(METAPKG)/version.BuildDate=$(BUILD_DATE)\
-X $(METAPKG)/version.GoVersion=$(GO_VERSION)"


-- 
Martín Ferrari (Tincho)

___
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] Minutes for the DebConf17 BoF

[Martín Ferrari]

On 20/08/17 18:46, Michael Stapelberg wrote:

> Side note, not meant to persuade anyone one way or the other: I just
> realized why I never saw any appeal in that argument: I find git
> packaging (or git in general?) too brittle and confusing to keep what
> I consider are multiple projects in the same repository.

Uhm.. I don't really have that feeling. Could you elaborate more?

> When I need to find out something about upstream repositories, I
> usually use the GitHub web interface, or my local gopath. I never use
> the git packaging repos, regardless of whether they have history or
> not.

Heh, I hate the github web interface, can't compare to gitk, git log, etc :)

Also, I don't even have a go path. To this day I get confused every time
I try to build things by hand!


> git config --add remote.origin.push "+refs/heads/*:refs/heads/*"
> git config --add remote.origin.push "+refs/tags/*:refs/tags/*"

The problem with this is that you push all tags and branches, even if
they are coming from upstream (I know, not relevant for you). I try to
keep the alioth repo free from that.

> But note that gbp recently gained “gbp push”:
> https://git.sigxcpu.org/cgit/git-buildpackage//commit/?id=cbacdfb40ca35633da06e9e05497ac0fb56cc4f9
> It’s included in 0.9.0~exp2, but I haven’t tried it out yet.
> Hopefully, it makes both our extra setup steps unnecessary :).

Oh, cool, I should try it!

> Given that you _also_ maintain history in git, using gbp dch seems
> like significantly cutting down the number of commands. Is there any
> rationale behind your decision to not use gbp dch, or are you just
> used to this way? :)

Mostly historical reasons and muscle memory :)


-- 
Martín Ferrari (Tincho)

___
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] Minutes for the DebConf17 BoF

[Martín Ferrari]

On 20/08/17 18:36, Michael Stapelberg wrote:
> I use gbp with sbuild, and I do see different behavior with/without
> exporting. Take for example the freeradius repository, where the build
> fails without git-export-dir: https://paste.debian.net/982241/

I guess the difference is with not having an export option at all, which
I have never tried..

>>> 2. My ~/.gbp.conf reads https://paste.debian.net/hidden/a48afca2/
>>> <https://paste.debian.net/hidden/a48afca2/> (informational)
>>
>> Sadly, this has expired
>
> Sorry about that. Here’s one that shouldn’t expire:
> https://paste.debian.net/982242/

Thanks, I like those sbuild options, I am saving this!


-- 
Martín Ferrari (Tincho)

___
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] Minutes for the DebConf17 BoF

[Martín Ferrari]

So, my turn to describe workflows.

I use gbp, pristine-tar, cowbuilder (but planning to move to sbuild),
dch, debcommit as my main tools. I have not really used dh-make-golang much.

My global gbp configuration is as follows:

[DEFAULT]
pristine-tar = True
sign-tags = True

[buildpackage]
export = WC
postbuild = lintian $GBP_CHANGES_FILE && debsign $GBP_CHANGES_FILE
export-dir = ../build-area/
tarball-dir = ../tarballs/
ignore-new = True
pbuilder = True

[import-orig]
postimport = dch -v%(version)s New upstream release.


In general, I try to keep existing structures in git, but for packages I
prepare, I use DEP14 branches and tags:

 * HEAD is debian/sid, other dists are debian/.
 * upstream/ tag for unpacked upstream source.
 * debian/ tag for uploaded packages.
 * I keep an "upstream" branch for unpackaged upstream sources, which is
tagged and then merged into the main packaging branch.

Depending on upstream having releases or not, I either use gbp
import-orig --uscan, or follow git history with an "upstream" remote. In
both cases, the sources end in a git branch.

For repackaging, I either use "excluded-files" in debian/changelog for
released projects, or create a second upstream branch "repackaged",
"unvendored", or somesuch, where I make changes and merge from
"upstream" after every import.

For the go ecosystem, I am feeling it is much more useful and productive
to keep complete upstream history than using the releases, and for some
packages with releases I started using this. It pays off every time I
need to troubleshoot api changes, backport fixes, and the such..

When I am doing this, I add this gbp.conf snippet in the debian/ directory:

[buildpackage]
dist = DEP14
upstream-tag = upstream/%(version)s
pristine-tar = True
pristine-tar-commit = True

For simplifying pushes, I also add this config:

$ git config --add remote.debian.push 'refs/heads/debian/*'
$ git config --add remote.debian.push 'refs/heads/upstream'
$ git config --add remote.debian.push 'refs/heads/pristine-tar'
$ git config --add remote.debian.push 'refs/tags/debian/*'
$ git config --add remote.debian.push 'refs/tags/upstream/*'
$ git config --add remote.debian.fetch 'refs/tags/*:refs/tags/*'


My preference for debian/changelog is:
 * distribution=UNRELEASED until the package is ready to upload.
 * I use dch for every change, and debcommit to commit with that same
message.
 * dch -r when package is ready for upload (changes dist).
 * debcommit -r after uploading (creates signed tag).


My workflow with upstream history is as this:

1. Init

(on alioth)

$ /git/pkg-go/setup-repository foo
$ git --git-dir=/git/pkg-go/packages/... symbolic-ref HEAD
refs/heads/debian/sid

(locally)
$ git remote add upstream https://...
$ git remote add debian ssh://git.debian.org/git/pkg-go/packages/...
$ git fetch --all
$ git checkout -b upstream upstream/master # or upstream tag
$ git tag upstream/0.0+gitMMDD.NNN
# optional, if repackaging is needed.
$ git ckeckout -b repackaged
$ git rm -rf vendor/; git commit -m repackage
$ git tag upstream/0.0+gitMMDD.NNN-ds
$ git checkout -b debian/sid
# create debian/* stuff, with dh-make-golang, or (usually) copy from
another package :-). Add gbp.conf snippet, git config, etc

2. Update

$ git fetch --all
$ git checkout debian/sid
$ git tag upstream/0.0+gitMMDD.NNN NNN
$ git merge upstream/0.0+gitMMDD.NNN
$ dch -v 0.0+gitMMDD.NNN-1 'New upstream snapshot.'
$ git add debian/changelog; debcommit
$ gbp buildpackage  # This also creates the pristine tar from the tag.

3. Work on the package

# Fix stuff
$ dch 'debian/foo: fix bar'; debcommit -a

# When finished
$ dch -r
$ git add debian/changelog; debcommit
$ gbp buildpackage

$ dput 
$ debcommit -r
$ git push debian


For backports is all the same, except that instead of using debian/sid,
I fork a debian/stretch-backports and work from there.

___
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] Minutes for the DebConf17 BoF

[Martín Ferrari]

Hey,

On 16/08/17 04:54, Michael Hudson-Doyle wrote:

> I think I /slightly/ prefer the upstream branch to be upstream's git
> history not a series of imports of tarballs. But I'm not set on it, and
> gbp doesn't really get on with this approach if you're just packaging a
> random commit rather than a tag AFAICS.

Actually, it works wonderfully: you just need to tag the right commit
with -say- `upstream/0.0+git20170808.deadbee`, and then `dch -v
0.0+git20170808.deadbeef-1`. With the right options, it creates the orig
tarball and commits it to pristine tar during the first build.

> Makes sense. Which gccgo arches are really being used today though? MIPS
> I guess, but that really should get golang-go once we figure out how to
> do that.

Not sure about being used, but we compile for mips* and arm*.

> https://nm.debian.org/process/198 :)

yay!!

-- 
Martín Ferrari (Tincho)

___
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] Minutes for the DebConf17 BoF

[Martín Ferrari]

Hi Mickael,

I haven't yet got the time to write down properly my workflow, but I
will still reply to some points. :)

On 15/08/17 23:02, Michael Stapelberg wrote:

> 1. I store packaging in e.g. ~/d/pkg/gocryptfs and build using `gbp
> buildpackage --git-export-dir=~/d/out/gocryptfs`. By using
> --git-export-dir, my working copy always stays clean. By collecting the
> output files per package, I can easily debdiff between versions. This
> point is informational and shouldn’t have any bearing on a canonical
> workflow.

Why do you need this? I use gbp with cowbuilder, and so the working copy
is never touched. Looking at my gbp.conf, I see my default is to export
to '../build-area', but probably that does not change much.

> 2. My ~/.gbp.conf reads https://paste.debian.net/hidden/a48afca2/
> <https://paste.debian.net/hidden/a48afca2/> (informational)

Sadly, this has expired

> 4. To update debian/changelog, I run `gbp dch -R --commit`. Note that
> this goes against our current policy of editing debian/changelog with an
> UNRELEASED entry — when using gbp-dch, the changelog is entirely
> auto-generated from git (but you do have the option to amend it before
> committing). Hence, I’d suggest we update that policy and start using
> gbp-dch.

This is one of these things were we should decide on one way to do
things, as it is incompatible with the other usual way, which is to
change debian/changelog on every commit.

> not the upstream source. This breaks quilt and confuses me. I’d suggest
> we codify that the branch must contain the upstream sources plus debian/.

+1

> different checksum, and my upload will be rejected. I’d suggest we
> codify that pristine-tar is a requirement.

+1

> 7. We don’t currently have a guideline with regards to branch naming,
> especially when maintaining branches for multiple debian versions (e.g.
> stretch, buster, stretch-backports, …). I’d suggest we adopt the
> debian/ branch naming scheme, e.g. debian/buster is the default
> branch, backports can be found in debian/stretch-backports, etc.

I have adopted DEP-14, which is basically this, and makes it very
pleasant to work with different distributions, specially since I have
been doing a lot of backporting.

One caveat: the default branch should (according to DEP-14) not be
debian/buster, but debian/sid (or just master).

> 8. (Optional/best effort) I recently came to understand that dgit is
> thought of as a universal approach for new users/maintainers to easily
> contribute to packaging (you get the same style of git checkout of any
> package in the archive). We should verify the above constraints still
> leave us in a place where dgit works well — it will work for any
> package, but it will work better for packages which are `dgit push`ed. I
> don’t yet know what the requirements for that are.

Same here, I haven't checked it out yet

-- 
Martín Ferrari (Tincho)

___
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#872402: golang-golang-x-tools-dev: Does not work on mips*

[Martín Ferrari]

reassign 872402 golang-golang-x-sys
thanks

> Since 0.0~git20170629.0.1b3bb8de-1 a patch has made the source files shipped
> fail to build in mips* architectures. It does not FTBFS just because tests 
> have
> been disabled in a previous version, but it is making other packages FTBFS.
> 

I am being stupid and mixing x/tools with x/sys. Sorry about the noise.

-- 
Martín Ferrari (Tincho)

___
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#872402: golang-golang-x-tools-dev: Does not work on mips*

[Martín Ferrari]

Package: golang-golang-x-tools-dev
Version: 0.0~git20170629.0.1b3bb8de-1
Severity: grave

Since 0.0~git20170629.0.1b3bb8de-1 a patch has made the source files shipped
fail to build in mips* architectures. It does not FTBFS just because tests have
been disabled in a previous version, but it is making other packages FTBFS.

This bug tries to point to the correct culprit.

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 
'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_IE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

___
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#870843: Bug#870843: golang-github-armon-go-metrics-dev: unhandled symlink to directory conversion: /usr/share/gocode/src/github.com/sirupsen/logrus -> ../Sirupsen/logrus

[Martín Ferrari]

reassign 870843 golang-github-sirupsen-logrus-dev
thanks

This bug is filed under the wrong package.

___
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] Minutes for the DebConf17 BoF

[Martín Ferrari]

Pkg-go BoF meeting minutes
==

On Tuesday, we had the first in-person meeting of the team. We met for 2
hours to discuss our current issues and to plan for the future.

People present
--

Alexandre Viau (aviau)
Martín Ferrari (Tincho)
Paul Tagliamonte (paultag)
Sascha Steinbiss (satta)

Test files
--

We discussed the issues raised about shipping test sources and fixtures
in the -dev packages. It was pointed out that they are not really needed
for autopkgtest or for reverse-dependencies, but that it will involve a
lot of work to achieve, so we decided to keep them for now.

Using -dev packages for development
---

Due to the friction that can bring with upstreams, it was agreed to
continue discouraging to use -dev packages for everyday golang development.

Outdated packages and binNMUs
-

Paultag proposed automating the detection of packages which have been
compiled with old versions of libraries. He will implement a first
version that just sends emails to remind of needed binNMUs, with the
idea of some day automatically triggering wanna-build.

He also indicated that he wants this automation to detect and warn about
circular dependencies.

Git workflows
-

It was discussed about the problem of having so many different
workflows, as it makes it difficult to work on packages prepared by
other team members.

The agreement was to find one standard and make it part of the team's
policy and incorporate into dh-make-golang.

To that end, it is requested that everyone sends an email to the mailing
list describing their preferred workflow, and after a period of
discussion we agree to a conclusion.

dh-make-golang
--

A few times people expressed the desire for dh-make-golang to grow an
`--update` option, as most packages are trivial to update, but tedious
to do so.

Satta requested an option to disable SSL verification for badly
configured redirection sites.

x/tools package
---

We discussed the current breakage in x/tools, and agreed that it is a
core package and that we should make it a shared responsibility to keep
it in a good shape.

gccgo support
-

We talked about the status of gccgo, paultag explained how mainline
golang promises the compiler will always be buildable by gccgo, and how
that makes bootstrapping and cross-building way simpler.

We agreed on working towards making it a first-class citizen in the
future, using golang-any by default, and only reverting to golang-go
when needed.

API changes in upstream
---

We ranted at length about upstreams, and noted that we need a system
that provides early warning of API breakages. We discussed using ratt
and autopkgtest for that purpose.

Aviau pointed out that he usually requests upstreams to make releases
and that he is usually successful. Tincho pointed out the problems with
meaningless releases and with upstreams releasing once and then
forgetting to do it when needed.

We discussed the possibility of changing "soname"s by renaming packages
when we detect API incompatibilities, but concluded that in general it
is too much work and that it makes more sense to try and fix
reverse-dependencies by bugging upstream or patching them ourselves.

Team collaboration
--

On the topic of team collaboration, we agreed to avoid using the DM ACL
mechanism too much, and instead help active contributors to become DDs.

We also revisited the policy on team uploads, and concluded that we want
to continue with avoiding hard ownership of packages and that by default
everything is team-maintained.

Plan of action
--

There was some talk about things to do in the immediate future to
improve the team work:

  * paultag will work on automated binNMU need detection
  * Automated updating and testing of packages.
  * Standarisation & documentation of workflows: Tincho will send a
request to the ML.
- After discussion, will be merged into policy & dh-make-golang.
  * aviau volunteers to document dh_golang options.
  * satta is going to take a look at policy cleanup.

Thanks to all for participating!

Tincho.

-- 
Martín Ferrari (Tincho)

___
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#871551: Bug#871551: Do not copy data to GOPATH before running tests

[Martín Ferrari]

On 09/08/17 01:52, Vincent Bernat wrote:

> When tests are trying to use data available in the root package, those
> data are not available because the copy done in the built GOPATH do
> not contain them. Example:
> 
>  https://github.com/osrg/gobgp/blob/master/config/bgp_configs_test.go#L103
> 
> ~/gobgp-1.22/obj-x86_64-linux-gnu/src/github.com/osrg/gobgp $ find -type f | 
> grep -v go$
> ./tools/grpc/cpp/gobgp_api_client.cc
> ./api/gobgp.proto

You are supposed to tell dh_golang about any extra files you need to
include, by exporting a DH_GOLANG_INSTALL_EXTRA variable that is a
space-separated list of regexes to match against pathnames.

-- 
Martín Ferrari (Tincho)

___
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] package go // Meeting of the pkg-go team,Edit

[Martín Ferrari]

Hi all,

The Go packaging team is going to have a meeting to discuss current
problems and plan future work. Hopefully we can also get some work done
along the week.

If you are interested, join us at:

Tuesday 7th (tomorrow), 11am
Upstairs in the Interior Garden.

Add your ideas for discussion here:
https://wiki.debian.org/Teams/DebianGoTeam/DebConf17BoF


PS: Title shamelessly stolen from the Perl team.

-- 
Martín Ferrari (Tincho)

___
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] pkg-go bof at debconf

[Martín Ferrari]

On 07/08/17 13:15, Alexandre Viau wrote:
> On 07/08/17 11:42 AM, Martín Ferrari wrote:
>> Please fill it before today at 18h (22h GMT), so I can schedule it in
>> the system.

So, everybody has already answered, and tomorrow at 11 seems to be the
perfect time. Friday at 11 is also good, but I'd rather have a meeting
tomorrow, and keep the option for a second meeting if we still have
stuff to work on.

But I went to book the slot for tomorrow morning (which everybody can
attend). But all the rooms were taken!

So, let's be creative and meet in the upper part of the interior garden,
which is usually very quiet.

For the remote participants, we need to use some conferencing software
in a laptop (video team does not offer streaming of ad-hoc events).

Any suggestions about something that works reliably? I have been using
Google Hangouts for work, but it requires a proprietary chromium plugin.

I will send an announce to the debconf mailing list in case somebody
else wants to join.

-- 
Martín Ferrari (Tincho)

___
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] pkg-go bof at debconf

[Martín Ferrari]

>> As for the timing, I would suggest a one-hour slot at Tuesday at 17:00
>> (21:00 UTC). Please let me know asap if this works for you or what would
>> be your availability.

Since there are a couple of guys that would like to join remotely and
the time is a bit difficult for them, I created a dudle at
https://dudle.inf.tu-dresden.de/go-pkg_bof/ to decide the final time.

Please fill it before today at 18h (22h GMT), so I can schedule it in
the system.


-- 
Martín Ferrari (Tincho)

___
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] pkg-go bof at debconf

[Martín Ferrari]

Since we reached critical mass (3 people!) I went ahead and submitted a
ad-hoc event for DebConf (https://debconf17.debconf.org/talks/216/
probably not yet visible)

The idea would be to discuss a bit the current status of the team and
ideas going forward. I created a wiki page to define the agenda, please
add your topics there:
https://wiki.debian.org/Teams/DebianGoTeam/DebConf17BoF

If somebody else would like to participate remotely, we can try to find
a way, but please speak up NOW!

As for the timing, I would suggest a one-hour slot at Tuesday at 17:00
(21:00 UTC). Please let me know asap if this works for you or what would
be your availability.

For this to happen, it needs to be registered before 19:00 on Monday, so
don't delay! :)

-- 
Martín Ferrari (Tincho)

___
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] Why we install the test files in dev pkg(was: Bug#870643: golang-github-pierrec-lz4-dev: please split off test data)

[Martín Ferrari]

On 04/08/17 04:48, Shengjing Zhu wrote:
> BTW, I always drop test dependencies for the -dev package.

This is not a problem, as the tests are not needed for *using* the
package. Autopkgtest uses the build-dependencies for that.


-- 
Martín Ferrari (Tincho)

___
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] Why we install the test files in dev pkg(was: Bug#870643: golang-github-pierrec-lz4-dev: please split off test data)

[Martín Ferrari]

On 04/08/17 04:46, Shengjing Zhu wrote:

> I'm wondering why we install the *_test.go files in the *-dev binary package.
> IMHO, other package won't import the test files from *-dev package.

I am not sure if this was ever discussed, but I kind of like the tests
being there in case I want to run them. It is the same for scritping
languages like perl and python, tests are installed.

> And the CI system is to test building the src package from scratch. It
> doesn't  run `go test ./...` from the -dev package.

> One doubt is that how the autopkgtest run for -dev pkg. Does it just
> run again the `go test` like CI for src pkg?

CI.debian.net uses autopkgtest, which in turn uses these installed
_test.go files to run the tests.


-- 
Martín Ferrari (Tincho)

___
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#870083: Bug#870083: prometheus-node-exporter: Inappropriate depends on daemon

[Martín Ferrari]

On 30/07/17 17:30, Tollef Fog Heen wrote:

>> Thanks for reporting this. I would still like to provide a seamless
>> install for sysv users like me, would a conditional depends like 'daemon
>> | systemd-sysv' work?
> 
> Recommends are enabled by default, so just demoting it to Recommends
> should work for most people, but otherwise yes, your suggestion should
> work fine.

This package is aimed at sysadmins, who would routinely disable
recommends installation. I would go the conditional depends route then.

Thanks again.


-- 
Martín Ferrari (Tincho)

___
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#811565: [uscan] git mode: allow for scanning repositories without tags

[Martín Ferrari]

On 29/07/17 17:44, Michael Stapelberg wrote:


> Given that we are talking about repositories which do not use tags, we
> could specify --depth=1 when cloning to get a shallow clone, i.e. only
> the latest commit. That saves bandwidth and disk space, but has the
> downside that we cannot do any additional validation, i.e. we can’t
> detect if upstream ever starts using tags — unfortunately, that is a
> plausible scenario, so I would suggest doing a full clone.

As a data point, I wrote a script a while ago to do exactly this
locally. I used the shallow clone on a temporary directory:

backticks("git", "clone", "--quiet", "--bare", "--depth=1", $url,
$dest);

my $commit_data = backticks("git", "--git-dir=$dest", "log", "-1",
"--date=format:%Y%m%d", "--format=%h %cd");

chomp($commit_data);
$commit_data =~ /^([0-9a-z]{7}) ([0-9]{8})$/m
or die("Invalid git response: $commit_data");
return ($1, $2);

-- 
Martín Ferrari (Tincho)

___
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#870083: Bug#870083: prometheus-node-exporter: Inappropriate depends on daemon

[Martín Ferrari]

Hi Tollef,

On 29/07/17 16:19, Tollef Fog Heen wrote:

> Most systems don't need the daemon dependency since it's only used with
> non-systemd setups.  It should be demoted to a Suggests or Recommends
> rather than a depends.

Thanks for reporting this. I would still like to provide a seamless
install for sysv users like me, would a conditional depends like 'daemon
| systemd-sysv' work?


-- 
Martín Ferrari (Tincho)

___
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#869800: Bug#869800: Bug#869800: golang-github-aws-aws-sdk-go: Please update to >= 1.4.13

[Martín Ferrari]

On 27/07/17 14:05, Michael Stapelberg wrote:
> It does break the API, as evinced by one build failure.
> 
> I’m not aware of situations in the past where we created a new binary.
> How would we name them? Is it worth the trouble?

We had to do it once, for golang-github-dgrijalva-jwt-go-v3-dev

Worth the trouble or not: depends on who gets to fix all the breakage
left behind :)

> Personally, I would just update the new version + the fixed affected
> packages in one go, to reduce the breakage to a minimum.

I would be OK with that.

-- 
Martín Ferrari (Tincho)

___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers