Your message dated Fri, 22 Jun 2018 14:45:27 +1000
with message-id <34786551.VEsZIAC1Vo@deblab>
and subject line Done: notary: FTBFS in testing
has caused the Debian Bug report #816984,
regarding notary: FTBFS in testing
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
816984: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816984
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:notary
Version: 0.0~git20150801.0.8e8122e-2
User: sanv...@debian.org
Usertags: binary-indep
Severity: important

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(i.e. only architecture-independent packages), and it failed:

--------------------------------------------------------------------------------
[...]
 debian/rules build-indep
dh build-indep --buildsystem=golang --with=golang
   dh_testdir -i -O--buildsystem=golang
   dh_update_autotools_config -i -O--buildsystem=golang
   dh_auto_configure -i -O--buildsystem=golang
   dh_auto_build -i -O--buildsystem=golang
        go install -v github.com/docker/notary/client 
github.com/docker/notary/client/changelist github.com/docker/notary/cmd/notary 
github.com/docker/notary/cmd/notary-server 
github.com/docker/notary/cmd/notary-signer 
github.com/docker/notary/cryptoservice github.com/docker/notary/errors 
github.com/docker/notary/keystoremanager 
github.com/docker/notary/pkg/passphrase github.com/docker/notary/proto 
github.com/docker/notary/server github.com/docker/notary/server/handlers 
github.com/docker/notary/server/storage 
github.com/docker/notary/server/timestamp github.com/docker/notary/signer 
github.com/docker/notary/signer/api github.com/docker/notary/signer/keys 
github.com/docker/notary/trustmanager github.com/docker/notary/utils 
github.com/docker/notary/version
github.com/Sirupsen/logrus
github.com/docker/distribution/uuid
github.com/docker/notary/client/changelist
github.com/agl/ed25519/edwards25519
github.com/agl/ed25519

[... snipped ...]

github.com/docker/notary/server/storage
github.com/tent/canonical-json-go
github.com/docker/notary/server/timestamp
github.com/docker/notary/server/handlers
github.com/docker/notary/utils
github.com/docker/notary/server
github.com/golang/protobuf/proto
golang.org/x/net/internal/timeseries
golang.org/x/net/trace
google.golang.org/grpc/codes
google.golang.org/grpc/credentials
google.golang.org/grpc/grpclog
google.golang.org/grpc/metadata
golang.org/x/net/http2/hpack
golang.org/x/net/http2
google.golang.org/grpc/transport
google.golang.org/grpc
github.com/docker/notary/proto
# github.com/docker/notary/proto
src/github.com/docker/notary/proto/signer.pb.go:248: cannot use 
_KeyManagement_CreateKey_Handler (type func(interface {}, context.Context, 
grpc.Codec, []byte) (interface {}, error)) as type grpc.methodHandler in field 
value
src/github.com/docker/notary/proto/signer.pb.go:252: cannot use 
_KeyManagement_DeleteKey_Handler (type func(interface {}, context.Context, 
grpc.Codec, []byte) (interface {}, error)) as type grpc.methodHandler in field 
value
src/github.com/docker/notary/proto/signer.pb.go:256: cannot use 
_KeyManagement_GetKeyInfo_Handler (type func(interface {}, context.Context, 
grpc.Codec, []byte) (interface {}, error)) as type grpc.methodHandler in field 
value
src/github.com/docker/notary/proto/signer.pb.go:315: cannot use 
_Signer_Sign_Handler (type func(interface {}, context.Context, grpc.Codec, 
[]byte) (interface {}, error)) as type grpc.methodHandler in field value
github.com/dvsekhvalnov/jose2go/base64url
github.com/dvsekhvalnov/jose2go/arrays
github.com/dvsekhvalnov/jose2go/aes
github.com/dvsekhvalnov/jose2go/compact
github.com/dvsekhvalnov/jose2go/kdf
github.com/dvsekhvalnov/jose2go/keys/ecc
github.com/dvsekhvalnov/jose2go/padding
github.com/dvsekhvalnov/jose2go
github.com/lib/pq/hstore
github.com/qor/inflection
github.com/jinzhu/gorm
github.com/docker/distribution/health
github.com/miekg/pkcs11
github.com/docker/notary/signer/keys
dh_auto_build: go install -v github.com/docker/notary/client 
github.com/docker/notary/client/changelist github.com/docker/notary/cmd/notary 
github.com/docker/notary/cmd/notary-server 
github.com/docker/notary/cmd/notary-signer 
github.com/docker/notary/cryptoservice github.com/docker/notary/errors 
github.com/docker/notary/keystoremanager 
github.com/docker/notary/pkg/passphrase github.com/docker/notary/proto 
github.com/docker/notary/server github.com/docker/notary/server/handlers 
github.com/docker/notary/server/storage 
github.com/docker/notary/server/timestamp github.com/docker/notary/signer 
github.com/docker/notary/signer/api github.com/docker/notary/signer/keys 
github.com/docker/notary/trustmanager github.com/docker/notary/utils 
github.com/docker/notary/version returned exit code 2
debian/rules:12: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2
--------------------------------------------------------------------------------

Sorry not to have a fix, as I am reporting many bugs similar to
this one. The common hints are:

* If the only architecture-independent packages are dummy transitional
ones and they were released with jessie, the easy fix is to drop them
now.

* When using "dh", it is allowed to use (independently)
optional targets override_dh_foo-arch and override_dh_foo-indep
(for several values of "foo").


Once that both "dpkg-buildpackage -A" and "dpkg-buildpackage -B" work
properly, the package would be suitable to be uploaded in source-only
form if you wish.

Thanks.

--- End Message ---
--- Begin Message ---
Current version of the package [0.6.1~ds1-1] builds in testing successfully.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 816...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---

Reply via email to