From: crtxcr <crtxcr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: libtasn1: update to 4.19.0. CVE-2021-46848
Date: Wed, 21 Dec 2022 23:15:44 +0100 [thread overview]
Message-ID: <20221221221544.y6LzjaxHwUP1s27U0IDrxv5H9INOUNXZSgMVkqcA5RY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41226@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 336 bytes --]
New comment by crtxcr on void-packages repository
https://github.com/void-linux/void-packages/pull/41226#issuecomment-1362173255
Comment:
tests/version.c test fails on musl, I suspect because strverscmp() used by lib/version.c behaves differently in musl. Maybe will just patch out that particular check in the test, as alpine does.
next prev parent reply other threads:[~2022-12-21 22:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-21 21:50 [PR PATCH] " crtxcr
2022-12-21 22:15 ` crtxcr [this message]
2023-01-19 6:05 ` [PR PATCH] [Merged]: " Vaelatern
2023-01-19 6:11 ` Vaelatern
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=20221221221544.y6LzjaxHwUP1s27U0IDrxv5H9INOUNXZSgMVkqcA5RY@z \
--to=crtxcr@users.noreply.github.com \
--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).