Github messages for voidlinux
 help / color / mirror / Atom feed
From: dkwo <dkwo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: openssl3
Date: Thu, 23 Jun 2022 14:10:54 +0200	[thread overview]
Message-ID: <20220623121054.1jaMdMCBka07Wtlb3mc0NrdNuEqNSTBtvFiVarHbilY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37576@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 540 bytes --]

New comment by dkwo on void-packages repository

https://github.com/void-linux/void-packages/pull/37576#issuecomment-1164329494

Comment:
Now it works, but of course it has a huge overlap with openssl. Perhaps it's simpler to have this as an update, rather than new package, as the shift will happen anyway at some point (the tricky part is rebuild anyything that shlib-requires libssl or libcrypto). To this end, is there a reason why `ca-certificates` depends on `openssl<=2.0_1` ? This seems to be the only manifest obstacle at present.

  parent reply	other threads:[~2022-06-23 12:10 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-15 19:48 [PR PATCH] New package: openssl3-3.0.3 dkwo
2022-06-16 14:30 ` dkwo
2022-06-17  7:49 ` [PR PATCH] [Updated] " dkwo
2022-06-17  7:51 ` dkwo
2022-06-17  8:08 ` dkwo
2022-06-18 13:30 ` dkwo
2022-06-18 13:40 ` dkwo
2022-06-18 13:52 ` dkwo
2022-06-22 14:35 ` New package: openssl3 dkwo
2022-06-22 14:37 ` [PR PATCH] [Updated] " dkwo
2022-06-22 14:37 ` dkwo
2022-06-22 15:41 ` leahneukirchen
2022-06-22 16:14 ` [PR PATCH] [Updated] " dkwo
2022-06-22 17:18 ` dkwo
2022-06-22 17:20 ` dkwo
2022-06-23 12:10 ` dkwo [this message]
2022-06-24 20:06 ` leahneukirchen
2022-06-25 17:02 ` [PR PATCH] [Closed]: " dkwo
2022-06-25 17:02 ` dkwo

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=20220623121054.1jaMdMCBka07Wtlb3mc0NrdNuEqNSTBtvFiVarHbilY@z \
    --to=dkwo@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).