[pkg-go] Accepted gitlab-ci-multi-runner 10.5.0+dfsg-2 (source amd64) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 26 Mar 2018 01:08:26 +1100 Source: gitlab-ci-multi-runner Binary: gitlab-runner Architecture: source amd64 Version: 10.5.0+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team <pkg-go-maintainers@lists.alioth.debian.org> Changed-By: Dmitry Smirnov <only...@debian.org> Description: gitlab-runner - GitLab Runner - runs continuous integration (CI) jobs Changes: gitlab-ci-multi-runner (10.5.0+dfsg-2) unstable; urgency=medium . * Upload to unstable. * postinst: remove broken "gitlab-runner.service" symlink if upgraded from "gitlab-ci-multi-runner". * New patch to fix test failure on [armel, armhf]. Checksums-Sha1: 3c8d562fd4b3a1768351439b59e0dbedfec52854 3732 gitlab-ci-multi-runner_10.5.0+dfsg-2.dsc 8245f8fe05a78fcf85f17a9f0ee8eaf701761029 15800 gitlab-ci-multi-runner_10.5.0+dfsg-2.debian.tar.xz c292e897be1fb105b7f31f458105627b0b88bac4 21180 gitlab-ci-multi-runner_10.5.0+dfsg-2_amd64.buildinfo b50a329a657546a2250c5d819bea905e8a552a2d 4367720 gitlab-runner-dbgsym_10.5.0+dfsg-2_amd64.deb 56c609ed8e15ee363fdf13ef22bc4490af7460dc 7588012 gitlab-runner_10.5.0+dfsg-2_amd64.deb Checksums-Sha256: be4d493d1a6dd0e835118cfb79dd9cec8ad7839b5b3b5da85858d67b4e3212dd 3732 gitlab-ci-multi-runner_10.5.0+dfsg-2.dsc e46035cf7a25ce9503c21904123f1d88d71a0a9a3ec45f24c2433b02c625b5b9 15800 gitlab-ci-multi-runner_10.5.0+dfsg-2.debian.tar.xz f16a06a7b1ead3b457f3a55054ecf68248d8da036939f12e51bcb251ad699df8 21180 gitlab-ci-multi-runner_10.5.0+dfsg-2_amd64.buildinfo dc1b879aa950833cc8d65166af176b6a248a3fc0ed181f849c3865628ad7dbbd 4367720 gitlab-runner-dbgsym_10.5.0+dfsg-2_amd64.deb 2c979404a5f647bc8575cf9f4742cfbd8e799205c6ab5cc61c1dc23efa901087 7588012 gitlab-runner_10.5.0+dfsg-2_amd64.deb Files: d191382c30a458798e18f528ee1c55df 3732 devel optional gitlab-ci-multi-runner_10.5.0+dfsg-2.dsc 795e766e88c36cda30740dcb882774fe 15800 devel optional gitlab-ci-multi-runner_10.5.0+dfsg-2.debian.tar.xz cb8a2705cdcd41c1236368279db6499f 21180 devel optional gitlab-ci-multi-runner_10.5.0+dfsg-2_amd64.buildinfo ec84f811daa32c0f9e997eeac251e086 4367720 debug optional gitlab-runner-dbgsym_10.5.0+dfsg-2_amd64.deb 03a458ea4301be6744766ccdc23be21f 7588012 devel optional gitlab-runner_10.5.0+dfsg-2_amd64.deb -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEULx8+TnSDCcqawZWUra72VOWjRsFAlq3rd0ACgkQUra72VOW jRuOGg//Q60GjSL2H3LG8L1vA5EnEty1rc4nK8qfiql+vjLcs562DCxY9+aU4r2G 5oPG2z+j/P6OJvlFDZAC+lxb2D1jU0JiN2RUdNBASYLefT/7hZEeJmtupHVCI9Nl FBqH9U2BR0GD7xWblvr28+TJJ6RrzXCKnwLkLzltheO4sGyKTOPgg4EhfNtDw+Ng FfMlw0OvNc2wLdd5DWLe0R/C9eVsqluH6GcuPCZSGdKP5wxdhptU/YflTmZXwz/h WNNAiVcPzHjyUYbHUi5Ns2v5hDD/dAaZfcZJhRUv7HWT430eI96PRm9p186LatBT 60tmbyOcVUJ6LY9faqe/efJgUtGSV1wqbH3wgtvL5IfKsdWv3R8JBGefgaxKi8Q4 wjPH1eGC+CJYb1u5bFlOs+m8XC6JwI0fBivZkButVsHjzsAvDATUWFEyVn1WASui E0SWgLcHYje+Rna8OsFii6u7tVVKoEWtIoqOhLtJLL1BJsYy9XsKopRYv9nAmPCG qgKPUQMU0olET++2pQYPSDyJ/1JDbfWbzi0OOZumkoN0JrfBchN9PDp7k2vY3twO kRLLBf6LY9z2iJS58voFvfGzlS8HUHlcCyUPLUirTOd/M/JPR1B1DVmhfh3gFBmO DaWeRz/0a3o1pPzY8gEyko3w9PelA8s+L7UFXEmbTWHqUCBdcGc= =cKb8 -END PGP SIGNATURE- ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Accepted gitlab-ci-multi-runner 10.5.0+dfsg-1 (source amd64) into experimental, experimental
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 21 Mar 2018 11:59:10 +1100 Source: gitlab-ci-multi-runner Binary: gitlab-runner Architecture: source amd64 Version: 10.5.0+dfsg-1 Distribution: experimental Urgency: medium Maintainer: Debian Go Packaging Team <pkg-go-maintainers@lists.alioth.debian.org> Changed-By: Dmitry Smirnov <only...@debian.org> Description: gitlab-runner - GitLab Runner - runs continuous integration (CI) jobs Changes: gitlab-ci-multi-runner (10.5.0+dfsg-1) experimental; urgency=medium . * New upstream release [February 2018]. * Build-Depends: - golang-github-codegangsta-cli-dev + golang-github-urfave-cli-dev + golang-github-go-ini-ini-dev + golang-github-mattn-go-zglob-dev * Renamed binary package: gitlab-ci-multi-runner --> gitlab-runner. * rules: set/embed package VERSION. Checksums-Sha1: 331965c58fb4dda1c42f5ec38103fcc69dc4e1f0 3732 gitlab-ci-multi-runner_10.5.0+dfsg-1.dsc eb90a40a9beac8b86c7e801cdb1e2db3e16de9c9 997820 gitlab-ci-multi-runner_10.5.0+dfsg.orig.tar.xz b88ef078f65c1f7f9d6cc32566ec16693970121f 15344 gitlab-ci-multi-runner_10.5.0+dfsg-1.debian.tar.xz e5bf7e7e667ee3ea73aca44cc9ecd682e577e25f 21183 gitlab-ci-multi-runner_10.5.0+dfsg-1_amd64.buildinfo a25ae4281ff1687f90d32b3bfa2e8344b33dc17c 4368916 gitlab-runner-dbgsym_10.5.0+dfsg-1_amd64.deb cdf1070003c0ee464c3dc57998dcaaab41850329 7586696 gitlab-runner_10.5.0+dfsg-1_amd64.deb Checksums-Sha256: 56f2f4be00854e1f5febc814ceff13422352b331081025293b693c486b637422 3732 gitlab-ci-multi-runner_10.5.0+dfsg-1.dsc 6bd855dc5fa0a6f32bda61fba92859ceeb832b758d06e1d21ec378e4f27a5be7 997820 gitlab-ci-multi-runner_10.5.0+dfsg.orig.tar.xz e547c48d19a15523bc1964b7f585a7849bcfbbe067e29a1f5298e6863fe95193 15344 gitlab-ci-multi-runner_10.5.0+dfsg-1.debian.tar.xz 81e86e5fd853a3fdb3fee1bbd5608f8c7e35a1722465439df759e03563ee4c4e 21183 gitlab-ci-multi-runner_10.5.0+dfsg-1_amd64.buildinfo f4031e926efb967e9e908e3b8c6a3cb467529dd82d048a7a821ed46c458a1d91 4368916 gitlab-runner-dbgsym_10.5.0+dfsg-1_amd64.deb 58ba00d6bba26ce55c7d00527835e6e56475f33a0ef64f763d4d4569d33597c6 7586696 gitlab-runner_10.5.0+dfsg-1_amd64.deb Files: e8ad4c454ceb046ff5c54b110fba8a8e 3732 devel optional gitlab-ci-multi-runner_10.5.0+dfsg-1.dsc 859da3b53b0bac4f25904377e4c32677 997820 devel optional gitlab-ci-multi-runner_10.5.0+dfsg.orig.tar.xz 0d9ffb74493dd56568824f100745e5fb 15344 devel optional gitlab-ci-multi-runner_10.5.0+dfsg-1.debian.tar.xz 7593bac0d7bdd050c66a62df69542f28 21183 devel optional gitlab-ci-multi-runner_10.5.0+dfsg-1_amd64.buildinfo 40c1d463af8d20adf46fa291896583ee 4368916 debug optional gitlab-runner-dbgsym_10.5.0+dfsg-1_amd64.deb e0304dc0eec85d4946fa7f6e9cd52406 7586696 devel optional gitlab-runner_10.5.0+dfsg-1_amd64.deb -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEULx8+TnSDCcqawZWUra72VOWjRsFAlqy/EcACgkQUra72VOW jRtHwg/+P8DfBclWO0Ckjwja87opEd7c1thgQZMtPDikVFW6f/TYQvmUCU4juWHd wwQB4ZSlHoJ9GBnvkfzMpedWl2+BZ63gVDO8f5ojpxFsrKtKxBxuUSKpAhsxoiBD NFViHjjZVCHap3BewadpyIJD7GCHdqwPD+pvCuzS31+RbDfhcpSezLrQQCzbLRCN ZM35MEDrKPjSTB6+YkfhGD/mK4Yb1JY70PbQAjIjOkP4qcBwP5XA7mjpCbn64Hcb 3P3J6LDnBYBjLsP854LsbNYgCE3ls5wBMq5jePu3F4uIZLGsB36Qd/s0aHxnQ1zZ h5QJFSl8Ue5vEsGXO8v28/SUWX8i4mnvM9/8b1pOGtta2KER8wQ2yBz7/kEgo5hd EenMz6ubz6WUWDM1P+2vv6Dtkw1WKDc9Vaeq5vmVccnFgJCc2nx3wyp95eHNcANP cxirXubkLeLBWD5meQFjjmMY3qWYmwtMGuHx8JJSYTsFKWKPlJayoxQ/cjja5RRB mSsowx8cx6tzv/iG2lShLnwPYhInddpiScrqKeB4im1zcECUcXVNn835UWl0VjFQ 1upyLo0eVJIh/CEUMsMbYnzN2tOnN4jWMRHH0lMjWo2rq4Jh2u+m+tnRhUaJnfif OpFVN/77ErysH8v0VSCIPhT8hJKOdNupQQx5mZLHDbQqSt/aEWA= =CI9z -END PGP SIGNATURE- ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#893680: gitaly: arch-dep-package-has-big-usr-share
Package: gitaly Version: 0.91.0+debian-1 Severity: important "gitaly" is not a -dev package therefore it should not install "usr/share/gocode" folder with all its sources and vendored deps. All the best, Dmitry Smirnov. --- If liberty means anything at all, it means the right to tell people what they do not want to hear. -- George Orwell signature.asc Description: This is a digitally signed message part. ___ 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] Accepted gitlab-ci-multi-runner 9.5.1+dfsg-2 (source amd64) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 19 Mar 2018 22:13:11 +1100 Source: gitlab-ci-multi-runner Binary: gitlab-ci-multi-runner Architecture: source amd64 Version: 9.5.1+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team <pkg-go-maintainers@lists.alioth.debian.org> Changed-By: Dmitry Smirnov <only...@debian.org> Description: gitlab-ci-multi-runner - GitLab Runner Changes: gitlab-ci-multi-runner (9.5.1+dfsg-2) unstable; urgency=medium . * Upload to unstable. * New patch to fix FTBFS on mips. * Updated URLs in "bug-presubj". * Build-Depends: - golang-github-docker-docker-dev * golang-github-docker-distribution-dev (>= 2.6.2~) * golang-github-docker-go-connections-dev (>= 0.3.0~) * golang-github-docker-docker-credential-helpers-dev (>= 0.5.0~) * NEWS file updated with link to snapshot.debian.org where GitLab v8 - compatible runner v1.11.4 packages can be found. Checksums-Sha1: 2742c2dde68cd22ac1fe089af8d8a00d2397f11f 3684 gitlab-ci-multi-runner_9.5.1+dfsg-2.dsc 7f94919a908d0b6efcc582664842d7f7088a7dbd 14876 gitlab-ci-multi-runner_9.5.1+dfsg-2.debian.tar.xz 7942ea106d24e1b63a98b5a99d5c87325add6e70 4363780 gitlab-ci-multi-runner-dbgsym_9.5.1+dfsg-2_amd64.deb a80e9bffe3c72ab8c818a1372901344018db33df 21169 gitlab-ci-multi-runner_9.5.1+dfsg-2_amd64.buildinfo 74d04e63fbf66aeb7161afb821f608d80b69a325 7553348 gitlab-ci-multi-runner_9.5.1+dfsg-2_amd64.deb Checksums-Sha256: aab49d25ad5f294cc03d3f270c797a02f21cdd0314b4f3203f1d7e5665f1eeb4 3684 gitlab-ci-multi-runner_9.5.1+dfsg-2.dsc d95dd87c837ca28796326b0e40cca561ccb4ec86dccd0b04f9f5e751a388911b 14876 gitlab-ci-multi-runner_9.5.1+dfsg-2.debian.tar.xz bb96b78bc818833e328cf4b6a11d6d7eec07914f066ff1656e2f7c9797b06298 4363780 gitlab-ci-multi-runner-dbgsym_9.5.1+dfsg-2_amd64.deb 8c22a63c6f900d9dd5a10537aeaa1560d5b9e0fab1e456357c77b9fc678e6812 21169 gitlab-ci-multi-runner_9.5.1+dfsg-2_amd64.buildinfo 7407b5461c2b6a742ecfa8a4c8fd550deeaea6b57ddcf75e513e155c42aa9702 7553348 gitlab-ci-multi-runner_9.5.1+dfsg-2_amd64.deb Files: ca8aa35900fca145f7d8f8a38cdf39ff 3684 devel optional gitlab-ci-multi-runner_9.5.1+dfsg-2.dsc 94f61cfc5852be224c4279f1872fd5d0 14876 devel optional gitlab-ci-multi-runner_9.5.1+dfsg-2.debian.tar.xz 560424d32dbefa9720f29c238b46e0f4 4363780 debug optional gitlab-ci-multi-runner-dbgsym_9.5.1+dfsg-2_amd64.deb d35707bf1fee8cc07ddcfe66e728baef 21169 devel optional gitlab-ci-multi-runner_9.5.1+dfsg-2_amd64.buildinfo a9771350f0580e1e96fe6f17527702e2 7553348 devel optional gitlab-ci-multi-runner_9.5.1+dfsg-2_amd64.deb -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEULx8+TnSDCcqawZWUra72VOWjRsFAlqvnIYACgkQUra72VOW jRvadQ//YNlOyePk9NsJ2HNVJpJGuaY87ucWdano9rzLEx7aBUpBB/nqYEzOHhW7 7y4yloGdXcAeKNRsszoG1tUCxmn9ZncfKBjb+78g1X7vveKUqfamMhdkHH/NT9bb DeYBEHlZe53bj3uH6H2EAijGYRbIAOpjRFMF20s47p/c3TDm7z8BxDYU0zPyAZeP SO/QPTpiTBIYH6DQsGYWBwzJn7HD+jnWURqaUMgrQ2ILhizoXRffABme6kAFkaq2 ZCc408HSypm/5tEdx9lCc6gsSNPUaVpZX8vDd0StH9nDllGpjvd8HJJUDj2xGJix 02jckloPC3rZhERwmLhn4o0SIolwcVIQwgG74JDFbJJtOr+HpQ95QaIvm/BtZNyk gbtwG7HDboVYmYl1+IFjRYNZ+JV5c3pAnwlRPrbuqKBLRv1WuCpKC0b+BY4az/K8 mbtRFx1UhY/F7I46TKU2TL8ktRi817cwvqnsvZb6bOi1O6hbiOaIDKi8Mf1E5Zes nXabUMb7eyf7N55F/tseQfWVa/QGvYDa957mz4mvtYbxMUcVxegoDLK8pHd4KOAi jyr8soZC7nWVYVNL1UnTr4I0vVj2jzeOuuA/6rRavRYJPACqJc00vLc7WFpk3UAh o/lA0RlpEKaKvXaPl8eNSBaeQV8M08d3ryQ++4Sk9y3DUrZ/Nps= =I39l -END PGP SIGNATURE- ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Accepted gitlab-ci-multi-runner 9.5.1+dfsg-1 (source amd64) into experimental
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 18 Mar 2018 13:37:52 +1100 Source: gitlab-ci-multi-runner Binary: gitlab-ci-multi-runner Architecture: source amd64 Version: 9.5.1+dfsg-1 Distribution: experimental Urgency: medium Maintainer: Debian Go Packaging Team <pkg-go-maintainers@lists.alioth.debian.org> Changed-By: Dmitry Smirnov <only...@debian.org> Description: gitlab-ci-multi-runner - GitLab Runner Closes: 891279 891739 Changes: gitlab-ci-multi-runner (9.5.1+dfsg-1) experimental; urgency=medium . * New upstream release [October 2017]. * Build-Depends: + golang-github-azure-go-ansiterm-dev + golang-github-gorilla-context-dev + golang-github-hashicorp-go-version-dev + golang-github-vbatts-tar-split-dev + golang-github-gorilla-mux-dev + golang-github-docker-docker-credential-helpers-dev + golang-github-emicklei-go-restful-swagger12-dev - golang-github-opencontainers-runc-dev + golang-github-opencontainers-docker-runc-dev - golang-github-stretchr-testify-dev + golang-github-stretchr-testify-dev (>= 1.2.1~) * Priority: optional * Standards-Version: 4.1.3 * debhelper & compat to versions 11. * Use "vendor/github.com/opencontainers/runtime-spec" to fix FTBFS. * New "swagger.patch" to fix FTBFS (Closes: #891279). * Updated Homepage URL. * rules: + remove all .generated.go files (Closes: #891739). + removed calls to dpkg-parsechangelog. + added "DH_GOLANG_GO_GENERATE := 1". * watch file is fixed and updated for new upstream repository location. Checksums-Sha1: 867eb3fdc1ffddcf2d47c6ee5d0f0a50d513dbb6 3681 gitlab-ci-multi-runner_9.5.1+dfsg-1.dsc a4779d1acf5561a4df5b14aba1eb245485780192 973040 gitlab-ci-multi-runner_9.5.1+dfsg.orig.tar.xz b0b1d327e0199df8f36e41fb3c6814268dc458ae 14524 gitlab-ci-multi-runner_9.5.1+dfsg-1.debian.tar.xz 2b987fe1f57bb7ce1c08ee75c03d72c7f5b7262c 4362088 gitlab-ci-multi-runner-dbgsym_9.5.1+dfsg-1_amd64.deb 8b9777b2bbfab690d5fd6b993e9ee1d4d3eac23a 21169 gitlab-ci-multi-runner_9.5.1+dfsg-1_amd64.buildinfo d51fe4e37cd45cd6b3d4435e2f7bff765848c91b 7550276 gitlab-ci-multi-runner_9.5.1+dfsg-1_amd64.deb Checksums-Sha256: e770edf321563dc81204076b58962d673dbad1dd0b5d6f722c0e6f6812248872 3681 gitlab-ci-multi-runner_9.5.1+dfsg-1.dsc 6a54ec8e6866bd8304825d0e1c271d805c98c9a54a1740fca1a69131c3fae1e8 973040 gitlab-ci-multi-runner_9.5.1+dfsg.orig.tar.xz 2c226f8fc805551a80dd8dd1b6ed82d7ba342aa3d6f1d3c64ea9f642c88b8188 14524 gitlab-ci-multi-runner_9.5.1+dfsg-1.debian.tar.xz 0b94b01f3387c9db9cf673c503306f48dac7e9dcb88300885bbdfd62a30a52d8 4362088 gitlab-ci-multi-runner-dbgsym_9.5.1+dfsg-1_amd64.deb 148a9ce9040bfe0bd183e3c59b79be1cf483db62de365b0475cb9edf276defc2 21169 gitlab-ci-multi-runner_9.5.1+dfsg-1_amd64.buildinfo fc36bb9d378fc6876bfdf6135468bb2cbf3955de095f9309754c1a1a36a8fc70 7550276 gitlab-ci-multi-runner_9.5.1+dfsg-1_amd64.deb Files: 565dd726cb6a81cf80c9ad249f6443cc 3681 devel optional gitlab-ci-multi-runner_9.5.1+dfsg-1.dsc 94ab5bb17045e80444802943ffe68698 973040 devel optional gitlab-ci-multi-runner_9.5.1+dfsg.orig.tar.xz 001074ad5880ee9b0cfddb5e018c76e8 14524 devel optional gitlab-ci-multi-runner_9.5.1+dfsg-1.debian.tar.xz e1f990320363caeb50a9ebd55ab39259 4362088 debug optional gitlab-ci-multi-runner-dbgsym_9.5.1+dfsg-1_amd64.deb d198db5fe17a8c30ccba4693a7889acf 21169 devel optional gitlab-ci-multi-runner_9.5.1+dfsg-1_amd64.buildinfo 2f8472cdb0a2ce7dd4523288ffd41b6a 7550276 devel optional gitlab-ci-multi-runner_9.5.1+dfsg-1_amd64.deb -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEULx8+TnSDCcqawZWUra72VOWjRsFAlqt0+wACgkQUra72VOW jRsOVQ//eA3QsCJniNEr6Kg3neaYVFVPd8JAlzMiKP6CboJqF43/2mDJ8c5FNnMn Rd2SbeM5voKtetQ2O5wLl7Mzu8FTlrXXrMXYwBsjtgLRCF5sJ/d+8lHrUc0z3+Wb uGD+TYexMFXrFAfq31PMeCpmAK+6dnju/G47ishGhH2VsMi0KLPEntZ7cG/fDSFx aDCCu9rPDD9jlVu/GPXNG0hHAvvMerh6iQMd7r5j4zw+mmLNKCzqEHd7zjeymMtr aTOo8aUJ02MHiLWoyNl71RXBK7+DImpwVSA/+YprkfEUzg2WCau91TO7pH5kCyot yZOTkJQJ9K/5zL8mzEN6dYBa8eproBK+iUkDYquJ+0/uHGiLV+pLjlbTVOvhi//M An9qtfp3BW3YKb/RzavbkZDNtKCYDrwda6NeEpabmqEqGr9gUt1gf94u1x9Plq27 emObgZy1GnFdl4UcitKgRM6I1fga2YG/ftvhw/3FlZ+Za8VfSu65EDugR5V6SH+p cG76+YmVqAqZHioP0QR+KTkd3UgHkrfbZJeQZ1Cl8fSjYSJNPPtt56ZTwkhsmwON HNzibxq9JKc/67WdiJxy8438l/M9set3KuiuxxCNsgUPEfdAhZG2f1Ii3Mpf+WPv qQDWc9SHFQfnyDy5z22YAvoeTH1p7Vr1t+b4931/prHql5+VcuI= =Qsqg -END PGP SIGNATURE- ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#892921: O: docker-swarm -- Docker's native clustering system
Package: wnpp Severity: normal X-Debbugs-CC: pkg-go-maintainers@lists.alioth.debian.org Control: affects -1 docker-swarm I have neither capacity nor motivation left to maintain "docker-swarm"... Maintaining this package requires time and skills. Please only adopt this package if you will have enough time and attention to work on it. If you want to be the new maintainer, please see [1] for detailed instructions how to adopt a package properly. [1]: https://www.debian.org/devel/wnpp/index.html#howto-o -- Regards, Dmitry Smirnov. signature.asc Description: This is a digitally signed message part. ___ 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#878059: ITP: golang-github-emicklei-go-restful-swagger12 -- Swagger extension to the go-restful package
Package: wnpp Severity: wishlist Owner: Dmitry Smirnov <only...@debian.org> X-Debbugs-CC: debian-de...@lists.debian.org, pkg-go-maintainers@lists.alioth.debian.org Control: block 871078 by -1 Package name: golang-github-emicklei-go-restful-swagger12 Version: 1.0.1 Upstream Author: Ernest Micklei License: Expat URL: https://github.com/emicklei/go-restful-swagger12 Vcs-Browser: https://anonscm.debian.org/cgit/pkg-go/packages/golang-github-emicklei-go-restful-swagger12.git Description: Swagger extension to the go-restful package Swagger 1.2 extension to the "golang-github-emicklei-go-restful-dev" package. --- This library has been split from "golang-github-emicklei-go-restful-dev" that no longer provides "swagger" since 2.4.0 causing FTBFS of at least one package... signature.asc Description: This is a digitally signed message part. ___ 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] Minutes for the DebConf17 BoF
On Tuesday, 15 August 2017 11:02:39 PM AEST Michael Stapelberg wrote:
> 6. I have come to appreciate pristine-tar, as it is the only reliable way
> (that I know of) to prepare uploads for packages which already have their
> orig tarball in Debian.
Then perhaps you should learn about `origtargz` utility from devscripts.
Also you can use
apt(-get) source {packagename}
to fetch uploaded package with tarball.
> I’d suggest we codify that pristine-tar is a requirement.
I found it disturbing and depressing to read proposals to enforce pristine-
tar workflow here and there...
IMHO pristine-tar is counter productive and maintaining it requires extra
effort. It should not be made mandatory just like GBP should not be required
to maintain Debian packages.
I'll expand further in separate email when I can...
Regards,
Dmitry Smirnov.
---
The truth is incontrovertible, malice may attack it, ignorance may deride
it, but in the end; there it is.
-- Winston Churchill
signature.asc
Description: This is a digitally signed message part.
___
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#852300: RM: fleet -- ROM; obsolete
Package: ftp.debian.org Severity: normal X-Debbugs-CC: timothy.pot...@hpe.com,pkg-go-maintainers@lists.alioth.debian.org Please remove source package "fleet" from "unstable". Fleet became obsolete as it was abandoned by upstream. Moreover currently Fleet is affected by FTBFS but considering its unmaintained state upstream Fleet is probably not worth time spent on it... -- Cheers, Dmitry Smirnov GPG key : 4096R/52B6BBD953968D1B --- Perhaps is is better to be irresponsible and right, than to be responsible and wrong. -- Winston Churchill signature.asc Description: This is a digitally signed message part. ___ 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#848316: Bug#848316: etcd: I saw that A new upstream version is available: 3.0.15 - Is this possible to upgrade ?
On Thursday, 19 January 2017 10:41:23 AM AEDT TFAUCK wrote: > Initially I thought that maintainers of etcd 2.0 which are also > maintainers for packages relative to go were going to do it, but I may > be wrong there. I'm not sure what are you trying to say... Maintainers (upstream developers) of Etcd are not maintainers of Debian package... > I can work with the package upgrade and submit the debdiff if that's the > idea ? Whatever you can do to help is welcome. I suggest to start working on dependency packages -- that's where usual >90% of effort will be spent... -- Best wishes, Dmitry Smirnov. --- To predict the behavior of ordinary people in advance, you only have to assume that they will always try to escape a disagreeable situation with the smallest possible expenditure of intelligence. -- Friedrich Nietzsche signature.asc Description: This is a digitally signed message part. ___ 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#848316: Bug#848316: etcd: I saw that A new upstream version is available: 3.0.15 - Is this possible to upgrade ?
On Friday, 13 January 2017 1:57:33 PM AEDT TFAUCK wrote: > So what do we do for that issue ? Hopefully fix it eventually by updating "etcd" package... > who's going to decide if there is a > need for new package or just and upgrade ? That would be me... :) The matter is quite simple: if my understanding is correct, upstream no longer support Etcd v2... The question is only who is going to update the package and when. Why do you think we need two packages and who is going to maintain 'em? -- All the best, Dmitry Smirnov. signature.asc Description: This is a digitally signed message part. ___ 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#848316: Bug#848316: etcd: I saw that A new upstream version is available: 3.0.15 - Is this possible to upgrade ?
On Wednesday, 4 January 2017 12:03:44 AM AEDT Potter, Tim wrote: > Hi there. I've currently got someone working on a etcd3 package - still > tossing up whether to create a new binary package and keep etcd as > implicitly version 2 only. That's what I'm leaning to at the moment. I think we should just upgrade etcd v2 --> v3 without making any new packages. -- All the best, Dmitry Smirnov. --- The belief in a supernatural source of evil is not necessary; men alone are quite capable of every wickedness. -- Joseph Conrad signature.asc Description: This is a digitally signed message part. ___ 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#846799: Pending fixes for bugs in the golang-google-cloud package
Hi Martín,
On Friday, 16 December 2016 6:36:18 PM AEDT pkg-go-
maintain...@lists.alioth.debian.org wrote:
> The full diff can be seen at
> https://anonscm.debian.org/cgit/pkg-go/packages/golang-google-cloud.git/com
> mit/?id=2262e13
>
> Commit message:
>
> Ensure the transition from symlink to directory is handled correctly.
> Closes: #846799
Thanks for fixing this problem. FYI there is a better way to do that.
Instead of duplicated section in preinst/postinst/postrm you can use one
"{PKGNAME}.maintscript" file with "symlink_to_dir" line.
See dpkg-maintscript-helper(1) for details.
I hope you'll find it handy.
--
All the best,
Dmitry Smirnov.
---
You have to start with the truth. The truth is the only way that we can
get anywhere. Because any decision-making that is based upon lies or
ignorance can't lead to a good conclusion.
-- Julian Assange, 2010
signature.asc
Description: This is a digitally signed message part.
___
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#846799: golang-google-cloud: fails to upgrade
Source: golang-google-cloud Version: 0.0~git20160615-6 Severity: serious `apt-get upgrade` failed as follows: The following packages will be upgraded: golang-google-cloud-compute-metadata-dev golang-google-cloud-dev 2 upgraded, 0 newly installed, 0 to remove and 10 not upgraded. Need to get 0 B/243 kB of archives. After this operation, 1,281 kB of additional disk space will be used. Do you want to continue? [Y/n] Reading changelogs... Done (Reading database ... 1104869 files and directories currently installed.) Preparing to unpack .../0-golang-google-cloud-dev_0.0~git20160615-6_all.deb ... Unpacking golang-google-cloud-dev (0.0~git20160615-6) over (0.0~git20160615-5) ... dpkg: error processing archive /tmp/apt-dpkg-install-Q8qBLL/0-golang-google-cloud-dev_0.0~git20160615-6_all.deb (--unpack): unable to open '/usr/share/gocode/src/google.golang.org/cloud/bigquery/bigquery.go.dpkg-new': No such file or directory Preparing to unpack .../1-golang-google-cloud-compute-metadata-dev_0.0~git20160615-6_all.deb ... Unpacking golang-google-cloud-compute-metadata-dev (0.0~git20160615-6) over (0.0~git20160615-5) ... dpkg: error processing archive /tmp/apt-dpkg-install-Q8qBLL/1-golang-google-cloud-compute-metadata-dev_0.0~git20160615-6_all.deb (--unpack): unable to open '/usr/share/gocode/src/google.golang.org/cloud/compute/metadata/metadata.go.dpkg-new': No such file or directory Errors were encountered while processing: /tmp/apt-dpkg-install-Q8qBLL/0-golang-google-cloud-dev_0.0~git20160615-6_all.deb /tmp/apt-dpkg-install-Q8qBLL/1-golang-google-cloud-compute-metadata-dev_0.0~git20160615-6_all.deb -- Regards, Dmitry Smirnov GPG key : 4096R/52B6BBD953968D1B --- Journalism is printing what someone else does not want printed: everything else is public relations. -- George Orwell signature.asc Description: This is a digitally signed message part. ___ 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#842380: gitlab-ci-multi-runner: mk-prebuilt-images.sh fails at install time
Hi Vincent,
Sorry it took so long for me to get back to this problem...
On Sunday, 30 October 2016 3:03:19 PM AEDT Vincent Danjean wrote:
> So, I will try to argue a little bit more ;-)
:)
> Do you try the cdebootstrap command itself?
Yes, through mk-prebuilt-images.sh and directly during development of mk-
prebuilt-images.sh. It actually works with cdebootstrap v0.6.4 but not with
later versions...
> Setting up gitlab-ci-multi-runner (1.7.1+dfsg-1) ...
> W: Docker is not available.
Docker is required to generate image...
> atsina:/tmp/test# cdebootstrap \
> --flavour=minimal \
> --exclude="dmsetup,e2fsprogs,init,systemd-sysv,systemd,udev" \
> --include="bash,ca-certificates,git,netcat-traditional" \
> stable ./debian-minbase |& tee /tmp/log
> P: Retrieving Release
> P: Retrieving Release.gpg
> [...]
> P: Configuring helper cdebootstrap-helper-apt
> E: Internal error: install
This may suggest an error in cdebootstrap...
I see you've already reported #842579 against cdebootstrap -- thank you.
> Do the cdebootstrap command really works on your systems?
It was working just a few days ago...
> I also tried to remove this file. mk-prebuilt-images.sh recreates
> a (not working) one.
That may give us a clue why it is happening... Do you have enough disk space
on the box? Maybe exporting/compressing image runs out of disk space and
produce invalid file as result?
Anyway I've found a bug that may result in incomplete images because bash
ignores errors in comands used with pipe even with "set -e". I've just
uploaded fix for that ("set -o pipefail").
> In this case, please remove the bad gitlab-runner-prebuilt.tar.xz
> Or ask the user to re-create it with a --force parameter to
> mk-prebuilt-images.sh if he wants to keep a probably problematic
> image.
Noted. I'll think about it. Thanks.
For now I've made some changes that should make image generation more
reliable. Hopefully "--force" won't be necessary.
Thanks again for your help, feedback and testing, Vincent.
Just uploaded 1.7.1+dfsg-2 should fix this problem.
--
Cheers,
Dmitry Smirnov.
---
What is the truth, but a lie agreed upon.
-- Friedrich Nietzsche
signature.asc
Description: This is a digitally signed message part.
___
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#836388: Bug#836388: When cache is present, job run from incorrect working directory
Hi Sam, On Friday, 2 September 2016 10:01:14 AM AEST Sam Hartman wrote: > If a job includes a cache, then it appears that the initial working > directory is some directory inside the cache, *not* the top of the > project directory. This problem could be related to #838012 that was fixed in 1.5.3. Could you please try again to check if this problem is still there? Thanks. -- All the best, Dmitry Smirnov. --- It is a fine thing to be honest, but it is also very important to be right. -- Winston Churchill signature.asc Description: This is a digitally signed message part. ___ 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#838011: gitlab-ci-multi-runner - No gitlab-runner-prebuilt.tar.xz
On Friday, 16 September 2016 1:50:15 PM AEST Bastian Blank wrote: > Severity: important What about (inflated?) severity? > A clean installation using docker.io fails every build with a missing > gitlab-runner-prebuilt.tar.xz. What do you mean? Installation gitlab-runner? > Please fail during startup so this > condition is properly logged in system log and not build log sent to the > user. I'm not sure I follow you... Even if Docker is installed to host, gitlab- runner may be configured with "shell" executor which requires no prebuilt image... -- All the best, Dmitry Smirnov. --- How would your relationships change if you resolved never to lie again? What truths about yourself might suddenly come into view? What kind of person would you become? And how might you change the people around you? It is worth finding out. -- Sam Harris, Lying signature.asc Description: This is a digitally signed message part. ___ 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#836388: Bug#836388: When cache is present, job run from incorrect working directory
On Saturday, 3 September 2016 6:43:05 AM AEST Sam Hartman wrote: > ...but I'm really > frustrated when I am told to "discuss with upstream." Too bad. Debian bug tracker is not a substitute to upstream one. If you had a chance to check upstream bug reports there are chances you could have found more information about the problem from existing bug reports... Of course it make sense to check Debian bug tracker first. > We, Debian, have > agreed to provide a coherent operating system that works together. > Part of what we sign up to do when we agree to maintain packages is to > do a fair bit of upstream coordination. Debian is mostly an integration project. We do not do (much) upstream development here. Therefore if your problem is about upstream features/ functionality then the right place to discuss it is at the upstream bug tracker. Also you can avoid delays and reduce maintenance burden by discussing the matter with upstream who have more expertise and more users who might be experiencing the same problem. > I don't know where the upstream bug tracker is. I don't have an account > there. https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/issues You do not need an account to check existing bug reports. > I don't wish to get an account there. Fair enough. > I don't wish to evaluate whether > Debian has applied patches that matter in this space. To some extent this problem exists even on pristine latest release as upstream not always indicates which version fixes the problem... > But the agreement we make to our users is that we provide a single > consistent interface for them to report bugs. I've never blamed you for opening a bug. What are you complaining about? > If you don't have the skills to work on this issue it's entirely > reasonable to forward it upstream. Which takes time. Besides forwarding bugs is not an effortless thing. One have to validate the problem and clearly describe it with reproducer. It could be that I'm just too tired (or don't have enough experience) but from your bug report I could not understand the problem nor to find out clear reproducer or get what desirable behaviour would be... It might take weeks before I'll be able to get to this problem and the situation is such that you are more likely to find help upstream. gitlab-ci-multi-runner is still a young package so you'd be lucky to get help from another Debian user. > It's also greatly appreciated that you let me know that if I want a > faster response I might want to deal with upstream directly. Sorry for not being able to be more helpful with this problem... -- Best wishes, Dmitry Smirnov. --- There is no society in human history that ever suffered because its people became too reasonable. -- Sam Harris signature.asc Description: This is a digitally signed message part. ___ 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#836388: Bug#836388: When cache is present, job run from incorrect working directory
On Friday, 2 September 2016 10:01:14 AM AEST Sam Hartman wrote: > If a job includes a cache, then it appears that the initial working > directory is some directory inside the cache, *not* the top of the > project directory. Please discuss upstream. From the description of the problem I'd say it is an upstream issue. I don't understand the problem well enough to help. Besides it may be worth trying the latest version... Thanks. -- Regards, Dmitry Smirnov. --- Democracy is a pathetic belief in the collective wisdom of individual ignorance. -- H. L. Mencken signature.asc Description: This is a digitally signed message part. ___ 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#835269: ITP: golang-github-circonus-labs-circonus-gometrics -- Golang implementation of metrics reporting for Cirocnus
Package: wnpp Severity: wishlist Owner: Dmitry Smirnov <only...@debian.org> X-Debbugs-CC: debian-de...@lists.debian.org, pkg-go-maintainers@lists.alioth.debian.org Control: affects -1 nomad Package name: golang-github-circonus-labs-circonus-gometrics Version: 0.0~git20160822 Upstream Author: Circonus, Inc. License: BSD-3-Clause URL: https://github.com/circonus-labs/circonus-gometrics Description: Golang implementation of metrics reporting for Cirocnus Circonus metrics tracking for Go applications. This library supports named counters, gauges and histograms. It also provides convenience wrappers for registering latency instrumented functions with Go's builtin http server. signature.asc Description: This is a digitally signed message part. ___ 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#835161: Bug#835161: Upgrade to a version supporting "v2"
On Tuesday, 23 August 2016 9:03:52 AM AEST Vincent Bernat wrote: > (or maybe upstream could tag a version). Please request a new tag upstream. Last time upstream kindly tagged 0.2 for us... :) Thanks. -- Cheers, Dmitry Smirnov. --- A wise man proportions his belief to the evidence. -- David Hume, "An Inquiry Concerning Human Understanding" signature.asc Description: This is a digitally signed message part. ___ 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#834702: ITP: golang-github-circonus-labs-circonusllhist -- implementation of Circonus log-linear histograms
Package: wnpp Severity: wishlist Owner: Dmitry Smirnov <only...@debian.org> X-Debbugs-CC: debian-de...@lists.debian.org, pkg-go-maintainers@lists.alioth.debian.org Package name: golang-github-circonus-labs-circonusllhist Version: 0.0~git20160526 Upstream Author: Circonus, Inc License: BSD-3-Clause URL: https://github.com/circonus-labs/circonusllhist Description: implementation of Circonus log-linear histograms A Golang implementation of Circonus log-linear histograms. signature.asc Description: This is a digitally signed message part. ___ 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#834384: ITP: golang-github-jamesclonk-vultr -- Vultr API client library
Package: wnpp Severity: wishlist Owner: Dmitry Smirnov <only...@debian.org> X-Debbugs-CC: debian-de...@lists.debian.org, pkg-go-maintainers@lists.alioth.debian.org Package name: golang-github-jamesclonk-vultr Version: 1.9 Upstream Author: Fabio Berchtold License: Expat URL: https://github.com/JamesClonk/vultr Description: Vultr API client library Vultr (https://www.vultr.com) API client library, written in Go. signature.asc Description: This is a digitally signed message part. ___ 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#834377: ITP: golang-golang-x-time -- Go supplementary time packages
Package: wnpp Severity: wishlist Owner: Dmitry Smirnov <only...@debian.org> X-Debbugs-CC: debian-de...@lists.debian.org, pkg-go-maintainers@lists.alioth.debian.org Package name: golang-golang-x-time Version: 0.0~git20160202 Upstream Author: The Go Authors License: BSD-3-Clause~Google URL: https://golang.org/x/time/rate Description: Go supplementary time packages Supplementary Go time packages. signature.asc Description: This is a digitally signed message part. ___ 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#833422: ITP: gitlab-ci-multi-runner -- GitLab Runner
Package: wnpp Severity: wishlist Owner: Dmitry Smirnov <only...@debian.org> X-Debbugs-CC: debian-de...@lists.debian.org, pkg-go-maintainers@lists.alioth.debian.org, prav...@debian.org Control: affects -1 gitlab Package name: gitlab-ci-multi-runner Version: 1.4.1 Upstream Author: GitLab B.V.; Kamil Trzciński <ayu...@ayufan.eu> License: Expat URL: https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/ Vcs-Browser: https://anonscm.debian.org/cgit/pkg-go/packages/gitlab-ci-multi-runner.git Description: GitLab Runner GitLab Runner runs tests and sends the results to GitLab. GitLab Continuous Integration (CI) service (included with GitLab) coordinates the testing. signature.asc Description: This is a digitally signed message part. ___ 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#832081: ITP: golang-github-miekg-dns --
Hi Nicolas, On Friday, 22 July 2016 12:31:10 AM AEST Nicolas Braud-Santoni wrote: > * Package name: golang-github-miekg-dns We already have this package as "golang-dns-dev". Sometimes it might be useful check library name space using "apt-file search". :) -- Cheers, Dmitry Smirnov. --- Democracy is a pathetic belief in the collective wisdom of individual ignorance. -- H. L. Mencken signature.asc Description: This is a digitally signed message part. ___ 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] golang-codegangsta-cli and upstream branch
On Thursday, 14 July 2016 8:51:10 AM AEST Vincent Bernat wrote: > I am using "gbp import-orig" (with --uscan if possible), Me too. :) > so I don't see > this branch as particularly difficult to maintain. Not too difficult. But quite often it fails on merge to "master"... Also repacking orig tarball and re-importing it with "gbp import-orig" have little value, given the effort. Imported tarballs quickly depreciate and maintenance cost is not negligible. KDE team maintains all their packages without overhead of "upstream" branches. IMHO abandoning "upstream" branches (especially if they are used merely to accommodate imported tarballs) would be particularly beneficial to our team where so many packages need DFSG- cleanup and repackaging. > I would only create it from this point of time. I don't think anybody is > likely to be interested by the complete history. Good idea. > So, I'll wait for Jelmer's opinion before switching to the classic gbp > layout. Thanks. I think he might appreciate that. But if he do not respond for some time please do not hesitate to do the right thing. :) -- Regards, Dmitry Smirnov. --- Good luck happens when preparedness meets opportunity. signature.asc Description: This is a digitally signed message part. ___ 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] golang-codegangsta-cli and upstream branch
On Thursday, 14 July 2016 7:41:22 AM AEST Vincent Bernat wrote: > Otherwise, what should I do? Just create this upstream branch? Or also > rename unstable to master? Yeah, this repository is a mess... I hope someone could rename "unstable" to "master". Perhaps Jelmer could acknowledge if he is all right with this? Personally I wish we didn't have to waste time maintaining "upstream" branch but if team members want it then it would be nice to have it for consistency. I think nobody have "upstream" branch from "codegangsta-cli" -- certainly not with complete history. Re-creating "upstream" branch will be difficult due to collisions with "master" where upstream releases were merged and tagged... "gbp import-dscs --debsnap" would not work so it looks like "upstream" branch would have to mirror upstream repository... -- Cheers, Dmitry Smirnov. --- A casual stroll through the lunatic asylum shows that faith does not prove anything. -- Friedrich Nietzsche signature.asc Description: This is a digitally signed message part. ___ 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] Comments regarding golang-github-cznic-lldb_1.0.1-1_amd64.changes
On Wednesday, 13 July 2016 9:47:12 AM AEST Chris Lamb wrote: > testdata/fortunes.txt has AT copyright nice. please fix on next upload. Committed, thanks. Though I think it is not a copyright attribution but just a fragment of random texts in "fortunes.txt"... I think copyrights for "fortunes.txt" are in corresponding "LICENSE" file... -- Cheers, Dmitry Smirnov. --- Democracy is a pathetic belief in the collective wisdom of individual ignorance. -- H. L. Mencken signature.asc Description: This is a digitally signed message part. ___ 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#830209: Bugs: "accesses the internet during build" -- strongly disagree on severity
On Wednesday, 13 July 2016 9:00:07 AM AEST Chris Lamb wrote: > > We should not trust build script not to access internet. Even pbuilder > > limits network access and build servers should do it as well. > > I think you are confused about these bugs. They are being filed against > packages that attempt network connectiviity but do not FTBFS if those > requests fail, so disabling internet access on buildds is an related but > actually different issue altogether. Makes sense. Thank you. > Furthermore, keeping packages as-is would still leak the privacy of > end-users, deriviates, etc. who are rebuilding packages. Absolutely. -- Regards, Dmitry Smirnov. --- He who cannot obey himself will be commanded. That is the nature of living creatures. -- Friedrich Nietzsche signature.asc Description: This is a digitally signed message part. ___ 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#830209: Bugs: "accesses the internet during build" -- strongly disagree on severity
On Tuesday, 12 July 2016 11:25:00 AM AEST Chris Lamb wrote: > > I was under impression that build servers do not allow internet access. > > They generally do. That certainly makes those bugs more important but also reveals a more serious problem. Is there anything you can do to restrict or limit internet access on buildd servers? We should not trust build script not to access internet. Even pbuilder limits network access and build servers should do it as well. Besides I've just disabled networking test in "franela-goreq" and it was not even trying to access internet -- the particular test in question was accessing unrouteable 10.255.255.1 from private subnet to test timeout -- IMHO not much of a threat even on unrestricted build servers to justify severity "serious" unless we follow the policy to the letter... -- Best wishes, Dmitry Smirnov. --- If liberty means anything at all, it means the right to tell people what they do not want to hear. -- George Orwell signature.asc Description: This is a digitally signed message part. ___ 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#830209: Bugs: "accesses the internet during build" -- strongly disagree on severity
On Tuesday, 12 July 2016 9:45:04 AM AEST Chris Lamb wrote: > Dmitry wrote: > > To me it looks more like bureaucratic exercise is enforcing policy > > This was not my intention and I have already gone out of my way to avoid > such an impression so I apologise if I could have made this clearer. No that's all right, you have nothing to apologize for. :) > I would believe these bugs to be serious, even if Policy was silent on this > issue. I'd say they are serious-ish (in a technical sense) and surely worth fixing yet I still see them as less serious than build failures. I recognize importance of fixing 'em but I can't treat 'em as a matter of urgency like severity "serious" suggests. > > Yes, _optional_ part of the build. ;) We don't have to run 'em but we > > want to. > > You say "yes", but then you directly counter my point - they are an > integral part of the build and upstream. Whilst you can disable the > running of tests, that's something one must go out of the way to do so. I was merely trying to provide some context. > Quality is not something "we kinda want" in Debian and nor should we > conflate the orthogonal ideas of severity and priority - using words like > "rush" make me more than a little nervous. Personally I feel uncomfortable when I receive bug that user submits with higher severity than necessary. Everybody wants their bugs fixed ASAP and surely from submitter prospective it is important to prioritize their bugs because they are affected. Who is the victim here? Build system? Maintainer? It is hard to say who suffers the most from those bugs that you reported. Whist I strive for perfection I also need to make the job done. Those bugs will be fixed as soon as I can (unless team will do it before me) but not sooner than I intend to address bugs that holding someone from doing something... IMHO bug's severity should help maintainer to prioritise properly. > I don't follow what you mean by "build environment is offline", and your > analogy does not seem to apply as the attempts are not futile.. I was under impression that build servers do not allow internet access. If build scripts can access WWW from buildd servers then it would be a much more serious bug. Surely there is corner case of "dpkg-buildpackage" that can be vulnerable to network access during build but even "pbuilder" successfully prevent attempts to access network. Even build logs suggest that packages attempt to access network but fail. I would be much more concerned about the issue if I knew that build environment allows internet access. -- All the best, Dmitry Smirnov. --- Criticism may not be agreeable, but it is necessary. It fulfils the same function as pain in the human body. It calls attention to an unhealthy state of things. -- Winston Churchill signature.asc Description: This is a digitally signed message part. ___ 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#830823: ITP: golang-github-cznic-lldb -- low level database engine
Package: wnpp Severity: wishlist Owner: Dmitry Smirnov <only...@debian.org> X-Debbugs-CC: debian-de...@lists.debian.org, pkg-go-maintainers@lists.alioth.debian.org Control: affects -1 rkt Package name: golang-github-cznic-lldb Version: 1.0.0 Upstream Author: Jan Mercl <0xj...@gmail.com> License: BSD-3-Clause URL: https://github.com/cznic/lldb Vcs-Browser: https://anonscm.debian.org/cgit/pkg-go/packages/golang-github-cznic-lldb.git Description: low level database engine lldb is Golang implementation of a low level database engine. "cznic/lldb" now considered to be mature so it is no longer will be a part of "cznic/ql". signature.asc Description: This is a digitally signed message part. ___ 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#830209: Bugs: "accesses the internet during build" -- strongly disagree on severity
On Monday, 11 July 2016 8:01:30 PM AEST Martín Ferrari wrote: > > Noted. I'm not against fixing the problem but there are more important > > issues to prioritise. > > I think this is not a valid argument. If you believe those issues are the most important ones to fix then be my guest and start addressing them as a matter of priority. You are welcome to work on those issues. Yet you may notice that those problems are not among ones that seriously affect users or other packages hence I don't feel inclined to prioritise them. > Chris is right that the packages > are not following policy, and that they should be fixed. Yes, he is right. Your point? > Packaging all > the world software does not serve our users if we are not following our > procedures. I think understand your implications. I'm doing shitty work, you mean. May I suggest you to maybe shut up? > I have seen already a few instances of packages you prepared where you > just skip the tests, or skip failures, instead of fixing the real > problems these are covering. This is not good for Debian and it is > definitely not good for the team. Thanks for criticism but I really got enough of it from you already. > Please, reconsider your attitude. I'd like to recommend you to do the same. I'm starting to feel pissed off by your rude passive aggressive attitude and nitpicking... -- Regards, Dmitry Smirnov. --- The surest way to corrupt a youth is to instruct him to hold in higher esteem those who think alike than those who think differently. -- Friedrich Nietzsche signature.asc Description: This is a digitally signed message part. ___ 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] [pkg-golang-devel] Security support for packages written in Go
On Monday, 11 July 2016 9:22:12 AM AEST Florian Weimer wrote:
> Hmm. I poked at a few packages, and here is what I found:
> golang-siphash-dev does not have any Built-Using header.
> golang-gopkg-tylerb-graceful.v1-dev does not list golang-x-text,
> although its dependency golang-golang-x-net-dev was built using it.
> (I'm looking at unstable.)
But you are looking at wrong packages. -dev packages are just sources that
strictly speaking are not "built" but more like "validated" on build time.
You do not need to re-build source/-dev packages so they do not have Built-
Using header intentionally. What you need to be looking at is arch:any binary
packages built from go sources involving multiple libraries.
Examples of Golang executables include docker.io, containerd, etcd, grafana,
runc, acbuild, docker2aci, influxdb, rkt, consul, fleet, nomad, skydns,
kubernetes-{node|master|client}, etc.
--
All the best,
Dmitry Smirnov.
---
To swallow and follow, whether old doctrine or new propaganda, is a
weakness still dominating the human mind.
-- Charlotte P. Gilman
signature.asc
Description: This is a digitally signed message part.
___
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] Bugs: "accesses the internet during build" -- strongly disagree on severity
On Sunday, 10 July 2016 11:28:07 AM AEST Chris Lamb wrote: > Severity: serious > Justification: Policy 4.9 > User: la...@debian.org > Usertags: network-access Hi Chris, Thank you for submitting those bugs. I agree that it is a legitimate problem that needs addressing. However I strongly disagree with severity of those bugs. Obviously packages should not download anything during build for security and reproducibility reasons. But here post-build tests attempt to access internet which is relatively harmless in this context. Indeed tests trying to access internet from offline environment is hardly a "serious" problem regardless of what policy says. Thanks to your bug reports we will eventually address and fix those problems. In the mean time this should not block testing migrations so I'm lowering severity of those bugs and I recommend submitting similar bugs with severity not higher than "important". -- All the best, Dmitry Smirnov. --- The most fatal blow to progress is slavery of the intellect. The most sacred right of humanity is the right to think, and next to the right to think is the right to express that thought without fear. -- Helen H. Gardner, "Men, Women and Gods" signature.asc Description: This is a digitally signed message part. ___ 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] FTBFS: build-dependency not installable: golang-clockwork-dev
On Sunday, 10 July 2016 1:07:53 AM AEST Potter, Tim (HPE Linux Support) wrote: > > Revision -5 of the package does not ship any source files. That was an easy to do mistake: debhelper installs everything directly to binary package when there is only one binary package. Once second binary package is introduced (on this instance it was a transitional package) debhelper/dh_auto_install installs to "debian/tmp" so you had to add an .install file as well. > Would you mind fixing it for me? Done. :) -- Best wishes, Dmitry Smirnov. --- It has been said that democracy is the worst form of government except all the others that have been tried. -- Winston Churchill signature.asc Description: This is a digitally signed message part. ___ 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] FTBFS: build-dependency not installable: golang-clockwork-dev
On Sunday, 10 July 2016 1:07:53 AM AEST Potter, Tim (HPE Linux Support) wrote: > Aww crap. I am going to have to declare defeat on this one. It must be multitasking. I know you are perfectly capable of taking care of such packages. > Would you mind fixing it for me? I'm going to be travelling for the next couple of days. OK. Normally I'd say "keep working and overcome the challenge" but on this instance I'll fix it for you. ;) > It's pretty frustrating that the very first packages that I worked on are > the ones that have given everyone the most grief. )-: Not too much grief. :) It is important to keep going despite mistakes and get better. -- Cheers, Dmitry Smirnov. --- Serious sport has nothing to do with fair play. It is bound up with hatred, jealousy, boastfulness, disregard of all rules and sadistic pleasure in witnessing violence: in other words it is war minus the shooting. -- George Orwell, "The Sporting Spirit", Tribune (14 December 1945) signature.asc Description: This is a digitally signed message part. ___ 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#830656: Bug#830656: src:golang-github-docker-libnetwork: FTBFS due to libkv changes
On Saturday, 9 July 2016 3:22:07 PM AEST Tianon Gravi wrote: > The newest upload of "docker-libkv" changed the API slightly, causing > the current libnetwork version to FTBFS. > > I've done a build test with the attached patch (downloaded via > https://github.com/docker/libnetwork/commit/b6b3642560f59f930d1ecf49d2991d7 > 4077d05f9.patch and only DEP-3 headers modified), and it appears to resolve > the issue. Thank you very much, Tianon. :) Would you prefer if I upgrade libnetwork to v0.7.2-rc.1 ? -- Best wishes, Dmitry Smirnov. --- Good luck happens when preparedness meets opportunity. signature.asc Description: This is a digitally signed message part. ___ 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#830530: ITP: golang-github-skarademir-naturalsort -- simple natural sorter for Go Strings
Package: wnpp Severity: wishlist Owner: Dmitry Smirnov <only...@debian.org> X-Debbugs-CC: debian-de...@lists.debian.org, pkg-go-maintainers@lists.alioth.debian.org Control: affects -1 docker-swarm Package name: golang-github-skarademir-naturalsort Version: 0.0~git20150715 Upstream Author: Saruhan Karademir License: Expat URL: https://github.com/skarademir/naturalsort Description: simple natural sorter for Go Strings A simple natural string sorter for Go. Implements the "sort.Interface". signature.asc Description: This is a digitally signed message part. ___ 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#830526: ITP: golang-github-rogpeppe-fastuuid -- fast generation of 192-bit UUIDs
Package: wnpp Severity: wishlist Owner: Dmitry Smirnov <only...@debian.org> X-Debbugs-CC: debian-de...@lists.debian.org, pkg-go-maintainers@lists.alioth.debian.org Control: block 829461 by -1 Package name: golang-github-rogpeppe-fastuuid Version: 0.0~git20150106 Upstream Author: Roger Peppe License: BSD-3-Clause URL: https://github.com/rogpeppe/fastuuid Description: fast generation of 192-bit UUIDs Package fastuuid provides fast UUID generation of 192 bit universally unique identifiers. It does not provide formatting or parsing of the identifiers (it is assumed that a simple hexadecimal or base64 representation is sufficient, for which adequate functionality exists elsewhere). signature.asc Description: This is a digitally signed message part. ___ 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] FTBFS: build-dependency not installable: golang-clockwork-dev
Tim, "golang-github-jonboulle-clockwork" that you prepared have neither "Provides" field nor transitional package for "golang-clockwork-dev". Now when the latter is removed many packages ended up broken. Here is one example: -- Forwarded Message -- Subject: [pkg-go] Bug#830366: golang-github-coreos-go-oidc: FTBFS: build- dependency not installable: golang-clockwork-dev [...] Relevant part (hopefully): > > The following packages have unmet dependencies: > sbuild-build-depends-golang-github-coreos-go-oidc-dummy : Depends: golang- clockwork-dev but it is not installable > E: Unable to correct problems, you have held broken packages. > apt-get failed. - It is important to rename packages properly as described in https://pkg-go.alioth.debian.org/packaging.html -- Regards, Dmitry Smirnov. --- "All government, of course, is against liberty. -- H. L. Mencken signature.asc Description: This is a digitally signed message part. ___ 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#829471: ITP: golang-github-nytimes-gziphandler -- Golang middleware to gzip HTTP responses
Package: wnpp Severity: wishlist Owner: Dmitry Smirnov <only...@debian.org> X-Debbugs-CC: debian-de...@lists.debian.org, pkg-go-maintainers@lists.alioth.debian.org Control: affects -1 nomad Package name: golang-github-nytimes-gziphandler Version: 0.0~git20160419 Upstream Author: The New York Times Company License: Apache-2.0 URL: https://github.com/NYTimes/gziphandler Description: Golang middleware to gzip HTTP responses This is a tiny Go package which wraps HTTP handlers to transparently gzip the response body, for clients which support it. signature.asc Description: This is a digitally signed message part. ___ 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#829461: RFP: golang-github-gengo-grpc-gateway -- gRPC to JSON proxy generator
Package: wnpp Severity: wishlist X-Debbugs-CC: debian-de...@lists.debian.org, pkg-go-maintainers@lists.alioth.debian.org Control: affects -1 etcd Package name: golang-github-gengo-grpc-gateway Version: 0.0~git20160615 Upstream Author: Gengo, Inc. License: BSD-3-Clause URL: https://github.com/gengo/grpc-gateway Description: gRPC to JSON proxy generator grpc-gateway is a plugin of protoc (http://github.com/google/protobuf). It reads gRPC (http://github.com/grpc/grpc-common) service definition, and generates a reverse-proxy server which translates a RESTful JSON API into gRPC. signature.asc Description: This is a digitally signed message part. ___ 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#829459: ITP: golang-github-urfave-cli -- package for building command line apps in Go
Package: wnpp Severity: wishlist Owner: Dmitry Smirnov <only...@debian.org> X-Debbugs-CC: debian-de...@lists.debian.org, pkg-go-maintainers@lists.alioth.debian.org Control: affects -1 etcd Package name: golang-github-urfave-cli Version: 1.18.0 Upstream Author: Jeremy Saenz License: Expat URL: https://github.com/urfave/cli Description: package for building command line apps in Go "Cli" is a simple, fast, and fun package for building command line apps in Go. The goal is to enable developers to write fast and distributable command line applications in an expressive way. signature.asc Description: This is a digitally signed message part. ___ 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#829453: ITP: golang-github-robfig-cron -- cron library for go
Package: wnpp Severity: wishlist Owner: Dmitry Smirnov <only...@debian.org> X-Debbugs-CC: debian-de...@lists.debian.org, pkg-go-maintainers@lists.alioth.debian.org Control: affects -1 kubernetes Package name: golang-github-robfig-cron Version: 1 Upstream Author: Rob Figueiredo License: Expat URL: https://github.com/robfig/cron Description: cron library for go This library implements a cron spec parser and runner. signature.asc Description: This is a digitally signed message part. ___ 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#829302: dh-golang: Respect "--parallel" and "--max-parallel" options
Package: dh-golang
Version: 1.18
Severity: wishlist
Tags: patch
Currently build is always parallel even in compat <= 9 mode because
dh-golang ignores "--parallel" and "--max-parallel" options.
Lack of support for parallel options is a practical problem because by
default "go build" aggressively uses all CPU cores which can overuse
resources on heavy packages. For example Kubernetes FTBFS on
workstation with 8 cores and 32+ GiB of RAM due to lack of memory or
(when there is enough RAM) it causes so much swapping during build
that the whole system becomes nearly unusable.
With Kubernetes and other packages it would be quite useful to be able
to limit build to certain number of cores by using debhelper's
"--max-parallel=N" option. The following patch does that:
--- lib/Debian/Debhelper/Buildsystem/golang.pm
+++ lib/Debian/Debhelper/Buildsystem/golang.pm
@@ -178,8 +178,9 @@
$this->_set_gopath();
if (exists($ENV{DH_GOLANG_GO_GENERATE}) && $ENV{DH_GOLANG_GO_GENERATE} ==
1) {
$this->doit_in_builddir("go", "generate", "-v", @_, get_targets());
}
+unshift @_, ('-p',$this->get_parallel());
$this->doit_in_builddir("go", "install", "-v", @_, get_targets());
}
as well as it makes build respect "--parallel" option for DH consistency.
--
Best wishes,
Dmitry Smirnov
GPG key : 4096R/53968D1B
---
What can be asserted without proof can be dismissed without proof.
-- Christopher Hitchens, 2004
signature.asc
Description: This is a digitally signed message part.
___
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#827697: Bug#827697: golang-github-shirou-gopsutil: Please update to latest release
On Friday, 24 June 2016 8:28:17 AM AEST Michael Hudson-Doyle wrote: > Isolating the packaging changes is hardly difficult: > https://anonscm.debian.org/cgit/pkg-go/packages/golang-github-shirou-gopsut > il.git/log/debian Cool that you can do it so easy in cgit. How about Gitg for a change? I don't usually inspect commits using web interface to git... -- Cheers, Dmitry Smirnov. --- Truth — Something somehow discreditable to someone. -- H. L. Mencken, 1949 signature.asc Description: This is a digitally signed message part. ___ 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] Grafana
Hi Martin, On Thursday, 23 June 2016 1:42:16 PM AEST Martín Ferrari wrote: > I see you listed pkg-go as uploaders for grafana. Are you planning to > move the package into the group? No. This is because team policy requires to maintain "upstream" branch but it is too much of an effort for Grafana... > I see it is still in collab-maint, but > if you are OK with it, I could do the move. It is intentionally on collab-maint, please do not move. > I am using currently grafana, and it is tightly related to prometheus, > so I am interested in working on it. Yay!! I'm so happy to read that my Grafana package is useful, and that you are not only using it but also interested to help. :) Thank you. I'd appreciate any help. > In particular, I have been experiencing some crashes :( > that have been fixed upstream, Any chance that you can point out relevant bugs or commits worth backporting? > and there is a big release available too. Unfortunately it is quite difficult to package: https://github.com/grafana/grafana/issues/5046 Also uploads of Grafana should be coordinated and tested for compatibility with "grafana-zabbix". -- Cheers, Dmitry Smirnov. --- Reality is that which, when you stop believing in it, doesn't go away. -- Philip K. Dick signature.asc Description: This is a digitally signed message part. ___ 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#827697: Bug#827697: golang-github-shirou-gopsutil: Please update to latest release
On Tuesday, 21 June 2016 6:32:46 PM AEST Martín Ferrari wrote: > On 20/06/16 05:11, Dmitry Smirnov wrote: > > I do not mind having full upstream history in "upstream" > > branch but not in "master"... > I don't really have any issue with having all the > commits, as it is pretty clear to me which ones belong to debian, I found it hard to believe. Looking at commit log [1], how many pages you need to skip to find packaging commits prior to merge of last upstream release to master? This is not the worst case as upstream is not too active but there are projects with thousands of commits between releases... All git GUIs are affected because those commits are obstructing. Besides depending on git GUI it may be not so clear which commits are related to packaging... [1]: https://anonscm.debian.org/cgit/pkg-go/packages/golang-github-shirou-gopsutil.git/log/ -- Regards, Dmitry Smirnov. --- A creative man is motivated by the desire to achieve, not by the desire to beat others. -- Ayn Rand signature.asc Description: This is a digitally signed message part. ___ 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] build-dependency loop: golang-github-coreos-pkg and golang-github-coreos-go-systemd
On Tuesday, 21 June 2016 5:02:19 PM AEST Michael Hudson-Doyle wrote: > Currently in sid golang-github-coreos-pkg and > golang-github-coreos-go-systemd Build-Depend on each other. This is an > accurate reflection of the upstream situation > (github.com/coreos/pkg/capnslog/journald_formatter imports > github.com/coreos/go-systemd/journal, > github.com/coreos/go-systemd/journal and > github.com/coreos/go-systemd/sdjournal/journal import > github.com/coreos/pkg/dlopen) but it's not good for a distribution. > Does anyone have any ideas as to how we could fix it? I guess > github.com/coreos/pkg/dlopen could become its own package? Hi Michael, It would be great if you could discuss this matter with upstream... -- All the best, Dmitry Smirnov. --- To swallow and follow, whether old doctrine or new propaganda, is a weakness still dominating the human mind. -- Charlotte P. Gilman signature.asc Description: This is a digitally signed message part. ___ 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#827697: Bug#827697: golang-github-shirou-gopsutil: Please update to latest release
On Sunday, 19 June 2016 9:59:30 PM AEST Martín Ferrari wrote: > On 19/06/16 20:47, Dmitry Smirnov wrote: > > I would be happy to upload updated package but I've noticed that > > "upstream" branch follows upstream history so "gbp import-orig" would > > break it and I'm not sure how to handle such repository configuration... > > I have just done it. These are the steps: > [...] Thank you, Martin. :) I think your procedure could be improved if "git merge upstream/2.1" is modified with "--squash" to produce one neat merge commit to "master" instead of flood of upstream commits that make it difficult to identify packaging-related commits. Merge from upstream branch that follows upstream history makes it difficult to review packaging changes therefore I see it as counter-productive especially for team-maintained packages. I do not mind having full upstream history in "upstream" branch but not in "master"... > I am just confused > as to why you removed the Build-Using field in control.. Because it was used on arch-all -dev package shipping sources... Built-Using on -dev packages is an artifact of older versions of dh-make- golang which do not add "Built-Using" to -dev packages any more. Anyway "Built-Using" is not meant to be used with -dev packages. Built-Using field is usually applied to binaries incorporating portion of another package or built using another package without explicit dependency. -dev packages should already depend on all related -dev dependencies. -- Cheers, Dmitry Smirnov. --- I believe in only one thing: liberty; but I do not believe in liberty enough to want to force it upon anyone. -- H. L. Mencken signature.asc Description: This is a digitally signed message part. ___ 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#827697: Bug#827697: Bug#827697: golang-github-shirou-gopsutil: Please update to latest release
On Monday, 20 June 2016 11:16:37 AM AEST Michael Hudson-Doyle wrote: > I suppose Built-Using on a -dev package lists source package versions > that the -dev package is known to build/pass tests with, which is > probably useful information. dh-buildinfo may be considered when it is necessary to capture information about build environment... -- All the best, Dmitry Smirnov. --- You have to start with the truth. The truth is the only way that we can get anywhere. Because any decision-making that is based upon lies or ignorance can't lead to a good conclusion. -- Julian Assange, 2010 signature.asc Description: This is a digitally signed message part. ___ 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#827697: golang-github-shirou-gopsutil: Please update to latest release
Source: golang-github-shirou-gopsutil Version: 1.0.0+git20160112-1 Severity: normal X-Debbugs-CC: iwama...@debian.org Please upload latest upstream release (at least one package is held by the dependency). Upstream is now tagging releases. I would be happy to upload updated package but I've noticed that "upstream" branch follows upstream history so "gbp import-orig" would break it and I'm not sure how to handle such repository configuration... Please advise. -- Cheers, Dmitry Smirnov GPG key : 4096R/53968D1B --- What is the truth, but a lie agreed upon. -- Friedrich Nietzsche signature.asc Description: This is a digitally signed message part. ___ 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#827219: Bug#827219: Bug#827219: Bug#827219: dh-golang: Built-Using calculation crashes on "golang-google-cloud"
On Wednesday, 15 June 2016 10:37:57 AM AEST Martín Ferrari wrote: > Actually, please don't. > > All of the team's work depends on dh-golang, so uploading without proper > testing is definitely *not ok*. Martin, I don't need to be reminded how painful it is to have dh-golang broken -- last time when it was unusable I fell a week behind my schedule because I could not upload... I did some testing and I believe changes are good enough for upload. I already uploaded short time ago. I appreciate your concerns. if anything goes wrong please let us know and we'll address the problem, if any. -- Cheers, Dmitry Smirnov. --- If forty million people say a foolish thing it does not become a wise one. -- W. Somerset Maugham, 1901 signature.asc Description: This is a digitally signed message part. ___ 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#827219: Bug#827219: Bug#827219: dh-golang: Built-Using calculation crashes on "golang-google-cloud"
On Wednesday, 15 June 2016 8:26:43 PM AEST Michael Hudson-Doyle wrote: > Ah, good point. Fix for that push to the bug-827219 branch, tested > with docker with reasonable-seeming results. Merge to master and > upload if it looks good to you? Yes, let's upload please. Unfortunately I don't have time to review code or do more extensive testing now... However providing that you respond to bugs so promptly I'm confident that you will rapidly fix whatever regressions is introduced (if any). :)) Thank you. -- Cheers, Dmitry Smirnov. --- In questions of science, the authority of a thousand is not worth the humble reasoning of a single individual. -- Galileo Galilei signature.asc Description: This is a digitally signed message part. ___ 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#827219: Bug#827219: dh-golang: Built-Using calculation crashes on "golang-google-cloud"
On Tuesday, 14 June 2016 4:19:59 PM AEST Michael Hudson-Doyle wrote: > Oh, sorry, I see that the failure is when building something that > depends on golang-google-cloud. I don't have time to test it now, but > I have pushed a proposed fix to > https://anonscm.debian.org/cgit/pkg-go/packages/dh-golang.git/log/?h=bug-82 > 7219. I'd be interested to hear if it helps! It works better now but when I built docker.io/experimental "golang-google- cloud" appeared twice in "misc:Built-Using" so I think it needs de- duplication... Thanks. -- Best wishes, Dmitry Smirnov. --- The choice for mankind lies between freedom and happiness and for the great bulk of mankind, happiness is better. -- George Orwell, 1984 signature.asc Description: This is a digitally signed message part. ___ 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#827219: Bug#827219: dh-golang: Built-Using calculation crashes on "golang-google-cloud"
On Wednesday, 15 June 2016 9:55:34 AM AEST Michael Hudson-Doyle wrote:
> Where can I get docker.io_1.11.1~ds1.orig.tar.{bz2,gz,lzma,xz} ?
?? Is something wrong with "uscan"?
You should be able to generate tarball by something like:
uscan --destdir=. --compression xz --repack --download-current-version
--
All the best,
Dmitry Smirnov.
---
Reality is that which, when you stop believing in it, doesn't go away.
-- Philip K. Dick
signature.asc
Description: This is a digitally signed message part.
___
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#827226: Bug#827226: incorrect preparation of build directory when pre-installed package is re-built
On Tuesday, 14 June 2016 12:14:56 PM AEST Michael Hudson-Doyle wrote: > On 14 June 2016 at 10:11, Dmitry Smirnov <only...@debian.org> wrote: > > Also it would be nice to produce a warning to notify maintainer about > > potential problem. > > If the problem is fixed as you describe, I'm not sure what the point > of the warning would be? Maybe just to warn about potential circular dependency that maintainer may not be aware of... -- Cheers, Dmitry Smirnov. --- You have enemies? Good. That means you've stood up for something, sometime in your life. -- Victor Hugo, "Villemain", 1845 (often misattributed to Winston Churchill) signature.asc Description: This is a digitally signed message part. ___ 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#827226: incorrect preparation of build directory when pre-installed package is re-built
Package: dh-golang Version: 1.17 Severity: normal --buildsystem=golang does a nice job preparing build directory in `dh_auto_configure` by symlinking source packages from under "/usr/share/gocode/src" to directory specified with "--builddirectory" argument. However it works incorrectly when $(DH_GOPKG) package (i.e. current package to build) is pre-installed because in such case installed and new version of the package are merged in build directory. Suppose you are building a "golang-github-foo-bar" package which no longer provides "github.com/foo/bar/obsolete-feature". If previous version of the package is installed then dh_golang incorrectly symlink "/usr/share/gocode/src/github.com/foo/bar/obsolete-feature" into build directory. This problem should be easy to detect and avoid as dh_golang already knows which package not to link from $(DH_GOPKG) or XS-Go-Import-Path header. I suppose we just need to ignore/skip pre-installed package which is build. Also it would be nice to produce a warning to notify maintainer about potential problem. Arguably circular dependencies are not in scope of what dh_golang should be doing but there are cases when package can be re-built (staged) on maintainer's machine in presence of previous version of the same package. Correct handling of such situations would be useful. Thanks. -- Regards, Dmitry Smirnov GPG key : 4096R/53968D1B --- Truth — Something somehow discreditable to someone. -- H. L. Mencken, 1949 signature.asc Description: This is a digitally signed message part. ___ 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#827219: dh-golang: Built-Using calculation crashes on "golang-google-cloud"
Package: dh-golang Version: 1.17 Severity: normal Control: affects -1 docker.io dh_golang invocation fails on "golang-google-cloud" as follows: dpkg-query: no packages found matching golang-google-cloud-compute-metadata-dev, dpkg-query -W failed with code 31488, at /usr/bin/dh_golang line 72. because it tries to process the following data: golang-google-cloud-compute-metadata-dev, golang-google-cloud-dev: /usr/share/gocode/src/google.golang.org/cloud golang-google-cloud-compute-metadata-dev: /usr/share/gocode/src/google.golang.org/cloud/compute/metadata golang-google-cloud-compute-metadata-dev, golang-google-cloud-dev: /usr/share/gocode/src/google.golang.org/cloud/internal Assuming only one package per directory instead of a list. Also I wish troubleshooting could be improved to print command and/or the data (or possibly leave temporary file behind on abort). Thanks. -- Regards, Dmitry Smirnov GPG key : 4096R/53968D1B signature.asc Description: This is a digitally signed message part. ___ 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] Final set of bugs posted for docker.io 1.11.0
On Thursday, 9 June 2016 2:55:14 AM AEST Potter, Tim (HPE Linux Support) wrote: > Could someone please take a look at golang-github-gorilla-mux? It's the > last remaining package not in unstable for building Docker 1.11.0. No, that's not the last one... We need latest Notary which introduced new dependencies. One of them is in NEW right now and once accepted I'll be able to continue working on Notary and Docker. As far as I'm aware gorilla-mux is not _required_ to build Docker_1.11.0 but it won't hurt to upload it if it does not break anything... -- Cheers, Dmitry Smirnov. --- Criticism may not be agreeable, but it is necessary. It fulfils the same function as pain in the human body. It calls attention to an unhealthy state of things. -- Winston Churchill signature.asc Description: This is a digitally signed message part. ___ 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#826598: ITP: golang-gopkg-dancannon-gorethink.v2 -- Go driver for RethinkDB
Package: wnpp Severity: wishlist Owner: Dmitry Smirnov <only...@debian.org> X-Debbugs-CC: debian-de...@lists.debian.org, pkg-go-maintainers@lists.alioth.debian.org Control: block -1 by 826597 Control: affects -1 notary Package name: golang-gopkg-dancannon-gorethink.v2 Version: 2.0.4 Upstream Author: Daniel Cannon License: Apache-2.0 URL: http://gopkg.in/dancannon/gorethink.v2 Description: Go driver for RethinkDB This package provides native Golang driver for RethinkDB. signature.asc Description: This is a digitally signed message part. ___ 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#825067: #825067 RM: golang-bindata -- ROM; No reverse-dependencies, unmaintained downstream
On Tuesday, 24 May 2016 9:11:29 AM AEST Mattia Rizzolo wrote: > On Tue, May 24, 2016 at 04:14:14PM +1000, Dmitry Smirnov wrote: > > Anyway I guess my frustration is more about how packages are being > > removed in general -- not just this particular one. > > umh? Very quick removals are very nice and useful. What's wrong with > them? IMHO that removals are too often unexpected. Removals from "testing" are noticeable in PTS and announced beforehand over email. However removals from "unstable" are sudden and unexpected. Autoremovals from "tetsing" have a lot more visibility so prospective maintainers have a chance to step in and improve situation. I wish how-can-i-help could notice about scheduled removals from "unstable" but for that removals should have some retention time. > One of them (I usually go the RC bug way) is usually (!= always) what > happens for RoQA, but for ROM this doesn't make much sense most of the > time... True. But ROMs do not take into account when packages are requested for removal by mistake especially while depending packages are processed through NEW queue... It is always unpleasant to find that package you've installed just yesterday (because you needed it) is no longer available... Of course that does not include removals of obsolete packages after transitions. We should not be hasty to remove seemingly unused packages. When in doubt I'd rather mark 'em for exclusion from "testing" with a "serious" bug. -- Cheers, Dmitry Smirnov. --- It has been said that democracy is the worst form of government except all the others that have been tried. -- Winston Churchill signature.asc Description: This is a digitally signed message part. ___ 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] github.com/XXX/YYY vs gopkg.in/XXX/YYY.v1
On Tuesday, 24 May 2016 1:20:34 PM AEST Vincent Bernat wrote: > I need this package for use in gobgp which > uses it through github.com/eapache/channels. > > Should I package golang-github-eapache-channels-dev or > golang-gopkg-eapache-channels.v1-dev? > > In the first case, should I provide a symbolic link for > gopkg.in/eapache/channels.v1 or wait for anything else needing this > symbolic link? I would go with first option because if package ever moves to .v2 you'll only need to update "Provides" field (and symlink). Providing compatibility symlink may be useful even if nobody uses it yet. -- Best wishes, Dmitry Smirnov. --- Good luck happens when preparedness meets opportunity. signature.asc Description: This is a digitally signed message part. ___ 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] #825067 RM: golang-bindata -- ROM; No reverse-dependencies, unmaintained downstream
On Tuesday, 24 May 2016 7:54:18 AM AEST Vincent Bernat wrote: > Sorry. I asked on pkg-go-maintainers@ one week ago without any answer. Yeah, I've missed that... Also I don't expect to be able to recognise all dependency packages by name and respond promptly to prevent their removal... Anyway I guess my frustration is more about how packages are being removed in general -- not just this particular one. Maybe we need some sort of delay and wider announcement for packages that are tagged for removal to give prospective maintainers opportunity for adoption... Or maybe removal could begin with RC-critical bug to drop packages from "testing" first... No worries, golang-bindata was just re-introduced. All good. -- Regards, Dmitry Smirnov. --- No person, no idea, and no religion deserves to be illegal to insult, not even the Church of Emacs. -- Richard Stallman signature.asc Description: This is a digitally signed message part. ___ 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] Two remaining uploads for docker 1.11.0
On Tuesday, 24 May 2016 12:14:13 PM AEST Dmitry Smirnov wrote: > > | golang-google-grpc-dev is version constrainted >= 0.0~git20151216~ > > I've accidentally uploaded newer snapshot... Please disregard this. It is the correct revision uploaded with incorrect date in version... :( -- Regards, Dmitry Smirnov. signature.asc Description: This is a digitally signed message part. ___ 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] Two remaining uploads for docker 1.11.0
On Monday, 23 May 2016 4:58:01 PM AEST Tianon Gravi wrote: > > * golang-gocapability-dev Uploaded. > > * golang-github-docker-go (new package, ITP #822219) Wouldn't it be better to keep it private/bundled? I doubt this particular library would be (re-)used by anything else... > By my own count, we've got a little bit more than that to get us > all the way: > golang-github-docker-libnetwork-dev is version constrainted >= > > 0.7.0~rc.7~. Libnetwork rc7 is for Docker-1.11.1. rc6 satisfies what Docker 1.11.0 needs... > | golang-github-docker-notary-dev is version constrainted >= 0.2.0~ We are certainly need this... > | golang-google-grpc-dev is version constrainted >= 0.0~git20151216~ I've accidentally uploaded newer snapshot... I hope it won't be a problem... Also I'm still getting the following build failures: # github.com/docker/docker/api/client src/github.com/docker/docker/api/client/trust.go:480: too many arguments in call to repo.CryptoService.Create # github.com/docker/docker/daemon/logger/awslogs src/github.com/docker/docker/daemon/logger/awslogs/cloudwatchlogs.go:72: undefined: defaults.DefaultConfig in defaults.DefaultConfig.Region src/github.com/docker/docker/daemon/logger/awslogs/cloudwatchlogs.go:72: cannot assign to defaults.DefaultConfig.Region src/github.com/docker/docker/daemon/logger/awslogs/cloudwatchlogs.go:124: undefined: defaults.DefaultConfig src/github.com/docker/docker/daemon/logger/awslogs/cloudwatchlogs.go:126: undefined: defaults.DefaultConfig in defaults.DefaultConfig.Merge -- Best wishes, Dmitry Smirnov. --- A man is his own easiest dupe, for what he wishes to be true he generally believes to be true. -- Demosthenes, Third Olynthiac, sct. 19 (349 BCE) signature.asc Description: This is a digitally signed message part. ___ 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] #825067 RM: golang-bindata -- ROM; No reverse-dependencies, unmaintained downstream
This is super annoying that RM bugs don't set "affects" header on removed package or take recent uploads to consideration. This package should not have been removed because it is a dependency of Kubernetes. Despite my upload on 17th of April bug filed on 23rd of May claims "unmaintained downstream" in title and package was removed on the same day(!) so nobody had a chance to object. WTF, this is just not helpful... :( This makes me feel very frustrated... -- Cheers, Dmitry Smirnov GPG key : 4096R/53968D1B --- You have enemies? Good. That means you've stood up for something, sometime in your life. -- Victor Hugo, "Villemain", 1845 (often misattributed to Winston Churchill) signature.asc Description: This is a digitally signed message part. ___ 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] debcheckout runc
On Friday, 20 May 2016 9:56:23 AM AEST Ian Campbell wrote: > The URLs are subtly different I think: > https://anonscm.debian.org/git/pkg-go/packages/runc.git > > git://anonscm.debian.org/pkg-go/packages/runc.git Well spotted, Ian. :) Vcs-Git URL corrected to https://anonscm.debian.org/git/pkg-go/packages/runc.git Thanks. -- Best wishes, Dmitry Smirnov. --- It is impossible to imagine Goethe or Beethoven being good at billiards or golf. -- H. L. Mencken signature.asc Description: This is a digitally signed message part. ___ 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] RFC: Enhancements to dh-golang
On Sunday, 8 May 2016 5:31:08 AM AEST Martín Ferrari wrote: > Thoughts? Awesome. :) I think --no-source and --no-binaries options are unnecessary. It is easy and more portable to do :rules: override_dh_auto_install: dh_auto_install --destdir=debian/tmp and put either "usr/bin" or "usr/share/gocode/src" to "install" file for binary and source packages respectively. "override_dh_auto_install" is only needed in case of single binary package. It is the default for multiple binary packages. Thanks. -- Regards, Dmitry Smirnov. --- The man who does not do his own thinking is a slave, and is a traitor to himself and to his fellow-men. -- Robert G. Ingersoll, "The Liberty of Man, Woman and Child" 1877 signature.asc Description: This is a digitally signed message part. ___ 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#823718: ITP: golang-github-franela-goreq -- minimal and simple request library for Go language
Package: wnpp Severity: wishlist Owner: Dmitry Smirnov <only...@debian.org> X-Debbugs-CC: debian-de...@lists.debian.org, pkg-go-maintainers@lists.alioth.debian.org Control: block -1 by 823715 Control: affects -1 grafana Package name: golang-github-franela-goreq Version: 0.0~git20160121 Upstream Author: Jonathan Leibiusky and Marcos Lilljedahl License: Expat, BSD-3-Clause~Google URL: https://github.com/franela/goreq Description: minimal and simple request library for Go language GoReq Simple and sane HTTP request library for Go language. signature.asc Description: This is a digitally signed message part. ___ 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#823715: ITP: golang-github-franela-goblin -- minimal and beautiful Go testing framework
Package: wnpp Severity: wishlist Owner: Dmitry Smirnov <only...@debian.org> X-Debbugs-CC: debian-de...@lists.debian.org, pkg-go-maintainers@lists.alioth.debian.org Package name: golang-github-franela-goblin Version: 0.0.1+git20160123 Upstream Author: Marcos Lilljedahl and Jonathan Leibiusky License: Expat URL: https://github.com/franela/goblin Description: minimal and beautiful Go testing framework Mocha (http://visionmedia.github.io/mocha/) like BDD testing framework for Golang. signature.asc Description: This is a digitally signed message part. ___ 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] DEP-14
On Friday, 6 May 2016 12:25:34 PM AEST Martín Ferrari wrote: > Well, some people *do* recognise it as useful. Maybe we can have a team > discussion? Maybe... > About leaving things alone or not, we all have preferences, and > personally I don't like some of yours, but let's try to discuss it with > proper arguments. Interesting. Which of my preferences annoy you? > "I don't like it" is not a great argument, but I am open for convincing > if you make a good case. That's nitpicking. But to provide more context I'd say that the more GBP workflow we enforce the more time I waste for compliance and less time doping the job done. > In any case, as I said many times before, I would like the team to adopt > a unique standard, but we are pretty far from that. "unique standard" already sounds like oxymoron... ;) -- Cheers, Dmitry Smirnov. --- If liberty means anything at all, it means the right to tell people what they do not want to hear. -- George Orwell signature.asc Description: This is a digitally signed message part. ___ 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] DEP-14
On Friday, 6 May 2016 1:12:28 AM AEST Potter, Tim (HPE Linux Support) wrote: > I'm not sure whether you want to delete the master branch and set > debian-branch to debian/sid. I feel very uncomfortable about all this master-to-sid renaming business. I do not recognise it as useful and I've seen some repositories without "master" that exhibit errors when cloned. I'd appreciate if repository layout could be left alone without disruptive changes. "Master" for uploads to "unstable" works great. Let's not mess with it please at least not on massive scale (for all team-maintained packages). -- Regards, Dmitry Smirnov. --- There is no society in human history that ever suffered because its people became too reasonable. -- Sam Harris signature.asc Description: This is a digitally signed message part. ___ 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#823466: Bug#823466: golang-github-docker-libnetwork: Please update to latest upstream release
On Thursday, 5 May 2016 1:15:21 AM AEST Potter, Tim (HPE Linux Support) wrote: > Please upload the latest snapshot of the golang-github-docker-libnetwork > package, 0.7.0~rc.6+dfsg. I've already packaged this in the repo on > alioth. Do we _really_ need ~RC version? I prefer to upload proper stable releases whenever possible... -- Best wishes, Dmitry Smirnov. --- I cannot believe in a God who wants to be praised all the time. -- Friedrich Nietzsche signature.asc Description: This is a digitally signed message part. ___ 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#822925: golang-github-gorilla-context: Please update to latest upstream snapshot
On Friday, 29 April 2016 9:57:31 AM AEST Potter, Tim (HPE Linux Support) wrote: > On 29 Apr 2016, at 7:27 pm, Mattia Rizzolo <mat...@debian.org> wrote: > > And btw, it's pretty weird way to file a bug like this just to ask for > > sponsorship. > > I have about a dozen packages to upload for docker.io, and it's easier to > keep track of them with BTS bugs than sending out an email on the mailing > list which often go unanswered. If I work towards the same goal it is quite useful to see what packages needs work/sponsorship. Blocking bugs are actually useful. -- Best wishes, Dmitry Smirnov. --- What opinions the masses hold, or do not hold, is looked on as a matter of indifference. They can be granted intellectual liberty because they have no intellect. -- George Orwell, 1984 signature.asc Description: This is a digitally signed message part. ___ 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#822213: containerd: Bug#822213: Please build development package
On Friday, 22 April 2016 4:41:20 AM AEST Potter, Tim (HPE Linux Support) wrote: > The development package, golang-github-docker-containerd-dev, needs to be > built for containerd as it's a dependency for Docker 1.11.0. I pushed few minor corrections -- IMHO package is ready for upload... :) -- Regards, Dmitry Smirnov. --- The Santa myth is one of the most effective means ever devised for intimidating children, eroding their self-esteem, twisting their behavior, warping their values, and slowing their development of critical thinking skills. -- Tom Flynn, "The Trouble with Christmas" signature.asc Description: This is a digitally signed message part. ___ 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#822218: Bug#822218: Please update to latest upstream release 0.3.3
On Friday, 22 April 2016 5:23:27 AM AEST Potter, Tim (HPE Linux Support) wrote: > I've already pushed a change to alioth for this - all it needs is a review > and upload. Tim, when packaging new upstream releases please always remember to compare last and new tarballs, file by file and update "copyright" file accordingly. Also I'd love to see package name in subjects of "Please update to latest upstream release" bugs... Thanks. -- Cheers, Dmitry Smirnov. --- I hate all sports as rabidly as a person who likes sports hates common sense. -- H. L. Mencken signature.asc Description: This is a digitally signed message part. ___ 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#822218: golang-github-docker-engine-api: Please update to latest upstream release 0.3.3
On Friday, 22 April 2016 5:23:27 AM AEST Potter, Tim (HPE Linux Support) wrote: > Please update golang-github-docker-engine-api to the latest upstream > version (0.3.3) required for packaging Docker 1.11.1. I think ideally upstream should clarify license first: https://github.com/docker/engine-api/issues/172 > I've already pushed a change to alioth for this - all it needs is a review > and upload. Did you? I've seen no changes since 0.2.3-1 yet... -- Cheers, Dmitry Smirnov. --- There is nothing more odious than the majority. It consist of a few powerful men who lead the way; of accommodating rascals and submissive weaklings; and of a mass of men who trot after them without in the least knowing their own minds. -- Johann Wolfgang von Goethe signature.asc Description: This is a digitally signed message part. ___ 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] contributors.debian.org source for pkg-go
On Thursday, 21 April 2016 1:08:13 PM AEST Martín Ferrari wrote: > Most of these repos are yours actually. I was not too sure about the > work-in-progress, as they don't have a single commit... Hence my message. Thanks for reminding. I already removed some that I recognised as useless. -- Cheers, Dmitry Smirnov. --- The more false we destroy the more room there will be for the true. -- Robert G. Ingersoll, 1902 signature.asc Description: This is a digitally signed message part. ___ 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] contributors.debian.org source for pkg-go
On Wednesday, 20 April 2016 5:23:30 PM AEST Martín Ferrari wrote: > I have just set up a new source in contributors.d.o to track our git > repos[1]. Nice, thank you. > Note that while doing this, I noticed quite a few repos that are > empty[2], we should review and possibly remove them. > > [2] http://paste.debian.net/439726/ Perhaps creation date could be a good criterion to decide what to delete. Some of those repositories are obviously work-in-progress for existing or to- be-submitted ITPs. -- Cheers, Dmitry Smirnov. --- Honesty is a gift we can give to others. It is also a source of power and an engine of simplicity. Knowing that we will attempt to tell the truth, whatever the circumstances, leaves us with little to prepare for. We can simply be ourselves. -- Sam Harris signature.asc Description: This is a digitally signed message part. ___ 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#821192: golang-bindata: new upstream version please
Source: golang-bindata Version: 3.0.5-1 Severity: normal Control: block 795652 by -1 Please upload new upstream release 3.0.7 -- it is required to build Kubernetes. Thanks. -- All the best, Dmitry Smirnov GPG key : 4096R/53968D1B --- Sometimes the first duty of intelligent men is the restatement of the obvious. -- George Orwell signature.asc Description: This is a digitally signed message part. ___ 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: golang-github-gorilla-context
On Thursday, 14 April 2016 10:29:55 PM AEST Potter, Tim (HPE Linux Support) wrote: > Nuts - fell for the old package already present under a different name - > golang-context. I might be helpful to check name space with "apt-file search" to detect whether files already provided by different package... -- Cheers, Dmitry Smirnov. --- A casual stroll through the lunatic asylum shows that faith does not prove anything. -- Friedrich Nietzsche signature.asc Description: This is a digitally signed message part. ___ 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] a mutual dependency problem (Packer)
On Thursday, 14 April 2016 10:38:15 PM AEST Daniel Stender wrote: > I have an idea but wanted to poll, how could get they both in the best way? Not sure for "best way" but here some ideas how this problem could be addressed: Sometimes one dependency required only by tests. In such case it may be safe to disable corresponding tests in order to break/remove circular dependency. Since Packer appears to be a bigger package it is likely that you are packaging "winrmcp" merely to satisfy dependency of Packer. There are two options: * To keep bundled/vendored version of "winrmcp" in Packer and do not package "winrmcp" separately; * To keep bundled/vendored portion of Packer code in "winrmcp". I would investigate those options in given order. Whatever you choose please remember to leave a note explaining your decision in README.source. -- Best wishes, Dmitry Smirnov. --- For a creative writer possession of the 'truth' is less important than emotional sincerity. -- George Orwell signature.asc Description: This is a digitally signed message part. ___ 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: consul 0.6.3~dfsg-3 -- Remove armon-gomdb dependency
On Monday, 11 April 2016 3:35:13 AM AEST Potter, Tim (HPE Linux Support) wrote: > Hi everyone. I'm on a rebuild-fest and have made a packaging-only fix to > consul to remove a dependency. > > The Debian auto removal watch bot has marked consul (and a few others) for > removal because of bug 819638. This bug turns out to be something weird > to do with a change in how cgo pointers are passed and is beyond my > ability to fix. > > Luckily for consul, it turns out that this package is no longer needed. > There's no longer any reference to gomdb in the consul source, and I've > just successfully completed a rebuild of consul in sid without that > dependency. > > Could someone please review and upload? Nice work Tim. I'll upload. Thanks. -- Cheers, Dmitry Smirnov. --- Every decent man is ashamed of the government he lives under. -- H. L. Mencken signature.asc Description: This is a digitally signed message part. ___ 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#820421: ITP: golang-github-smartystreets-assertions -- fluent assertion-style functions
Package: wnpp Severity: wishlist Owner: Dmitry Smirnov <only...@debian.org> X-Debbugs-CC: debian-de...@lists.debian.org, pkg-go-maintainers@lists.alioth.debian.org Control: affects -1 golang-github-smartystreets-goconvey Package name: golang-github-smartystreets-assertions Version: 1.6.0 Upstream Author: SmartyStreets, LLC License: Expat URL: https://github.com/smartystreets/assertions Description: fluent assertion-style functions This package contains the implementations for all assertions which are referenced in goconvey package (github.com/smartystreets/goconvey/convey) and gunit (github.com/smartystreets/gunit) for use with the So(...) method. They can also be used in traditional Go test functions and even in applications. signature.asc Description: This is a digitally signed message part. ___ 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] Security support for packages written in Go
On Tuesday, 5 April 2016 10:41:04 PM AEST Paul Tagliamonte wrote: > | Backports are packages taken from the next Debian release (called > | "testing"), adjusted and recompiled for usage on Debian stable. > > So my confusion here is that you don't want to see them in Stable, but > you do want to see them in testing (and backports). This isn't what > testing is for, of course :) I'm not comfortable with this idea. It requires a lot more work as well. I just entertain possibility if we have to drop golang apps from next stable. After all even if not in next stable we might have some good ideas for next stable+1... > I don't see anything inherent about Go that makes it unsupportable. You are certainly more optimistic than I am. :) > I *do* see more software being developed in a way that makes it nearly > impossible for Debian to distribute. But I'm not talking about distribution. We can distribute but security support is very difficult. Maybe we should just give up on it... > This, however, is a much bigger conversation. True... -- Regards, Dmitry Smirnov. --- Lies are the social equivalent of toxic waste: Everyone is potentially harmed by their spread. -- Sam Harris signature.asc Description: This is a digitally signed message part. ___ 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] golang-yaml.v2_0.0~git20160301.0.a83829b-1_amd64.changes REJECTED
On Tuesday, 5 April 2016 8:06:32 PM AEST Paul Tagliamonte wrote: > But you see, that's not my point. Really, in reality, *semantically*, > we're shipping a release *less than* 0.0. To say we're shipping something > semantically *newer* 0.0 is wrong. ~ means before, like an RC. + means > after, like fixing a broken already uploaded non-free release to main > with +dfsg. What you are saying about semantic significance of '~' and '+' makes sense. But I'm thinking about slightly different example. Suppose we have upstream releases "1.0" and "1.1-rc1" (tagged or just to be tagged). Debian package can express version greater than 1.0 as something like "1.0+git20150505" or as "1.1~git20150505" (assuming that "1.1~rc1" is not tagged upstream). Both versions express idea of version somwhere in between 1.0 and 1.1. Neither version is "wrong". Both approaches are (more or less) equally correct. When upstream have no higher version tagged using "1.0+" appears to be more appropriate. When there are no tags whatsoever I tend to agree that "0~" seems to be better that "0+" but I don't have a strong preference. I hope that difference between "~" and "+" in version numbers make sence in context but not as an absolute thing. > Anyway, I realize you don't like this because it doesn't git tag right, > but I'm going to keep saying + is less correct than ~. You'll likely > have to live with this fact of life. No worries. :) > I hope you can empathize with my love of expressing things semantically, > and I hope you can also understand this wasn't me going around claiming > anyone is a bad developer for doing this. Understood. I want to make it clear that I've never implied bad intentions on your side. I merely feel that calling a legitimate (but perhaps not ideal) versioning scheme as "wrong" is too strong. > I *am* saying it's semantically wrong, and I'll continue to complain about > this by bitching to the list once in a while. I have no problem with that. :) -- Regards, Dmitry Smirnov. --- "All government, of course, is against liberty. -- H. L. Mencken signature.asc Description: This is a digitally signed message part. ___ 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] golang-yaml.v2_0.0~git20160301.0.a83829b-1_amd64.changes REJECTED
On Tuesday, 5 April 2016 7:44:22 PM AEST Paul Tagliamonte wrote:
> The version in sid is funny, and we need to break our version to sort
> greater than.
Change as simple as 's{~}{+}' should fix it. :)
> I wonder what happens when they release version 0.0, now.
If ever. ;)
> 1:0.0, I guess.
As an option. Or we could ask upstream to tag 0.0.1 (or 0.1.0 or 1.0.0) as
they might naturally do if they choose to use semantic versioning.
--
Cheers,
Dmitry Smirnov.
---
Sometimes people don't want to hear the truth because they don't want their
illusions destroyed.
-- Friedrich Nietzsche
signature.asc
Description: This is a digitally signed message part.
___
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] golang-yaml.v2_0.0~git20160301.0.a83829b-1_amd64.changes REJECTED
On Tuesday, 5 April 2016 7:24:45 PM AEST Paul Tagliamonte wrote: > Sigh. Someone uploaded a version that's silly. We'll have to damage this > package accordingly. There is no need to blame for that. I feel that "damage" is too strong to describe change in versioning scheme. Mistake is minor and easy to correct. No harm is done. -- Cheers, Dmitry Smirnov. --- It has been said that democracy is the worst form of government except all the others that have been tried. -- Winston Churchill signature.asc Description: This is a digitally signed message part. ___ 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] Security support for packages written in Go
On Tuesday, 5 April 2016 9:27:27 AM AEST Florian Weimer wrote: > we need to discuss how we can support applications written in Go for > stretch. > > The most radical approach would be not to ship any Go applications in > stretch, only the basic Go language implementations. This is probably > not desirable. Alternatively we could explicitly disclaim security support for Golang applications. IMHO Golang community abused almost as much as possible with static linking, embedding resources to executables, not using versioning and breaking API at any time, etc. Even if we find effective technical solution to detect dependency chains there is a problem of re-building ever growing number of all packages indirectly depending on vulnerable package. Golang is just too young, unstable and fragile. I have a feeling that few upstream projects take security concerns seriously. Many upstream projects have no concept of "stable" releases so I doubt it is practical to offer any kind of security support for Golang when too many projects introduce new dependencies with almost every new versioned release while old release is abandoned as soon as new one becomes available. Unless we can exclude Golang from security support I think we should not ship any Golang applications with next stable release. Unfortunately if we exclude Golang binaries from release Debian will not be competitive in the enterprise sector: industry is rapidly developing Golang tools for container solutions and they are crucial for Debian success. To some extent we can compensate for absence of Golang binaries in stable release if we continue developing in "testing" and make selected apps available through stretch-backports suite. > One approach would be to ship applications as source code only (just > like libraries), and compile them locally upon installation. This is > what Emacs and Common Lisp implementations already do. With the > growth of Go compilation and link times, this seems less and less > attractive, though. This is a possible solution but with Golang it is not practical as building some packages takes too much time and resources. Also we still need to build packages on build servers to have tests coverage and build logs. Unfortunately shipping Golang applications in sources only (no binaries) is not an option... -- All the best, Dmitry Smirnov. --- Good luck happens when preparedness meets opportunity. signature.asc Description: This is a digitally signed message part. ___ 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] autopkgtest
On Thursday, 31 March 2016 1:59:14 AM AEST Martín Ferrari wrote: > So another approach was mentioned to me: autopkgtest. > > I know about that project for a while, as I saw pkg-perl people > implement it. But I did not follow any of the details. Today I took a > deeper look, and it seems that we would benefit tremendously from that! It is always nice to use all those lovely practices of Perl team. :) > The idea of autopkgtest is to mark packages as having an automated > post-build test suite, so the ci.debian.net project would pick them > automatically (and also for our own testing). > > These tests would trigger each time the package or its dependencies are > updated, and they consist of installing the package and its > dependencies, and running a series of scripts to verify proper > behaviour, run unit tests, etc. All executed using the installed package > instead of a source tree. It seems that Autopkgtest could be useful to run test suites that require root priviledges etc. > Here is the description of how the pkg-perl did their integration, > making most of the testing automatic: > http://pkg-perl.alioth.debian.org/autopkgtest.html Nice. Thanks for this information. > I think this would be a great asset for the team. What do you people think? There is no doubts that more testing would be useful. Also it would be useful if we learn to detect breakage of long dependency chains before upload... To certain extent we could address that problem with increased pressure to upstreams in order to convince them to tag releases and vendoring by tags as much as possible... -- Regards, Dmitry Smirnov. --- Democracy is a pathetic belief in the collective wisdom of individual ignorance. -- H. L. Mencken signature.asc Description: This is a digitally signed message part. ___ 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: Update to golang-yaml.v2 for golang 1.6
On Tuesday, 5 April 2016 3:40:13 AM AEST Martín Ferrari wrote: > On 05/04/16 02:22, Michael Hudson-Doyle wrote: > Again, this is my fault. The first golang packages I prepared had a + > instead of a ~, because I was mistaken. Had to package so many > dependencies, got some things wrong :( Don't be so hard on yourself, Martin. It is not much of a problem anyway and I wouldn't even recognise it as problem. :) -- Best wishes, Dmitry Smirnov. --- The great enemy of the truth is very often not the lie -- deliberate, contrived and dishonest, but the myth, persistent, persuasive, and unrealistic. Belief in myths allows the comfort of opinion without the discomfort of thought. -- John F Kennedy signature.asc Description: This is a digitally signed message part. ___ 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: golang-protobuf-extensions patch to disable failing test
On Tuesday, 5 April 2016 1:35:28 AM AEST Potter, Tim (HPE Linux Support) wrote: > Hi Dmitry. I'm only removing one of the tests out of this file - about 40 > lines out of 320 so a bit over 10%. I thought that would be OK. Of course it is OK. I didn't realise that you are removing just a fragment of file and not the whole file. However I've seen you dropping the entire file with patches more than once in other packages and I did not have a chance to tell you about it. > What do you mean by "debian/clien"? "debian/clean" of course. See dh_clean(1). > If there's a better way of removing > entire files (because that does happen occasionally, especially with tests) > I'm happy to do that in preference to a patch. OK. I think the better way is to include name of the file you want removed to "debian/clean" and `dh_clean` will delete it for you. Alternatively you can pass file names of files to remove as arguments to dh_clean. -- All the best, Dmitry Smirnov. --- Criticism may not be agreeable, but it is necessary. It fulfils the same function as pain in the human body. It calls attention to an unhealthy state of things. -- Winston Churchill signature.asc Description: This is a digitally signed message part. ___ 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: golang-protobuf-extensions patch to disable failing test
On Monday, 4 April 2016 11:10:51 PM AEST Potter, Tim (HPE Linux Support) wrote: > Hi again. I've made a small patch to golang-protobuf-extensions to allow > it to be built under the version of Go currently in stretch. According to > the github issue tracker it's a known problem with Go 1.5 and higher, but > has not been fixed at this stage. I've even added a DEP3 header recording > this info. Tim, removing file(s) using patches is unmaintainable and tend to break on slightest changes. I recommend adding file you want to remove to "debian/ clien" with relevant comments from patch header. I hope it make sense. -- Regards, Dmitry Smirnov. --- And those who were seen dancing were thought to be insane by those who could not hear the music. -- Friedrich Nietzsche signature.asc Description: This is a digitally signed message part. ___ 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#819699: ITP: golang-github-appc-goaci -- build go projects into ACIs
Package: wnpp Severity: wishlist Owner: Dmitry Smirnov <only...@debian.org> X-Debbugs-CC: debian-de...@lists.debian.org, pkg-go-maintainers@lists.alioth.debian.org Control: block 782441 by -1 Package name: golang-github-appc-goaci Version: 1.0.0 Upstream Author: The appc Authors / CoreOS Inc. License: Apache-2.0 URL: https://github.com/appc/goaci Description: build go projects into ACIs Goaci is a tool to build Go projects into ACIs which confirm to the Applicatio Container Specification. signature.asc Description: This is a digitally signed message part. ___ 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#817215: RFS: golang-github-alecthomas-template/0.0~git20151201.0.14fd436 -- text templates with newline elision for Go
Hi Peter, On Wednesday, 9 March 2016 12:24:19 AM AEDT Peter Colberg wrote: > I am looking for a sponsor for the package > "golang-github-alecthomas-template": Upstream does not have a license and commented the following: "as Go 1.6 now supports whitespace elision [1], I won't be making any further changes to this package and will probably delete it soon." [2] Is this package really needed? Please investigate. Meanwhile I'm tagging this bug as "wontfix" for now. Also please note that "BSD-style license" is not necessary the same as "BSD-3-clause". You can't make such assumption because there are too many "BSD style" licenses so techically speaking it can be any of them (and not limited to the list): https://fedoraproject.org/wiki/Licensing:BSD [1]: https://golang.org/pkg/text/template/#hdr-Text_and_spaces [2]: https://github.com/alecthomas/template/issues/3#issuecomment-188537775 -- Cheers, Dmitry Smirnov. --- Truth — Something somehow discreditable to someone. -- H. L. Mencken, 1949 signature.asc Description: This is a digitally signed message part. ___ 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] prometheus debian/init: sleep longer when stopping the daemon
On Saturday, 26 March 2016 6:34:47 PM AEDT Debian FTP Masters wrote: >* debian/init: sleep longer when stopping the daemon. Sleep loop could be completely replaced by "start-stop-daemon" with parameter "--retry=TERM/30/KILL/5"... Current solution may be insufficient if daemon needs even more time to terminate... -- All the best, Dmitry Smirnov. --- Good luck happens when preparedness meets opportunity. signature.asc Description: This is a digitally signed message part. ___ 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#819286: ITP: golang-github-coreos-go-tspi -- TSPI bindings for Golang
Package: wnpp Severity: wishlist Owner: Dmitry Smirnov <only...@debian.org> X-Debbugs-CC: debian-de...@lists.debian.org, pkg-go-maintainers@lists.alioth.debian.org Control: block 782441 by -1 Package name: golang-github-coreos-go-tspi Version: 0.0~git20160324 Upstream Author: CoreOS, Inc. License: Apache-2.0 URL: https://github.com/coreos/go-tspi Description: TSPI bindings for Golang Golang bindings and support code for libtspi and tpm communication This library provides a set of bindings for communication between code written in Go and libtspi, the library responsible for providing a TPM control interface. signature.asc Description: This is a digitally signed message part. ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
