I guess it would be better to feed the source files rather than the directory to dpkg-source.
On 14 June 2016 at 08:36, Dmitry Smirnov <only...@debian.org> wrote: > 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 > > _______________________________________________ > Pkg-go-maintainers mailing list > pkg-go-maintain...@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
