Re: [pkg-go] Minutes for the DebConf17 BoF

[Shengjing Zhu]

On Sat, Aug 12, 2017 at 4:01 AM, Martín Ferrari  wrote:
> Git workflows
> -
>
> It was discussed about the problem of having so many different
> workflows, as it makes it difficult to work on packages prepared by
> other team members.
>
> The agreement was to find one standard and make it part of the team's
> policy and incorporate into dh-make-golang.
>
> To that end, it is requested that everyone sends an email to the mailing
> list describing their preferred workflow, and after a period of
> discussion we agree to a conclusion.
>

I just use gbp in the workflow.
* use `gbp import-orig` to update the upstream/pristine-tar/master
branch when new upstream released.
  The reason to use this, is we often need to exclude some files from
upstream. Thus I think we can't just pull all upstream commits to
upstream branch.
* use `gbp pq` to handle patches.
  It integrates the git workflow well.
* use `gbp buildpackge` to build

Currently I'm just not comfortable when I need to create an orig
tarball if the upstream doesn't have a TAG.
I hope #811565 can be fixed soon to get rid of this pain :)

-- 
Best regards,
Shengjing Zhu

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

[pkg-go] golang-github-rsc-letsencrypt is marked for autoremoval from testing

[Debian testing autoremoval watch]

golang-github-rsc-letsencrypt 0.0~git20160929.0.76104d2-3 is marked for 
autoremoval from testing on 2017-09-04

It (build-)depends on packages with these RC bugs:
869270: golang-github-xenolf-lego: golang-github-xenolf-lego FTBFS: 
vultr.go:52: c.client.CreateDnsRecord undefined


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

[pkg-go] golang-github-opencontainers-specs 1.0.0~rc2+git20160926.38.1c7c27d-2 MIGRATED to testing

[Debian testing watch]

FYI: The status of the golang-github-opencontainers-specs source package
in Debian's testing distribution has changed.

  Previous version: 1.0.0~rc2+git20160926.38.1c7c27d-1
  Current version:  1.0.0~rc2+git20160926.38.1c7c27d-2

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.

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

[pkg-go] golang-github-dnephin-cobra REMOVED from testing

[Debian testing watch]

FYI: The status of the golang-github-dnephin-cobra source package
in Debian's testing distribution has changed.

  Previous version: 1.5.1+git20170113.0.0e9ca70-2
  Current version:  (not in testing)
  Hint: 
Bug #868617: golang-github-dnephin-cobra FTBFS: test failures

The script that generates this mail tries to extract removal
reasons from comments in the britney hint files. Those comments
were not originally meant to be machine readable, so if the
reason for removing your package seems to be nonsense, it is
probably the reporting script that got confused. Please check the
actual hints file before you complain about meaningless removals.

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.

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

Re: [pkg-go] Minutes for the DebConf17 BoF

[Michael Hudson-Doyle]

On 12 August 2017 at 08:01, Martín Ferrari  wrote:

> Pkg-go BoF meeting minutes
> ==
>
> On Tuesday, we had the first in-person meeting of the team. We met for 2
> hours to discuss our current issues and to plan for the future.
>
> People present
> --
>
> Alexandre Viau (aviau)
> Martín Ferrari (Tincho)
> Paul Tagliamonte (paultag)
> Sascha Steinbiss (satta)
>
> Test files
> --
>
> We discussed the issues raised about shipping test sources and fixtures
> in the -dev packages. It was pointed out that they are not really needed
> for autopkgtest or for reverse-dependencies, but that it will involve a
> lot of work to achieve, so we decided to keep them for now.
>

Makes sense tbh.


> Using -dev packages for development
> ---
>
> Due to the friction that can bring with upstreams, it was agreed to
> continue discouraging to use -dev packages for everyday golang development.
>

+1


> Outdated packages and binNMUs
> -
>
> Paultag proposed automating the detection of packages which have been
> compiled with old versions of libraries. He will implement a first
> version that just sends emails to remind of needed binNMUs, with the
> idea of some day automatically triggering wanna-build.
>
> He also indicated that he wants this automation to detect and warn about
> circular dependencies.
>

Sounds good.


> Git workflows
> -
>
> It was discussed about the problem of having so many different
> workflows, as it makes it difficult to work on packages prepared by
> other team members.
>
> The agreement was to find one standard and make it part of the team's
> policy and incorporate into dh-make-golang.
>
> To that end, it is requested that everyone sends an email to the mailing
> list describing their preferred workflow, and after a period of
> discussion we agree to a conclusion.
>

I think I /slightly/ prefer the upstream branch to be upstream's git
history not a series of imports of tarballs. But I'm not set on it, and gbp
doesn't really get on with this approach if you're just packaging a random
commit rather than a tag AFAICS.


> dh-make-golang
> --
>
> A few times people expressed the desire for dh-make-golang to grow an
> `--update` option, as most packages are trivial to update, but tedious
> to do so.
>

Oh yes please.  Although the ideas that would let gbp import-orig --uscan
work without upstream tarballs would also be fine.


> Satta requested an option to disable SSL verification for badly
> configured redirection sites.
>
> x/tools package
> ---
>
> We discussed the current breakage in x/tools, and agreed that it is a
> core package and that we should make it a shared responsibility to keep
> it in a good shape.
>

It is also a random bag of stuff, it's not really the best bit of factoring
from upstream :)


> gccgo support
> -
>
> We talked about the status of gccgo, paultag explained how mainline
> golang promises the compiler will always be buildable by gccgo, and how
> that makes bootstrapping and cross-building way simpler.
>
> We agreed on working towards making it a first-class citizen in the
> future, using golang-any by default, and only reverting to golang-go
> when needed.
>

Makes sense. Which gccgo arches are really being used today though? MIPS I
guess, but that really should get golang-go once we figure out how to do
that.


> API changes in upstream
> ---
>
> We ranted at length about upstreams, and noted that we need a system
> that provides early warning of API breakages. We discussed using ratt
> and autopkgtest for that purpose.
>

It would be good to have some automation and central resources around this
for sure.


> Aviau pointed out that he usually requests upstreams to make releases
> and that he is usually successful. Tincho pointed out the problems with
> meaningless releases and with upstreams releasing once and then
> forgetting to do it when needed.
>
> We discussed the possibility of changing "soname"s by renaming packages
> when we detect API incompatibilities, but concluded that in general it
> is too much work


Yeah, don't do this :)


> and that it makes more sense to try and fix
> reverse-dependencies by bugging upstream or patching them ourselves.
>




> Team collaboration
> --
>
> On the topic of team collaboration, we agreed to avoid using the DM ACL
> mechanism too much, and instead help active contributors to become DDs.
>

https://nm.debian.org/process/198 :)

(Although the bottleneck is me answering my DAM currently...)


> We also revisited the policy on team uploads, and concluded that we want
> to continue with avoiding hard ownership of packages and that by default
> everything is team-maintained.
>

+100, _especially_ for -dev packages.

Cheers,
mwh

Plan of action
> --
>
> There was some talk about things to do in the immediate future 

Re: [pkg-go] Minutes for the DebConf17 BoF

[Michael Stapelberg]

Thanks for sending these out. Comments inline:

On Fri, Aug 11, 2017 at 10:01 PM, Martín Ferrari  wrote:

> Pkg-go BoF meeting minutes
> ==
>
> On Tuesday, we had the first in-person meeting of the team. We met for 2
> hours to discuss our current issues and to plan for the future.
>
> People present
> --
>
> Alexandre Viau (aviau)
> Martín Ferrari (Tincho)
> Paul Tagliamonte (paultag)
> Sascha Steinbiss (satta)
>
> Test files
> --
>
> We discussed the issues raised about shipping test sources and fixtures
> in the -dev packages. It was pointed out that they are not really needed
> for autopkgtest or for reverse-dependencies, but that it will involve a
> lot of work to achieve, so we decided to keep them for now.
>
> Using -dev packages for development
> ---
>
> Due to the friction that can bring with upstreams, it was agreed to
> continue discouraging to use -dev packages for everyday golang development.
>
> Outdated packages and binNMUs
> -
>
> Paultag proposed automating the detection of packages which have been
> compiled with old versions of libraries. He will implement a first
> version that just sends emails to remind of needed binNMUs, with the
> idea of some day automatically triggering wanna-build.
>
> He also indicated that he wants this automation to detect and warn about
> circular dependencies.
>
> Git workflows
> -
>
> It was discussed about the problem of having so many different
> workflows, as it makes it difficult to work on packages prepared by
> other team members.
>
> The agreement was to find one standard and make it part of the team's
> policy and incorporate into dh-make-golang.
>
> To that end, it is requested that everyone sends an email to the mailing
> list describing their preferred workflow, and after a period of
> discussion we agree to a conclusion.
>

This sounds very good.

I have come to appreciate the following properties of working with
git-buildpackage:

1. I store packaging in e.g. ~/d/pkg/gocryptfs and build using `gbp
buildpackage --git-export-dir=~/d/out/gocryptfs`. By using
--git-export-dir, my working copy always stays clean. By collecting the
output files per package, I can easily debdiff between versions. This point
is informational and shouldn’t have any bearing on a canonical workflow.

2. My ~/.gbp.conf reads https://paste.debian.net/hidden/a48afca2/
(informational)

3. To import a new upstream version, I run `gbp import-orig --uscan`. This
of course only works with tagged releases until #811565 is fixed (hopefully
soon).

4. To update debian/changelog, I run `gbp dch -R --commit`. Note that this
goes against our current policy of editing debian/changelog with an
UNRELEASED entry — when using gbp-dch, the changelog is entirely
auto-generated from git (but you do have the option to amend it before
committing). Hence, I’d suggest we update that policy and start using
gbp-dch.

5. I use quilt for managing patches, and am reasonably happy with that,
i.e. I personally don’t see the need for anything more fancy than that,
especially given that we usually only carry very few patches per package.
Some of our packages use branches which only contain debian/, not the
upstream source. This breaks quilt and confuses me. I’d suggest we codify
that the branch must contain the upstream sources plus debian/.

Here are some more thoughts, not directly related to how I maintain my own
packages:

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. Whenever I come across a package which isn’t using
pristine-tar, the generated orig tarball will have a different checksum,
and my upload will be rejected. I’d suggest we codify that pristine-tar is
a requirement.

7. We don’t currently have a guideline with regards to branch naming,
especially when maintaining branches for multiple debian versions (e.g.
stretch, buster, stretch-backports, …). I’d suggest we adopt the
debian/ branch naming scheme, e.g. debian/buster is the default
branch, backports can be found in debian/stretch-backports, etc.

8. (Optional/best effort) I recently came to understand that dgit is
thought of as a universal approach for new users/maintainers to easily
contribute to packaging (you get the same style of git checkout of any
package in the archive). We should verify the above constraints still leave
us in a place where dgit works well — it will work for any package, but it
will work better for packages which are `dgit push`ed. I don’t yet know
what the requirements for that are.

Thoughts? :)


>
> dh-make-golang
> --
>
> A few times people expressed the desire for dh-make-golang to grow an
> `--update` option, as most packages are trivial to update, but tedious
> to do so.
>

See point ③ above — I’m optimistic that we can use uscan for that 

[pkg-go] Bug#872293: nmu: loads of golang stuff

[Paul Tagliamonte]

Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: binnmu
Severity: normal
X-Debbugs-CC: pkg-go-maintainers@lists.alioth.debian.org
thanks

Howdy, release!

Due to the way that Go packages are built, I've started keeping an eye
on packages that were built using an out of date version of another
corner of the archive.

I've written a script that generates a list of things to binNMU, but
I've only just written it on the flight back from DebConf, and I am not
super sure of it yet.

So, here's a list of some things that look sensible by eye. I've got
a *lot* more, so if this turns out OK, I'll send another bug with more.

  nmu sia . any . -m 'out of date'
  nmu prometheus-node-exporter . any . -m 'out of date'
  nmu go-md2man . any . -m 'out of date'
  nmu webhook . any . -m 'out of date'
  nmu kcptun . any . -m 'out of date'
  nmu acbuild . any . -m 'out of date'
  nmu notary . any . -m 'out of date'
  nmu dh-make-golang . any . -m 'out of date'
  nmu robustirc-bridge . any . -m 'out of date'
  nmu runc . any . -m 'out of date'
  nmu prometheus . any . -m 'out of date'
  nmu skydns . any . -m 'out of date'
  nmu gb . any . -m 'out of date'
  nmu golang-golang-x-tools . any . -m 'out of date'
  nmu systemd-docker . any . -m 'out of date'
  nmu golang-github-xordataexchange-crypt . any . -m 'out of date'
  nmu abci . any . -m 'out of date'
  nmu prometheus-varnish-exporter . any . -m 'out of date'
  nmu gosu . any . -m 'out of date'
  nmu rclone . any . -m 'out of date'
  nmu docker-registry . any . -m 'out of date'
  nmu golang-petname . any . -m 'out of date'
  nmu prometheus-mongodb-exporter . any . -m 'out of date'
  nmu prometheus-mysqld-exporter . any . -m 'out of date'
  nmu consul . any . -m 'out of date'
  nmu minica . any . -m 'out of date'
  nmu gitlab-ci-multi-runner . any . -m 'out of date'
  nmu ratt . any . -m 'out of date'

Thank you!
  Paul

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

[pkg-go] golang-github-neowaylabs-wabbit_0.0~git20170406.0.cfb5237-2_amd64.changes ACCEPTED into unstable

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 15 Aug 2017 17:15:43 +0200
Source: golang-github-neowaylabs-wabbit
Binary: golang-github-neowaylabs-wabbit-dev
Architecture: source all
Version: 0.0~git20170406.0.cfb5237-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 

Changed-By: Sascha Steinbiss 
Description:
 golang-github-neowaylabs-wabbit-dev - Golang AMQP mocking library
Changes:
 golang-github-neowaylabs-wabbit (0.0~git20170406.0.cfb5237-2) unstable; 
urgency=medium
 .
   * Fix tests failing due to alignment issues on ARM and i386.
Checksums-Sha1:
 e70073bee3139f2cdd9e4a73963e1b1766571160 2120 
golang-github-neowaylabs-wabbit_0.0~git20170406.0.cfb5237-2.dsc
 c65c474c6b00a2976f565fc13cd88f54b3ebf236 2400 
golang-github-neowaylabs-wabbit_0.0~git20170406.0.cfb5237-2.debian.tar.xz
 0c3c1715ebc28746830c308f9404d0d855aa3571 18504 
golang-github-neowaylabs-wabbit-dev_0.0~git20170406.0.cfb5237-2_all.deb
 7a517990c67843805b6793178a5637d863376416 5557 
golang-github-neowaylabs-wabbit_0.0~git20170406.0.cfb5237-2_amd64.buildinfo
Checksums-Sha256:
 3301a1921c6bd674c4e8d166c8420502f1cfef0e1e88f854d1c21cd4a3c612db 2120 
golang-github-neowaylabs-wabbit_0.0~git20170406.0.cfb5237-2.dsc
 be2175775108ede56138e0b0ebf8217e0edcef11786f8c2f78964a18fda85338 2400 
golang-github-neowaylabs-wabbit_0.0~git20170406.0.cfb5237-2.debian.tar.xz
 0a9d098502849abd06384eda76ffe2950692ed230d04b3c44d92cdad7b8ce338 18504 
golang-github-neowaylabs-wabbit-dev_0.0~git20170406.0.cfb5237-2_all.deb
 6f02e68a01487ce890f58ee9d9a234476652ac466234c28d1509b978b9607566 5557 
golang-github-neowaylabs-wabbit_0.0~git20170406.0.cfb5237-2_amd64.buildinfo
Files:
 a0f2130e2df715cb3c099fa428f50ae3 2120 devel extra 
golang-github-neowaylabs-wabbit_0.0~git20170406.0.cfb5237-2.dsc
 01a7b6323b76b179eac812c0ca5a1549 2400 devel extra 
golang-github-neowaylabs-wabbit_0.0~git20170406.0.cfb5237-2.debian.tar.xz
 8a4311800949c1eb21657e80052bf6e5 18504 devel extra 
golang-github-neowaylabs-wabbit-dev_0.0~git20170406.0.cfb5237-2_all.deb
 03fdd25f3bdf6faeefa44b57e9fd3bd4 5557 devel extra 
golang-github-neowaylabs-wabbit_0.0~git20170406.0.cfb5237-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEhFH5F4Fy5+Lcc/eVUfhKj+zKfgkFAlmTERAACgkQUfhKj+zK
fglDkAf+Mo+Dp5DPRvhrM9+uSuHlU+G4xIqDq9qwhigAe7hfqTv5AASCY3A/pe/n
BSqRdVRkiJa5XRXstd7M/YuEn79N9OxCe7ZeLG1bPFvHRsYSs67Bs/Uuppqqw87+
/zWob1CgxlU3lsT+FzgrJ/uVrABNsq8ELKqV2xYh2/jKjC0BB0zip//zDY7v/aoU
3U7PEsX6KlnByZjHCMIFWJWAol1PfufDva7tZAYysjevI6ggrTvctCdvYQgWRvtS
jeGCCzeYQLI/pMPb2HXF3mk6PygCwmp67uc7Yn49FXlCaDH0tkBODvsY59LmToaG
ticunZhFBPjAUp3iA0Aoc3OnHo1VDw==
=vQ5H
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

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

[pkg-go] Processing of golang-github-neowaylabs-wabbit_0.0~git20170406.0.cfb5237-2_amd64.changes

[Debian FTP Masters]

golang-github-neowaylabs-wabbit_0.0~git20170406.0.cfb5237-2_amd64.changes 
uploaded successfully to localhost
along with the files:
  golang-github-neowaylabs-wabbit_0.0~git20170406.0.cfb5237-2.dsc
  golang-github-neowaylabs-wabbit_0.0~git20170406.0.cfb5237-2.debian.tar.xz
  golang-github-neowaylabs-wabbit-dev_0.0~git20170406.0.cfb5237-2_all.deb
  golang-github-neowaylabs-wabbit_0.0~git20170406.0.cfb5237-2_amd64.buildinfo

Greetings,

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

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

[pkg-go] golang-github-dcso-bloom_0.2.0-1_amd64.changes ACCEPTED into unstable

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 14 Aug 2017 17:44:25 +0200
Source: golang-github-dcso-bloom
Binary: golang-github-dcso-bloom-dev golang-github-dcso-bloom-cli
Architecture: source amd64 all
Version: 0.2.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 

Changed-By: Sascha Steinbiss 
Description:
 golang-github-dcso-bloom-cli - highly efficient bloom filter implementation 
for Go, CLI tool
 golang-github-dcso-bloom-dev - highly efficient bloom filter implementation 
for Go
Changes:
 golang-github-dcso-bloom (0.2.0-1) unstable; urgency=medium
 .
   * New upstream release.
Checksums-Sha1:
 098dbddab470f3d3de61fdce36ffc68af462e41f 1950 
golang-github-dcso-bloom_0.2.0-1.dsc
 78609b5d1ab25ecc216108f37a21d383e7e6040e 11819 
golang-github-dcso-bloom_0.2.0.orig.tar.gz
 1941bafc658727c39c5a8e7ea633a6b31f163de0 4412 
golang-github-dcso-bloom_0.2.0-1.debian.tar.xz
 1e99005c4f12528f9fd12da6fc6ba072e8caa274 651218 
golang-github-dcso-bloom-cli_0.2.0-1_amd64.deb
 6d6d2a41f7fa5090284f92165c20330bd16f5dd7 10278 
golang-github-dcso-bloom-dev_0.2.0-1_all.deb
 91783024303ff8dec77e7d3e83059ef83bdf7f2b 5873 
golang-github-dcso-bloom_0.2.0-1_amd64.buildinfo
Checksums-Sha256:
 0766ba4f7bdbda799def601cd79119e9ac70461185a696b118ed1505a0a03af9 1950 
golang-github-dcso-bloom_0.2.0-1.dsc
 65a6490adfa434e165ad6c0a4988a1aa1de4436aadc8c9162f91b884d418ca3d 11819 
golang-github-dcso-bloom_0.2.0.orig.tar.gz
 a247a72bc8ed916e6a80297dbe14c537246d141d699e9b00face82aa9f8b0335 4412 
golang-github-dcso-bloom_0.2.0-1.debian.tar.xz
 6fd75871e1b0d73f3f2137e5f7e2126512ce50951f4ee5bd2b90b86aca87fcc8 651218 
golang-github-dcso-bloom-cli_0.2.0-1_amd64.deb
 123ad49809669b5ac3d385b87e30929955c66baab1273b3594daf4f4c983542d 10278 
golang-github-dcso-bloom-dev_0.2.0-1_all.deb
 3376aa9c3454e520a1ee259a2cf1ae0b9386ad3744f5886c3a5e3f7fc96b0f48 5873 
golang-github-dcso-bloom_0.2.0-1_amd64.buildinfo
Files:
 62494417f39736ce7e95848d61799d67 1950 devel extra 
golang-github-dcso-bloom_0.2.0-1.dsc
 7986108b3e92bdb2e8c8b0e4c16bb810 11819 devel extra 
golang-github-dcso-bloom_0.2.0.orig.tar.gz
 e35ebc4dabc7328f52a6ac918d9d9df8 4412 devel extra 
golang-github-dcso-bloom_0.2.0-1.debian.tar.xz
 83e9648530acd40093f3d871ed619bee 651218 devel extra 
golang-github-dcso-bloom-cli_0.2.0-1_amd64.deb
 aee10c87c80e95a95f90325d3317a1ea 10278 devel extra 
golang-github-dcso-bloom-dev_0.2.0-1_all.deb
 23da330ba6eed0cca0a2772fddf34b6e 5873 devel extra 
golang-github-dcso-bloom_0.2.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEhFH5F4Fy5+Lcc/eVUfhKj+zKfgkFAlmS3IgACgkQUfhKj+zK
fgk/cwf/UmlAP63dIIRLHUrN/uBjbKZ3EmdyTJfTI+FYLl6K9nUpBz9Z2M1+C2BH
lMhta0EnvKAmlqO02NwBLp9InxmhR37nrwNUPrp62aqTWMoJ1QL4gHJdce4yCxlR
cSpfUIqLNcHuzI907b+/mt5vgZjkO5PL2QMipkFJMRwjNKHw1xMxIxnVfBtb6E2H
1yCiDgE6ILMQei5rC3szmFfODWAFRSTBi9k9Wwt2qeCChfxAlHR+8ffiVdld81B+
sDcpP18KLu1SEsikmVPmOtdMAjQ9gjaTnnjIm5qHYKdS+j1KobA+sf5OuRTu6nxC
unnQnJXw+rk9aFLHDaAJhFg/1vtB3w==
=7W4E
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

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

[pkg-go] Processing of golang-github-dcso-bloom_0.2.0-1_amd64.changes

[Debian FTP Masters]

golang-github-dcso-bloom_0.2.0-1_amd64.changes uploaded successfully to 
localhost
along with the files:
  golang-github-dcso-bloom_0.2.0-1.dsc
  golang-github-dcso-bloom_0.2.0.orig.tar.gz
  golang-github-dcso-bloom_0.2.0-1.debian.tar.xz
  golang-github-dcso-bloom-cli_0.2.0-1_amd64.deb
  golang-github-dcso-bloom-dev_0.2.0-1_all.deb
  golang-github-dcso-bloom_0.2.0-1_amd64.buildinfo

Greetings,

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

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

[pkg-go] Bug#872206: restic: broken symlinks: /usr/share/doc/restic/_static/*/* -> ../../../../sphinx_rtd_theme/*/*

[Andreas Beckmann]

Package: restic
Version: 0.7.1-1
Severity: normal
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

>From the attached log (scroll to the bottom...):

1m50.4s ERROR: FAIL: Broken symlinks:
  /usr/share/doc/restic/_static/js/theme.js -> 
../../../../sphinx_rtd_theme/static/js/theme.js
  /usr/share/doc/restic/_static/js/modernizr.min.js -> 
../../../../sphinx_rtd_theme/static/js/modernizr.min.js
  /usr/share/doc/restic/_static/fonts/fontawesome-webfont.woff -> 
../../../../sphinx_rtd_theme/static/fonts/fontawesome-webfont.woff
  /usr/share/doc/restic/_static/fonts/fontawesome-webfont.ttf -> 
../../../../sphinx_rtd_theme/static/fonts/fontawesome-webfont.ttf
  /usr/share/doc/restic/_static/fonts/fontawesome-webfont.svg -> 
../../../../sphinx_rtd_theme/static/fonts/fontawesome-webfont.svg
  /usr/share/doc/restic/_static/fonts/fontawesome-webfont.eot -> 
../../../../sphinx_rtd_theme/static/fonts/fontawesome-webfont.eot
  /usr/share/doc/restic/_static/fonts/RobotoSlab-Regular.ttf -> 
../../../../sphinx_rtd_theme/static/fonts/RobotoSlab-Regular.ttf
  /usr/share/doc/restic/_static/fonts/RobotoSlab-Bold.ttf -> 
../../../../sphinx_rtd_theme/static/fonts/RobotoSlab-Bold.ttf
  /usr/share/doc/restic/_static/fonts/Lato-Regular.ttf -> 
../../../../sphinx_rtd_theme/static/fonts/Lato-Regular.ttf
  /usr/share/doc/restic/_static/fonts/Lato-Bold.ttf -> 
../../../../sphinx_rtd_theme/static/fonts/Lato-Bold.ttf
  /usr/share/doc/restic/_static/fonts/Inconsolata-Regular.ttf -> 
../../../../sphinx_rtd_theme/static/fonts/Inconsolata-Regular.ttf
  /usr/share/doc/restic/_static/fonts/Inconsolata-Bold.ttf -> 
../../../../sphinx_rtd_theme/static/fonts/Inconsolata-Bold.ttf
  /usr/share/doc/restic/_static/css/theme.css -> 
../../../../sphinx_rtd_theme/static/css/theme.css
  /usr/share/doc/restic/_static/css/badge_only.css -> 
../../../../sphinx_rtd_theme/static/css/badge_only.css


Is restic missing a Depends/Recommends/Suggests: sphinx-rtd-theme-common ?


cheers,

Andreas


restic_0.7.1-1.log.gz
Description: application/gzip
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers