Hi,
Moving to varnish-misc.
This isn't a mistake, the ABI version is basically the git commit hash of
the version, so each new version will have a different value.
Vmods can require either a loose or a strict API/ABI compatibility. Loose
is only a check on the external API number (7.x at the moment I believe)
and strict is what you are experiencing.
You either need to rebuild your vmods, or, if possible, switch to a loose
check (only if you don't use internal APIs)
Hope that clarifies things.
On Wed, Nov 27, 2019, 04:22 Massimiliano Bellomi <
massimiliano@scientiamobile.com> wrote:
> Hi,
>
> it seems that the source rpm package published on packagecloud.io (
> https://packagecloud.io/varnishcache/varnish60lts/packages/el/7/varnish-6.0.5-1.el7.src.rpm
> )
> contains a wrong VMOD_ABI_Version define.
>
> #define VMOD_ABI_Version "Varnish 6.0.4
> 204a927f4a4283529fc89f5182fe8cc3f2d0f617"
> instead of
> #define VMOD_ABI_Version "Varnish 6.0.5
> 3065ccaacc4bb537fb976a524bd808db42c5fe40"
>
> This cause a "Incompatible VMOD" message when you try to import modules
> built using that source package.
>
> The source package listed in the 6.0.5 release page (
> https://varnish-cache.org/releases/rel6.0.5.html) contains the
> right VMOD_ABI_Version define
>
> Regards
> -Massimiliano
> --
> Massimiliano Bellomi
> Senior Software Engineer
> Scientiamobile Italy - massimiliano@scientiamobile.com +39 338 6990288
> Milano Office : +39 02 620227260
> skype: massimiliano.bellomi
> _______________________________________________
> varnish-dist mailing list
> varnish-dist@varnish-cache.org
> https://www.varnish-cache.org/lists/mailman/listinfo/varnish-dist
>
Moving to varnish-misc.
This isn't a mistake, the ABI version is basically the git commit hash of
the version, so each new version will have a different value.
Vmods can require either a loose or a strict API/ABI compatibility. Loose
is only a check on the external API number (7.x at the moment I believe)
and strict is what you are experiencing.
You either need to rebuild your vmods, or, if possible, switch to a loose
check (only if you don't use internal APIs)
Hope that clarifies things.
On Wed, Nov 27, 2019, 04:22 Massimiliano Bellomi <
massimiliano@scientiamobile.com> wrote:
> Hi,
>
> it seems that the source rpm package published on packagecloud.io (
> https://packagecloud.io/varnishcache/varnish60lts/packages/el/7/varnish-6.0.5-1.el7.src.rpm
> )
> contains a wrong VMOD_ABI_Version define.
>
> #define VMOD_ABI_Version "Varnish 6.0.4
> 204a927f4a4283529fc89f5182fe8cc3f2d0f617"
> instead of
> #define VMOD_ABI_Version "Varnish 6.0.5
> 3065ccaacc4bb537fb976a524bd808db42c5fe40"
>
> This cause a "Incompatible VMOD" message when you try to import modules
> built using that source package.
>
> The source package listed in the 6.0.5 release page (
> https://varnish-cache.org/releases/rel6.0.5.html) contains the
> right VMOD_ABI_Version define
>
> Regards
> -Massimiliano
> --
> Massimiliano Bellomi
> Senior Software Engineer
> Scientiamobile Italy - massimiliano@scientiamobile.com +39 338 6990288
> Milano Office : +39 02 620227260
> skype: massimiliano.bellomi
> _______________________________________________
> varnish-dist mailing list
> varnish-dist@varnish-cache.org
> https://www.varnish-cache.org/lists/mailman/listinfo/varnish-dist
>
