all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: Timotej Lazar <timotej.lazar@araneo.si>
Cc: 62878-done@debbugs.gnu.org, 62913-done@debbugs.gnu.org
Subject: [bug#62913] [PATCH core-updates] gnu: openhsm: Fix test failure with openssl-3.
Date: Tue, 18 Apr 2023 22:05:20 +0200	[thread overview]
Message-ID: <ZD74AM+x3SyZ5W+Z@jurong> (raw)
In-Reply-To: <87edoi465g.fsf@araneo.si>

Am Mon, Apr 17, 2023 at 10:15:23PM +0200 schrieb Timotej Lazar:
> Not exactly sure what you mean, the package already uses that URL for
> the homepage. The www.softhsm.org domain is just a CNAME for
> www.opendnssec.org.

Right, never mind!

> > Could you add a pointer to the source of the patch (at the top of the file,
> > for instance)? I did not find it in the Debian package.
> I took the patch off a mailing list. It turns out that the final version
> used by the Debian package is slightly different. I updated my patch to
> use that version and added a link to the source:
> https://sources.debian.org/patches/softhsm2/2.6.1-2.1/0003-fix-ftbfs-with-opensslv3.patch/

Great, thanks for the contribution!

I have just pushed the patch.

Andreas





      parent reply	other threads:[~2023-04-18 20:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-16  8:45 [bug#62878] [PATCH core-updates] gnu: openhsm: Fix test failure with openssl-3 Timotej Lazar
2023-04-17  9:18 ` Andreas Enge
2023-04-17 20:15   ` Timotej Lazar
2023-04-17 20:18     ` [bug#62913] [PATCH core-updates v2] " Timotej Lazar
     [not found]       ` <handler.62913.B.16817627115691.ack@debbugs.gnu.org>
2023-04-17 21:10         ` [bug#62913] Acknowledgement ([PATCH core-updates v2] gnu: openhsm: Fix test failure with openssl-3.) Timotej Lazar
2023-04-18 20:05     ` Andreas Enge [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=ZD74AM+x3SyZ5W+Z@jurong \
    --to=andreas@enge.fr \
    --cc=62878-done@debbugs.gnu.org \
    --cc=62913-done@debbugs.gnu.org \
    --cc=timotej.lazar@araneo.si \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.