unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Roel Janssen <roel@gnu.org>
To: Leo Famulari <leo@famulari.name>
Cc: 47826@debbugs.gnu.org
Subject: [bug#47826] [PATCH] gnu: Update blast+ to 2.11.0.
Date: Fri, 16 Apr 2021 20:14:27 +0200	[thread overview]
Message-ID: <daec05a12651971815b6101a89f2d75d5cfcf366.camel@gnu.org> (raw)
In-Reply-To: <YHm9PrPcbgRFTsOY@jasmine.lan>

Hi Leo,

On Fri, 2021-04-16 at 12:37 -0400, Leo Famulari wrote:
> On Fri, Apr 16, 2021 at 01:22:59PM +0200, Roel Janssen wrote:
> > Hi Guix,
> > 
> > Here's a patch to update blast+ to 2.11.0.
> > 
> > Kind regards,
> > Roel Janssen
> > 
> 
> > From 92d8f8602a285fc3ed61656c314a697cd87ae4f4 Mon Sep 17 00:00:00
> > 2001
> > From: Roel Janssen <roel@gnu.org>
> > Date: Fri, 16 Apr 2021 13:20:53 +0200
> > Subject: [PATCH] gnu: Update blast+ to 2.11.0.
> > 
> > * gnu/packages/bioinformatics.scm (blast+): Update to 2.11.0.
> 
> LGTM, assuming the packages the depend on it still build.
> 

Let's see if I got this right:
$ ./pre-inst-env guix refresh --list-dependent blast+
/home/roel/Programming/guix/gnu/packages/bioinformatics.go
Building the following 2 packages would ensure 2 dependent packages are
rebuilt: roary@3.12.0 proteinortho@6.0.14

So I built roary and proteinortho with the blast+ patch applied, and
both build fine.

Can I conclude from this that packages depending on blast+ still build
fine?

Kind regards,
Roel Janssen





  reply	other threads:[~2021-04-16 18:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-16 11:22 [bug#47826] [PATCH] gnu: Update blast+ to 2.11.0 Roel Janssen
2021-04-16 16:37 ` Leo Famulari
2021-04-16 18:14   ` Roel Janssen [this message]
2021-04-16 18:22     ` Leo Famulari
2021-04-16 18:58       ` bug#47826: " Roel Janssen

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=daec05a12651971815b6101a89f2d75d5cfcf366.camel@gnu.org \
    --to=roel@gnu.org \
    --cc=47826@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 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).