From: Leo Famulari <leo@famulari.name>
To: guix-devel@gnu.org
Subject: Re: bug#22831: OpenSSL should not depend on Perl
Date: Mon, 29 Feb 2016 19:43:33 -0500 [thread overview]
Message-ID: <20160301004333.GA4741@jasmine> (raw)
In-Reply-To: <20160229084815.GC18766@jasmine>
On Mon, Feb 29, 2016 at 03:48:15AM -0500, Leo Famulari wrote:
> On Sun, Feb 28, 2016 at 02:37:54PM +0100, Ludovic Courtès wrote:
> > Leo Famulari <leo@famulari.name> skribis:
> >
> > > On Sat, Feb 27, 2016 at 06:05:29PM +0100, Ludovic Courtès wrote:
> > >> Commit 784d6e91 changed OpenSSL such that it does not depend on Perl,
> > >> but one of the subsequent upgrades broke it:
> > >
> > > Bisecting, I narrowed it down to:
> > > 86c8f1daf8ed10f13f2b1e973a28845629b8ce47
> > > (gnu: openssl: Update to 1.0.2e [fixes CVE-2015-{3193,3194,3195}].).
> > >
> > > I'll get the openssl sources corresponding to the good and bad commmits
> > > and try to figure out what changed that pulled perl back in.
> >
> > Also we should add something like:
> >
> > #:allowed-references (list (canonical-package glibc)
> > (list (canonical-package gcc) "lib")
> > "out")
> >
> > to avoid regressions.
>
> Okay, good idea.
Normally I wouldn't forward mail from bug-guix to guix-devel. I need
help with a patch addressing a bug that I'd like to see fixed alongside
tomorrow's OpenSSL update, so I'm trying to increase the exposure.
I need help setting up #:allowed-references:
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=22831#23
next parent reply other threads:[~2016-03-01 0:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87lh66xew6.fsf@gnu.org>
[not found] ` <20160228011027.GC6690@jasmine>
[not found] ` <87lh65vtu5.fsf@gnu.org>
[not found] ` <20160229084815.GC18766@jasmine>
2016-03-01 0:43 ` Leo Famulari [this message]
2016-03-01 20:48 ` bug#22831: OpenSSL should not depend on Perl Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160301004333.GA4741@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).