[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

varnish_2.0.4-5~bpo50+1_i386.changes is NEW



(new) libvarnish-dev_2.0.4-5~bpo50+1_i386.deb optional libdevel
development files for Varnish
 Development files for the Varnish HTTP accelerator.
(new) libvarnish1_2.0.4-5~bpo50+1_i386.deb optional libs
shared libraries for Varnish
 Shared libraries for the Varnish HTTP accelerator.
(new) varnish_2.0.4-5~bpo50+1.diff.gz optional web
(new) varnish_2.0.4-5~bpo50+1.dsc optional web
(new) varnish_2.0.4-5~bpo50+1_i386.deb optional web
a state-of-the-art, high-performance HTTP accelerator
 Varnish is a state-of-the-art, high-performance HTTP accelerator.  It uses the
 advanced features in Linux 2.6, FreeBSD 6/7 and Solaris 10 to achieve its high
 performance.
 .
 Some of the features include:
  * A modern design
  * VCL - a very flexible configuration language
  * Load balancing with health checking of backends
  * Partial support for ESI - Edge Side Includes
  * URL rewriting
  * Graceful handling of "dead" backends
(new) varnish_2.0.4.orig.tar.gz optional web
Changes: varnish (2.0.4-5~bpo50+1) lenny-backports; urgency=low
 .
  * Update backport to current testing version
 .
varnish (2.0.4-5) unstable; urgency=low
 .
  * Add s390 to list of architectures not using jemalloc
 .
varnish (2.0.4-4) unstable; urgency=low
 .
  * Remove s390 jemalloc patch
  * Add patch for varnishd(1)
 .
varnish (2.0.4-3) unstable; urgency=low
 .
  * Actually check for s390 in the jemalloc patch.
 .
varnish (2.0.4-2) unstable; urgency=low
 .
  * Change Vcs-Browser and Vcs-Svn to reflect the packaging move to
    alioth
  * Add support for VCL reload via /etc/init.d/varnishd reload
  * Added a symbols file for libvarnish1
  * Add patch from Ingvar Hagelund to define *_2POW on s390, we should then be
    able to use jemalloc
  * Add build dependency on quilt
 .
varnish (2.0.4-1) unstable; urgency=low
 .
  * New upstream version
 .
varnish (2.0.3-2) UNRELEASED; urgency=low
 .
  * Add /usr/lib/pkgconfig/varnishapi.pc to the libvarnish-dev package
 .
varnish (2.0.3-1) unstable; urgency=low
 .
  * New upstream version
 .
varnish (2.0.2-1) unstable; urgency=low
 .
  * New upstream version
  * Change defaults to use configuration file /etc/varnish/default.vcl
    when starting varnishd
 .
varnish (2.0.1-2) unstable; urgency=low
 .
  [ Kees Cook ]
  * debian/rules: disable jemalloc on architectures that lack *_2POW
    definitions (Closes: #503381).
 .
  [ Stig Sandbeck Mathisen ]
  * Add a man page for varnishtest
  * Disable jemalloc on m64k as well
 .
varnish (2.0.1-1) unstable; urgency=low
 .
  * New upstream version
  * Fix synopsis on binary packages (Closes: #502118)
 .
varnish (2.0-1) unstable; urgency=low
 .
  * New upstream version
  * Add varnishncsa init script, defaults and log rotation (Closes: #501454)
  * Add dependency on libc6.1-dev (Closes: #481067)
 .
varnish (2.0~rc1-1) unstable; urgency=low
 .
  * New upstream version
  * Fix syntax error in varnishlog init script
 .
varnish (2.0~beta1-1) UNRELEASED; urgency=low
 .
  [ Stig Sandbeck Mathisen ]
  * New upstream release
 .
  [ Tollef Fog Heen ]
  * Fix up clean rule so as to work correctly on fresh sources too.
  * Fix up Makefile.am to get rid of files we don't ship.
  * Fix XSIsm in debian/varnish.varnishlog.init (-o in a test).
  * Rename libvarnish0-dev to libvarnish-dev again, bump soname to
    libvarnish1.
 .
varnish (1.2-0) unstable; urgency=low
 .
  [ Stig Sandbeck Mathisen ]
  * New upstream release.
  * Check if varnishlog is running before attempting reload from
    logrotate postscript. (Closes: #462029)
 .
  [ Fabio Tranchitella ]
  * debian/varnish.dirs: removed unused lintian overrides dir.
  * debian/rules: backup and restore of config.sub and config.guess to not
    include them into the diff.gz in case of multiple builds from the same
    working directory.
 .
  [ Tollef Fog Heen ]
  * Remove TODO from Makefile.am to make make dist happier.
  * Run make distclean if Makefile exists.


Override entries for your package:

Announcing to backports-changes@lists.backports.org


Your package contains new components which requires manual editing of
the override file.  It is ok otherwise, so please be patient.  New
packages are usually added to the override file about once a week.

You may have gotten the distribution wrong.  You'll get warnings above
if files already exist in other distributions.
ns.

Reply to: