Upgrade Varnish will not replace the libraries
kelvin1111111 at gmail.com
Tue Oct 2 04:10:29 CEST 2012
Just thought of sharing it to have some suggestion/enhancement on
Using Ubuntu 10.04 LTS 64-bit, with Varnish 3.0.2. When I tried to
upgrade Varnish to 3.0.3, It seems that it cannot upgrade the Varnish
shared libraries automatically.
# apt-get install varnish
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be upgraded:
1 upgraded, 0 newly installed, 0 to remove and 105 not upgraded.
Need to get 531kB of archives.
After this operation, 49.2kB of additional disk space will be used.
Get:1 http://repo.varnish-cache.org/ubuntu/ lucid/varnish-3.0 varnish
Fetched 531kB in 3s (156kB/s)
(Reading database ... 46434 files and directories currently installed.)
Preparing to replace varnish 3.0.2-1~1lucid1 (using
* Stopping HTTP accelerator varnishd [ OK ]
Unpacking replacement varnish ...
dpkg: warning: unable to delete old directory '/var/lib/varnish':
Directory not empty
Processing triggers for ureadahead ...
ureadahead will be reprofiled on next reboot
Processing triggers for man-db ...
Setting up varnish (3.0.3-1~lucid) ...
Installing new version of config file /etc/init.d/varnishncsa ...
Installing new version of config file /etc/default/varnishlog ...
Installing new version of config file /etc/default/varnishncsa ..
Configuration file `/etc/default/varnish'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : background this process to examine the situation
The default action is to keep your current version.
*** varnish (Y/I/N/O/D/Z) [default=N] ?
* Starting HTTP accelerator varnishd [ OK ]
# dpkg -l | grep varnish
ii libvarnishapi1 3.0.2-1~1lucid1
libraries for Varnish
ii varnish 3.0.3-1~lucid
state of the art, high-performance web accel
Delete the /var/lib/varnish manually before the upgrade will do the
trick, but would be better to have it done in automated way :)
More information about the varnish-misc