Hi. My script "check-nocheck" tells me that the attached patch would
be enough to fix the bug.

(But no claim that this is the only possible fix, maybe there is
another way which does not involve dropping <!nocheck> annotations).

Thanks.
commit e7a01478679b87883e30d28c199270b5e4e92037
Author: Santiago Vila <[email protected]>
Date:   Wed Dec 10 21:39:00 2025 +0100

    d/control: Drop <!nocheck> from libboost-filesystem-dev and 
libboost-test-dev. Closes: #1122300.

diff --git a/debian/control b/debian/control
index f94db6c..51319e0 100644
--- a/debian/control
+++ b/debian/control
@@ -7,10 +7,10 @@ Build-Depends:
  debhelper-compat (= 13),
  dh-sequence-python3,
  libboost-dev (>= 1.66~),
- libboost-filesystem-dev (>= 1.66~) <!nocheck>,
+ libboost-filesystem-dev (>= 1.66~),
 # remove system after 1.74, see 
0001-Remove-unused-Boost-component-dependencies.patch
  libboost-system-dev (>= 1.66~),
- libboost-test-dev (>= 1.66~) <!nocheck>,
+ libboost-test-dev (>= 1.66~),
  libnuma-dev,
  libzstd-dev,
  python3-dev,

Reply via email to