1
Description: Upstream changes introduced in version 2.1.3-8
2
This patch has been created by dpkg-source during the package build.
3
Here's the last changelog entry, hopefully it gives details on why
4
those changes were made:
6
varnish (2.1.3-8) unstable; urgency=high
8
* Fix random secret creation on non-Linux kernels (Closes: #596373)
9
* Urgency "high" due to FTBFS RC bug during squeeze freeze
11
The person named in the Author field signed this changelog entry.
12
Author: Stig Sandbeck Mathisen <ssm@debian.org>
13
Bug-Debian: http://bugs.debian.org/596373
16
The information above should follow the Patch Tagging Guidelines, please
17
checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here
18
are templates for supplementary fields that you might want to add:
20
Origin: <vendor|upstream|other>, <url of original patch>
21
Bug: <url in upstream bugtracker>
22
Bug-Debian: http://bugs.debian.org/<bugnumber>
23
Bug-Ubuntu: https://launchpad.net/bugs/<bugnumber>
24
Forwarded: <no|not-needed|url proving that it has been forwarded>
25
Reviewed-By: <name and email of someone who approved the patch>
26
Last-Update: <YYYY-MM-DD>
28
--- varnish-2.1.3.orig/bin/varnishtest/tests/v00014.vtc
29
+++ varnish-2.1.3/bin/varnishtest/tests/v00014.vtc
32
test "Check req.backend.healthy"
34
+# probe will hit this to check healthiness
38
@@ -16,8 +17,8 @@ varnish v1 -vcl {
49
@@ -33,25 +34,33 @@ varnish v1 -vcl {
53
+# probe runs every 0.1s and needs 2 (threshold) out of the latest 3 (window) to
54
+# be successful. Make sure this does *not* happen: the first probe would be
55
+# successful (s1 was started and finished), but let the next one or two to fail
56
+# (and hence making the backend unhealthy) by idling.
60
+# verify that backend is unhealthy as expected
64
expect resp.status == 500
69
- expect req.url == "/"
70
- txresp -body "slash"
72
+# now let three consecutive probe checks to succeed by starting them and
73
+# waiting for them to finish. This will lead varnish to believe that the
74
+# backend is healthly. (note that s1 ports are reused)
75
+server s1 -repeat 3 -start -wait
78
+# do an actual check with a healthy backend, expecting to get a 200 back
81
expect req.url == "/foo"
89
expect resp.status == 200
90
--- varnish-2.1.3.orig/doc/changes-2.1.0-2.1.1.xml
91
+++ varnish-2.1.3/doc/changes-2.1.0-2.1.1.xml
95
<para><code>varnishsizes</code>, which is
96
- like <code>varnishhost</code>, but for the length of objects,
97
+ like <code>varnishhist</code>, but for the length of objects,
98
has been added..</para>
101
--- varnish-2.1.3.orig/doc/changes-2.1.1.html
102
+++ varnish-2.1.3/doc/changes-2.1.1.html
106
<p><span class="code">varnishsizes</span>, which is
107
- like <span class="code">varnishhost</span>, but for the length of objects,
108
+ like <span class="code">varnishhist</span>, but for the length of objects,