Your message dated Sat, 12 Apr 2014 20:23:43 +0200
with message-id <[email protected]>
and subject line Closing old bug
has caused the Debian Bug report #660910,
regarding varnishtop segfaults
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
660910: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=660910
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: varnish
Version: 2.1.3-8
Severity: normal

varnishtop segfaults on start.

This bug is reported as fixed in Ubuntu, with patches:

https://bugs.launchpad.net/ubuntu/+source/varnish/+bug/708939


-- System Information:
Debian Release: 6.0.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 3.0.18-linode43 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages varnish depends on:
ii  adduser                   3.112+nmu2     add and remove users and groups
ii  gcc                       4:4.4.5-1      The GNU C compiler
ii  libc6                     2.11.3-3       Embedded GNU C Library: Shared lib
ii  libc6-dev [libc-dev]      2.11.3-3       Embedded GNU C Library: Developmen
ii  libncurses5               5.7+20100313-5 shared libraries for terminal hand
ii  libvarnish1               2.1.3-8        shared libraries for Varnish

varnish recommends no packages.

varnish suggests no packages.

-- Configuration Files:
/etc/default/varnish changed [not included]
/etc/varnish/default.vcl changed [not included]

-- no debconf information



--- End Message ---
--- Begin Message ---
Version: 2.1.4-1

This was fixed upstream in 2.1.4, so I'm closing this bug. Thanks for
reporting it.

-- 
Stig Sandbeck Mathisen

--- End Message ---

Reply via email to