vmemcache (0.8.1-4) unstable; urgency=medium

  * Give up trying to support 32-bit.  There's no pmem hardware there,
    and won't ever be.  The library is meant for multi-terabyte datasets
    (or shards of even bigger stuff), so 32-bit chroots make little sense,
    either.

 -- Adam Borowski <kilobyte@angband.pl>  Fri, 20 Nov 2020 07:04:46 +0100

vmemcache (0.8.1-3) unstable; urgency=medium

  * Disable valgrind tests on mips64* (fails on glibc code).
  * Fix -latomic linkage on m68k.
  * Fix test failure on 32-bit that is also bad-endian.
    You can guess my level of motivation for platforms that are not ever
    going to get pmem hardware...

 -- Adam Borowski <kilobyte@angband.pl>  Wed, 11 Nov 2020 02:37:13 +0100

vmemcache (0.8.1-2) unstable; urgency=medium

  * Fix FTBFS on 32-bit and bad-endian.
  * Fix -latomic linkage (closes: #972967), thanks Adrian Bunk.

 -- Adam Borowski <kilobyte@angband.pl>  Wed, 11 Nov 2020 00:04:28 +0100

vmemcache (0.8.1-1) unstable; urgency=medium

  * New upstream point release.
  * dh 12.
  * Add vmemcache_exists to symbols.

 -- Adam Borowski <kilobyte@angband.pl>  Wed, 21 Oct 2020 16:10:17 +0200

vmemcache (0.8-4) unstable; urgency=medium

  * Install the man page.
  * Fix an intermittent test failure on 32-bit.

 -- Adam Borowski <kilobyte@angband.pl>  Fri, 19 Jul 2019 01:45:46 +0200

vmemcache (0.8-3) unstable; urgency=medium

  * Hard-code -latomic.
  * Avoid some Linuxisms.
  * Handle missing PATH_MAX.
  * Don't assume hard-coded sizes of pthread types.

 -- Adam Borowski <kilobyte@angband.pl>  Thu, 02 May 2019 17:31:06 +0200

vmemcache (0.8-2) unstable; urgency=medium

  * Unbreak tests on 32-bit archs.
  * Migrate from __sync_fetch to __atomic_fetch, link with -latomic.
  * Don't Build-Depend on valgrind on archs that lack it.

 -- Adam Borowski <kilobyte@angband.pl>  Mon, 29 Apr 2019 15:25:03 +0200

vmemcache (0.8-1) unstable; urgency=medium

  * Initial release (Closes: #925980)

 -- Adam Borowski <kilobyte@angband.pl>  Fri, 29 Mar 2019 19:00:34 +0100