Score:0

Can't make my Architecture: any debian control file work

us flag

I'm POC-ing a simple .deb package.

Its content is:

enter image description here

As you can see, I have a FW (that will be loaded to another machine form the host) and a .cpp file that will be compiled by the postinst, which looks something like:

set -e
cd /share/opt/ && make install # I'll move it to a sub-dir inside `opt` later...

When building the package with dpkg-deb --build --root-owner-group hello_1.0_any I get a nice .deb file hello_1.0_any.deb which I can't install:

package architecture (any) does not match system (amd64)

However, when running with architecture "all", it works.

My control file looks like:

Package: hello-world
Version: 1.0
Architecture: any
Maintainer: _
Description: hello world

Why would this break?

Why Don't I use "all"? Because .deb postinst compiles a driver on the target machine, which is an architecture-dependent, but the sources are not - so "any" seems more appropriate, see docs:

An architecture wildcard identifying a set of Debian machine architectures, see Architecture wildcards. any matches all Debian machine architectures and is the most frequently used.

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.