-
libxcrypt (1:2.4-3) unstable; urgency=low
* QA upload (see #679703). Skipping 1:2.4-2 to avoid archive filename
conflicts with prior 2.4-2 upload.
* FTBFS fix: Change __libc_lock to use pthread_mutex interfaces, as
__libc_lock is deprecated. Patch courtesy of Chris J Arges.
(Closes: #697714)
-- Nicholas Breen <email address hidden> Fri, 11 Jan 2013 14:16:32 -0800
-
libxcrypt (1:2.4-1.1ubuntu1) raring; urgency=low
* Change __libc_lock to use pthread_mutex interfaces because
__libc_lock interfaces were deprecated by patch 9463518d in glibc.
-- Chris J Arges <email address hidden> Tue, 08 Jan 2013 12:39:07 -0600
-
libxcrypt (1:2.4-1.1) unstable; urgency=low
* Non-Maintainer Upload to fix RC security bug
* Added patch (casting to unsigned) in order to prevent weak password
hashes.See http://security-tracker.debian.org/tracker/CVE-2011-2483
(closes: #679628)
* debian/rules: #commented out two cp commands to preserve the config.guess
and config.sub versions already in 1:2.4-1.
-- Kai Lüke <email address hidden> Mon, 17 Sep 2012 03:52:06 +0200
-
libxcrypt (1:2.4-1build1) jaunty; urgency=low
* Artificial version number bump to get around the fact that 2.4-1 is
still in earlier versions of Ubuntu and shares archive filenames.
libxcrypt (1:2.4-1) unstable; urgency=low
* Alas, we have to use an epoch to revert from 3.0 to 2.4 for now.
* Build failures in 3.0 are irrelevant now, we'll deal with them when we
give 3.0 another shot. (Closes: Bug#489840)
libxcrypt (3.0-2) unstable; urgency=low
* Force --with-pic in configure.
libxcrypt (3.0-1) unstable; urgency=low
* New upstream version, new soname, binary package is now libxcrypt2.
Force libdir to /lib not /lib64.
-- Colin Watson <email address hidden> Wed, 05 Nov 2008 00:35:43 +0000
