all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Leo Famulari <leo@famulari.name>
Cc: 54627@debbugs.gnu.org
Subject: [bug#54627] [PATCH] gnu: libressl: Update to 3.3.6.
Date: Wed, 30 Mar 2022 20:33:31 +0200	[thread overview]
Message-ID: <387826c2ba196edd1f53a7492aba32b96d3deb80.camel@gmail.com> (raw)
In-Reply-To: <YkOEG1dC3K/tCm2J@jasmine.lan>

Am Dienstag, dem 29.03.2022 um 18:11 -0400 schrieb Leo Famulari:
> On Tue, Mar 29, 2022 at 09:52:43PM +0200, Liliana Marie Prikler
> wrote:
> > * gnu/packages/tls.scm (libressl): Update to 3.3.6.
> > ---
> > Hi Guix,
> > 
> > In light of lfam's comment over at guix-devel, I tried updating
> > libressl.
> > Version 3.3.6 is currently the latest in the 3.3 tree, so it ought
> > to be save
> > to bump, but I didn't verify that with all packages yet.  Bumping
> > to 3.5 won't 
> > be possible without addressing a failing test case.
> 
> Thanks!
> 
> Will you be able to test the build of the packages that depend on
> libressl?
I'm currently testing the builds.  The first one to fail among the list
returned by `guix refresh' was epic5, which is a leaf package and also
fails for me outside the pre-inst-env.  We might want to investigate
that separately.




  reply	other threads:[~2022-03-30 19:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-29 19:52 [bug#54627] [PATCH] gnu: libressl: Update to 3.3.6 Liliana Marie Prikler
2022-03-29 22:11 ` Leo Famulari
2022-03-30 18:33   ` Liliana Marie Prikler [this message]
2022-03-31  4:24     ` Liliana Marie Prikler
2022-04-12 18:46   ` bug#54627: " Liliana Marie Prikler
2022-04-27 22:58     ` [bug#54627] " Leo Famulari
2022-04-11 19:51 ` [bug#54627] kiasoc5--- via Guix-patches via

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=387826c2ba196edd1f53a7492aba32b96d3deb80.camel@gmail.com \
    --to=liliana.prikler@gmail.com \
    --cc=54627@debbugs.gnu.org \
    --cc=leo@famulari.name \
    /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.