trafficserver (9.2.4+ds-2) unstable; urgency=medium

  Due to the RUN directory being mounted with the noexec option,
  remap plugins (from remap.config file) can not be properly loaded.
  Therefore, we are now disabling the dynamic reload feature.
  Details can be found in bug #1020989.

 -- Jean Baptiste Favre <debian@jbfavre.org>  Tue, 16 Apr 2024 08:53:13 +0200

trafficserver (6.0.0-3) unstable; urgency=medium

  Due to uncertainty around wccp feature, and failing build,
  support has been temporarily disabled in Debian.
  It might be re-enabled, depending on how things will evolve

 -- Jean Baptiste Favre <debian@jbfavre.org>  Sat, 26 Dec 2020 22:55:18 +0100

trafficserver (6.0.0-3) unstable; urgency=medium

  If you are using 32-bits package, please not that upstream has
  discontinued 32-bit support.
  32-bits Debian package will still be built, but is subject to removal
  whenever 32-bit fails.

 -- Jean Baptiste Favre <debian@jbfavre.org>  Mon, 14 Dec 2015 10:29:12 +0100

trafficserver (3.0.0-1) unstable; urgency=low

  If you are upgrading from v2.1.8 or earlier to ATS 3.0 you need to migrate
  to the new `records.config' configuration file. If possible, let Debian
  overwrite your `records.config' configuration file.

  Moreover you should clear all caches after upgrading (e.g. do "traffic_server
  -Cclear").

  The host.db data abse isn't required anymore. Therefore you can delete
  `/etc/trafficserver/internal/hostdb.config' and `/var/cache/trafficserver/
  host.db'.

 -- Arno Töll <debian@toell.net>  Wed, 15 Jun 2011 16:23:13 +0200
