Script 'mail_helper' called by obssrc Hello community, here is the log from the commit of package varnish for openSUSE:Factory checked in at 2022-11-01 13:43:10 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/varnish (Old) and /work/SRC/openSUSE:Factory/.varnish.new.2275 (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "varnish" Tue Nov 1 13:43:10 2022 rev:41 rq:1032578 version:7.2.0 Changes: -------- --- /work/SRC/openSUSE:Factory/varnish/varnish.changes 2022-09-26 18:47:57.472026375 +0200 +++ /work/SRC/openSUSE:Factory/.varnish.new.2275/varnish.changes 2022-11-01 13:43:15.536116549 +0100 @@ -1,0 +2,80 @@ +Sat Oct 29 13:43:46 UTC 2022 - Dirk M??ller <dmuel...@suse.com> + +- update to 7.2.0: + * Functions ``VRT_AddVDP()``, ``VRT_AddVFP()``, + ``VRT_RemoveVDP()`` and ``VRT_RemoveVFP()`` are deprecated. + * Cookie headers generated by vmod_cookie no longer have a + spurious trailing semicolon at the end of the string. This + could break VCL relying on the previous incorrect behavior. + * The ``SessClose`` and ``BackendClose`` reason ``rx_body``, + which previously output ``Failure receiving req.body``, has + been rewritten to ``Failure receiving body``. + * Prototypical Varnish Extensions (VEXT). Similar to VMODs, a + VEXT is loaded by the cache process. Unlike VMODs that have + the combined lifetime of all the VCLs that reference them, a + VEXT has the lifetime of the cache process itself. There are + no built-in extensions so far. + * Duration parameters can optionally take a unit, with the same + syntax as duration units in VCL. + * Calls to ``VRT_CacheReqBody()`` and ``std.cache_req_body`` + from outside client vcl subs now fail properly instead of + triggering an assertion failure. + * New "B" string for the package branch in ``VCS_String()``. + For the 7.2.0 version, it would yield the 7.2 branch. + * The new ``vcc_feature`` bits parameter replaces previous + ``vcc_*`` boolean parameters. The latter still exist as + deprecated aliases. + * The ``-k`` option from ``varnishlog`` is now supported by + ``varnishncsa``. + * New functions ``std.now()`` and ``std.timed_call()`` in + vmod_std. + * New ``MAIN.shm_bytes`` counter. + * A ``req.http.via`` header is set before entering + ``vcl_recv``. Via headers are generated using the + ``server.identity`` value. It defaults to the host name and + can be turned into a pseudonym with the ``varnishd -i`` + option. Via headers are appended in both directions, to work + with other hops that may advertise themselves. + * A ``resp.http.via`` header is no longer overwritten by + varnish, but rather appended to. + * The ``server.identity`` syntax is now limited to a "token" as + defined in the HTTP grammar to be suitable for Via headers. + * In ``varnishtest`` a Varnish instance will use its VTC + instance name as its instance name (``varnishd -i``) by + default for predictable Via headers in test cases. + * VMOD and VEXT authors can use functions from ``vnum.h``. + * Do not filter pseudo-headers as regular headers. + * The termination rules for ``WRK_BgThread()`` were relaxed to + allow VMODs to use it. + * ``(struct worker).handling`` has been moved to the newly + introduced ``struct wrk_vpi`` and replaced by a pointer to + it, as well as ``(struct vrt_ctx).handling`` has been + replaced by that pointer. ``struct wrk_vpi`` is for state at + the interface between VRT and VGC and, in particular, is not + const as ``struct vrt_ctx`` aka ``VRT_CTX``. + * Panics now contain information about VCL source files and + lines. + * The ``Begin`` log record has a 4th field for subtasks like + ESI sub-requests. + * The ``-E`` option for log utilities now works as documented, + with any type of sub-task based on the ``Begin[4]`` field. + This covers ESI like before, and sub-tasks spawned by VMODs + (provided that they log the new field). + * No more ``req.http.transfer-encoding`` for ESI sub-requests. + * The thread pool reserve is now limited to tasks that can be + queued. A backend background fetch is no longer eligible for + queueing. It would otherwise slow a grace hit down + significantly when thread pools are saturated. + * The unused ``fetch_no_thread`` counter was renamed to + ``bgfetch_no_thread`` because regular backend fetch tasks are + always scheduled. + * The macros ``FEATURE()``, ``EXPERIMENT()``, ``DO_DEBUG()``, + ``MGT_FEATURE()``, ``MGT_EXPERIMENT()``, ``MGT_DO_DEBUG()`` + and ``MGT_VCC_FEATURE()`` now return a boolean value (``0`` + or ``1``) instead of the (private) flag value. + * A regression in the transport code led MAIN.client_req to be + incremented for requests coming back from the waiting list, + it was fixed. +- Delete varnish-5.1.2-add-fallthrough-comments.patch + +------------------------------------------------------------------- Old: ---- varnish-5.1.2-add-fallthrough-comments.patch varnish-7.1.1.tgz New: ---- varnish-7.2.0.tgz ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ varnish.spec ++++++ --- /var/tmp/diff_new_pack.Cm5xxS/_old 2022-11-01 13:43:16.492121635 +0100 +++ /var/tmp/diff_new_pack.Cm5xxS/_new 2022-11-01 13:43:16.496121655 +0100 @@ -25,7 +25,7 @@ %define _fillupdir %_localstatedir/adm/fillup-templates %endif Name: varnish -Version: 7.1.1 +Version: 7.2.0 Release: 0 Summary: Accelerator for HTTP services License: BSD-2-Clause @@ -38,7 +38,6 @@ Source7: varnish.service Source8: varnishlog.service Source9: varnish_reload_vcl -Patch1: varnish-5.1.2-add-fallthrough-comments.patch Patch2: uninit.patch BuildRequires: libxslt-devel BuildRequires: ncurses-devel ++++++ varnish-7.1.1.tgz -> varnish-7.2.0.tgz ++++++ ++++ 90586 lines of diff (skipped)
