From: Ricardo Wurmus <rekado@elephly.net>
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: failing packages
Date: Sun, 18 Oct 2015 07:32:11 +0200 [thread overview]
Message-ID: <87h9lohhd0.fsf@elephly.net> (raw)
In-Reply-To: <20151017203457.GA16824@debian>
Andreas Enge <andreas@enge.fr> writes:
> There is a new version upstream (1.2.2); is it safe to try an update,
> or do the bioinformaticians need to keep the old version?
We could update. If someone needs an older version they could easily
create a variant, I suppose.
(I cannot make the update myself as I’ll be mostly offline for the next
couple of days.)
~~ Ricardo
next prev parent reply other threads:[~2015-10-18 5:32 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-06 9:48 failing packages Efraim Flashner
2015-10-06 11:38 ` Ludovic Courtès
2015-10-06 11:47 ` Pjotr Prins
2015-10-06 12:25 ` Ricardo Wurmus
2015-10-06 12:56 ` Andreas Enge
2015-10-06 15:30 ` Alex Kost
2015-10-06 16:47 ` Ludovic Courtès
[not found] ` <5613B60C.6050901@uq.edu.au>
2015-10-14 10:41 ` Ben Woodcroft
2015-10-14 13:29 ` Andreas Enge
2015-10-14 13:37 ` Ben Woodcroft
2015-10-14 17:03 ` Efraim Flashner
2015-10-16 20:11 ` Andreas Enge
2015-10-16 21:02 ` Andreas Enge
2015-10-17 8:11 ` Ricardo Wurmus
2015-10-17 16:24 ` Andreas Enge
2015-10-17 10:52 ` Pjotr Prins
2015-10-17 19:56 ` Andreas Enge
2015-10-17 20:04 ` Ricardo Wurmus
2015-10-17 20:34 ` Andreas Enge
2015-10-18 5:32 ` Ricardo Wurmus [this message]
2015-10-17 20:37 ` Andreas Enge
2015-10-17 21:01 ` Andreas Enge
2015-10-17 20:40 ` Efraim Flashner
-- strict thread matches above, loose matches on Subject: below --
2015-10-17 11:14 Federico Beffa
2015-10-17 15:20 ` Federico Beffa
2015-10-17 16:18 ` Federico Beffa
2015-10-17 16:21 ` Andreas Enge
2015-10-17 16:33 ` Andreas Enge
2015-10-17 16:45 ` Federico Beffa
2015-10-17 16:53 ` Andreas Enge
2015-10-17 17:55 ` Federico Beffa
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=87h9lohhd0.fsf@elephly.net \
--to=rekado@elephly.net \
--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 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).