Package: libsensors4-dev
Version: 1:3.6.0-6
Severity: important
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs
Control: affects -1 + src:mrtgutils src:wmtemp

libsensors4-dev is wrongly marked Multi-Arch: foreign. Thus a build
dependency on libsensors4-dev results in the build architecture library
while the host architecture one was requested. This causes cross build
failures for the affected packages. libsensors4-dev must not be
Multi-Arch: foreign. This borders on an rc-bug. Beyond removing the
foreign marking, I suggest turning it Architecture: any + Multi-Arch:
same (also known as the multiarch interpreter workaround). Doing so
fixes the cross builds. I strongly prefer fixing this in time for
bullseye as this kind of issue causes difficult to diagnose failures and
is a gross multiarch violation.

Helmut
diff --minimal -Nru lm-sensors-3.6.0/debian/changelog 
lm-sensors-3.6.0/debian/changelog
--- lm-sensors-3.6.0/debian/changelog   2021-01-25 01:03:48.000000000 +0100
+++ lm-sensors-3.6.0/debian/changelog   2021-01-28 15:02:17.000000000 +0100
@@ -1,3 +1,10 @@
+lm-sensors (1:3.6.0-6.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Convert libsensors4-dev to Architecture: any. (Closes: #-1)
+
+ -- Helmut Grohne <hel...@subdivi.de>  Thu, 28 Jan 2021 15:02:17 +0100
+
 lm-sensors (1:3.6.0-6) unstable; urgency=medium
 
   * Restart fancontrol.service after power sleep.  Closes: #664141.
diff --minimal -Nru lm-sensors-3.6.0/debian/control 
lm-sensors-3.6.0/debian/control
--- lm-sensors-3.6.0/debian/control     2021-01-11 00:21:45.000000000 +0100
+++ lm-sensors-3.6.0/debian/control     2021-01-28 15:02:17.000000000 +0100
@@ -77,9 +77,9 @@
  development.
 
 Package: libsensors4-dev
-Architecture: all
-Multi-Arch: foreign
-Depends: libsensors-dev (>= ${source:Version}), ${misc:Depends}
+Architecture: any
+Multi-Arch: same
+Depends: libsensors-dev (= ${binary:Version}), ${misc:Depends}
 Section: libdevel
 Description: transitional dummy package
  This is a transitional dummy package, it can be safely removed.

Reply via email to