Package: dkms Version: 2.6.1-4 Severity: normal Tags: patch Dear Maintainer,
Running dkms mkdeb --source-only generates an architecture-dependent package, while it should generate an architecture-independent package. Previous versions generated an architecture-independent package even when --binaries-only option was given, as reported in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832558 However, the fix breaks the expected (and correct) behavior when --source-only is given. The attached patch solves this issue. Note that if the --source-only option is not given, the generated package will be still architecture-dependent. I'm not sure if this would be the correct behavior (from my understanding should be the correct way, as it is including architecture-dependent binaries). This bug is confirmed on dkms 2.6.1-4 (current version in buster). -- System Information: Debian Release: 10.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ca_ES.utf8, LC_CTYPE=ca_ES.utf8 (charmap=UTF-8), LANGUAGE=ca_ES.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages dkms depends on: ii build-essential 12.6 ii coreutils 8.30-3 ii dpkg-dev 1.19.7 ii gcc 4:8.3.0-1 ii kmod 26-1 ii make 4.2.1-1.2 ii patch 2.7.6-3 Versions of packages dkms recommends: ii fakeroot 1.23-1 ii linux-headers-amd64 4.19+105 ii lsb-release 10.2019051400 ii sudo 1.8.27-1 Versions of packages dkms suggests: ii menu 2.1.47+b1 pn python3-apport <none> -- no debconf information
2979c2979,2983 < debian_build_arch=$(dpkg-architecture -qDEB_BUILD_ARCH) --- > if [[ $source_only ]];then > debian_build_arch=all > else > debian_build_arch=$(dpkg-architecture -qDEB_BUILD_ARCH) > fi
