[pkg-go] Bug#921351: Bug#921351: prometheus-postfix-exporter: Init script missing

2019-02-06 Thread Michael Stapelberg 
On Thu, Feb 7, 2019 at 8:46 AM Scott Kitterman  wrote:

> No.  It's an actual policy violation, so the bug is correct.  I'd leave it
> as is and ask the release team to mark it buster-ignore.
>

Could you kindly point me to where the process is described for this? I’m
not sure what I’d need to do to get it marked buster-ignore. Thanks.


>
> Scott K
>
> On February 7, 2019 7:29:01 AM UTC, Michael Stapelberg <
> stapelb...@debian.org> wrote:
> >On Wed, Feb 6, 2019 at 11:01 PM Scott Kitterman 
> >wrote:
> >
> >> It's not the FTP Team's job to fix policy compliance issues in
> >packages.
> >> If you have a problem with that being a policy must, then you should
> >take
> >> it up with the policy team.
> >>
> >
> >Yeah, I’ll post to #911165
> >
> >
> >>
> >> I completely understand the frustration, but in my own packages I
> >take the
> >> time to do it because Debian policy says it's required, not because I
> >> particularly care about sysvinit.
> >>
> >
> >I don’t think fulfilling the policy for fulfilling the policy’s sake is
> >a
> >good use of anyone’s time.
> >
> >Can we close this bug until someone comes along who actually cares? :)
> >
> >
> >>
> >> Scott K
> >>
> >> On February 6, 2019 9:23:46 PM UTC, Michael Stapelberg <
> >> stapelb...@debian.org> wrote:
> >> >Can you provide a patch if you care about sysvinit please? The Go
> >> >packaging
> >> >team is pretty manpower-constrained and non-systemd is a niche case,
> >so
> >> >any
> >> >help is appreciated. Thanks!
> >> >
> >> >On Wed, Feb 6, 2019 at 7:49 PM Scott Kitterman
> >
> >> >wrote:
> >> >
> >> >> Package: prometheus-postfix-exporter
> >> >> Version: 0.1.2-1
> >> >> Severity: serious
> >> >> Justification: Policy 9.11
> >> >>
> >> >> Excerpt from policy 9.11:
> >> >>
> >> >> However, any package integrating with other init systems
> >> >> must also be backwards-compatible with sysvinit by providing a
> >SysV-
> >> >> style init script with the same name as and equivalent
> >functionality
> >> >> to any init-specific job, as this is the only start-up
> >configuration
> >> >> method guaranteed to be supported by all init implementations.
> >> >>
> >> >> The package violates a policy must by not providing s sysvint init
> >> >script.
> >> >>
> >> >> Scott K
> >> >>
> >> >> ___
> >> >> Pkg-go-maintainers mailing list
> >> >> Pkg-go-maintainers@alioth-lists.debian.net
> >> >>
> >> >
> >>
> >
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-go-maintainers
> >>
>


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

[pkg-go] Bug#921351: Bug#921351: prometheus-postfix-exporter: Init script missing

2019-02-06 Thread Michael Stapelberg 
On Wed, Feb 6, 2019 at 11:01 PM Scott Kitterman 
wrote:

> It's not the FTP Team's job to fix policy compliance issues in packages.
> If you have a problem with that being a policy must, then you should take
> it up with the policy team.
>

Yeah, I’ll post to #911165


>
> I completely understand the frustration, but in my own packages I take the
> time to do it because Debian policy says it's required, not because I
> particularly care about sysvinit.
>

I don’t think fulfilling the policy for fulfilling the policy’s sake is a
good use of anyone’s time.

Can we close this bug until someone comes along who actually cares? :)


>
> Scott K
>
> On February 6, 2019 9:23:46 PM UTC, Michael Stapelberg <
> stapelb...@debian.org> wrote:
> >Can you provide a patch if you care about sysvinit please? The Go
> >packaging
> >team is pretty manpower-constrained and non-systemd is a niche case, so
> >any
> >help is appreciated. Thanks!
> >
> >On Wed, Feb 6, 2019 at 7:49 PM Scott Kitterman 
> >wrote:
> >
> >> Package: prometheus-postfix-exporter
> >> Version: 0.1.2-1
> >> Severity: serious
> >> Justification: Policy 9.11
> >>
> >> Excerpt from policy 9.11:
> >>
> >> However, any package integrating with other init systems
> >> must also be backwards-compatible with sysvinit by providing a SysV-
> >> style init script with the same name as and equivalent functionality
> >> to any init-specific job, as this is the only start-up configuration
> >> method guaranteed to be supported by all init implementations.
> >>
> >> The package violates a policy must by not providing s sysvint init
> >script.
> >>
> >> Scott K
> >>
> >> ___
> >> Pkg-go-maintainers mailing list
> >> Pkg-go-maintainers@alioth-lists.debian.net
> >>
> >
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-go-maintainers
>


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

[pkg-go] Bug#921351: Bug#921351: prometheus-postfix-exporter: Init script missing

2019-02-06 Thread Michael Stapelberg 
Can you provide a patch if you care about sysvinit please? The Go packaging
team is pretty manpower-constrained and non-systemd is a niche case, so any
help is appreciated. Thanks!

On Wed, Feb 6, 2019 at 7:49 PM Scott Kitterman  wrote:

> Package: prometheus-postfix-exporter
> Version: 0.1.2-1
> Severity: serious
> Justification: Policy 9.11
>
> Excerpt from policy 9.11:
>
> However, any package integrating with other init systems
> must also be backwards-compatible with sysvinit by providing a SysV-
> style init script with the same name as and equivalent functionality
> to any init-specific job, as this is the only start-up configuration
> method guaranteed to be supported by all init implementations.
>
> The package violates a policy must by not providing s sysvint init script.
>
> Scott K
>
> ___
> Pkg-go-maintainers mailing list
> Pkg-go-maintainers@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-go-maintainers



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

Re: [pkg-go] rclone update

2018-10-01 Thread Michael Stapelberg 
rclone 1.41 is in Debian testing and unstable, so I assume you’re talking
about Debian stable.

We won’t update software in Debian stable except for security fixes.

If you’d like to use a newer version of rclone from Debian, you’ll need to
either upgrade or pin the rclone package from Debian testing.

On Mon, Oct 1, 2018 at 7:57 PM Thomas Coxe  wrote:

> Hello,
> I am wondering about the process of updating the software offered by your
> repository. I use rclone to update logfiles to a cloud server and the new
> version (1.43) works great, but the one in the apt repository (1.35) does
> not have the options that I need. Anyway I have the new new version up and
> running, I am just wondering about the process for adoption into your
> repository.
>
> Thanks,
> Tom
> ___
> Pkg-go-maintainers mailing list
> Pkg-go-maintainers@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-go-maintainers



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

[pkg-go] Bug#908082: Bug#908082: golang-github-juju-testing: Autobuilder hangs when building with eatmydata

2018-09-06 Thread Michael Stapelberg 
This is not a bug with this package, but with mongodb-server:

root@gce1535991:~# mongod --version
db version v3.4.15
git version: 52e5b5fbaa3a2a5b1a217f5e647b5061817475f9
OpenSSL version: OpenSSL 1.1.0f  25 May 2017
allocator: tcmalloc
modules: none
build environment:
distarch: x86_64
target_arch: x86_64
root@gce1535991:~# eatmydata mongod --version
^C

This package uses mongodb in its tests, hence the hang.

I’ll leave it up to you to merge and reassign accordingly.

On Thu, Sep 6, 2018 at 1:05 AM, Santiago Vila  wrote:

> Package: src:golang-github-juju-testing
> Version: 0.0~git20170608.2fe0e88-3
> Severity: wishlist
>
> Dear maintainer:
>
> When I build this package using sbuild + eatmydata this is what happens:
>
> 
> 
> [...]
>  debian/rules build-indep
> dh build-indep --buildsystem=golang --with=golang
>dh_update_autotools_config -i -O--buildsystem=golang
>dh_autoreconf -i -O--buildsystem=golang
>dh_auto_configure -i -O--buildsystem=golang
>dh_auto_build -i -O--buildsystem=golang
> cd obj-x86_64-linux-gnu && go install -gcflags=\"-trimpath=/<<
> BUILDDIR>>/golang-github-juju-testing-0.0\~git20170608.
> 2fe0e88/obj-x86_64-linux-gnu/src\" -asmflags=\"-trimpath=/<<
> BUILDDIR>>/golang-github-juju-testing-0.0\~git20170608.
> 2fe0e88/obj-x86_64-linux-gnu/src\" -v -p 1 github.com/juju/testing
> github.com/juju/testing/checkers github.com/juju/testing/filetesting
> github.com/juju/testing/httptesting
> github.com/juju/errors
> github.com/juju/loggo
> github.com/juju/retry
> gopkg.in/check.v1
> gopkg.in/mgo.v2/internal/json
> gopkg.in/mgo.v2/bson
> gopkg.in/yaml.v2
> github.com/juju/testing/checkers
> github.com/juju/utils/clock
> golang.org/x/crypto/pbkdf2
> golang.org/x/net/context
> github.com/juju/utils
> github.com/juju/version
> gopkg.in/mgo.v2/internal/scram
> gopkg.in/mgo.v2
> github.com/juju/testing
> github.com/juju/testing/filetesting
> github.com/juju/testing/httptesting
>dh_auto_test -i -O--buildsystem=golang
> cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1
> github.com/juju/testing github.com/juju/testing/checkers
> github.com/juju/testing/filetesting github.com/juju/testing/httptesting
> === RUN   Test
> SIGQUIT: quit
> PC=0x472298 m=0 sigcode=0
>
> goroutine 6 [syscall]:
> syscall.Syscall6(0xf7, 0x1, 0x7d43, 0xc420069600, 0x104, 0x0, 0x0,
> 0x0, 0xbafe20, 0x0)
> /usr/lib/go-1.10/src/syscall/asm_linux_amd64.s:44 +0x5
> fp=0xc4200695a8 sp=0xc4200695a0 pc=0x472275
> os.(*Process).blockUntilWaitable(0xc420026780, 0x0, 0x0, 0x2)
> /usr/lib/go-1.10/src/os/wait_waitid.go:31 +0x98 fp=0xc4200696a8
> sp=0xc4200695a8 pc=0x493668
> os.(*Process).wait(0xc420026780, 0xc4200feb60, 0xc4200ce4f8, 0xc4200ce4f8)
> /usr/lib/go-1.10/src/os/exec_unix.go:22 +0x3c fp=0xc420069720
> sp=0xc4200696a8 pc=0x48d5ac
> os.(*Process).Wait(0xc420026780, 0x936048, 0x936050, 0x936040)
> /usr/lib/go-1.10/src/os/exec.go:123 +0x2b fp=0xc420069750
> sp=0xc420069720 pc=0x48cb5b
> os/exec.(*Cmd).Wait(0xc4200ce420, 0x0, 0x0)
> /usr/lib/go-1.10/src/os/exec/exec.go:461 +0x5c fp=0xc4200697c8
> sp=0xc420069750 pc=0x53cc8c
> os/exec.(*Cmd).Run(0xc4200ce420, 0xc420088910, 0x1)
> /usr/lib/go-1.10/src/os/exec/exec.go:305 +0x5c fp=0xc4200697f0
> sp=0xc4200697c8 pc=0x53c16c
> os/exec.(*Cmd).Output(0xc4200ce420, 0xf, 0xc4200578b8, 0x1, 0x1,
> 0xc4200ce420)
> /usr/lib/go-1.10/src/os/exec/exec.go:500 +0xf5 fp=0xc420069840
> sp=0xc4200697f0 pc=0x53d085
> github.com/juju/testing.detectMongoVersion(0xc420154b40, 0xf, 0x0, 0x0,
> 0x0, 0x0, 0x0, 0x0, 0xc420057cb0, 0xe0)
> /<>/obj-x86_64-linux-gnu/src/github.com/juju/
> testing/mgo.go:396 +0xb0 fp=0xc4200699b8 sp=0xc420069840 pc=0x7f0e90
> github.com/juju/testing.(*mongodCache).Get(0xbaf180, 0x0, 0x0, 0x0, 0x0,
> 0x0, 0x0, 0x0, 0x0, 0x0, ...)
> /<>/obj-x86_64-linux-gnu/src/github.com/juju/
> testing/mgo.go:359 +0x170 fp=0xc420069a58 sp=0xc4200699b8 pc=0x7f0830
> github.com/juju/testing.(*MgoInstance).run(0xbaf300, 0xc, 0xc420057e78)
> /<>/obj-x86_64-linux-gnu/src/github.com/juju/
> testing/mgo.go:260 +0x1a8 fp=0xc420069da0 sp=0xc420069a58 pc=0x7ef848
> github.com/juju/testing.(*MgoInstance).Start(0xbaf300, 0x0, 0x17f7a0e4,
> 0x17f7a0e400a2d078)
> /<>/obj-x86_64-linux-gnu/src/github.com/juju/
> testing/mgo.go:206 +0x38f fp=0xc420069f48 sp=0xc420069da0 pc=0x7ef1bf
> github.com/juju/testing.MgoTestPackage(0xc4201660f0, 0x0)
> /<>/obj-x86_64-linux-gnu/src/github.com/juju/
> testing/mgo.go:455 +0x3b fp=0xc420069f88 sp=0xc420069f48 pc=0x7f186b
> github.com/juju/testing_test.Test(0xc4201660f0)
> /<>/obj-x86_64-linux-gnu/src/github.com/juju/
> testing/package_test.go:13 +0x34 fp=0xc420069fa8 sp=0xc420069f88
> pc=0x805d34
> testing.tRunner(0xc4201660f0, 0x935870)
> /usr/lib/go-1.10/src/testing/testing.go:777 +0xd0 fp=0xc420069fd0
> sp=0xc420069fa8 pc=0x4ed330
>

[pkg-go] Bug#908083: Bug#908083: golang-gopkg-macaroon-bakery.v2: Autobuilder hangs when building with eatmydata

2018-09-06 Thread Michael Stapelberg 
This is not a bug with this package, but with mongodb-server:

root@gce1535991:~# mongod --version
db version v3.4.15
git version: 52e5b5fbaa3a2a5b1a217f5e647b5061817475f9
OpenSSL version: OpenSSL 1.1.0f  25 May 2017
allocator: tcmalloc
modules: none
build environment:
distarch: x86_64
target_arch: x86_64
root@gce1535991:~# eatmydata mongod --version
^C

This package uses mongodb in its tests, hence the hang.

I’ll leave it up to you to merge and reassign accordingly.


On Thu, Sep 6, 2018 at 1:05 AM, Santiago Vila  wrote:

> Package: src:golang-gopkg-macaroon-bakery.v2
> Version: 0.0~git20171221.21d9e9a-5
> Severity: wishlist
>
> Dear maintainer:
>
> When I build this package using sbuild + eatmydata this is what happens:
>
> 
> 
> [...]
>  debian/rules build-indep
> dh build-indep --buildsystem=golang --with=golang
>dh_update_autotools_config -i -O--buildsystem=golang
>dh_autoreconf -i -O--buildsystem=golang
>dh_auto_configure -i -O--buildsystem=golang
>dh_auto_build -i -O--buildsystem=golang
> cd obj-x86_64-linux-gnu && go install -gcflags=\"-trimpath=/<<
> BUILDDIR>>/golang-gopkg-macaroon-bakery.v2-0.0\~
> git20171221.21d9e9a/obj-x86_64-linux-gnu/src\" -asmflags=\"-trimpath=/<<
> BUILDDIR>>/golang-gopkg-macaroon-bakery.v2-0.0\~
> git20171221.21d9e9a/obj-x86_64-linux-gnu/src\" -v -p 1
> gopkg.in/macaroon-bakery.v2/bakery gopkg.in/macaroon-bakery.v2/
> bakery/checkers gopkg.in/macaroon-bakery.v2/bakery/identchecker
> gopkg.in/macaroon-bakery.v2/bakery/internal/macaroonpb
> gopkg.in/macaroon-bakery.v2/bakery/mgorootkeystore
> gopkg.in/macaroon-bakery.v2/bakerytest gopkg.in/macaroon-bakery.v2/
> httpbakery gopkg.in/macaroon-bakery.v2/httpbakery/agent
> gopkg.in/macaroon-bakery.v2/httpbakery/form gopkg.in/macaroon-bakery.v2/
> internal/httputil
> github.com/juju/loggo
> github.com/rogpeppe/fastuuid
> golang.org/x/crypto/curve25519
> golang.org/x/crypto/internal/subtle
> golang.org/x/crypto/poly1305
> golang.org/x/crypto/salsa20/salsa
> golang.org/x/crypto/nacl/secretbox
> golang.org/x/crypto/nacl/box
> golang.org/x/net/context
> gopkg.in/errgo.v1
> gopkg.in/macaroon.v2
> gopkg.in/macaroon-bakery.v2/bakery/checkers
> github.com/golang/protobuf/proto
> gopkg.in/macaroon-bakery.v2/bakery/internal/macaroonpb
> gopkg.in/macaroon-bakery.v2/bakery
> gopkg.in/macaroon-bakery.v2/bakery/identchecker
> gopkg.in/mgo.v2/internal/json
> gopkg.in/mgo.v2/bson
> gopkg.in/mgo.v2/internal/scram
> gopkg.in/mgo.v2
> gopkg.in/macaroon-bakery.v2/bakery/mgorootkeystore
> github.com/julienschmidt/httprouter
> golang.org/x/net/html/atom
> golang.org/x/net/html
> gopkg.in/httprequest.v1
> github.com/juju/webbrowser
> golang.org/x/net/context/ctxhttp
> golang.org/x/net/publicsuffix
> gopkg.in/macaroon-bakery.v2/internal/httputil
> gopkg.in/macaroon-bakery.v2/httpbakery
> gopkg.in/macaroon-bakery.v2/bakerytest
> gopkg.in/macaroon-bakery.v2/httpbakery/agent
> github.com/juju/errors
> github.com/juju/utils/clock
> golang.org/x/crypto/pbkdf2
> gopkg.in/yaml.v2
> github.com/juju/utils
> github.com/juju/schema
> github.com/juju/utils/keyvalues
> gopkg.in/juju/environschema.v1
> golang.org/x/sys/unix
> golang.org/x/crypto/ssh/terminal
> gopkg.in/juju/environschema.v1/form
> gopkg.in/macaroon-bakery.v2/httpbakery/form
>dh_auto_test -i -O--buildsystem=golang
> cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1
> gopkg.in/macaroon-bakery.v2/bakery gopkg.in/macaroon-bakery.v2/
> bakery/checkers gopkg.in/macaroon-bakery.v2/bakery/identchecker
> gopkg.in/macaroon-bakery.v2/bakery/internal/macaroonpb
> gopkg.in/macaroon-bakery.v2/bakery/mgorootkeystore
> gopkg.in/macaroon-bakery.v2/bakerytest gopkg.in/macaroon-bakery.v2/
> httpbakery gopkg.in/macaroon-bakery.v2/httpbakery/agent
> gopkg.in/macaroon-bakery.v2/httpbakery/form gopkg.in/macaroon-bakery.v2/
> internal/httputil
> === RUN   TestPackage
> OK: 71 passed
> --- PASS: TestPackage (0.05s)
> PASS
> ok  gopkg.in/macaroon-bakery.v2/bakery  0.050s
> === RUN   TestPackage
> OK: 19 passed
> --- PASS: TestPackage (0.00s)
> PASS
> ok  gopkg.in/macaroon-bakery.v2/bakery/checkers 0.003s
> === RUN   TestPackage
> OK: 19 passed
> --- PASS: TestPackage (0.01s)
> PASS
> ok  gopkg.in/macaroon-bakery.v2/bakery/identchecker 0.012s
> ?   gopkg.in/macaroon-bakery.v2/bakery/internal/macaroonpb  [no test
> files]
> === RUN   TestPackage
> SIGQUIT: quit
> PC=0x472258 m=0 sigcode=0
>
> goroutine 5 [syscall]:
> syscall.Syscall6(0xf7, 0x1, 0x3d5d, 0xc420069600, 0x104, 0x0, 0x0,
> 0x0, 0xba1480, 0x0)
> /usr/lib/go-1.10/src/syscall/asm_linux_amd64.s:44 +0x5
> fp=0xc4200695a8 sp=0xc4200695a0 pc=0x472235
> os.(*Process).blockUntilWaitable(0xc4200267b0, 0x0, 0x0, 0x2)
> /usr/lib/go-1.10/src/os/wait_waitid.go:31 +0x98 fp=0xc4200696a8
> sp=0xc4200695a8 pc=0x493358
> os.(*Process).wait(0xc4200267b0, 0xc420106a80, 0xc4200cc918, 0xc4200cc918)
>

Re: [pkg-go] Go security support in buster

2018-09-05 Thread Michael Stapelberg 
Can you give some pointers as to how one would go about developing a
solution to this?

I.e., can one set up the archive locally, or is there a test instance, or
how would one go about that?

Also, are we looking to develop a separate tool, or a feature integrated
into some existing tool? (dak?)

Have you had a chance to look at the Built-Using query by ansgar which I
referenced upthread? That should reliably figure out the affected packages.

On Wed, Sep 5, 2018 at 10:56 PM, Moritz Muehlenhoff  wrote:

> On Wed, Sep 05, 2018 at 08:34:10PM +0200, Florian Weimer wrote:
> > * Michael Stapelberg:
> >
> > > I thought haskell was in a similar boat? They have tooling to schedule
> > > binNMUs for affected packages.
> >
> > My understanding is that you can't simply schedule binNMUs on the
> > security archive because the security archive does not have the
> > sources until the first upload of the package.  (But I'm a bit out of
> > touch; this may have changed.)
>
> Indeed. There's two problems we need to solve:
>
> 1. Find a reliable mechanism if/which packages need to be rebuild. I guess
>typical use cases are
>* Vulnerability issue in Golang itself
>* Vulnerability in some golang-foo package which is used in build
> dependencies
>  (and transitive ones). Let's say some crypto libs need to be fixed.
>
> 2. Once we have a list of affected packages needing a rebuild, there's the
>issue of actually building them. Due to some underlying complexities
> the security
>archive and the main archive are separate. Ideally that would be
> resolved
>in general, but I have no idea how hard it is and there's very little
> people
>involved in dak development. So for all practical purpose this will need
>a solution kludging around it: If package foo is to be updated
>in bar-security, the first upload of bar needs to include source (-sa
>option in dpkg-buildpackage). That's annoying, and still manageable for
>single packages, but doesn't scale for rebuilding statically linked
> applications.
>So we need a reliable mechanism which imports the list of affected
> packages
>derived in 1.) and triggers binNMUs for them along with an automated
> source
>import to the security archive.
>
> As for Michael's earlier question wrt Haskell, it's true that this also
> affects
> Haskell, but it hasn't been a practical issue (while in buster we'll have
> applications like Prometheus or Docker which will definitely need updates
> across
> the lifetime of buster). Ideally whatever it being done for Go is generic
> enough
> to also cater for Haskell if we ever need it (or for Rust when it becomes
> more
> prevalent).
>
> Cheers,
> Moritz
>



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

Re: [pkg-go] Go security support in buster

2018-09-05 Thread Michael Stapelberg 
Could one automate uploads for all required binNMUs as well?

On Wed, Sep 5, 2018 at 8:34 PM, Florian Weimer  wrote:

> * Michael Stapelberg:
>
> > I thought haskell was in a similar boat? They have tooling to schedule
> > binNMUs for affected packages.
>
> My understanding is that you can't simply schedule binNMUs on the
> security archive because the security archive does not have the
> sources until the first upload of the package.  (But I'm a bit out of
> touch; this may have changed.)
>



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

Re: [pkg-go] Go security support in buster

2018-09-05 Thread Michael Stapelberg 
Aside from ratt, I also have a more specific tool to calculate binNMUs.
There’s also
https://ftp-master.debian.org/users/ansgar/outdated-built-using.txt, which
might suffice.

That said, I’m not sure merely identifying binNMUs is what’s required here…?

On Wed, Sep 5, 2018 at 4:51 PM, Stephen Gelman  wrote:

> Is this something that ratt could help with?  The general idea is similar:
> when a dependency changes the security team needs to know what other
> packages depend on it that need to be binNUM’d.
>
> Stephen
>
>
> On Sep 4, 2018, at 1:27 AM, Michael Stapelberg 
> wrote:
>
> I thought haskell was in a similar boat? They have tooling to schedule
> binNMUs for affected packages.
>
> If you can outline in more specific steps what needs to be done, maybe we
> can find someone to do the work. Right now, I have no familiarity with
> Debian’s archive infrastructure.
>
> On Mon, Sep 3, 2018 at 11:42 PM, Moritz Muehlenhoff 
> wrote:
>
>> Hi,
>> there were earlier discussions about this before (2015 or so),
>> but this is now becoming critical for buster, see my original
>> mail to the release team:
>> https://lists.debian.org/debian-release/2018/07/msg2.html
>>
>> If Go-based applications are to be included in Debian buster
>> and covered by security support, someone needs to step up
>> and implement a solution for this.
>>
>> Cheers,
>> Moritz
>>
>> ___
>> Pkg-go-maintainers mailing list
>> Pkg-go-maintainers@alioth-lists.debian.net
>> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg
>> -go-maintainers
>
>
>
>
> --
> Best regards,
> Michael
> ___
> Pkg-go-maintainers mailing list
> Pkg-go-maintainers@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/
> pkg-go-maintainers
>
>
>


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

Re: [pkg-go] Go security support in buster

2018-09-04 Thread Michael Stapelberg 
I thought haskell was in a similar boat? They have tooling to schedule
binNMUs for affected packages.

If you can outline in more specific steps what needs to be done, maybe we
can find someone to do the work. Right now, I have no familiarity with
Debian’s archive infrastructure.

On Mon, Sep 3, 2018 at 11:42 PM, Moritz Muehlenhoff  wrote:

> Hi,
> there were earlier discussions about this before (2015 or so),
> but this is now becoming critical for buster, see my original
> mail to the release team:
> https://lists.debian.org/debian-release/2018/07/msg2.html
>
> If Go-based applications are to be included in Debian buster
> and covered by security support, someone needs to step up
> and implement a solution for this.
>
> Cheers,
> Moritz
>
> ___
> Pkg-go-maintainers mailing list
> Pkg-go-maintainers@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/
> pkg-go-maintainers




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

[pkg-go] Bug#907263: dh-golang: Failed to build with gccgo-8

2018-08-26 Thread Michael Stapelberg 
If that’s required to fix the bug, then so be it :)

On Sun, Aug 26, 2018 at 5:52 PM, Shengjing Zhu  wrote:

> On Sun, Aug 26, 2018 at 11:33 PM Michael Stapelberg
>  wrote:
> >
> > There is a way, dh-make-golang does it: https://github.com/Debian/dh-
> make-golang/blob/f0afc0f7169eb4f261449d8c4bd6fc
> 7950583617/make.go#L177-L192
> >
>
> Thanks for this info, first time to know `go list std` usage.
>
> However if we go with filtering out std libraries(only for gccgo?),
> more lines will be in dh_golang...lol. And different logic for gccgo?
>
> --
> Best regards,
> Shengjing Zhu
>



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

[pkg-go] Bug#907263: Bug#907263: dh-golang: Failed to build with gccgo-8

2018-08-26 Thread Michael Stapelberg 
There is a way, dh-make-golang does it:
https://github.com/Debian/dh-make-golang/blob/f0afc0f7169eb4f261449d8c4bd6fc7950583617/make.go#L177-L192

On Sun, Aug 26, 2018 at 12:34 PM, Shengjing Zhu  wrote:

> On Sun, Aug 26, 2018 at 5:44 PM Michael Hudson-Doyle
>  wrote:
> >
> > I've forgotten everything about this code even though I wrote it, but
> wouldn't it be better to filter out the standard library dependencies?
> >
>
> For golang-go, currently it uses std library to producing the
> Built-Using for golang-go compiler. For gccgo, there's no such need
> because it will depends libgo.
> So for gccgo, it's true that we can filter out the std library. But I
> doubt if there's clean way...
>
> --
> Best regards,
> Shengjing Zhu
>
> ___
> Pkg-go-maintainers mailing list
> Pkg-go-maintainers@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/
> pkg-go-maintainers




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

[pkg-go] Bug#905839: Bug#905839: debiman: autopkgtest fails with mdocml version 1.14.4-1

2018-08-10 Thread Michael Stapelberg 
control: tag -1 + pending

On Fri, Aug 10, 2018 at 2:59 PM, Michael Stapelberg 
wrote:

> This is fixed upstream in https://github.com/Debian/debiman/commit/
> 210e94b3cf101d62b74211d0866f6308c6bee4db
>
> Feel free to do what is necessary to get the fix into Debian.
>
> On Fri, Aug 10, 2018 at 2:37 PM, Paul Gevers  wrote:
>
>> Source: debiman
>> Version: 0.0~git20180711.cb414bd-2
>> X-Debbugs-CC: debian...@lists.debian.org, mdo...@packages.debian.org
>> User: debian...@lists.debian.org
>> Usertags: needs-update
>> Control: affects -1 src:mdocml
>>
>> Dear maintainers,
>>
>> Recently version 1.14.4-1 of mdocml was uploaded to the Debian archive.
>> Your autopkgtest started to fail with the error copied below.
>>
>> Could you please investigate? It seems that you are comparing generated
>> output with a reference. Looking at the text I can't spot obvious
>> mistakes (but I may be missing details), so I think you need to update
>> your reference to the new output. Please reassign this bug to mdocml if
>> you think that package has this bug instead. This regression is
>> currently delaying the migration of mdocml to unstable by 10 days, so
>> cooperation to fix this swiftly is appreciated.
>>
>> Don't forget the set the appropriate Versioned (test) depends to let
>> autopkgtest figure out which version is needed and maybe consider making
>> your tests less sensitive to this kind of changes if they shouldn't
>> delay or block other packages. If your tests aren't suitable for gating
>> other packages, you can also mark them skippable and exit 77 in case of
>> regressions.
>>
>> Paul
>>
>> https://ci.debian.net/data/autopkgtest/testing/amd64/d/debim
>> an/796100/log.gz
>>
>> 2018/08/10 05:11:23 mandocd not found, falling back to fork+exec for
>> each manpage
>> --- FAIL: TestToHTML (0.00s)
>> --- FAIL: TestToHTML/i3lock (0.01s)
>> convert_test.go:92: unexpected conversion result: (diff from want
>> →
>> got):
>> --- /tmp/debiman-314812002  2018-08-10
>> 05:11:23.148127262 +
>> +++ /tmp/debiman-841037135  2018-08-10
>> 05:11:23.148127262 +
>> @@ -7,65 +7,65 @@
>>
>>  
>>  
>> +
>> +
>>  NAME> href="#NAME">¶
>>  i3lock - improved screen locker
>> - 
>> +
>>  SYNOPSIS> href="#SYNOPSIS">¶
>>  i3lock [-v] [-c color]
>> - 
>> +
>>  DESCRIPTION> class="anchor"
>> href="#DESCRIPTION">¶
>>  i3lock is a simple screen locker like slock. After
>> starting it, you will
>>see a white screen (you can configure the color/an
>> image). You
>> can return to
>>your screen by entering your password.
>> - 
>> +
>>  IMPROVEMENTS> class="anchor"
>> href="#IMPROVEMENTS">¶
>>  
>> -  •
>> -  i3lock forks, so you can combine it
>> with an
>> alias to
>> -  suspend to RAM (run i3lock  echo
>> mem 
>> -  /sys/power/state to get a locked screen after
>> waking
>> up your
>> -  computer from suspend to RAM)
>> +  •
>> +  i3lock forks, so you can combine it with an alias
>> to
>> suspend to RAM (run
>> +  i3lock  echo mem 
>> /sys/power/state
>> to get a
>> +  locked screen after waking up your computer from
>> suspend to
>> RAM)
>>  
>>  
>> -  •
>> -  You can specify either a background
>> color or
>> a PNG image
>> -  which will be displayed while your screen is
>> locked.
>> +  •
>> +  You can specify either a background color or a PNG
>> image
>> which will be
>> +  displayed while your screen is locked.
>>  
>>  
>> -  •
>> -  You can specify whether i3lock
>> should bell
>> upon a wrong
>> -

[pkg-go] Bug#905839: Bug#905839: debiman: autopkgtest fails with mdocml version 1.14.4-1

2018-08-10 Thread Michael Stapelberg 
   OPTIONS href="#OPTIONS">¶
>  
> -  -v, --version
> -  Display the version of your
> i3lock
> - 
> +  -v, --version
> +  Display the version of your i3lock
> +
>
>  
>  
> -  -c rrggbb,
> --color=rrggbb
> -  Turn the screen into the given color
> instead
> of white.
> -  Color must be given in 3-byte format: rrggbb (i.e.
> ff
> is red).
> - 
> +  -c rrggbb,
> --color=rrggbb
> +  Turn the screen into the given color instead of
> white.
> Color must be given
> +  in 3-byte format: rrggbb (i.e. ff is red).
> +
>
>  
>  DPMS href="#DPMS">¶
>  The -d (--dpms) option.
> - 
> +
>verbatim
>  
> - 
> +
>  SEE ALSO href="#SEE_ALSO">¶
>  xautolock(1) - use i3lock as your screen saver
> - 
> +
>  AUTHOR href="#AUTHOR">¶
>  Michael Stapelberg michael+i3lock@example.
> invalid
>  
>
> --- FAIL: TestToHTML/refs (0.01s)
> convert_test.go:92: unexpected conversion result: (diff from want →
> got):
> --- /tmp/debiman-766785508  2018-08-10
> 05:11:23.148127262 +
> +++ /tmp/debiman-681617497  2018-08-10
> 05:11:23.148127262 +
> @@ -9,19 +9,19 @@
>  
>  NAME href="#NAME">¶
>  refs - test file
> - 
> +
>  SEE ALSO href="#SEE_ALSO">¶
>  http://w3m.sourceforge.net;>project
> website
> - 
> +
>  More details can be found in the  href="testing/i3lock/i3lock.1.C">i3lock(1) or refs(1) man pages.
> - 
> +
>  References to i3-msg(1)
> might cause trouble when matching on word boundaries.
> - 
> +
>  References to  href="testing/systemd/systemd.service.5.C">systemd.service(5)
> contain a dot.
> - 
> +
>  URLs in plain text, like  href="http://debian.org;>http://debian.org are also recognized and
> converted.
>URLs in brackets, like  href="http://debian.org/;>http://debian.org/ are correctly
> recognized.
> - 
> +
>  Marked up URLs like  href="http://gnome.org;>http://gnome.org are also converted.
>  
>
>
> === RUN   TestXref
> --- PASS: TestXref (0.00s)
> === RUN   TestHref
> --- PASS: TestHref (0.00s)
> === RUN   TestXrefHref
> --- PASS: TestXrefHref (0.00s)
> === RUN   TestFormattedXref
> --- PASS: TestFormattedXref (0.00s)
> FAIL
> FAILgithub.com/Debian/debiman/internal/convert  0.016s
>
>
>
> ___
> Pkg-go-maintainers mailing list
> Pkg-go-maintainers@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/
> pkg-go-maintainers
>



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

[pkg-go] Bug#904574: Bug#904574: ratt should depend on dose-extra

2018-07-27 Thread Michael Stapelberg 
Sounds reasonable. Could you send a merge request at
https://salsa.debian.org/go-team/packages/ratt/blob/master/debian/control
please? You can use the Edit button to perform the edit in your browser
(but please test the resulting package). If you don’t have an account yet,
see https://signup.salsa.debian.org/

Thanks!

On Wed, Jul 25, 2018 at 11:42 AM, Nicolas Braud-Santoni <
nico...@braud-santoni.eu> wrote:

> Package: ratt
> Version: 0.0~git20160202.0.a14e2ff-1+b3
> Severity: normal
>
> Hi,
>
> When using ratt, it attempts to call dose-ceve (from the dose-extra
> package)
> and if the binary is missing it falls back to interpreting the sources
> index
> itself.
>
> As such, I believe ratt should declare an optional dependency (Recommends
> or
> Suggests) on dose-extra; I believe Recommends would be appropriate as ratt
> has degraded functionality without it (as far as I understand).
>
>
> Best,
>
>   nicoo
>
> -- System Information:
> Debian Release: buster/sid
>   APT prefers testing
>   APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 4.16.0-1-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored:
> LC_ALL set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored:
> LC_ALL set to en_US.UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages ratt depends on:
> ii  libc6  2.27-5
>
> ratt recommends no packages.
>
> ratt suggests no packages.
>
> -- no debconf information
>
> ___
> Pkg-go-maintainers mailing list
> Pkg-go-maintainers@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/
> pkg-go-maintainers




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

Re: [pkg-go] debian-go mailing list

2018-07-27 Thread Michael Stapelberg 
I have access to the web interface and can list the subscribers, but I
don’t see an easy way to get the 67 subscribers in a machine-readable
format.

I made you a mod, maybe that allows you the same kind of access, and maybe
you’re more successful in interacting with the UI than I am? :)

I think it might be easiest to contact the debian-lists admins so that they
can use the mailman command line tools to export the subscribers.

On Fri, Jul 27, 2018 at 10:57 AM, Alexandre Viau  wrote:

> Hello Michael,
>
> According to the following page, you are the admin of the alioth list:
>  - https://alioth-lists.debian.net/cgi-bin/mailman/admin/pkg-
> go-maintainers
>
> > Pkg-go-maintainers list run by stapelberg at debian.org
>
> Are you able to export the list of subscribers?
>
> If yes, we might be able to open a bug similar to this one, and get our
> subscribers transfered:
>  - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896615
>
> If you are not able to access the admin interface, please let me know
> and I will contact the alioth-lists.debian.net admins.
>
> Cheers,
>
> On 2018-06-24 12:08 PM, Michael Stapelberg wrote:
> > I don’t know :). You’d have to talk to listmasters, I guess?
> >
> > On Sun, Jun 24, 2018 at 5:48 PM, Alexandre Viau  > <mailto:av...@debian.org>> wrote:
> >
> > On 2018-06-24 10:09 AM, Michael Stapelberg wrote:
> > > The debian-go mailing list has been
> > > created: https://lists.debian.org/debian-go/
> > <https://lists.debian.org/debian-go/>
> >
> > Great!
> >
> > > I currently don’t have cycles to do any sort of migration, but if
> > > someone wants to tackle this task, please let us know :).
> >
> > You are talking about transferring subscribers?
> >
> > Is there an admin interface that allows adding subscribers in bulk?
> Or
> > maybe we can script it easily?
> >
> > I am willing to help.
> >
> > Cheers,
> >
> > --
> > Alexandre Viau
> > av...@debian.org <mailto:av...@debian.org>
> >
> >
> >
> >
> > --
> > Best regards,
> > Michael
>
> --
> Alexandre Viau
> av...@debian.org
>
>
>


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

Re: [pkg-go] Joining Debian Go Packaging Team?

2018-07-16 Thread Michael Stapelberg 
Approved, welcome to the team! Please familiarize yourself with our
documentation at https://go-team.pages.debian.net/ if you haven’t already.

On Mon, Jul 16, 2018 at 11:58 AM, Julian Gilbey  wrote:

> Hello,
>
> I've received a pull request on go-fuse, but I discover that I'm not
> in the Debian Go Packaging Team group on salsa.  I've put in a request
> to join it (which I assume is the right thing to do).  Do I need to be
> a member of the group in order to handle this request?
>
> Best wishes,
>
>Julian
>
> ___
> Pkg-go-maintainers mailing list
> Pkg-go-maintainers@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/
> pkg-go-maintainers




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

Re: [pkg-go] debian-go mailing list

2018-07-09 Thread Michael Stapelberg 
On Mon, Jul 9, 2018 at 3:05 PM, Clément Hermann  wrote:

> On 25/06/2018 14:33, Pirate Praveen wrote:
> >
> >
> > On June 25, 2018 11:55:54 AM GMT+05:30, Michael Stapelberg <
> stapelb...@debian.org> wrote:
> >> Ah, thanks for pointing that out. We already have
> >> https://tracker.debian.org/teams/pkg-go/ apparently. What is the
> >> maintainer
> >> address in that entry being used for?
> >>
> >
> > From what I guessed, the current team is auto created (or some one
> created it manually) from the current maintainer email address (alioth).
> >
> > It may be enough to start using team+pkg...@tracker.debian.org for new
> uploads to come under this team. But its better to confirm with someone who
> knows more about tracker.
> >
>
> In case people missed it, there was a post on d-d-announce from Raphael
> Hertzog describing the features of the tracker in this regard:
> https://lists.debian.org/debian-devel-announce/2018/07/msg1.html
>
> So, to summarize: it was indeed auto-created; it is usable as maintainer
> address, and can even be used as a discussion list but messages aren't
> archived.
>
> IMO, it would be nice to use this as a maintainer address and have all
> the "cruft" (notifications and such) messages going to it, while keeping
> a proper mailing list (maybe asking for one @lists.debian.org) for
> discussion.
>

The start of this thread was the fact that our debian...@lists.debian.org
mailing list was created :).


>
> Actually, even if we don't use the tracker, I think it would be nice to
> separate the notifications from the discussion - at least it would ease
> my own workflow ;)
>
> Thoughts ?
>

Sounds reasonable. Can you outline how we would migrate? Do we need to
change the maintainer field to a tracker address? Would we communicate with
the tracker primarily, and add debian-go@ for things that might interest
the broader group?


>
>
> --
> nodens
>
>
>
> ___
> Pkg-go-maintainers mailing list
> Pkg-go-maintainers@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/
> pkg-go-maintainers
>



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

[pkg-go] Bug#903385: Bug#903385: dh-golang: Allow the "build" dh stage to call "go build" instead of "go install"

2018-07-09 Thread Michael Stapelberg 
Would such a flag be useful for any other package than the fscrypt package?

If no, I’d recommend to not change dh-golang for the time being, and let
this be a one-off in the fscrypt package until it makes sense to centralize
the logic.

On Mon, Jul 9, 2018 at 12:15 PM, Paride Legovini  wrote:

> Package: dh-golang
> Version: 1.34
> Severity: normal
>
> Hi,
>
> There is at least one case when it would be preferable to have the build
> dh stage to call ’go build’ instead of ’go install’. This is when
> building c-shared libraries with -buildmode=c-shared. In this case ‘go
> install’ builds the shared library object, but gives it a ‘.a’ extension
> and installs it in a not well defined location. This is discussed in this
> upstream issue:
>
> https://github.com/golang/go/issues/24253
>
> The upstream indication is that "The expectation is that people will use
> go build -buildmode=c-shared -o foo.so" and that using ‘go install’ "will
> put the shared library in a relatively unpredictable place".
>
> Given these facts, I think dh-golang should support a ‘go build’ mode.
> One way this could be implemented is via a --build-only flag to be
> passed to dh_auto_build. If there is consensus on this I can send a
> patch implementing it.
>
> This problem arose while packaging fscrypt, see in particular:
>
> https://salsa.debian.org/go-team/packages/fscrypt/blob/
> d15d123eb301d50c0376a10615e472054dd3b88d/debian/rules#L36
>
> Paride
> ___
> Pkg-go-maintainers mailing list
> Pkg-go-maintainers@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/
> pkg-go-maintainers




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

Re: [pkg-go] Blog post about the docker.io package

2018-07-05 Thread Michael Stapelberg 
That’s great news! Thanks everyone for all your hard work on this.

On Thu, Jul 5, 2018 at 4:17 AM, Arnaud Rebillout <
arnaud.rebill...@collabora.com> wrote:

>   Hello Go packaging team,
>
> you might remember that I showed up on this mailing list a few months
> ago, talking about docker packaging and asking around for package reviews
> :)
>
> Since then, Dmitry Smirnov joined the battle, and thanks to his effort
> the docker.io package is now back to life.
>
> I wrote a blog post to talk about that! If you're interested, grap a cup
> of coffee/tea, and take some time to read:
>
> https://www.collabora.com/news-and-blog/blog/2018/07/04/
> docker-io-debian-package-back-to-life/
>
> I will be at DebConf in Taiwan to talk about that as well, hope to meet
> you there!
>
>   Arnaud
>
>
>
>
> ___
> Pkg-go-maintainers mailing list
> Pkg-go-maintainers@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/
> pkg-go-maintainers




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

Re: [pkg-go] debian-go mailing list

2018-06-24 Thread Michael Stapelberg 
I don’t know :). You’d have to talk to listmasters, I guess?

On Sun, Jun 24, 2018 at 5:48 PM, Alexandre Viau  wrote:

> On 2018-06-24 10:09 AM, Michael Stapelberg wrote:
> > The debian-go mailing list has been
> > created: https://lists.debian.org/debian-go/
>
> Great!
>
> > I currently don’t have cycles to do any sort of migration, but if
> > someone wants to tackle this task, please let us know :).
>
> You are talking about transferring subscribers?
>
> Is there an admin interface that allows adding subscribers in bulk? Or
> maybe we can script it easily?
>
> I am willing to help.
>
> Cheers,
>
> --
> Alexandre Viau
> av...@debian.org
>
>


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

[pkg-go] debian-go mailing list

2018-06-24 Thread Michael Stapelberg 
Hey,

The debian-go mailing list has been created:
https://lists.debian.org/debian-go/

The intention was to use that list as a longer-term mailing list after the
alioth list replacement server shuts down, too.

I currently don’t have cycles to do any sort of migration, but if someone
wants to tackle this task, please let us know :).

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

Re: [pkg-go] Code review: golang-github-danverbraganza-varcaser

2018-06-24 Thread Michael Stapelberg 
Can you file an issue at https://github.com/Debian/dh-make-golang please?

On Sun, Jun 24, 2018 at 7:09 AM, Shengjing Zhu  wrote:

> On Sun, Jun 24, 2018 at 4:17 AM Anthony Fok  wrote:
> > "golang-x-text-dev" is a deprecated transitional package and will
> > be removed eventually.
> > Use "golang-golang-x-text-dev" instead.
>
> Actually this is bug in dh-make-golang,
>
> $ dh-make-golang search golang.org/x/text
> golang-x-text-dev: golang.org/x/text
>
>
> --
> Best regards,
> Shengjing Zhu
>
> ___
> Pkg-go-maintainers mailing list
> Pkg-go-maintainers@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/
> pkg-go-maintainers
>



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

Re: [pkg-go] gbp buildpackage

2018-06-18 Thread Michael Stapelberg 
I use gbp buildpackage --git-export-dir=/tmp/export, the builder
configuration happens in ~/.gbp.conf entirely.

On Mon, Jun 18, 2018 at 9:49 PM, Tong Sun  wrote:

> On Sat, Jun 16, 2018 at 5:38 PM Michael Stapelberg -
> stapelb...@debian.org
>  wrote:
> >
> > I’m using sbuild (as the buildds run sbuild, too), which you can set up
> using https://people.debian.org/~stapelberg//2018/03/19/sbuild-
> debian-developer-setup.html
> >
> > In my ~/.gbp.conf, I specify:
> > [buildpackage]
> > builder = sbuild --source-only-changes -s -v -A --no-clean-source
>
> Thanks for your input Michael, it is working for me now. One more question,
>
> Do you do build with
>
> gbp buildpackage --git-pbuilder
>
> or use some other parameters?
>
> ___
> Pkg-go-maintainers mailing list
> Pkg-go-maintainers@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/
> pkg-go-maintainers
>



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

Re: [pkg-go] gbp buildpackage

2018-06-17 Thread Michael Stapelberg 
Which version of sbuild are you using this with? Try installing sbuild from
unstable (or testing), too.

On Sun, Jun 17, 2018 at 10:40 PM, Tong Sun  wrote:

> On Sat, Jun 16, 2018 at 5:38 PM Michael Stapelberg wrote:
>
> > I’m using sbuild (as the buildds run sbuild, too), which you can set up
> using https://people.debian.org/~stapelberg//2018/03/19/sbuild-
> debian-developer-setup.html
> >
> > In my ~/.gbp.conf, I specify:
> > [buildpackage]
> > builder = sbuild --source-only-changes -s -v -A --no-clean-source
>
> Thanks a lot for your input Michael,
>
> I gave it a try, but got `E: Error parsing command-line options` when
> doing `sudo sbuild-debian-developer-setup`. Tried several times:
>
> ```
> $ sudo apt-cache policy sbuild-debian-developer-setup
> sbuild-debian-developer-setup:
>   Installed: 0.76.0-1
>   Candidate: 0.76.0-1
>   Version table:
>  *** 0.76.0-1 100
> 100 http://debian-archive.trafficmanager.net/debian
> unstable/main amd64 Packages
> 100 /var/lib/dpkg/status
>  0.76.0-1~bpo9+1 100
> 100 http://debian-archive.trafficmanager.net/debian
> stretch-backports/main amd64 Packages
>
> $ sudo apt-get remove --purge sbuild-debian-developer-setup
> . . .
> Purging configuration files for sbuild-debian-developer-setup (0.76.0-1)
> ...
>
> $ sudo apt install -t unstable sbuild-debian-developer-setup
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> The following NEW packages will be installed:
>   sbuild-debian-developer-setup
> 0 upgraded, 1 newly installed, 0 to remove and 609 not upgraded.
> Need to get 64.1 kB of archives.
> After this operation, 79.9 kB of additional disk space will be used.
> Get:1 http://debian-archive.trafficmanager.net/debian unstable/main
> amd64 sbuild-debian-developer-setup all 0.76.0-1 [64.1 kB]
> Fetched 64.1 kB in 0s (984 kB/s)
> Selecting previously unselected package sbuild-debian-developer-setup.
> (Reading database ... 93318 files and directories currently installed.)
> Preparing to unpack .../sbuild-debian-developer-setup_0.76.0-1_all.deb ...
> Unpacking sbuild-debian-developer-setup (0.76.0-1) ...
> Setting up sbuild-debian-developer-setup (0.76.0-1) ...
>
> $ sudo apt-cache policy sbuild-debian-developer-setup
> sbuild-debian-developer-setup:
>   Installed: 0.76.0-1
>   Candidate: 0.76.0-1
>   Version table:
>  *** 0.76.0-1 100
> 100 http://debian-archive.trafficmanager.net/debian
> unstable/main amd64 Packages
> 100 /var/lib/dpkg/status
>  0.76.0-1~bpo9+1 100
> 100 http://debian-archive.trafficmanager.net/debian
> stretch-backports/main amd64 Packages
>
>
> $ sudo sbuild-debian-developer-setup
> The user `u' is already a member of `sbuild'.
> Unknown option: command-prefix
> E: Error parsing command-line options
> I: Run 'sbuild-createchroot --help' to list usage example and all
> available options
> sbuild-createchroot failed:  at /usr/bin/sbuild-debian-developer-setup
> line 53.
> ```
>
> Consequently, the rest of sbuild operation will fail.
>
> What I've missed? Thx.
>
> ___
> Pkg-go-maintainers mailing list
> Pkg-go-maintainers@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/
> pkg-go-maintainers
>



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

Re: [pkg-go] gbp buildpackage

2018-06-16 Thread Michael Stapelberg 
I’m using sbuild (as the buildds run sbuild, too), which you can set up
using
https://people.debian.org/~stapelberg//2018/03/19/sbuild-debian-developer-setup.html

In my ~/.gbp.conf, I specify:
[buildpackage]
builder = sbuild --source-only-changes -s -v -A --no-clean-source


On Sat, Jun 16, 2018 at 4:46 PM, Anthony Fok  wrote:

> Hi again,
>
> On Sat, Jun 16, 2018 at 8:35 AM, Anthony Fok  wrote:
> > Hi Tong,
> >
> > On Sat, Jun 16, 2018 at 7:19 AM, Tong Sun 
> wrote:
> >> However, I'm having problem with `cowbuilder --create` --
> >>
> >> - If I run it with `fakeroot`, then it'll break at the end with:
> >>
> >> chroot: cannot change root directory to '/var/cache/pbuilder/base.cow':
> >> Operation not permitted
> >> ..
> >>
> >> - If I run it without `fakeroot`, then it'll break at the beginning
> with:
> >>
> >> E: debootstrap can only run as root
> >
> > 1. man fakeroot
> > 2. man sudo
> > 3. man su
>
> I don't know how you manage to run cowbuilder as a non-root because
> /usr/sbin isn't even in the PATH for non-root users.
>
> Anyhow, nowadays, I am using a higher-level tool:
>
>   git-pbuilder - Wrapper around cowbuilder/qemubuilder for gbp buildpackage
>
> It is part of the git-buildpackage package:
>
> $ dpkg -S git-pbuilder
> git-buildpackage: /usr/bin/git-pbuilder
> git-buildpackage: /usr/share/man/man1/git-pbuilder.1.gz
>
> It lives in /usr/bin/git-pbuilder and calls sudo for you, and does
> other nice things for you.
> So, instead of calling "sudo cowbuilder create" directly,
> you call "git-pbuilder create".
>
> Have fun exploring (Google about it) and experimenting!
>
> Anthony
>
> ___
> Pkg-go-maintainers mailing list
> Pkg-go-maintainers@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/
> pkg-go-maintainers
>



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

[pkg-go] Bug#898397: Bug#898397: dh-make-golang: allow authentication to github API to avoid hitting limits

2018-05-14 Thread Michael Stapelberg 
fixed in
https://github.com/Debian/dh-make-golang/commit/db00c3774281436cc182d81463fbc86d791ec019

On Fri, May 11, 2018 at 6:58 AM, Paul Wise  wrote:

> Package: dh-make-golang
> Version: 0.0~git20180410.bcfd5bf-1
> Severity: wishlist
>
> I packaged a bunch of dependencies for git-lab and then I started
> getting 403 errors from github URLs. It looks like dh-make-golang
> easily hits the github API rate limit for anonymous users.
>
> Allowing authenticated requests could help to avoid the limit.
>
> $ dh-make-golang make github.com/avast/retry-go
> 2018/05/11 12:51:52 Downloading "github.com/avast/retry-go/..."
> 2018/05/11 12:51:53 Determining upstream version number
> 2018/05/11 12:51:53 Package version is "1.0.2"
> 2018/05/11 12:51:53 Determining dependencies
> 2018/05/11 12:51:57 Could not determine long description for "
> github.com/avast/retry-go": unexpected HTTP status: got 403, want 200
> 2018/05/11 12:51:58 Could not determine copyright for "
> github.com/avast/retry-go": parsing time "" as "2006-01-02T15:04:05Z":
> cannot parse "" as "2006"
> 2018/05/11 12:51:59 Could not determine author for "
> github.com/avast/retry-go": parsing time "" as "2006-01-02T15:04:05Z":
> cannot parse "" as "2006"
> 2018/05/11 12:51:59 Could not determine long description for "
> github.com/avast/retry-go": unexpected HTTP status: got 403, want 200
> ...
>
> $ curl -s https://api.github.com/users/pabs3 | jq
> {
>   "message": "API rate limit exceeded for . (But here's the good
> news: Authenticated requests get a higher rate limit. Check out the
> documentation for more details.)",
>   "documentation_url": "https://developer.github.com/v3/#rate-limiting;
> }
>
> -- System Information:
> Debian Release: buster/sid
>   APT prefers testing-debug
>   APT policy: (900, 'testing-debug'), (900, 'testing'), (800,
> 'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700,
> 'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 4.16.0-1-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8),
> LANGUAGE=en_AU.utf8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages dh-make-golang depends on:
> ii  git   1:2.17.0-1
> ii  git-buildpackage  0.9.8
> ii  golang-any2:1.10~5
> ii  libc6 2.27-3
> ii  pristine-tar  1.42
>
> Versions of packages dh-make-golang recommends:
> ii  exim4-daemon-light [mail-transport-agent]  4.91-3
>
> dh-make-golang suggests no packages.
>
> -- no debconf information
>
> --
> bye,
> pabs
>
> https://wiki.debian.org/PaulWise
>
> ___
> Pkg-go-maintainers mailing list
> Pkg-go-maintainers@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/
> pkg-go-maintainers
>



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

Re: [pkg-go] Typo when creating a salsa repo, and how to delete the project

2018-04-27 Thread Michael Stapelberg 
Deleted it. There’s no inactivity cleanup that I know of.

On Fri, Apr 27, 2018 at 7:58 AM, Arnaud Rebillout <
arnaud.rebill...@collabora.com> wrote:

> Hello Go packagers,
>
> Let's say I used `dh-make-golang create-salsa-project` and I made a
> typo. Now there's a project at
> ,
> and I would like to remove it, however I don't have the rights for that.
>
> Will this repo automatically disappear due to inactivity? Or should
> someone remove it for me?
>
> Sorry for that :/
>
>   Arnaud
>
>
> ___
> Pkg-go-maintainers mailing list
> Pkg-go-maintainers@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/
> pkg-go-maintainers




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

[pkg-go] Fixed repository settings

2018-04-17 Thread Michael Stapelberg 
Hey,

I just noticed that I had an older version of the “ci” binary lying around,
preventing my cronjob from updating newly created repositories.

This would explain why pushes to some repositories would not result in IRC
messages.

I fixed this and am currently running the tool to update our repositories.
Sorry for the mass changes in case they manifest themselves through
messages in any kind for you.

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

Re: [pkg-go] RFS: golang-github-smartystreets-gunit

2018-04-17 Thread Michael Stapelberg 
Thanks, this is now uploaded.

On Sun, Apr 15, 2018 at 9:21 PM, Raju Devidas <raju...@disroot.org> wrote:

> In between.
>
> Michael Stapelberg:
> > I recommend changing the copyright to “SmartyStreets, LLC”, which is
> > clearer for the reader and consistent with what we already have in the
> > archive.
>
> Hey, Michael, as per discussion here. I have made the changes and pushed
> to salsa.
>
> You or anyone else should review and upload it.
>
> Thanks
>
> <>
>
> ___
> Pkg-go-maintainers mailing list
> Pkg-go-maintainers@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/
> pkg-go-maintainers




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