Re: [pkg-go] Plans for uploading Go 1.5 to unstable?

[Michael Hudson-Doyle]

If you're impatient, I'm pretty sure recent enough docker builds with
gccgo on arm64.

On 14 October 2015 at 12:43, Potter, Tim (Converged Cloud)
 wrote:
> Hi tianon.  I was curious what your plans were for uploading Go 1.5 to 
> unstable.  Is there anything you can share?
>
> I’m pretty keen on seeing Docker running on arm64 which should get pulled in 
> as golang-go is a B-D.
>
>
> Thanks,
>
> Tim.
> ___
> 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] Plans for uploading Go 1.5 to unstable?

[Michael Hudson-Doyle]

On 16 October 2015 at 06:40, Michael Stapelberg  wrote:
>
>
> On Thu, Oct 15, 2015 at 6:44 PM, Tianon Gravi  wrote:
>>
>> On 13 October 2015 at 16:43, Potter, Tim (Converged Cloud)
>>  wrote:
>> > Hi tianon.  I was curious what your plans were for uploading Go 1.5 to
>> > unstable.  Is there anything you can share?
>>
>> Go 1.5 has some minor breaking changes, so I've been waiting until I
>> (or some other kind soul) has had the time to do a full ratt run on Go
>> 1.5 and make sure all our packages either build/test successfully or
>> that we have a plan/patches ready to fix the issues that are bound to
>> come up.
>
>
> FWIW, I don’t think that’s necessary for the compiler itself. Go adheres to
> its Go 1 stability guarantee, and any package which breaks likely did
> something wrong in the first place :). If this is the only thing that’s
> holding back the upload, I’d recommend to just go ahead with the upload.

That's a nice idea, and for pure go things it might even be close to
true, but it's definitely not true universally. Here's a few reasons
for failures I saw when prepping 1.5 for ubuntu:

1) cgo is a particularly rich source of incompatibilities (see docker,
and also the tightening over time rules about passing Go pointers to
C)
2) the go tool now explodes if you're careless and set GOPATH to have
an empty component
3) packages that have expectations of what tracebacks look like in
their testsuite
4) testing/quick can produce nil pointers now
5) golang-x-text was broken by a new unicode version
6) a few ftbfs on arm builders with low ram

Some of these are definitely bugs in the package or packaging but not all.

Cheers,
mwh

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

[pkg-go] Processing of golang-github-lib-pq_0.0~git20151007.0.ffe986a-1_amd64.changes

[Debian FTP Masters]

golang-github-lib-pq_0.0~git20151007.0.ffe986a-1_amd64.changes uploaded 
successfully to localhost
along with the files:
  golang-github-lib-pq_0.0~git20151007.0.ffe986a-1.dsc
  golang-github-lib-pq_0.0~git20151007.0.ffe986a.orig.tar.xz
  golang-github-lib-pq_0.0~git20151007.0.ffe986a-1.debian.tar.xz
  golang-github-lib-pq-dev_0.0~git20151007.0.ffe986a-1_all.deb
  golang-pq-dev_0.0~git20151007.0.ffe986a-1_all.deb

Greetings,

Your Debian queue daemon (running on host franck.debian.org)

___
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] golang-github-lib-pq_0.0~git20151007.0.ffe986a-1_amd64.changes is NEW

[Debian FTP Masters]

binary:golang-github-lib-pq-dev is NEW.
source:golang-github-lib-pq 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

___
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#785649: marked as done (go-md2man: Enable the build for gccgo platforms)

[Debian Bug Tracking System]

Your message dated Thu, 15 Oct 2015 21:20:41 +
with message-id 
and subject line Bug#785649: fixed in go-md2man 1.0.4-3
has caused the Debian Bug report #785649,
regarding go-md2man: Enable the build for gccgo platforms
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
785649: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785649
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: go-md2man
Version: 1-2
Severity: important
Tags: patch

go-md2man FTBFS on ppc64el architecture because it depends on golang that is
still not ported to ppc64el.  In this case, we would like to depend on gccgo
for ppc64el architecture. 

This patch change the build-depends on ppc64el from golang to gccgo.

Thanks
Breno

-- System Information:
Debian Release: 8.0
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: ppc64el (ppc64le)

Kernel: Linux 3.16.0-4-powerpc64le (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Index: go-md2man-1/debian/control
===
--- go-md2man-1.orig/debian/control
+++ go-md2man-1/debian/control
@@ -3,7 +3,8 @@ Section: doc
 Priority: extra
 Maintainer: Tianon Gravi 
 Uploaders: Docker Packaging Team 
-Build-Depends: debhelper (>= 9), dh-golang, golang-blackfriday-dev, golang-go
+Build-Depends: debhelper (>= 9), dh-golang, golang-blackfriday-dev,
+   golang-go [!ppc64el], gccgo [ppc64el]
 Standards-Version: 3.9.5
 Homepage: https://github.com/cpuguy83/go-md2man
 Vcs-Git: git://anonscm.debian.org/pkg-go/packages/go-md2man.git
--- End Message ---
--- Begin Message ---
Source: go-md2man
Source-Version: 1.0.4-3

We believe that the bug you reported is fixed in the latest version of
go-md2man, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 785...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Tianon Gravi  (supplier of updated go-md2man package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 15 Oct 2015 13:00:34 -0700
Source: go-md2man
Binary: go-md2man golang-github-cpuguy83-go-md2man-dev
Architecture: source
Version: 1.0.4-3
Distribution: unstable
Urgency: medium
Maintainer: pkg-go 
Changed-By: Tianon Gravi 
Description:
 go-md2man  - utility to create manpages from markdown
 golang-github-cpuguy83-go-md2man-dev - utility to create manpages from 
markdown (source)
Closes: 785649
Changes:
 go-md2man (1.0.4-3) unstable; urgency=medium
 .
   * Allow gccgo to satisfy our "go" needs (Closes: #785649).
Checksums-Sha1:
 216b2a7b8443451a44f348f3cb9ff260258c 2137 go-md2man_1.0.4-3.dsc
 cc455a4d69facc2627b8a2ef6ea44d302a9e0760 2444 go-md2man_1.0.4-3.debian.tar.xz
Checksums-Sha256:
 bf6582f03e6f0b08fc0c6c5dcbf717ec4d615d97a0624e8adcb77d22a4a5daff 2137 
go-md2man_1.0.4-3.dsc
 e23f601476e51a6f6d29d0a45a5f198c7e0bdf5b11f3c2a991f375c0350ff087 2444 
go-md2man_1.0.4-3.debian.tar.xz
Files:
 92c903ac882e5666e3525efd179cbaab 2137 doc extra go-md2man_1.0.4-3.dsc
 9cbef25b59a3f99dfa5b1ae0363b64a6 2444 doc extra go-md2man_1.0.4-3.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJWIAYRAAoJEANqnCW/NX3UrkQP/jmZuT5jSzq8y9DVw9AHq1/3
cc3/BZDJFcxy1Ql/Zpj1DfGjc9trt1nEMe7OWJMGqhksWLyb1/gdIEBZyOHb7Byg
0Waqxx4kIqraEdwdU5lhE/Bq0wPCQgnEMIFmxWZ9FLSbIuc9stMexUMKZKQSL4jl
N54ddiNRU1lwiTnRXxTxo7/05S+oXq6bz82eryyGLG83yBdJCUr6YL5NG2UkJwiW
g2Qvtx+R2X3BPL9O7+AUSORpWIJe6qBHPnt4TIoTxPNLOy9+EMv83hD/vIJ04UnO
mWhFG99umlK1Ysyfk0XVvm/NzM1V49AxrK4NORvtO3z+/PPWQ0KM63bK/OrHUhhF
wHRRN+hamFg1+z3B0aQAlA1/7lESofjEbRzTr0H0fGCGUV7X380Hl1tlwZlx+NLz
l7w3a73NCT7Ba47mL5dpjUX72kmnFcxcOUetmHFtCUK6aS8bcyFnscjEHuuD2A6z
CAePj/ihy0K3ZsaG5bj5lZgQNZIaxt/RDl6sxnVPCWJdSqv027nBj7Wffk1V6f+u
m36776vKIVZ14QaF6mjV6tMjXpiFBsiF15xLvg9FDTkAYo1yRCu0oSMnplrJt8v5
k+5BpFBh/WM0V7j3Hzz4RUEdondlLqARhtymBrmaD4i04j8F6Ns122A8zyQJMS0u

[pkg-go] Bug#801593: Bug#801593: Bug#801593: ratt does not find all reverse build dependencies

[Tianon Gravi]

On 14 October 2015 at 22:37, Johannes Schauer  wrote:
> Extracting all binary packages introduced by your upload is trivial. Just look
> at the Binary: field in your .changes file.

Just to note, in the case of Paul's interface in
"pault.ag/go/debian/control", that'd be changes.Binaries [1]. :)

[1]: https://godoc.org/pault.ag/go/debian/control#Changes

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4

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

[pkg-go] gosu 1.6-1 MIGRATED to testing

[Debian testing watch]

FYI: The status of the gosu source package
in Debian's testing distribution has changed.

  Previous version: 1.5-1
  Current version:  1.6-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

Re: [pkg-go] Plans for uploading Go 1.5 to unstable?

[Tianon Gravi]

Sure! :)  On the Docker end, the discussion is in
https://github.com/docker/docker/pull/15703 (and you're correct that
it's Docker doing something "wrong", but isn't it still worth checking
so we don't get random FTBFS?  or do we just not worry about it and do
something about them as they come?)

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4


On 15 October 2015 at 11:08, Michael Stapelberg  wrote:
> Do you have a link with details? I’m curious.
>
> On Thu, Oct 15, 2015 at 7:45 PM, Tianon Gravi  wrote:
>>
>> On 15 October 2015 at 10:40, Michael Stapelberg 
>> wrote:
>> > FWIW, I don’t think that’s necessary for the compiler itself. Go adheres
>> > to
>> > its Go 1 stability guarantee, and any package which breaks likely did
>> > something wrong in the first place :). If this is the only thing that’s
>> > holding back the upload, I’d recommend to just go ahead with the upload.
>>
>> Right, in theory, that's supposed to be the case.  I've seen several
>> examples already where that's not the case, including Docker itself.
>>
>> ♥,
>> - Tianon
>>   4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4
>
>
>
>
> --
> Best regards,
> Michael

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

Re: [pkg-go] Plans for uploading Go 1.5 to unstable?

[Tianon Gravi]

On 15 October 2015 at 10:40, Michael Stapelberg  wrote:
> FWIW, I don’t think that’s necessary for the compiler itself. Go adheres to
> its Go 1 stability guarantee, and any package which breaks likely did
> something wrong in the first place :). If this is the only thing that’s
> holding back the upload, I’d recommend to just go ahead with the upload.

Right, in theory, that's supposed to be the case.  I've seen several
examples already where that's not the case, including Docker itself.

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4

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

Re: [pkg-go] Plans for uploading Go 1.5 to unstable?

[Michael Stapelberg]

On Thu, Oct 15, 2015 at 6:44 PM, Tianon Gravi  wrote:

> On 13 October 2015 at 16:43, Potter, Tim (Converged Cloud)
>  wrote:
> > Hi tianon.  I was curious what your plans were for uploading Go 1.5 to
> unstable.  Is there anything you can share?
>
> Go 1.5 has some minor breaking changes, so I've been waiting until I
> (or some other kind soul) has had the time to do a full ratt run on Go
> 1.5 and make sure all our packages either build/test successfully or
> that we have a plan/patches ready to fix the issues that are bound to
> come up.
>

FWIW, I don’t think that’s necessary for the compiler itself. Go adheres to
its Go 1 stability guarantee, and any package which breaks likely did
something wrong in the first place :). If this is the only thing that’s
holding back the upload, I’d recommend to just go ahead with the upload.


>
> To Michael's point about compiling Docker via gccgo -- as the
> maintainer of the build scripts for upstream, please don't do that for
> anything serious.  I've been working closely with IBM on that, and
> none of us are really thrilled with the results so far, but it's the
> only way we can get anything at all on some of their more interesting
> architectures like s390x.
>
> ♥,
> - Tianon
>   4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4
>
> ___
> Pkg-go-maintainers mailing list
> Pkg-go-maintainers@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
>



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