From: Patrick Steinhardt <ps@pks.im>
To: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
Cc: git@vger.kernel.org, Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: [PATCH 6/7] meson: update wrappers
Date: Mon, 5 Oct 2026 12:25:04 +0200 [thread overview]
Message-ID: <asN7AJdVmPCzov7l@pks.im> (raw)
In-Reply-To: <3de4ba2b-9b0c-499b-98bb-7077e0d7613b@gmail.com>
On Mon, Oct 05, 2026 at 03:12:34PM +0530, Kaartic Sivaraam wrote:
> On 9/24/26 19:39, Patrick Steinhardt wrote:
> > diff --git a/subprojects/openssl.wrap b/subprojects/openssl.wrap> index
> 873d55106e..e775bb104f 100644
> > --- a/subprojects/openssl.wrap
> > +++ b/subprojects/openssl.wrap
> > @@ -1,15 +1,14 @@
> > [wrap-file]
> > [ snip ]> -wrapdb_version = 3.0.8-3
> > [ snip ]> +wrapdb_version = 3.0.10-1
> >
>
> We are using the latest versions from the wrap DB for the above but the
> versions available via wrap DB itself appears quite old. For instance,
>
> - curl 8.12.1 was released on Feb/2025. The latest available
> is 8.22.0 (released Sep/2026)
>
> - OpenSSL 3.0.10 was released on Aug/2023. The latest available are
> 3.0.22 (released Aug/2026) and 4.0.1 (released Jun/2026).
>
> Is this version gap something we need to document / think about?
Maybe, but I think the proper way to fix this would be to update the
wrap DB if we really care about this. For now we only use this so that
we can have a mostly dependencyless Windows build with GitLab CI. I
don't think anybody uses this for a production-facing build.
So I'd leave this as-is for now, but agree that we should maybe iterate
a bit on this going forward and collaborate with upstream.
Thanks!
Patrick
next prev parent reply other threads:[~2026-10-05 10:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 14:09 [PATCH 0/7] A couple of Meson improvements Patrick Steinhardt
2026-09-24 14:09 ` [PATCH 1/7] meson: avoid recompiling HTTP sources several times Patrick Steinhardt
2026-09-30 12:00 ` Karthik Nayak
2026-10-05 8:03 ` Kaartic Sivaraam
2026-09-24 14:09 ` [PATCH 2/7] meson: don't recompile git-remote-http(1) multiple times for tests Patrick Steinhardt
2026-09-24 14:09 ` [PATCH 3/7] meson: use precompiled headers for our test-helper Patrick Steinhardt
2026-09-30 12:20 ` Karthik Nayak
2026-09-24 14:09 ` [PATCH 4/7] meson: use precompiled headers for unit tests Patrick Steinhardt
2026-10-05 9:34 ` Kaartic Sivaraam
2026-10-05 10:24 ` Patrick Steinhardt
2026-09-24 14:09 ` [PATCH 5/7] meson: fix outdated completion helpers Patrick Steinhardt
2026-09-24 14:09 ` [PATCH 6/7] meson: update wrappers Patrick Steinhardt
2026-09-30 12:24 ` Karthik Nayak
2026-10-05 9:42 ` Kaartic Sivaraam
2026-10-05 10:25 ` Patrick Steinhardt [this message]
2026-09-24 14:09 ` [PATCH 7/7] gitlab-ci: fix hanging MSVC jobs Patrick Steinhardt
2026-09-30 12:26 ` Karthik Nayak
2026-09-30 12:48 ` Patrick Steinhardt
2026-09-30 12:26 ` [PATCH 0/7] A couple of Meson improvements Karthik Nayak
2026-10-05 9:51 ` Kaartic Sivaraam
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=asN7AJdVmPCzov7l@pks.im \
--to=ps@pks.im \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=kaartic.sivaraam@gmail.com \
/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