[From nobody Fri Apr 17 15:37:13 2026
Received: (at maintonly) by bugs.debian.org; 31 May 2025 19:20:10 +0000
X-Spam-Checker-Version: SpamAssassin 4.0.1-bugs.debian.org_2005_01_02
 (2024-03-25) on buxtehude.debian.org
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 required=4.0 tests=BAYES_00,DKIM_SIGNED,
 DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_NONE,SPF_NONE
 autolearn=ham autolearn_force=no
 version=4.0.1-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 2; hammy, 150; neutral, 57; spammy, 0.
 spammytokens: hammytokens:0.000-+--trixie, 0.000-+--H*F:U*helmut,
 0.000-+--H*F:D*subdivi.de, 0.000-+--H*RU:sk:helmut@,
 0.000-+--H*rp:U*helmut
Return-path: <helmut@subdivi.de>
Received: from isilmar-4.linta.de ([136.243.71.142]:53378)
 by buxtehude.debian.org with esmtps
 (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_256_GCM:256)
 (Exim 4.96) (envelope-from <helmut@subdivi.de>) id 1uLRkY-000U6q-10
 for maintonly@bugs.debian.org; Sat, 31 May 2025 19:20:10 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=subdivi.de;
 s=k16.isilmar-4; t=1748718685;
 bh=llj48eVYZozYt34AHsVUaMXpXWAdHssrAjkH8ICmDDI=;
 h=From:To:Subject:Date:From;
 b=3oMKoirbRHItlrO3sGbt/XJxW4EIClSnkRPhrPGFCixZDI6D3NpxxlYGeewLRc+Hx
 k+qh6dF6EfNLSKHVNf899TAZePTRPUqW52rzPU2Zg2oUyhSM74/ktEE8PMMQCzC6IT
 EGu/DlPxkaGirNgaUOaTWuqTTVVL1xK0XmOt+1XDIym6k2mLOC4xCeH7gaYsTUJ5jh
 5WddROW4Xem9sCJVJbfEufVsZjtDxDNGNKpFGIJwBADKd5w3UuE+UQnEk/5rg0WAwv
 MkHcfQjXhARkpdJoLKtznzOy7Y5UL0qRsA2ZWff5TJhicAr7dknh7RUrtiUBm4mnE8
 SdPq7XZxRcEEQ==
Received: from isilmar-4.linta.de (isilmar.linta [10.0.0.1])
 by isilmar-4.linta.de (Postfix) with ESMTP id 5AD4F2006EF
 for <maintonly@bugs.debian.org>; Sat, 31 May 2025 19:11:25 +0000 (UTC)
From: helmut@subdivi.de
To: maintonly@bugs.debian.org
Subject: 389-ds-base: add libcrypt-dev to Build-Depends
Date: Sat, 31 May 2025 21:09:48 +0200
X-Generator: mass-bug from devscripts 2.23.4+deb12u2
Message-Id: <20250531191125.5AD4F2006EF@isilmar-4.linta.de>
Delivered-To: maintonly@bugs.debian.org

Source: 389-ds-base
Version: 3.1.1+dfsg1-3
Severity: normal
User: helmutg@debian.org
Usertags: libcrypt-direct

Hello,

please add "libcrypt-dev" to Build-Depends. Presently, libcrypt-dev is
transitively build-essential, because libc6-dev depends on it. There is an
effort[1] to drop this dependency with the result of removing libcrypt-dev from
the build-essential package set. This package was identified as needing an
explicit dependency on libcrypt-dev for one or more of several reasons:
 * It failed building in an archive-rebuild with the dependency dropped.
 * One of its binary packages issues a binary package dependency on libcrypt1.
 * Inspection of source identified "#include <crypt.h>" or -lcrypt.

Rarely, the dependency is of indirect nature. The most common cae is perl
extension modules. For those, a different bug has been filed requesting a
perl-xs-dev dependency instead. As other classes have been excluded from this
filing, it is expected that a direct "Build-Depnds: libcrypt-dev" is indeed
necessary.  Once the libcrypt-dev dependency issued by libc6-dev is dropped,
this package will fail to build or build with its crypt-related functionality
disabled. This change will not happen in the trixie cycle but some months into
the forky cycle. Please add the additional dependency in time. Whilst the
additional dependency is safe for inclusion in trixie, it should be added in
the forky cycle to avoid disrupting the trixie release.

Thank you

Helmut

[1] https://lists.debian.org/debian-devel/2025/04/msg00113.html
]