[pkg-go] Bug#840711: golang-github-appc-docker2aci: CVE-2016-8579

2016-10-13 Thread Salvatore Bonaccorso
Source: golang-github-appc-docker2aci
Version: 0.12.0+dfsg-1
Severity: grave
Tags: security upstream patch
Forwarded: https://github.com/appc/docker2aci/issues/203

Hi,

the following vulnerability was published for golang-github-appc-docker2aci.

CVE-2016-8579[0]:
infinite loop in deps walking

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-8579
[1] https://github.com/appc/docker2aci/issues/203
[2] 
https://github.com/lucab/docker2aci/commit/54331ec7020e102935c31096f336d31f6400064f

Regards,
Salvatore

___
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] gobgp is marked for autoremoval from testing

2016-10-13 Thread Debian testing autoremoval watch
gobgp 1.12-1 is marked for autoremoval from testing on 2016-11-02

It (build-)depends on packages with these RC bugs:
835336: influxdb: FTBFS in testing (go generate returned exit code 1)
839364: golang: FTBFS: Go version is "go1.6.1", ignoring -next 
/<>/api/next.txt


___
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] PSA: the freeze is coming

2016-10-13 Thread Ben Kochie
There are several open CI pipeline systems out there that can watch for 
git changes and do this kind of thing.


We already use Travis to do all of the branch testing for Prometheus 
projects.


Option 1, we can use the Travis SaaS. https://travis-ci.org/
Option 2, we can deploy our own with the source. https://github.com/travis-ci/

-ben

On Thu, 13 Oct 2016, Martín Ferrari wrote:


On 13/10/16 15:03, Ben Kochie wrote:

PS: I am thinking that we should have some kind of automated ratt setup
(maybe even a private upload queue that runs ratt and then automatically
uploads to sid, and make that mandatory policy for the team), but I
don't really have the bandwidth now to implement it. Anybody else thinks
that would be a good idea?


Being new to the team, I haven't contributed yet.  But I'm +1000 for
automation, especially if it helps prevent bad thigns from happening.

I'd be willing to look into this given there are some docs I can read.


That'd be great!

Ratt is a tool written by Michael that rebuilds the reverse dependencies
of a package, to check for breakage. But it currently lacks support for
transitive dependencies, which IMO severely limits its usefulness.

What I had in mind was maybe to build a upload queue, which would be a
directory in some server, where some cronjob or something will trigger a
ratt run and based on that decide to discard the package or reupload to
the official incoming queue using dput or something similar.

--
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-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#840681: etcd: Section should not be “devel”

2016-10-13 Thread Ben Finney
Package: etcd
Version: 3.5.1-1
Severity: minor

Dear Maintainer,

The section “devel” is for packages primarily for developing software.
Its packages are primarily of interest only to programmers.

The package ‘etcd’ installs primarily an administrative daemon, of
interest to system administrators. It should not be in the “devel”
section.

By the section descriptions, this package may belong in section
“admin”.

Please set the field “Section” appropriately on this package.


Since the package is already in Debian with a different section, you
will also need to submit a request to override the existing section
.

Then mark this bug report as blocked by that new one, and be sure not
to close this one until that new one is completed.

-- 
 \ “Pinky, are you pondering what I'm pondering?” “Uh, I think so, |
  `\  Brain, but balancing a family and a career ... ooh, it's all |
_o__) too much for me.” —_Pinky and The Brain_ |
Ben Finney 


signature.asc
Description: 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#840676: RFP: golang-github-kardianos-osext -- Extensions to the standard "os" package

2016-10-13 Thread Guillem Jover
Package: wnpp
Severity: wishlist
Tags: patch

* Package name: golang-github-kardianos-osext
  Version : 0.0~git20160811.0.c2c54e5-1
  Upstream Author : Daniel Theophanes
* URL : https://github.com/kardianos/osext
* License : BSD-3-clause
  Programming Lang: Go
  Description : Extensions to the standard "os" package

 There is sometimes utility in finding the current executable file that is
 running. This can be used for upgrading the current executable or finding
 resources located relative to the executable file. Both working directory
 and the os.Args[0] value are arbitrary and cannot be relied on; os.Args[0]
 can be "faked".


This package is a dependency of golang-github-kardianos-service, which
is a dependency of latest telegraf upstream releases.

Attached a working and tested packaging. It only requires filling in
this ITP bug number in debian/changelog, changing the Maintainer field
and adding Vcs fields.

Thanks,
Guillem


golang-github-kardianos-osext_0.0~git20160811.0.c2c54e5-1.debian.tar.xz
Description: application/xz
___
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] Processed: [bts-link] source package src:gobgp

2016-10-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> #
> # bts-link upstream status pull for source package src:gobgp
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #840031 (http://bugs.debian.org/840031)
> # Bug title: gobgp: FTBFS (32-bit): constant 4294967295 overflows int
> #  * https://github.com/osrg/gobgp/pull/1139
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 840031 + fixed-upstream
Bug #840031 [src:gobgp] gobgp: FTBFS (32-bit): constant 4294967295 overflows int
Added tag(s) fixed-upstream.
> usertags 840031 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
840031: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840031
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
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] gobgp 1.12-1 MIGRATED to testing

2016-10-13 Thread Debian testing watch
FYI: The status of the gobgp source package
in Debian's testing distribution has changed.

  Previous version: 1.11-1
  Current version:  1.12-1

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more 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#840656: influxdb: Please package upstream release 1.0.1

2016-10-13 Thread Guillem Jover
Source: influxdb
Source-Version: 0.13.0+dfsg1-4
Severity: wishlist
Tags: patch
Control: block -1 by 840633

Hi!

There's a new upstream release 1.0.1. It would be nice to get that
uploaded so that it can get into stretch. This one drops the
clustering support, so perhaps a NEWS entry is in order (probably
pointing to influxdb-relay, for which I'll file also an RFP)?

This new release depends on the golang-github-retailnext-hllpp package
for which I've filed an RFP with ready-made packaging.

Also attached the necessary changes, which have been tested locally.

Thanks,
Guillem
From ed4f3006daa4e999bfa316ecf424afc77ed6e24e Mon Sep 17 00:00:00 2001
From: Guillem Jover 
Date: Thu, 13 Oct 2016 17:11:07 +0200
Subject: [PATCH] Package influxdb 1.0.1

---
 debian/changelog   |   6 ++
 debian/control |  10 +--
 debian/influxdb.conf   | 157 +
 debian/patches/disable-reporting.patch |  15 ++--
 4 files changed, 80 insertions(+), 108 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index 4d6fd88..b65f936 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+influxdb (1.0.1-1) UNRELEASED; urgency=medium
+
+  * New upstream release.
+
+ -- Guillem Jover   Thu, 29 Sep 2016 14:31:48 +
+
 influxdb (0.13.0+dfsg1-4) unstable; urgency=medium
 
   * Replace uglifyjs by yui-compressor
diff --git a/debian/control b/debian/control
index 7648b15..b9e357e 100644
--- a/debian/control
+++ b/debian/control
@@ -21,13 +21,12 @@ Build-Depends: debhelper (>= 9),
golang-github-boltdb-bolt-dev,
golang-github-peterh-liner-dev,
golang-github-bmizerany-pat-dev,
-   golang-gopkg-fatih-pool.v2-dev,
golang-github-rakyll-statik-dev,
+   golang-github-retailnext-hllpp-dev,
golang-github-kimor79-gollectd-dev,
golang-collectd-dev,
-   golang-github-hashicorp-raft-boltdb-dev,
-   golang-github-hashicorp-raft-dev,
golang-github-davecgh-go-spew-dev,
+   golang-github-dgrijalva-jwt-go-dev,
golang-github-dgryski-go-bitstream-dev,
golang-github-dgryski-go-bits-dev,
golang-github-jwilder-encoding-dev (>= 0.0~git20160426.0.ac74639),
@@ -53,13 +52,12 @@ Depends: ${misc:Depends},
  golang-github-boltdb-bolt-dev,
  golang-github-peterh-liner-dev,
  golang-github-bmizerany-pat-dev,
- golang-gopkg-fatih-pool.v2-dev,
  golang-github-rakyll-statik-dev,
+ golang-github-retailnext-hllpp-dev,
  golang-github-kimor79-gollectd-dev,
  golang-collectd-dev,
- golang-github-hashicorp-raft-boltdb-dev,
- golang-github-hashicorp-raft-dev,
  golang-github-davecgh-go-spew-dev,
+ golang-github-dgrijalva-jwt-go-dev,
  golang-github-dgryski-go-bitstream-dev,
  golang-github-dgryski-go-bits-dev,
  golang-github-jwilder-encoding-dev (>= 0.0~git20160426.0.ac74639),
diff --git a/debian/influxdb.conf b/debian/influxdb.conf
index b5f9b4a..739afa5 100644
--- a/debian/influxdb.conf
+++ b/debian/influxdb.conf
@@ -21,19 +21,17 @@ reporting-enabled = false
 ###
 
 [meta]
-  # Controls if this node should run the metaservice and participate in the Raft group
-  enabled = true
-
   # Where the metadata/raft database is stored
   dir = "/var/lib/influxdb/meta"
 
-  bind-address = ":8088"
   retention-autocreate = true
-  election-timeout = "1s"
-  heartbeat-timeout = "1s"
-  leader-lease-timeout = "500ms"
-  commit-timeout = "50ms"
-  cluster-tracing = false
+
+  # If log messages are printed for the meta service
+  logging-enabled = true
+  pprof-enabled = false
+
+  # The default duration for leases.
+  lease-duration = "1m0s"
 
 ###
 ### [data]
@@ -50,36 +48,13 @@ reporting-enabled = false
 
   dir = "/var/lib/influxdb/data"
 
-  # The following WAL settings are for the b1 storage engine used in 0.9.2. They won't
-  # apply to any new shards created after upgrading to a version > 0.9.3.
-  max-wal-size = 104857600 # Maximum size the WAL can reach before a flush. Defaults to 100MB.
-  wal-flush-interval = "10m" # Maximum time data can sit in WAL before a flush.
-  wal-partition-flush-delay = "2s" # The delay time between each WAL partition being flushed.
-
   # These are the WAL settings for the storage engine >= 0.9.3
   wal-dir = "/var/lib/influxdb/wal"
   wal-logging-enabled = true
-  data-logging-enabled = true
-
-  # When a series in the WAL in-memory cache reaches this size in bytes it is marked as ready to
-  # flush to the index
-  # wal-ready-series-size = 25600
-
-  # Flush and compact a partition once this ratio of series are over the ready size
-  # wal-compaction-threshold = 0.6
-
-  # Force a flush and compaction if any series in a partition gets above this size in bytes
-  # 

[pkg-go] Processed: influxdb: Please package upstream release 1.0.1

2016-10-13 Thread Debian Bug Tracking System
Processing control commands:

> block -1 by 840633
Bug #840656 [src:influxdb] influxdb: Please package upstream release 1.0.1 
840656 was not blocked by any bugs.
840656 was not blocking any bugs.
Added blocking bug(s) of 840656: 840633

-- 
840656: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840656
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
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#840636: influxdb: Improve and fix init script

2016-10-13 Thread Guillem Jover
Package: influxdb
Version: 0.13.0+dfsg1-4
Severity: normal
Tags: patch

Hi!

The attached file is a fixed and improveed init script for influxdb.
It removes things for which there's better guaranteed alternatives in
Debian and fixes few behavior nits.

Thanks,
Guillem
commit b5063ad4ff15aca76670f8635d292264fb34c3b1
Author: Guillem Jover 
Date:   Fri Sep 30 17:36:31 2016 +0200

Fix init script

diff --git a/debian/influxdb.init b/debian/influxdb.init
index e9db2d0..71e54f8 100644
--- a/debian/influxdb.init
+++ b/debian/influxdb.init
@@ -1,4 +1,4 @@
-#!/bin/bash
+#!/bin/sh
 
 ### BEGIN INIT INFO
 # Provides:  influxdb
@@ -32,13 +32,13 @@ USER=influxdb
 GROUP=influxdb
 
 if [ -r /lib/lsb/init-functions ]; then
-source /lib/lsb/init-functions
+. /lib/lsb/init-functions
 fi
 
 DEFAULT=/etc/default/influxdb
 
 if [ -r $DEFAULT ]; then
-source $DEFAULT
+. $DEFAULT
 fi
 
 if [ -z "$STDOUT" ]; then
@@ -58,48 +58,6 @@ fi
 
 OPEN_FILE_LIMIT=65536
 
-function pidofproc() {
-if [ $# -ne 3 ]; then
-echo "Expected three arguments, e.g. $0 -p pidfile daemon-name"
-fi
-
-pid=$(pgrep -f $3)
-local pidfile=$(cat $2)
-
-if [ "x$pidfile" == "x" ]; then
-return 1
-fi
-
-if [ "x$pid" != "x" -a "$pidfile" == "$pid" ]; then
-return 0
-fi
-
-return 1
-}
-
-function killproc() {
-if [ $# -ne 3 ]; then
-echo "Expected three arguments, e.g. $0 -p pidfile signal"
-fi
-
-PID=`cat $2`
-
-/bin/kill -s $3 $PID
-while true; do
-pidof `basename $daemon` >/dev/null
-if [ $? -ne 0 ]; then
-return 0
-fi
-
-sleep 1
-n=$(expr $n + 1)
-if [ $n -eq 30 ]; then
-/bin/kill -s SIGKILL $PID
-return 0
-fi
-done
-}
-
 # Process name ( For display )
 name=influxd
 desc=database
@@ -122,45 +80,10 @@ config=/etc/influxdb/influxdb.conf
 # If the daemon is not there, then exit.
 [ -x $daemon ] || exit 0
 
-function wait_for_startup() {
-control=1
-while [ $control -lt 5 ]
-do
-if [ ! -e $pidfile ]; then
-sleep 1
-control=$((control+1))
-else
-break
-fi
-done
-}
-
-function is_process_running() {
-# Checked the PID file exists and check the actual status of process
-if [ -e $pidfile ]; then
-pidofproc -p $pidfile $daemon > /dev/null 2>&1 && status="0" || status="$?"
-# If the status is SUCCESS then don't need to start again.
-if [ "x$status" = "x0" ]; then
-return 0
-else
-return 1
-fi
-else
-return 1
-fi
-}
-
 case $1 in
 start)
 log_daemon_msg "Starting $desc" "$name"
 
-# Check if it's running first
-is_process_running
-if [ $? -eq 0 ]; then
-log_end_msg 0
-exit 0
-fi
-
 # Bump the file limits, before launching the daemon. These will carry over to
 # launched processes.
 ulimit -n $OPEN_FILE_LIMIT
@@ -170,41 +93,22 @@ case $1 in
 exit 1
 fi
 
-if which start-stop-daemon > /dev/null 2>&1; then
-start-stop-daemon --chuid $GROUP:$USER --start --quiet --pidfile $pidfile --exec $daemon -- -pidfile $pidfile -config $config $INFLUXD_OPTS >>$STDOUT 2>>$STDERR &
-else
-su $USER -c "nohup $daemon -pidfile $pidfile -config $config $INFLUXD_OPTS >>$STDOUT 2>>$STDERR &"
-fi
+start-stop-daemon --start --quiet --oknodo --exec $daemon \
+  --chuid $GROUP:$USER --pidfile $pidfile --background \
+  -- -pidfile $pidfile -config $config $INFLUXD_OPTS \
+  >>$STDOUT 2>>$STDERR
 
-wait_for_startup && is_process_running
-if [ $? -ne 0 ]; then
-log_progress_msg "$name process failed to start"
-log_end_msg 1
-exit 1
-else
-log_end_msg 0
-exit 0
-fi
+log_end_msg $?
 ;;
 
 stop)
 log_daemon_msg "Stopping $desc" "$name"
 
 # Stop the daemon.
-is_process_running
-if [ $? -ne 0 ]; then
-log_progress_msg "$name process is not running"
-log_end_msg 0
-exit 0 # Exit
-else
-if killproc -p $pidfile SIGTERM && /bin/rm -rf $pidfile; then
-log_end_msg 0
-exit 0
-else
-log_end_msg 1
-exit 1
-fi
-fi
+start-stop-daemon --stop --quiet --oknodo \
+  --exec $daemon --pidfile $pidfile
+
+log_end_msg $?
 ;;
 
 restart|force-reload)
@@ -216,19 +120,7 @@ case $1 in
 ;;
 
 status)
-log_daemon_msg "Checking status of $desc" "$name"
-
-# Check the status of the process.
-is_process_running
-if [ $? -eq 0 ]; then
-log_progress_msg "running"
-  

[pkg-go] Processed: Re: Bug#793836: ITP: golang-gopkg-shopify-sarama -- Go library for Apache Kafka 0.8

2016-10-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> block 793749 by 840627
Bug #793749 [wnpp] ITP: telegraf -- plugin-driven server agent for reporting 
metrics into InfluxDB
793749 was blocked by: 793836 798230 793750 794252
793749 was not blocking any bugs.
Added blocking bug(s) of 793749: 840627
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
793749: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793749
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
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] PSA: the freeze is coming

2016-10-13 Thread Ben Kochie

PS: I am thinking that we should have some kind of automated ratt setup
(maybe even a private upload queue that runs ratt and then automatically
uploads to sid, and make that mandatory policy for the team), but I
don't really have the bandwidth now to implement it. Anybody else thinks
that would be a good idea?


Being new to the team, I haven't contributed yet.  But I'm +1000 for 
automation, especially if it helps prevent bad thigns from happening.


I'd be willing to look into this given there are some docs I can read.


--
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-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] PSA: the freeze is coming

2016-10-13 Thread Martín Ferrari
On 13/10/16 15:03, Ben Kochie wrote:
>> PS: I am thinking that we should have some kind of automated ratt setup
>> (maybe even a private upload queue that runs ratt and then automatically
>> uploads to sid, and make that mandatory policy for the team), but I
>> don't really have the bandwidth now to implement it. Anybody else thinks
>> that would be a good idea?
> 
> Being new to the team, I haven't contributed yet.  But I'm +1000 for
> automation, especially if it helps prevent bad thigns from happening.
> 
> I'd be willing to look into this given there are some docs I can read.

That'd be great!

Ratt is a tool written by Michael that rebuilds the reverse dependencies
of a package, to check for breakage. But it currently lacks support for
transitive dependencies, which IMO severely limits its usefulness.

What I had in mind was maybe to build a upload queue, which would be a
directory in some server, where some cronjob or something will trigger a
ratt run and based on that decide to discard the package or reupload to
the official incoming queue using dput or something similar.

-- 
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#840633: RFP: golang-github-retailnext-hllpp -- HyperLogLog++ cardinality estimation algorithm

2016-10-13 Thread Guillem Jover
Package: wnpp
Severity: wishlist

* Package name: golang-github-retailnext-hllpp
  Version : 0.0~git20160427.0.83bfdfd-1
  Upstream Author : RetailNext, Inc.
* URL : https://github.com/retailnext/hllpp
* License : BSD-3-clause
  Programming Lang: Go
  Description : HyperLogLog++ cardinality estimation algorithm

 hllpp is an implementation of the HyperLogLog++ cardinality estimation
 algorithm in go. It optimizes for memory usage over CPU usage. It
 implements all the HyperLogLog optimizations introduced in the
 HyperLogLog++ paper (http://goo.gl/Z5Sqgu). Some notable features include:
 .
  * Marshaling so you can serialize to your datastore,
  * Extra space savings by only using 5 bits per register when possible,
  * Built-in non-streaming murmur3 implementation for fast hashing of input
data.


This package is required by the latest influxdb upstream. Attached tested
packaging, which only needs the ITP bug filled in debian/changelog,
Maintainer field changed, and Vcs fields added.

Thanks,
Guillem


golang-github-retailnext-hllpp.debian.tar.xz
Description: application/xz
___
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] PSA: the freeze is coming

2016-10-13 Thread Martín Ferrari
Hey all,

As you all know, the freeze is getting close, and we are all working to
get our packages in shape for Stretch.

We have a few big projects that share many common dependencies. This
being the golang ecosystem, we are walking in a minefield.

Only two days ago we had a big breakage introduced by API breaking
changes in libraries, without upstream using any kind of SONAME change.
I think it is the first time I see this happening, but it will only get
worse as we package more parts of the golang world.


Personally, I have been working for 1.5 years in getting Prometheus
ready for Stretch. I know many people here have devoted comparable
amounts of time in other projects. So let's all be considerate of these
efforts and be very careful not to break things.

It was removed from testing yesterday, and I hope to have it back in a
few days, but if it breaks again because of a change in another package,
I think I am going to go postal :-)


So that, let's all be excellent to each other!


PS: I am thinking that we should have some kind of automated ratt setup
(maybe even a private upload queue that runs ratt and then automatically
uploads to sid, and make that mandatory policy for the team), but I
don't really have the bandwidth now to implement it. Anybody else thinks
that would be a good idea?

-- 
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] Processed: golang-github-shopify-sarama: Please package upstream release 1.10.1

2016-10-13 Thread Debian Bug Tracking System
Processing control commands:

> block -1 by 840626
Bug #840627 [src:golang-github-shopify-sarama] golang-github-shopify-sarama: 
Please package upstream release 1.10.1
840627 was not blocked by any bugs.
840627 was not blocking any bugs.
Added blocking bug(s) of 840627: 840626

-- 
840627: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840627
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
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#840627: golang-github-shopify-sarama: Please package upstream release 1.10.1

2016-10-13 Thread Guillem Jover
Source: golang-github-shopify-sarama
Source-Version: 1.9.0
Severity: wishlist
Tags: upstream patch
Control: block -1 by 840626

Hi!

The latest telegraf upstream releases depend on a newer upstream
release of this package. And at the same time the new releases of
Shopify/sarama require golang-github-eapache-go-xerial-snappy-dev,
for which there's now an RFP with packaging attached.

Trivial patch tested and attached for the new upstream release.

Thanks,
Guillem
diff --git i/debian/changelog w/debian/changelog
index 0aaf0f6..295d212 100644
--- i/debian/changelog
+++ w/debian/changelog
@@ -1,3 +1,10 @@
+golang-github-shopify-sarama (1.10.1-1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * New upstream release.
+
+ -- Guillem Jover   Wed, 05 Oct 2016 18:41:13 +0200
+
 golang-github-shopify-sarama (1.9.0-1) unstable; urgency=medium
 
   [ Paul Tagliamonte ]
diff --git i/debian/control w/debian/control
index 15d9339..61cd5a0 100644
--- i/debian/control
+++ w/debian/control
@@ -7,6 +7,7 @@ Build-Depends: debhelper (>= 9),
dh-golang,
golang-go,
 golang-github-davecgh-go-spew-dev,
+golang-github-eapache-go-xerial-snappy-dev,
 golang-gopkg-eapache-go-resiliency.v1-dev | golang-github-eapache-go-resiliency-dev,
 golang-gopkg-eapache-queue.v1-dev | golang-github-eapache-queue-dev,
 golang-github-golang-snappy-dev,
@@ -24,6 +25,7 @@ Depends: ${shlibs:Depends},
  ${misc:Depends},
  golang-go,
 golang-github-davecgh-go-spew-dev,
+golang-github-eapache-go-xerial-snappy-dev,
 golang-gopkg-eapache-go-resiliency.v1-dev | golang-github-eapache-go-resiliency-dev,
 golang-gopkg-eapache-queue.v1-dev | golang-github-eapache-queue-dev,
 golang-github-golang-snappy-dev,
___
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#768073: LXC team take over ITP?

2016-10-13 Thread Martín Ferrari
Hi Jon,

On 13/10/16 11:59, Jonathan Dowland wrote:

> Just a quick mail to say hello, I recently joined because I am interested

Welcomed! :)

> in packaging (at least) build dependencies for LXD, which is Canonical's
> container hypervisor platform.
> 
> The specific go dependencies that we need to package are:

A few of these dependencies are already in the archive, not all have the
standard naming yet, but I think about half of those are already packaged.

-- 
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#840626: RFP: golang-github-eapache-go-xerial-snappy -- Xerial-compatible Snappy framing support for golang

2016-10-13 Thread Guillem Jover
Package: wnpp
Severity: wishlist

* Package name: golang-github-eapache-go-xerial-snappy
  Version : 0.0~git20160609.0.bb955e0-1
  Upstream Author : Evan Huus
* URL : https://github.com/eapache/go-xerial-snappy
* License : MIT
  Programming Lang: Go
  Description : Xerial-compatible Snappy framing support for golang

 Packages using Xerial for snappy encoding use a framing format
 incompatible with basically everything else in existence. This package
 wraps Go's built-in snappy package to support it.


This is a requirement for new usptream releases of
golang-github-shopify-sarama (>= 1.10.x), which is a requirement for
packaging telegraf (its latest versions).

Tested and working packaging attached. Just needs filling in the ITP
bug number in the changelog, changing the Maintainer, and possibly
adding the Vcs fields.

Thanks,
Guillem


golang-github-eapache-go-xerial-snappy.debian.tar.xz
Description: application/xz
___
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#768073: LXC team take over ITP?

2016-10-13 Thread Jonathan Dowland
Hi Team,

Just a quick mail to say hello, I recently joined because I am interested
in packaging (at least) build dependencies for LXD, which is Canonical's
container hypervisor platform.

The specific go dependencies that we need to package are:

* golang-gopkg-flosch-pongo2.v3-dev
* golang-gopkg-inconshreveable-log15.v2-dev
* golang-gopkg-lxc-go-lxc.v2-dev
* golang-any-shared-dev
* golang-go.crypto-dev
* golang-context-dev
* golang-github-gorilla-mux-dev
* golang-github-gosexy-gettext-dev
* golang-github-mattn-go-colorable-dev
* golang-github-mattn-go-sqlite3-dev
* golang-github-olekukonko-tablewriter-dev
* golang-github-pborman-uuid-dev
* golang-gocapability-dev
* golang-gopkg-tomb.v2-dev
* golang-yaml.v2-dev
* golang-websocket-dev

I'm looking at flosch-pongo2 right now, but I thought I'd post the list to this
mailing list just in case anyone else was interested in getting involved!

I've set up this wiki.d.o page to track progress on the above:
https://wiki.debian.org/LXD


Thanks,

-- 
Jonathan Dowland


signature.asc
Description: Digital 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