Re: Bug#1106798: condor: statically linked against glibc without a Built-Using: field

[Aurelien Jarno <aurel32@debian.org>]

Hi,

On 2025-05-29 22:53, Aurelien Jarno wrote:
> Package: condor
> Version: 23.2.0+dfsg-1
> Severity: serious
> Justification: Policy 7.8
> 
> Dear maintainer,
> 
> condor provides /usr/libexec/condor/singularity_test_sandbox/exit_37
> which is statically linked against glibc.
> 
> glibc is mostly is mostly licensed under the LGPL, which requires that
> the full source code of the incorporating binary package be made
> available. According to Debian Policy §7.8 [1] such a binary package
> MUST list the glibc source package (and possibly others) in the
> Built-Using: field.

Please find attached to fix the issue. Please note that the exit_37 file 
is statically compiled on all architectures except amd64, hence the 
architecture specification in debian/control next to the Built-Using 
field.

Regards
Aurelien

-- 
Aurelien Jarno                          GPG: 4096R/1DDD8C9B
aurelien@aurel32.net                     http://aurel32.net

--- condor-23.9.6+dfsg/debian/control
+++ condor-23.9.6+dfsg/debian/control
@@ -8,6 +8,7 @@
                debhelper-compat (= 13),
                default-jdk,
                dh-python,
+               dh-sequence-builtusing,
                libboost-filesystem-dev,
                libboost-program-options-dev,
                libboost-python-dev,
@@ -81,6 +82,7 @@
         libclassad16
 Replaces: htcondor (<< ${binary:Version}),
           libclassad16
+Built-Using: ${dh-builtusing:libc-dev-bin} [!amd64]
 Description: distributed workload management system
  Like other full-featured batch systems, HTCondor provides a job queueing
  mechanism, scheduling policy, priority scheme, resource monitoring, and