Patrick Schleizer:
> I am maintaining two Debian derivatives distributions, Whonix and
> Kicksecure. (Open Source) I hope you don't mind my question.
>
> I am trying to build a custom meta package with 'Architecture: all' that
> has an architecture specific dependency:
> hardened-malloc [amd64]
As best I can tell at the moment, from the point of view of dh and/or dpkg with
this would be "for all architectures install the following, including
hardened-malloc [amd64]" -- i.e. I think this logic is interpreted as a request
to install an amd64 package regardless of the local architecture.
I've been having a read through section 7.1. of Debian Policy concerning
architecture-specific entries in control fields:
https://www.debian.org/doc/debian-policy/ch-relationships
and this paragraph describes the problem -- the architecture-specific entries
are only allowed on build relationship fields:
"For binary relationship fields and the Built-Using field, the
architecture restriction syntax is only supported in the source
package control file debian/control. When the corresponding binary
package control file is generated, the relationship will either be
omitted or included without the architecture restriction based on
the architecture of the binary package. This means that architecture
restrictions must not be used in binary relationship fields for
architecture-independent packages"
P.S. Thanks very much for your work on whonix :)
-- Chris
--
Chris Knadle
Chris.Knadle@coredump.us
Attachment:
signature.asc
Description: OpenPGP digital signature