Your message dated Fri, 06 Dec 2019 21:23:56 +0000
with message-id <e1idl4u-0006l3...@fasolo.debian.org>
and subject line Bug#941853: fixed in glibc 2.29-5
has caused the Debian Bug report #941853,
regarding crypt(3) should be provided by libxcrypt
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 ow...@bugs.debian.org
immediately.)


-- 
941853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941853
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: glibc
Version: 2.29-2
Severity: normal

The libc implementation of crypt(3) has been deprecated since 2.28.
libxcrypt is needed to support modern hashing algorithms.

How do you want to coordinate switching to libxcrypt?

The libxcrypt implementation is source and binary backward compatible, 
so no transitions are needed. I think that we only need to coordinate 
Replaces/Depends.

The libxcrypt package lives in https://salsa.debian.org/md/libxcrypt .

It has been in Fedora since over one year:
https://fedoraproject.org/wiki/Changes/Replace_glibc_libcrypt_with_libxcrypt

-- 
ciao,
Marco

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.29-5

We believe that the bug you reported is fixed in the latest version of
glibc, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 941...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Aurelien Jarno <aure...@debian.org> (supplier of updated glibc package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Fri, 06 Dec 2019 21:33:17 +0100
Source: glibc
Architecture: source
Version: 2.29-5
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers <debian-glibc@lists.debian.org>
Changed-By: Aurelien Jarno <aure...@debian.org>
Closes: 941853
Changes:
 glibc (2.29-5) unstable; urgency=medium
 .
   * Upload to unstable.
 .
 glibc (2.29-4) experimental; urgency=medium
 .
   [ Aurelien Jarno ]
   * Upload to experimental.
   * debian/control.in/libc: make libc depends on libcrypt1, libc-dev depends
     on libcrypt1-dev and libc-udeb depends on libcrypt1-udeb.  Closes:
     #941853.
   * debian/rules, debian/rules.d/build.mk, debian/rules.d/debhelper.mk,
     debian/sysdeps/amd64.mk: disable libcrypt by passing --disable-crypt
     except for bi/triarch builds.
Checksums-Sha1:
 cac71800e7e4ea00c45f99c95eaf8e6e2ee6fe9a 8735 glibc_2.29-5.dsc
 5615a774e8c62546550e7ef49830917c7dfd8038 854368 glibc_2.29-5.debian.tar.xz
 2bd413ee16842c91600b6fd3a331df73427ac962 7115 glibc_2.29-5_source.buildinfo
Checksums-Sha256:
 735125a44421e44a046af0022e6f444d753e5f47dcdd25490696a8d59538b3de 8735 
glibc_2.29-5.dsc
 6422b87831e6578bf3ed3bfe3f565fdd9deacdc2660f0e480a4c5229a0117777 854368 
glibc_2.29-5.debian.tar.xz
 a7eea9f6504963b08cfc3f4f4570e769fd488bcfedbb0c36fc918b4bb2b8ec6c 7115 
glibc_2.29-5_source.buildinfo
Files:
 d623daeac8cd377691d94d5f67bb4a41 8735 libs required glibc_2.29-5.dsc
 ed415e5899a24efa97d596fc04638978 854368 libs required 
glibc_2.29-5.debian.tar.xz
 d1ab6643431d635d076dadae639ec020 7115 libs required 
glibc_2.29-5_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEUryGlb40+QrX1Ay4E4jA+JnoM2sFAl3qwsoACgkQE4jA+Jno
M2vFGg/7B84hN+jBPWqagnebW7/EYTTNTuo4kEnM3La8HcFqDw1LLDYvGeT83GTy
hGsRJIju3VajXlcmG0Z1KQP5qDrXXiwLuGWIP4/ya+vGpjoxvhLVYfYp9YQ4XJns
JPZ4utyC8tG92VoDl4DJBJtL/agx4Pqe5WIGnoRe4OzbRNAjx9V1QCVfhyBE1ep7
rxsgoCSlpx55wPAiXhCTrjmum5/KI/c1IAuWt0/mLud3wn9IL3Fe/FK6lljw29jz
Q55Prtxe/ZQzPSqPY3nDX9TFLI9X0oNBavFFIJE5pQTjBlLFam1QZFEP+AdgRfQt
la5t7A+1pbRoXwWTGfWHwdi3JaREaLNPbsCblUzOFuvgW0RTx36BI782P+++ICft
euEhsj/Ft4OWRCtOsJrRvQvsWD6cV2MaVQaVTzbjs8uElGaj3EyzBRIwvsMhx/Tp
jwxv0eMV27Uy6jNFr4aDkd/U8xm+XnVUrjkznv8o2RtCFq5ks5OZQEk/96Szekhu
xXUeToxgMC5nJa8DRLMBMiuIBgE3LTfwf5FWLhjTsow2NQIATlDJO3VgL/J4R4lk
+8Z7dz9Ads0RDCy2fmS0o104qI6bCMXqYXhPup90FCpeknioVi3XwAhbGNCriVSE
R9FITJOCju7YbH+alPHbpXXlbQLwVmraDnM8mHZ4/Jt0bPUxqjA=
=IKzd
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to