From: owner@bugs.debian.org 
  
 This is a multi-part message in MIME format... 
  
 Your message dated Tue, 07 Oct 2025 22:18:59 +0000 
 with message-id  
 and subject line Bug#1106973: fixed in axmail 2.13-2 
 has caused the Debian Bug report #1106973, 
 regarding axmail: add libcrypt-dev to Build-Depends 
 to be marked as done. 
  
 This means that you claim that the problem has been dealt with. 
 If this is not the case it is now your responsibility to reopen the 
 Bug report if necessary, and/or fix the problem forthwith. 
  
 (NB: If you are a system administrator and have no idea what this 
 message is talking about, this may indicate a serious mail system 
 misconfiguration somewhere. Please contact owner@bugs.debian.org 
 immediately.) 
  
  
 -- 
 1106973: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1106973 
 Debian Bug Tracking System 
 Contact owner@bugs.debian.org with problems 
  
 Received: (at maintonly) by bugs.debian.org; 31 May 2025 19:20:27 +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, 3; hammy, 150; neutral, 53; 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:  
 Received: from isilmar-4.linta.de ([136.243.71.142]:55780) 
  by buxtehude.debian.org with esmtps (TLS1.3:ECDHE_X25519__RSA_P 
 S_RSAE_SHA256__AES_256_GCM:256) 
  (Exim 4.96) 
  (envelope-from ) 
  id 1uLRko-000UMI-2d 
  for maintonly@bugs.debian.org; 
  Sat, 31 May 2025 19:20:26 +0000 
 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=subdivi.de; 
  s=k16.isilmar-4; t=1748718798; 
  bh=57s7RxjUVyrV+v2+jd67mRKt9dW0of6SoSttc7ESdHA=; 
  h=From:To:Subject:Date:From; 
  b=zBAdBXQ8ARvv2ZH8KZBWHMwpl6YRJmgHc+G1U98baNUcgHuez6FWFZO4jK06FwDjg 
   NubPQEa/OADiIShjJOVAKqpGquoM+a8Bp9M2KaVz0/eEAu6UY4frdnxrM+VeY4Wh48 
   FrXBuNSANBaxgWClfeG2YAwbOQMK7S4VNhe70bDJCeIn9s9XGBdza3MVZbReZMOHfW 
   UF86/hxrkGJSnW1qyc/IDZoW1RmHjyCCbe979FhmJGSsPbsv+RaGgumz3dDOCR3j3g 
   LmEsphwdtGByc7cXjQno7rG9gE2mYsnCyCOD9dLgCThn3j+TQ374ocP6fLYcivuBDl 
   a2KtVBWriHxig== 
 Received: from isilmar-4.linta.de (isilmar.linta [10.0.0.1]) 
  by isilmar-4.linta.de (Postfix) with ESMTP id ED3D32009D3 
  for ; Sat, 31 May 2025 19:13:18 +0000 (UTC) 
 From: helmut@subdivi.de 
 To: maintonly@bugs.debian.org 
 Subject: axmail: 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: <20250531191318.ED3D32009D3@isilmar-4.linta.de> 
 Delivered-To: maintonly@bugs.debian.org 
  
 Source: axmail 
 Version: 2.13-1 
 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 " 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 
  
 Received: (at 1106973-close) by bugs.debian.org; 7 Oct 2025 22:19:03 +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=-113.1 required=4.0 tests=BAYES_00,DKIM_SIGNED, 
  DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FVGT_m_MULTI_ODD,HAS_BUG_NUMBER, 
  MD5_SHA1_SUM,PGPSIGNATURE,RCVD_IN_DNSWL_MED,SPF_HELO_PASS,SPF_NONE, 
  USER_IN_DKIM_WELCOMELIST autolearn=ham autolearn_force=no 
  version=4.0.1-bugs.debian.org_2005_01_02 
 X-Spam-Bayes: score:0.0000 Tokens: new, 93; hammy, 150; neutral, 136; 
 spammy, 
  0. spammytokens: hammytokens:0.000-+--HX-Debian:DAK, 
  0.000-+--H*rp:D*ftp-master.debian.org, 0.000-+--HX-DAK:process-upload, 
  0.000-+--UD:debian.tar.xz, 0.000-+--Hx-spam-relays-external:sk:fasolo. 
 Return-path:  
 Received: from mitropoulos.debian.org ([2001:648:2ffc:deb:216:61 
 f:fe9d:958d]:54348) 
  
 [continued in next message] 
  
 --- SoupGate-Win32 v1.05 
  * Origin: you cannot sedate... all the things you hate (1:229/2)