[pkg-go] golang-github-eknkc-amber_0.0~git20171010.cdade1c-1_source.changes ACCEPTED into unstable

2018-02-07 Thread Debian FTP Masters 


Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 07 Feb 2018 22:13:47 +0100
Source: golang-github-eknkc-amber
Binary: golang-github-eknkc-amber-dev amber
Architecture: source
Version: 0.0~git20171010.cdade1c-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 

Changed-By: Dr. Tobias Quathamer 
Description:
 amber  - Elegant HTML templating engine for Go, inspired from HAML and Jad
 golang-github-eknkc-amber-dev - Elegant HTML templating engine for Go, 
inspired from HAML and Jad
Changes:
 golang-github-eknkc-amber (0.0~git20171010.cdade1c-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream version 0.0~git20171010.cdade1c
   * Use debhelper v11
   * Update to Standards-Version 4.1.3
 - Use Priority: optional
Checksums-Sha1:
 15a42928eac9f85e1f5c4cc45e4b12a6e2f74d5f 2379 
golang-github-eknkc-amber_0.0~git20171010.cdade1c-1.dsc
 bf54ab84e271515d71abae2b657621d8a08a39ef 18364 
golang-github-eknkc-amber_0.0~git20171010.cdade1c.orig.tar.xz
 e8474dc5ba0fb55f4544245cce24f370b9daf4eb 3436 
golang-github-eknkc-amber_0.0~git20171010.cdade1c-1.debian.tar.xz
 b9b5668dda519c3318bda7c3bf72873a781a8acd 5990 
golang-github-eknkc-amber_0.0~git20171010.cdade1c-1_amd64.buildinfo
Checksums-Sha256:
 fa91699fa5cd17f20903fa27f00c6c93b4a58442128512e2011e400051f9ba76 2379 
golang-github-eknkc-amber_0.0~git20171010.cdade1c-1.dsc
 d5478c0899fa4b770489d45286c84ee6bce8c1e11e43beb125c0619415d7c8ca 18364 
golang-github-eknkc-amber_0.0~git20171010.cdade1c.orig.tar.xz
 19e20c2dbba32bf96a64a06f9cf5fcd54a634f7efc73870f0dd68764c7d659a4 3436 
golang-github-eknkc-amber_0.0~git20171010.cdade1c-1.debian.tar.xz
 011cb77cd08028aab19a903989b0a3652c1ad59c1b002753ca4f92ff107ca1a4 5990 
golang-github-eknkc-amber_0.0~git20171010.cdade1c-1_amd64.buildinfo
Files:
 1dbb187cdafaa5d09be07f6e1dd9fffc 2379 devel optional 
golang-github-eknkc-amber_0.0~git20171010.cdade1c-1.dsc
 0dd72e418926ecdf2045b2e89b1c8b4b 18364 devel optional 
golang-github-eknkc-amber_0.0~git20171010.cdade1c.orig.tar.xz
 1f863cd7ae4f30f711d21214dc0aa698 3436 devel optional 
golang-github-eknkc-amber_0.0~git20171010.cdade1c-1.debian.tar.xz
 67135584c5d5699060a2d103f79a9b54 5990 devel optional 
golang-github-eknkc-amber_0.0~git20171010.cdade1c-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE0cuPObxd7STF0seMEwLx8Dbr6xkFAlp7bJkACgkQEwLx8Dbr
6xlF0A//fGpR59fFsnF7NzH06msK9yNUAY39TA+FJAhsnirnc2SRATFuwsagIzUX
nnQfwg/TDXqUZuDs/XOh0tm7nwLVBk9fmWt693nJnkiZN9g2xUYYGAVYBVQhqxyy
NMzd8KSZ65hci+Z+nMRk9W39XpKoAhtZSFLYZioIu7gtFI5DhLIlGU9f3rrAjNjt
Pnv3Ywb9BsuMpsbdsTT73B0+w3mdYl1T6+yDdnoRidKO9Ajp4aQifdI1kukegHs6
cscEMU/0vM2CBXfJyrsSErnDgmWCqLIwDf6FNrboO6oQpW3Elj2gWH5w2wKxm0Yd
ZWiFn1oY4NYBr+sMJHDPWt4s7LUZGxJWho81uTMT4OdVa5YaP6vaq9laceuNAIX7
x8FZL9RVtrY2T3qX0QkihGYWd+BkYfyG2TTBi2IZwH9ne0BCvhsVQFiT6muH0sfI
MFmCq1wa6sB71+y/b96+XZnsGa+QsXwbWgoZ5e5wkfSl8tcXz7qAiVp+iY4fO9Hh
e9WP2wdEIRFUWjJUuU8NQg4MqrYwPH6NBU2MiLAmoRyVkG0Dq1cW/RIG8c6M8I7B
E3B/NU0duLim1tqpC8NSf8eI6cIA5dsiDWQTiplW1PFiTLLK3b+HAKLi7t9Z1Eo8
RrlRxhJ0Xs26ONno9Q/HUGC7bdAV8JMLRzSkmEqRMzqfq6FVclQ=
=gPKm
-END PGP SIGNATURE-


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] golang-github-chaseadamsio-goorgeous_2.0.0+git20171126.dcf1ef8-1_source.changes ACCEPTED into unstable

2018-02-07 Thread Debian FTP Masters 


Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 07 Feb 2018 21:58:46 +0100
Source: golang-github-chaseadamsio-goorgeous
Binary: golang-github-chaseadamsio-goorgeous-dev
Architecture: source
Version: 2.0.0+git20171126.dcf1ef8-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 

Changed-By: Dr. Tobias Quathamer 
Description:
 golang-github-chaseadamsio-goorgeous-dev - Go org syntax parser to html
Changes:
 golang-github-chaseadamsio-goorgeous (2.0.0+git20171126.dcf1ef8-1) unstable; 
urgency=medium
 .
   * New upstream version 2.0.0+git20171126.dcf1ef8
   * Use debhelper v11
   * Update to Standards-Version 4.1.3
   * Update d/copyright
Checksums-Sha1:
 d77602db22b5fe1146253e52edffe0f4e4ee6e11 2591 
golang-github-chaseadamsio-goorgeous_2.0.0+git20171126.dcf1ef8-1.dsc
 a7a3dd5b6372ae6e6ac527446c0a4725ecbb 31196 
golang-github-chaseadamsio-goorgeous_2.0.0+git20171126.dcf1ef8.orig.tar.xz
 c765f67085b0a93e95bcf550712ce476182dc3f3 2132 
golang-github-chaseadamsio-goorgeous_2.0.0+git20171126.dcf1ef8-1.debian.tar.xz
 9e458477bfcd5b99a73886b3379dedf98a42d8b6 5933 
golang-github-chaseadamsio-goorgeous_2.0.0+git20171126.dcf1ef8-1_amd64.buildinfo
Checksums-Sha256:
 8c09db2405d6e21a63d90482521aebe8f7176ef0853ed864ef43b38208364992 2591 
golang-github-chaseadamsio-goorgeous_2.0.0+git20171126.dcf1ef8-1.dsc
 c9a1a265818325c245c7890e181d7e28fd33f7dfc0346a51f6fef0447e068444 31196 
golang-github-chaseadamsio-goorgeous_2.0.0+git20171126.dcf1ef8.orig.tar.xz
 91d37c14be1d68d713a1fe024b439f2805626e8817d006d30c20cd74c7abf6df 2132 
golang-github-chaseadamsio-goorgeous_2.0.0+git20171126.dcf1ef8-1.debian.tar.xz
 6e4cfb474f9c60e4aa9df91cccf0c5b0efb83442285c706c887f69e2734e1e6d 5933 
golang-github-chaseadamsio-goorgeous_2.0.0+git20171126.dcf1ef8-1_amd64.buildinfo
Files:
 6fe8acce88ed40add9a1f813965c298a 2591 devel optional 
golang-github-chaseadamsio-goorgeous_2.0.0+git20171126.dcf1ef8-1.dsc
 d57798279adfec745878f7f681871c22 31196 devel optional 
golang-github-chaseadamsio-goorgeous_2.0.0+git20171126.dcf1ef8.orig.tar.xz
 df164615ea2d9f82a5f58daf909bda3e 2132 devel optional 
golang-github-chaseadamsio-goorgeous_2.0.0+git20171126.dcf1ef8-1.debian.tar.xz
 a877f6b3922b70948f7f53b222468591 5933 devel optional 
golang-github-chaseadamsio-goorgeous_2.0.0+git20171126.dcf1ef8-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE0cuPObxd7STF0seMEwLx8Dbr6xkFAlp7aRAACgkQEwLx8Dbr
6xlPVw//UQaTO09OxgnrB3+csmroolW67Gu6SZZ5TY7f5LX4tCG0ttwZhSNee5q7
6hsKLVlx5s/ZrA+TOhqWzXG9TzyazxBG2+P856CEznBEFwsKHaCvEOQKZQEaA843
hIRDqa7ESE1VV5p5QbbAt/gkRdHxyrLT4+MVUXzUjL4dhP2hDD1387bhDnzZ1yqh
ZWCgj75lafdXmrFUHdCVFQGgBzT8vJ6qxQYU4empJkzRdiVFEs5wGNq/nO3hzzSL
QV043ClCvzXYm5hivNdk8wd/ouRhhuU0aB6xCjl6KtFBnef7n3nJDqtuQUvsTpW6
vReqNBqAvdlUJvTnGuU1DjXLt5Z3XK4fRdRp6xNvCzESn2xpNVaoy760fdUYJOhI
RcHoMqjaybhUWKGF8vM+xzHl/r/PvCI4nOET8EDzoZ+INjMjN11vQrePgwEt3k8m
VgjY2mwbt9Teft4F+sFQHCAWQlxtSt2Te6mPJgnYWtQ0aME7thbcS/FVJCELOSyY
jzEBvPrsVnyuYv4ID5wb9iR66G+jpnLNcDTUSzv78DAvaBpCt7lgJpna1pTrWk9C
U1Syg9ezs2qXvoMUIvdTSMfwF6YuWhP+k131p+NsvKu3NJUhKnlAHCt/itPL4H9A
HVNxxbYPuEFfsnGSqQ0tN0GLBjk+Jme5sd3Sqk4c7H0iv71hjYw=
=5Aw0
-END PGP SIGNATURE-


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

Re: [pkg-go] Bug#888985: RFS: irtt/0.9-1 [ITP] (#888985)

2018-02-07 Thread Michael Stapelberg 
Sorry, only saw this email after my other reply. Somehow the threading
broke, it seems.

On Wed, Feb 7, 2018 at 12:20 PM, Pete Heist  wrote:

>
> > On Feb 7, 2018, at 12:01 PM, Clément Hermann  wrote:
> >
> > On 07/02/2018 11:39, Pete Heist wrote:
> >>
> >> Ah, ok. IRTT has an API, but it's not published yet. I think a
> >> binary-only package may be better at this point, and a separate source
> >> package later when that’s ready? If you agree, could you suggest a
> >> simple, current binary package hosted on github as a good example?
> >
> > You can have a single upstream package and produce 2 binary packages -
> > it's a bit more complicated though. Hence the example of Debian Code
> Search.
>
> Ok, I’m getting there, bear with me. :) In my case, would I not want to
> produce both a binary package and eventually a source package?
>

Be careful not to confuse the Debian concept of source packages (i.e. .dsc
files) and binary packages (i.e. .deb files) with a Debian binary package
containing binary files (e.g. a .deb with files in /usr/bin) and a Debian
binary package containing Go source code (e.g. a .deb with files in
/usr/share/gocode).

You always operate on 1 Debian source package (in your case, named irtt)
generating at least 1 Debian binary package (in your case, also named
irtt). We discussed generating 2 Debian binary packages (irtt and
golang-github-peteheist-irtt-dev).


>
> > Usually you would host the packaging on Alioth (soon salsa.debian.org),
> > and leave the upstream on github. Debian Code Search is a bit different
> > since it's specific to Debian. That doesn't change the usefulness of the
> > example for binary/api separation though.
> >
> > Regarding the workflow, the easiest is to tag your releases on github
> > (you probably already do it anyway) and merge the upstream remote in the
> > upstream branch on alioth/salsa every time you want to release (the tag
> > isn't mandatory, it's just easier, and allows for a debian/watch file).
>
> Got it...
>
> > You're expected to run unstable (Sid) for packaging work. At least in a
> > virtual machine.
> >
> > By the way, it's also a good practice to actually build the package in a
> > chroot (using git-buildpackage pbuilder options for instance), to avoid
> > build-depends issues.
>
> That explains a lot. I’ve got my work cut out for me on this part.
>
> Thank you kindly…
>
>
> ___
> 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

Re: [pkg-go] RFS: irtt/0.9-1 [ITP] (#888985)

2018-02-07 Thread Michael Stapelberg 
On Wed, Feb 7, 2018 at 12:01 PM, Clément Hermann  wrote:

> On 07/02/2018 11:39, Pete Heist wrote:
> >
> > Ah, ok. IRTT has an API, but it's not published yet. I think a
> > binary-only package may be better at this point, and a separate source
> > package later when that’s ready? If you agree, could you suggest a
> > simple, current binary package hosted on github as a good example?
>
> You can have a single upstream package and produce 2 binary packages -
> it's a bit more complicated though. Hence the example of Debian Code
> Search.
>

Given the early stage of the API, I would agree that a binary-only package
is a good choice for now. Just modify debian/rules to delete the source
after installation and you should be good.


>
>
> > Debian Code Search? Though its compat version is 8. I just liked how the
> > debian directory is hosted right in the github repo, which brings me to
> > another question...
> >
> > Is it possible to maintain everything on github, or does it need to be
> > on alioth, and if so, what is a good workflow for when I want to pull in
> > changes from upstream for a new release?
>
> Usually you would host the packaging on Alioth (soon salsa.debian.org),
> and leave the upstream on github. Debian Code Search is a bit different
> since it's specific to Debian. That doesn't change the usefulness of the
> example for binary/api separation though.
>

Yeah, I agree: keeping debian/ in the upstream repo is usually not the best
solution: we really like to have our packages team-maintained, i.e. hosted
on our infrastructure alongside all of our other packages, with the same
workflows, etc.


>
> Regarding the workflow, the easiest is to tag your releases on github
> (you probably already do it anyway) and merge the upstream remote in the
> upstream branch on alioth/salsa every time you want to release (the tag
> isn't mandatory, it's just easier, and allows for a debian/watch file).
>
> [snip]
>
> >
> > Hrm, any idea why I'm seeing large differences in lintian output? I
> > didn’t see any warnings before I posted, but I do see new ones after the
> > .lintianrc changes, just they look completely different...
> >
> > $ cat /etc/debian_version
> > 9.3
> > $ lintian --version
> > Lintian v2.5.50.4
> > $ cat .lintianrc
> > display-info = yes
> > display-experimental = yes
> > pedantic = yes
> > show-overrides = no
> > color = auto
> > $ lintian ~/src/github.com/peteheist/irtt/dpkg/irtt_0.9-1_amd64.changes
> > 
> > P: irtt source: debian-watch-may-check-gpg-signature
> > I: irtt: hardening-no-fortify-functions usr/bin/irtt
> > I: irtt: spelling-error-in-binary usr/bin/irtt writeN written
> > I: irtt: spelling-error-in-binary usr/bin/irtt ot to
> > I: irtt: hardening-no-bindnow usr/bin/irtt
> > I: irtt: hardening-no-pie usr/bin/irtt
> > P: irtt: no-upstream-changelog
> >
> > Also, some of the warnings (like compat-version) just come from output
> > from dh-make-golang, which I just installed with ‘apt-get install
> > dh-make-golang’. Do I need a newer version?
>
> You're expected to run unstable (Sid) for packaging work. At least in a
> virtual machine.
>
> By the way, it's also a good practice to actually build the package in a
> chroot (using git-buildpackage pbuilder options for instance), to avoid
> build-depends issues.
>
>
> Cheers,
>
> --
> nodens
>
> ___
> 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

[pkg-go] Processing of golang-github-eknkc-amber_0.0~git20171010.cdade1c-1_source.changes

2018-02-07 Thread Debian FTP Masters 
golang-github-eknkc-amber_0.0~git20171010.cdade1c-1_source.changes uploaded 
successfully to localhost
along with the files:
  golang-github-eknkc-amber_0.0~git20171010.cdade1c-1.dsc
  golang-github-eknkc-amber_0.0~git20171010.cdade1c.orig.tar.xz
  golang-github-eknkc-amber_0.0~git20171010.cdade1c-1.debian.tar.xz
  golang-github-eknkc-amber_0.0~git20171010.cdade1c-1_amd64.buildinfo

Greetings,

Your Debian queue daemon (running on host usper.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] Processing of golang-github-chaseadamsio-goorgeous_2.0.0+git20171126.dcf1ef8-1_source.changes

2018-02-07 Thread Debian FTP Masters 
golang-github-chaseadamsio-goorgeous_2.0.0+git20171126.dcf1ef8-1_source.changes 
uploaded successfully to localhost
along with the files:
  golang-github-chaseadamsio-goorgeous_2.0.0+git20171126.dcf1ef8-1.dsc
  golang-github-chaseadamsio-goorgeous_2.0.0+git20171126.dcf1ef8.orig.tar.xz
  golang-github-chaseadamsio-goorgeous_2.0.0+git20171126.dcf1ef8-1.debian.tar.xz
  
golang-github-chaseadamsio-goorgeous_2.0.0+git20171126.dcf1ef8-1_amd64.buildinfo

Greetings,

Your Debian queue daemon (running on host usper.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] Processed: Merge duplicates

2018-02-07 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> reassign 889819 src:golang-gopkg-mgo.v2
Bug #889819 [src:prometheus-mongodb-exporter] prometheus-mongodb-exporter FTBFS 
on 32bit: constant 9007199254740992 overflows int
Bug reassigned from package 'src:prometheus-mongodb-exporter' to 
'src:golang-gopkg-mgo.v2'.
No longer marked as found in versions prometheus-mongodb-exporter/1.0.0-1.
Ignoring request to alter fixed versions of bug #889819 to the same values 
previously set
> forcemerge 886432 889819
Bug #886432 [src:golang-gopkg-mgo.v2] snapd FTBFS on 32bit: json.go:320:7: 
constant 9007199254740992 overflows int
Bug #889818 [src:golang-gopkg-mgo.v2] prometheus-mongodb-exporter: FTBFS on 
32-bit architectures - constant 9007199254740992 overflows int
Bug #889819 [src:golang-gopkg-mgo.v2] prometheus-mongodb-exporter FTBFS on 
32bit: constant 9007199254740992 overflows int
Added indication that 889819 affects src:snapd,src:prometheus-mongodb-exporter
Marked as fixed in versions golang-gopkg-mgo.v2/2016.08.01-2.
Marked as found in versions golang-gopkg-mgo.v2/2016.08.01-3 and 
golang-gopkg-mgo.v2/2016.08.01-1.
Bug #889818 [src:golang-gopkg-mgo.v2] prometheus-mongodb-exporter: FTBFS on 
32-bit architectures - constant 9007199254740992 overflows int
Removed indication that 889818 affects src:prometheus-mongodb-exporter and 
src:snapd
Added indication that 889818 affects src:snapd,src:prometheus-mongodb-exporter
Removed indication that 886432 affects src:prometheus-mongodb-exporter and 
src:snapd
Added indication that 886432 affects src:snapd,src:prometheus-mongodb-exporter
Merged 886432 889818 889819
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
886432: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886432
889818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889818
889819: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889819
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#889819: prometheus-mongodb-exporter FTBFS on 32bit: constant 9007199254740992 overflows int

2018-02-07 Thread Adrian Bunk 
Source: prometheus-mongodb-exporter
Version: 1.0.0-1
Severity: serious
Tags: buster sid

Some recent change in unstable makes prometheus-mongodb-exporter FTBFS on 32bit:

https://tests.reproducible-builds.org/debian/history/prometheus-mongodb-exporter.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/i386/prometheus-mongodb-exporter.html
https://buildd.debian.org/status/package.php?p=prometheus-mongodb-exporter=sid

...
   dh_auto_build -a -O--buildsystem=golang -O--builddir=build
cd build && go install 
-gcflags=\"-trimpath=/<>/build/src\" 
-asmflags=\"-trimpath=/<>/build/src\" -v -p 1 
github.com/dcu/mongodb_exporter github.com/dcu/mongodb_exporter/collector 
github.com/dcu/mongodb_exporter/shared
github.com/golang/glog
gopkg.in/mgo.v2/internal/json
gopkg.in/mgo.v2/bson
# gopkg.in/mgo.v2/bson
src/gopkg.in/mgo.v2/bson/json.go:320:7: constant 9007199254740992 overflows int
gopkg.in/mgo.v2/internal/scram
github.com/beorn7/perks/quantile
github.com/golang/protobuf/proto
github.com/prometheus/client_model/go
github.com/matttproud/golang_protobuf_extensions/pbutil
github.com/prometheus/common/internal/bitbucket.org/ww/goautoneg
github.com/prometheus/common/model
github.com/prometheus/common/expfmt
github.com/prometheus/procfs/xfs
github.com/prometheus/procfs
github.com/prometheus/client_golang/prometheus
dh_auto_build: cd build && go install 
-gcflags=\"-trimpath=/<>/build/src\" 
-asmflags=\"-trimpath=/<>/build/src\" -v -p 1 
github.com/dcu/mongodb_exporter github.com/dcu/mongodb_exporter/collector 
github.com/dcu/mongodb_exporter/shared returned exit code 2
debian/rules:14: recipe for target 'build-arch' failed
make: *** [build-arch] Error 2

___
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: add affects to #886432

2018-02-07 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> affects 886432 src:snapd src:prometheus-mongodb-exporter
Bug #886432 [src:golang-gopkg-mgo.v2] snapd FTBFS on 32bit: json.go:320:7: 
constant 9007199254740992 overflows int
Bug #889818 [src:golang-gopkg-mgo.v2] prometheus-mongodb-exporter: FTBFS on 
32-bit architectures - constant 9007199254740992 overflows int
Added indication that 886432 affects src:snapd and 
src:prometheus-mongodb-exporter
Added indication that 889818 affects src:snapd and 
src:prometheus-mongodb-exporter
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
886432: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886432
889818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889818
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#889818: prometheus-mongodb-exporter: FTBFS on 32-bit architectures - constant 9007199254740992 overflows int

2018-02-07 Thread James Cowgill 
Control: unarchive 886432
Control: reassign -1 src:golang-gopkg-mgo.v2
Control: forcemerge 886432 -1
Control: found 886432 2016.08.01-3

Hi,

On 07/02/18 11:54, James Cowgill wrote:
> Source: prometheus-mongodb-exporter
> Version: 1.0.0-1
> Severity: serious
> Tags: sid buster
> 
> Hi,
> 
> prometheus-mongodb-exporter FTBFS on mips in a recent rebuild, but since
> I can reproduce this failure on i386 as well, presumably it fails on all
> 32-bit architectures.
> 
> The error is:
>> github.com/golang/glog
>> gopkg.in/mgo.v2/internal/json
>> gopkg.in/mgo.v2/bson
>> # gopkg.in/mgo.v2/bson
>> src/gopkg.in/mgo.v2/bson/json.go:320:7: constant 9007199254740992 overflows 
>> int

This is a recurrence of #886432

It looks to me like the patch to fix this was not added to git so the
next upload removed the patch.

Also the Vcs-* URLs are currently dead. I had to go on a hunt for where
the packaging repo was stored for this package.

Thanks,
James



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

[pkg-go] Processed: Bug#889818: prometheus-mongodb-exporter: FTBFS on 32-bit architectures - constant 9007199254740992 overflows int

2018-02-07 Thread Debian Bug Tracking System 
Processing control commands:

> unarchive 886432
Bug #886432 {Done: Michael Hudson-Doyle } 
[src:golang-gopkg-mgo.v2] snapd FTBFS on 32bit: json.go:320:7: constant 
9007199254740992 overflows int
Unarchived Bug 886432
> reassign -1 src:golang-gopkg-mgo.v2
Bug #889818 [src:prometheus-mongodb-exporter] prometheus-mongodb-exporter: 
FTBFS on 32-bit architectures - constant 9007199254740992 overflows int
Bug reassigned from package 'src:prometheus-mongodb-exporter' to 
'src:golang-gopkg-mgo.v2'.
No longer marked as found in versions prometheus-mongodb-exporter/1.0.0-1.
Ignoring request to alter fixed versions of bug #889818 to the same values 
previously set
> forcemerge 886432 -1
Bug #886432 {Done: Michael Hudson-Doyle } 
[src:golang-gopkg-mgo.v2] snapd FTBFS on 32bit: json.go:320:7: constant 
9007199254740992 overflows int
Bug #889818 [src:golang-gopkg-mgo.v2] prometheus-mongodb-exporter: FTBFS on 
32-bit architectures - constant 9007199254740992 overflows int
Marked Bug as done
Marked as fixed in versions golang-gopkg-mgo.v2/2016.08.01-2.
Marked as found in versions golang-gopkg-mgo.v2/2016.08.01-1.
Bug #886432 {Done: Michael Hudson-Doyle } 
[src:golang-gopkg-mgo.v2] snapd FTBFS on 32bit: json.go:320:7: constant 
9007199254740992 overflows int
Added tag(s) sid and buster.
Merged 886432 889818
> found 886432 2016.08.01-3
Bug #886432 {Done: Michael Hudson-Doyle } 
[src:golang-gopkg-mgo.v2] snapd FTBFS on 32bit: json.go:320:7: constant 
9007199254740992 overflows int
Bug #889818 {Done: Michael Hudson-Doyle } 
[src:golang-gopkg-mgo.v2] prometheus-mongodb-exporter: FTBFS on 32-bit 
architectures - constant 9007199254740992 overflows int
Marked as found in versions golang-gopkg-mgo.v2/2016.08.01-3 and reopened.
Marked as found in versions golang-gopkg-mgo.v2/2016.08.01-3 and reopened.

-- 
886432: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886432
889818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889818
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#889818: prometheus-mongodb-exporter: FTBFS on 32-bit architectures - constant 9007199254740992 overflows int

2018-02-07 Thread James Cowgill 
Source: prometheus-mongodb-exporter
Version: 1.0.0-1
Severity: serious
Tags: sid buster

Hi,

prometheus-mongodb-exporter FTBFS on mips in a recent rebuild, but since
I can reproduce this failure on i386 as well, presumably it fails on all
32-bit architectures.

The error is:
> github.com/golang/glog
> gopkg.in/mgo.v2/internal/json
> gopkg.in/mgo.v2/bson
> # gopkg.in/mgo.v2/bson
> src/gopkg.in/mgo.v2/bson/json.go:320:7: constant 9007199254740992 overflows 
> int
> gopkg.in/mgo.v2/internal/scram
> github.com/beorn7/perks/quantile
> github.com/golang/protobuf/proto
> github.com/prometheus/client_model/go
> github.com/matttproud/golang_protobuf_extensions/pbutil
> github.com/prometheus/common/internal/bitbucket.org/ww/goautoneg
> github.com/prometheus/common/model
> github.com/prometheus/common/expfmt
> github.com/prometheus/procfs/xfs
> github.com/prometheus/procfs
> github.com/prometheus/client_golang/prometheus
> dh_auto_build: cd build && go install 
> -gcflags=\"-trimpath=/<>/build/src\" 
> -asmflags=\"-trimpath=/<>/build/src\" -v -p 1 
> github.com/dcu/mongodb_exporter github.com/dcu/mongodb_exporter/collector 
> github.com/dcu/mongodb_exporter/shared returned exit code 2

Thanks,
James



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

Re: [pkg-go] Bug#888985: RFS: irtt/0.9-1 [ITP] (#888985)

2018-02-07 Thread Pete Heist 

> On Feb 7, 2018, at 12:01 PM, Clément Hermann  wrote:
> 
> On 07/02/2018 11:39, Pete Heist wrote:
>> 
>> Ah, ok. IRTT has an API, but it's not published yet. I think a
>> binary-only package may be better at this point, and a separate source
>> package later when that’s ready? If you agree, could you suggest a
>> simple, current binary package hosted on github as a good example?
> 
> You can have a single upstream package and produce 2 binary packages -
> it's a bit more complicated though. Hence the example of Debian Code Search.

Ok, I’m getting there, bear with me. :) In my case, would I not want to produce 
both a binary package and eventually a source package?

> Usually you would host the packaging on Alioth (soon salsa.debian.org),
> and leave the upstream on github. Debian Code Search is a bit different
> since it's specific to Debian. That doesn't change the usefulness of the
> example for binary/api separation though.
> 
> Regarding the workflow, the easiest is to tag your releases on github
> (you probably already do it anyway) and merge the upstream remote in the
> upstream branch on alioth/salsa every time you want to release (the tag
> isn't mandatory, it's just easier, and allows for a debian/watch file).

Got it...

> You're expected to run unstable (Sid) for packaging work. At least in a
> virtual machine.
> 
> By the way, it's also a good practice to actually build the package in a
> chroot (using git-buildpackage pbuilder options for instance), to avoid
> build-depends issues.

That explains a lot. I’ve got my work cut out for me on this part.

Thank you kindly…


___
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: irtt/0.9-1 [ITP] (#888985)

2018-02-07 Thread Clément Hermann 
On 07/02/2018 11:39, Pete Heist wrote:
> 
> Ah, ok. IRTT has an API, but it's not published yet. I think a
> binary-only package may be better at this point, and a separate source
> package later when that’s ready? If you agree, could you suggest a
> simple, current binary package hosted on github as a good example?

You can have a single upstream package and produce 2 binary packages -
it's a bit more complicated though. Hence the example of Debian Code Search.


> Debian Code Search? Though its compat version is 8. I just liked how the
> debian directory is hosted right in the github repo, which brings me to
> another question...
> 
> Is it possible to maintain everything on github, or does it need to be
> on alioth, and if so, what is a good workflow for when I want to pull in
> changes from upstream for a new release?

Usually you would host the packaging on Alioth (soon salsa.debian.org),
and leave the upstream on github. Debian Code Search is a bit different
since it's specific to Debian. That doesn't change the usefulness of the
example for binary/api separation though.

Regarding the workflow, the easiest is to tag your releases on github
(you probably already do it anyway) and merge the upstream remote in the
upstream branch on alioth/salsa every time you want to release (the tag
isn't mandatory, it's just easier, and allows for a debian/watch file).

[snip]

> 
> Hrm, any idea why I'm seeing large differences in lintian output? I
> didn’t see any warnings before I posted, but I do see new ones after the
> .lintianrc changes, just they look completely different...
> 
> $ cat /etc/debian_version 
> 9.3
> $ lintian --version
> Lintian v2.5.50.4
> $ cat .lintianrc 
> display-info = yes
> display-experimental = yes
> pedantic = yes
> show-overrides = no
> color = auto
> $ lintian ~/src/github.com/peteheist/irtt/dpkg/irtt_0.9-1_amd64.changes
> 
> P: irtt source: debian-watch-may-check-gpg-signature
> I: irtt: hardening-no-fortify-functions usr/bin/irtt
> I: irtt: spelling-error-in-binary usr/bin/irtt writeN written
> I: irtt: spelling-error-in-binary usr/bin/irtt ot to
> I: irtt: hardening-no-bindnow usr/bin/irtt
> I: irtt: hardening-no-pie usr/bin/irtt
> P: irtt: no-upstream-changelog
> 
> Also, some of the warnings (like compat-version) just come from output
> from dh-make-golang, which I just installed with ‘apt-get install
> dh-make-golang’. Do I need a newer version?

You're expected to run unstable (Sid) for packaging work. At least in a
virtual machine.

By the way, it's also a good practice to actually build the package in a
chroot (using git-buildpackage pbuilder options for instance), to avoid
build-depends issues.


Cheers,

-- 
nodens

___
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: irtt/0.9-1 [ITP] (#888985)

2018-02-07 Thread Pete Heist 

> On Feb 7, 2018, at 10:03 AM, Michael Stapelberg  wrote:
> 
> Thanks for contributing this package.

Not at all, thank you kindly for patience with my complete newness to this!

> The resulting binary package irtt_0.9-1_amd64.deb contains both a binary and 
> Go source code. This is a bit unusual: in Debian, we only package Go source 
> code to build other Go programs (not for developers). Hence, we usually 
> provide either a binary package with programs or an arch:all package with Go 
> source. It’s fine to have a source package which provides both, but please 
> separate the source from the binaries. Have a look at 
> https://anonscm.debian.org/cgit/collab-maint/codesearch.git/ 
>  for an example 
> of this pattern.

Ah, ok. IRTT has an API, but it's not published yet. I think a binary-only 
package may be better at this point, and a separate source package later when 
that’s ready? If you agree, could you suggest a simple, current binary package 
hosted on github as a good example? Debian Code Search? Though its compat 
version is 8. I just liked how the debian directory is hosted right in the 
github repo, which brings me to another question...

Is it possible to maintain everything on github, or does it need to be on 
alioth, and if so, what is a good workflow for when I want to pull in changes 
from upstream for a new release?

> Further, please address the following lintian warnings:
> 
> P: irtt source: package-uses-old-debhelper-compat-version 10
> P: irtt source: insecure-copyright-format-uri 
> http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ 
> 
> I: irtt source: out-of-date-standards-version 3.9.8 (released 2016-04-06) 
> (current is 4.1.3)
> I: irtt source: testsuite-autopkgtest-missing
> W: irtt: priority-extra-is-replaced-by-priority-optional
> 
> You can run lintian like so:
> % cat >> ~/.lintianrc <<'EOT'
> display-info = yes
> display-experimental = yes
> pedantic = yes
> show-overrides = no
> color = auto
> EOT
> % lintian irtt_0.9-1_amd64.changes

Hrm, any idea why I'm seeing large differences in lintian output? I didn’t see 
any warnings before I posted, but I do see new ones after the .lintianrc 
changes, just they look completely different...

$ cat /etc/debian_version 
9.3
$ lintian --version
Lintian v2.5.50.4
$ cat .lintianrc 
display-info = yes
display-experimental = yes
pedantic = yes
show-overrides = no
color = auto
$ lintian ~/src/github.com/peteheist/irtt/dpkg/irtt_0.9-1_amd64.changes
P: irtt source: debian-watch-may-check-gpg-signature
I: irtt: hardening-no-fortify-functions usr/bin/irtt
I: irtt: spelling-error-in-binary usr/bin/irtt writeN written
I: irtt: spelling-error-in-binary usr/bin/irtt ot to
I: irtt: hardening-no-bindnow usr/bin/irtt
I: irtt: hardening-no-pie usr/bin/irtt
P: irtt: no-upstream-changelog

Also, some of the warnings (like compat-version) just come from output from 
dh-make-golang, which I just installed with ‘apt-get install dh-make-golang’. 
Do I need a newer version?

> Let me know once this is done and I’ll be happy to take another look.
> 
> BTW, you don’t need to upload the package to mentors. I always work with the 
> git repository directly.

Ok, that makes sense to me also- received that tip from a different Debian 
package admin. Thanks! :)

___
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: irtt/0.9-1 [ITP] (#888985)

2018-02-07 Thread Michael Stapelberg 
Thanks for contributing this package.

The resulting binary package irtt_0.9-1_amd64.deb contains both a binary
and Go source code. This is a bit unusual: in Debian, we only package Go
source code to build other Go programs (not for developers). Hence, we
usually provide either a binary package with programs or an arch:all
package with Go source. It’s fine to have a source package which provides
both, but please separate the source from the binaries. Have a look at
https://anonscm.debian.org/cgit/collab-maint/codesearch.git/ for an example
of this pattern.

Further, please address the following lintian warnings:

P: irtt source: package-uses-old-debhelper-compat-version 10
P: irtt source: insecure-copyright-format-uri
http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
I: irtt source: out-of-date-standards-version 3.9.8 (released 2016-04-06)
(current is 4.1.3)
I: irtt source: testsuite-autopkgtest-missing
W: irtt: priority-extra-is-replaced-by-priority-optional

You can run lintian like so:
% cat >> ~/.lintianrc <<'EOT'
display-info = yes
display-experimental = yes
pedantic = yes
show-overrides = no
color = auto
EOT
% lintian irtt_0.9-1_amd64.changes

Let me know once this is done and I’ll be happy to take another look.

BTW, you don’t need to upload the package to mentors. I always work with
the git repository directly.

Thanks!

On Tue, Feb 6, 2018 at 8:26 PM, Pete Heist  wrote:

> Package: sponsorship-requests
> Severity: wishlist
>
> Dear mentors,
>
> I am looking for a sponsor for my package "irtt"
>
>  Package name: irtt
>  Version : 0.9-1
>  Upstream Author : Pete Heist 
>  URL : https://github.com/peteheist/irtt
>  License : GPL-3
>  Section : devel
>
> It builds those binary packages:
>
>   irtt  - Isochronous Round-Trip Tester
>
> To access further information about this package, please visit the
> following URL:
>
>   https://mentors.debian.net/package/irtt
>
> Alternatively, one can download the package with dget using this command:
>
>   dget -x https://mentors.debian.net/debian/pool/main/i/irtt/irtt_
> 0.9-1.dsc
>
> More information about irtt can be obtained from https://github.com/
> peteheist/irtt.
>
> The flent package (https://packages.debian.org/source/sid/flent) from
> pkg-netmeasure will use irtt as a dependency.
>
> Changes since the last upload: none
>
> Regards,
> Pete Heist
>
> ___
> 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