[Varnish] #1679: After upgrade, custom vmods are not moved so vcl does not compile

[Varnish]

#1679: After upgrade, custom vmods are not moved so vcl does not compile
-----------------------+--------------------
 Reporter:  razvanphp  |       Type:  defect
   Status:  new        |   Priority:  normal
Milestone:             |  Component:  vmod
  Version:  4.0.3      |   Severity:  normal
 Keywords:             |
-----------------------+--------------------
 Today we upgraded to varnish 4.0.3 from the official debian wheezy repo.

 For some reason (I can't find the changelog or motivation for this) the
 vmod directory changed from `/usr/lib/varnish/vmods/` to `/usr/lib/x86_64
 -linux-gnu/varnish/vmods/`. The std and directory vmods were moved to the
 new folder, but custom ones not, resulting in errors and failed startup:


 {{{
 Unpacking replacement varnish ...
 dpkg: warning: unable to delete old directory '/usr/lib/varnish/vmods':
 Directory not empty
 dpkg: warning: unable to delete old directory '/usr/lib/varnish':
 Directory not empty
 ...
 [FAIL] Starting HTTP accelerator: varnishd failed!
 Message from VCC-compiler:
 Could not load VMOD geoip
         File name: /usr/lib/x86_64-linux-
 gnu/varnish/vmods/libvmod_geoip.so
         dlerror:: /usr/lib/x86_64-linux-
 gnu/varnish/vmods/libvmod_geoip.so: cannot open shared object file: No
 such file or directory
 ('input' Line 21 Pos 8)
 import geoip;
 -------#####-
 }}}

-- 
Ticket URL: <https://www.varnish-cache.org/trac/ticket/1679>
Varnish <https://varnish-cache.org/>
The Varnish HTTP Accelerator