[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

How to best express that a particular golang-*-dev only builds on some archs?



All,

It seems

https://tracker.debian.org/pkg/golang-github-google-go-tpm-tools

doesn't work on ppc64el and s390x which I reported upstream:

https://github.com/google/go-tpm-tools/issues/703

The package is Architecture:all and we don't notice any problem until
the golang-*-dev package is used as a (Build-)Depends.

The autopkgtest/debci checks trigger this situation well, and currently
fails.

In the 0.4.7-3 upload, I added

Build-Depends: unsupported-architecture [ppc64el s390x],

which clarify that you can't build the Architecture:all package on
ppc64el+s390x (a somewhat theoretetical concern), but it doesn't help
with users of the golang-*-dev package.

What is the right approach here?

I think this is a problematic package to have as a dependency
regardless, as it implicitly creates a dependency on libssl3t64 and
doesn't work on all release archs.

Several packages in Debian are patched to avoid using
github.com/google/go-tpm-tools because we didn't have it packaged.  Now
we could remove those patches, but until things works on all release
archs, maybe we should wait with that.

Another aspects is that normally this package is only used during
self-checks, not during actual real running code.  So introducing a lot
of arch-specific complexity just because of self-tests may be the wrong
trade-off.

/Simon

Attachment: signature.asc
Description: PGP signature


Reply to: