From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: varnish: update to 6.3.0.
Date: Fri, 04 Oct 2019 10:22:52 +0200 [thread overview]
Message-ID: <20191004082252.MNmgi197A4EXzJwQ1CqpgGqynW3eRCTOlUrTL2nvBks@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-14940@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1427 bytes --]
There's a merged pull request on the void-packages repository
varnish: update to 6.3.0.
https://github.com/void-linux/void-packages/pull/14940
Description:
Adds Varnish back to packages.
- Don't use jemalloc on -musl builds. This appears to be leading to
the segfault described in the earlier broken= message for those.
Noticed the segfault doesn't happen in Alpine's build, and the only
major difference there is that they disable jemalloc (because they
don't support it, but given that it's the only difference, it was
worth disabling to get builds working).
jemalloc remains enabled for glibc.
- Disable pcrejit by default. There is a build option to turn it on,
but this is disabled by default for cross builds. We could add
a check for target machine == host machine and enable it on those
by default if desired, but the build option may be easier. Could
also hack around the config cache, but I'm less confident in JIT
availability on ARM and such than I am basic socket definitions.
- The package originally included a varnish-vcl-reload file in the
files directory. This has been removed because it is, as far as
I can tell, unused.
- Rewrite run file. Old one doesn't work at all, no reason to
preserve it.
- Add _varnish and _vcache system users for default jail argument in
run file. These share a system group.
prev parent reply other threads:[~2019-10-04 8:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-02 4:29 [PR PATCH] " voidlinux-github
2019-10-02 4:32 ` [PR PATCH] [Updated] " voidlinux-github
2019-10-02 4:32 ` voidlinux-github
2019-10-02 4:33 ` voidlinux-github
2019-10-02 4:33 ` voidlinux-github
2019-10-04 8:22 ` voidlinux-github [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191004082252.MNmgi197A4EXzJwQ1CqpgGqynW3eRCTOlUrTL2nvBks@z \
--to=voidlinux-github@inbox.vuxu.org \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).