[From nobody Fri May 15 08:07:07 2026
Received: (at maintonly) by bugs.debian.org; 31 May 2025 19:20:15 +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, 5; hammy, 150; neutral, 52; 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]:39966)
 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 1uLRkd-000UC2-2N
 for maintonly@bugs.debian.org; Sat, 31 May 2025 19:20:15 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=subdivi.de;
 s=k16.isilmar-4; t=1748718783;
 bh=kIwIbAaHuB2ABKvHxn5poaeircp9c3jZoxfClCr7DIc=;
 h=From:To:Subject:Date:From;
 b=bU83kMuEmI1vTaK+b1j5bckhPa16JMl7EboDdJSBMVHPCvUS9aeCKGQNA9mtzkzZO
 58KRM3bKueikQm0usWCRh4lIFSyC7f5waFUb5va0iQg8v9hC+6txaoHEE/DuViCiDt
 QWz1clfeGjDdcQAn0Fdcf19dIePJhjxBtPK2joIUqUO8PZdLs9ZejIcoXBEFkNEaWo
 Pxq3bYDzD3uMvnBxHEynMvs8saVkDT3E5iV7V3ThYZBluNihrRwukK7pBUsoiu7wox
 18wj0LeODnb1ljokFlzVwDMdkh8e+E6JWuJqnKOazVRMt1w1lDzlpB5MSxIk8e3BHt
 FO7bzX2E9aJYQ==
Received: from isilmar-4.linta.de (isilmar.linta [10.0.0.1])
 by isilmar-4.linta.de (Postfix) with ESMTP id 4CB2520098E
 for <maintonly@bugs.debian.org>; Sat, 31 May 2025 19:13:03 +0000 (UTC)
From: helmut@subdivi.de
To: maintonly@bugs.debian.org
Subject: ruby3.3: add libcrypt-dev to Build-Depends
Date: Sat, 31 May 2025 21:09:50 +0200
X-Generator: mass-bug from devscripts 2.23.4+deb12u2
Message-Id: <20250531191303.4CB2520098E@isilmar-4.linta.de>
Delivered-To: maintonly@bugs.debian.org

Source: ruby3.3
Version: 3.3.8-2
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
]