Hi, Quoting Andreas Beckmann (2024-05-27 18:52:58) > On 27/05/2024 18.32, Johannes Schauer Marin Rodrigues wrote: > > I'm inclined to just restrict the kernel to amd64, arm64 and riscv64 as the > > relevant hardware is unlikely (or rather impossible) to be found on other > > architectures. Or do you think that this would be a bed "solution"? > > No objections. > > Either make the package Architecture: <list> instead of all or try > BUILD_EXCLUSIVE_ARCH="<list>" in dkms.conf > (directive exists, but I've never used it and AFAIK no other Debian > package does use it; maybe needs kernel architectures instead of Debian > architectures) > or if you can anchor it on some CONFIG_* option > BUILD_EXCLUSIVE_CONFIG="CONFIG_FOO !CONFIG_BAR" > (it's an AND-ed list, no OR possible) > > You may need to add debian/tests/autopkgtest-pkg-dkms.conf with > architecture = <list> > if the package is not arch:all as autodep8 may not (be able to) take the > architecture list of the binary packages into account.
the package is already using: BUILD_EXCLUSIVE_CONFIG="CONFIG_WIRELESS" which prevents building it for the cloud kernel, for example. I read a bit into the dkms.in sources and found that BUILD_EXCLUSIVE_ARCH is a bash regex, so I set it up like tihs now: BUILD_EXCLUSIVE_ARCH="^(aarch64|x86_64|riscv64)$" The architectures seem to be what "uname -m" is printing. Thanks! cheers, josch
signature.asc
Description: signature
