[pkg-go] Bug#789991: FTBFS: Test failures including FixtureS.TestPanicOnSetUpSuite, FixtureS.TestPanicOnSetUpTest
Anthony Fok
foka at debian.org
Sun Nov 22 15:58:11 UTC 2015
Source: golang-gocheck
Followup-For: Bug #789991
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi Sergio and Martín,
Seeing how that https://launchpad.net/gocheck points the user to
https://github.com/go-check/check, which the golang-check.v1 package
provides as "gopkg.in/check.v1", and seeing that lots of activities
happened with the golang-check.v1 package and none here, am I correct to
assume that the consensus is to let this old golang-gocheck package be
auto-removed while we update the affected packages to build-depend on
golang-check.v1-dev instead? :-)
According to
https://packages.qa.debian.org/g/golang-github-juju-ratelimit.html
the affected packages are:
* golang-github-juju-ratelimit (Maintainer: pkg-go)
* golang-go-dbus (Maintainer: Sergio Schvezov)
* golang-goyaml (Maintainer: pkg-go)
* ngrok (Maintainer: Vincent Bernat; Uploaders: pkg-go)
* slt (Maintainer: Daniel Kahn Gillmor)
To test the water, I went ahead and uploaded a new Debian version of
golang-github-juju-ratelimit, changing the build-dependency from
golang-gocheck-dev to golang-check.v1-dev:
https://tracker.debian.org/news/727430
Is that the right way to go? If so, should I do the same for the other
packages that are maintained by pkg-go, and file bug reports for the
others?
Many thanks!
Anthony
- -- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.2.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBCAAGBQJWUeYPAAoJEOolALQSxZrPpUUQAKQ1ZDoEa5s+Sa+1oTDVCCnJ
v7RheiZ4JktOKu2OyntkHmn4VyyiPDplvcJJPpwQlOT8dxl8SJZsX/W1SeMGEM3b
2KblBvzs/PfEVDJBHnNFwm/t1qnWkINO+ULEIft9wqc1DyQAPOGrM/BFLQMYFy8I
nCvhRPTWvUNzMfi41wBsZSVVdE7NC1JhriS1vnZkwfrqKT8EEHElqKsrBq2JNTI0
RZHKonS0UiO9EI3OgLO+tUyomHXzaQvGdsbScFbhe9GkPk1mek5Pf1wQ7ozX0DJ6
yZxHn/WX/Xq4Vd6qEZVZWPXPsXY9W4SfMkKYS6Ihj8G9a1NE2neft9H7h8Nsdm+M
iBY4+sI47JMMhvS1VRnmc9p98G6CIO0+wuUikdGKuY+uQeXCNzQagGWpx+9F57Pw
KdH40Y+mkJIzEBpNS1XWl3QuuChRWXLVcEh0FwHAbVWzZfkML6IDJn415SkbC1U7
/dwwBhYIugyuvRgga+jFfE/YwjMRLZ7aFb4RrpuvXLeJIPmKROGTIHI3XOeme6vW
qC6YfM10jqlBS2HGnjzUkUjjLsppUFcp/id4upCRYbbrNZai/1vGkC9FfVpxwTaP
jyYThkYahQjbQMhpIMbzvFxRDoAH5kMsaH6vFs7PoWftv2TGZxq+yOi9ZWV2+ISw
UsnHxfGUOtnOZRWQNUjO
=Z5Kq
-----END PGP SIGNATURE-----
More information about the Pkg-go-maintainers
mailing list