all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: 01/01: gnu: boost: Update to 1.58.0.
Date: Fri, 10 Jul 2015 17:28:10 -0400	[thread overview]
Message-ID: <87615rn1n9.fsf@netris.org> (raw)
In-Reply-To: <20150710192556.GA3066@debian> (Andreas Enge's message of "Fri, 10 Jul 2015 21:25:56 +0200")

Andreas Enge <andreas@enge.fr> writes:

> I will push this to a wip-boost branch, and try to build a dependent package
> locally. I wonder if I should base wip-boost on openssl-update; but with
> only 69 dependent packages (if the count is true), it probably does not
> matter.

I see that you pushed this branch and asked Hydra to build it.  First, I
don't think that we should be building a new branch against a version of
openssl with a known security flaw.  It will only have to be immediately
rebuilt again.

I would also prefer to prioritize getting this openssl security fix
deployed, if you don't mind.  Toward that end, I'm going to delete the
jobset on Hydra for now.  If you disagree, can we talk about it?

      Mark

      parent reply	other threads:[~2015-07-10 21:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20150708211909.12880.83730@vcs.savannah.gnu.org>
     [not found] ` <E1ZCwkI-0003Mp-SX@vcs.savannah.gnu.org>
2015-07-08 23:12   ` 01/01: gnu: boost: Update to 1.58.0 Mark H Weaver
2015-07-09 22:00     ` Mark H Weaver
2015-07-09 23:17       ` Andreas Enge
2015-07-10 16:52         ` Mark H Weaver
2015-07-10 19:25           ` Andreas Enge
2015-07-10 20:03             ` Mark H Weaver
2015-07-11  8:32               ` Andreas Enge
2015-07-11 13:37                 ` Mark H Weaver
2015-07-10 21:28             ` Mark H Weaver [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=87615rn1n9.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=andreas@enge.fr \
    --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 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.