unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Roel Janssen <roel@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>, guix-devel@gnu.org
Subject: Re: Updating to latest Bioconductor release
Date: Mon, 16 Nov 2020 13:38:01 +0100	[thread overview]
Message-ID: <5b6c661babc4fbda5cda5c72a654e79b14b0bf67.camel@gnu.org> (raw)
In-Reply-To: <86k0ulscwv.fsf@gmail.com>

Hi Simon,

On Mon, 2020-11-16 at 13:29 +0100, zimoun wrote:
> Hi Roel,
> 
> On Mon, 16 Nov 2020 at 13:10, Roel Janssen <roel@gnu.org> wrote:
> 
> > Hehe. I'm building all R packages in the "wip-r" branch now to see
> > what's left for me to fix.
> 
> Cool!  I do not know if Ricardo fetched my branch to update ’wip-r’
> because an error about a missing symbol was there and then I
> corrected
> it in my branch.  Anyway.
> 
> BTW, I would like to add the type ’workflow’ in addition to
> ’annotation’
> and ’experiment’.  Because I need:
> 
> <https://bioconductor.org/packages/3.11/workflows/html/cytofWorkflow.html
> >
> 
> Well, I do not know if that should go to ’wip-r’ or directly to
> ’master’.  WDYT?

Well, I see we're getting R packages that fail to build because the
source cannot be downloaded (anymore), due to the outdated Bioconductor
version.  So if we can do an upgrade to 3.12 soon, and add the
'workflow' type later, that'd be my preferred route.

So to achieve that, I think we need to:
1. Update the Bioconductor version to 3.12
2. Update/build the Bioconductor packages that are already in Guix.
3. --> When all build failures have been resolved, push to master?

4. Add the bits for 'workflow' packages.
5. Add workflow packages / adjust the ones we have (do we have any?)
and build/test them.
6. --> Push to master?

WDYT?

Kind regards,
Roel Janssen




  reply	other threads:[~2020-11-16 12:38 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-16 10:49 Updating to latest Bioconductor release Roel Janssen
2020-11-16 11:27 ` zimoun
2020-11-16 12:10   ` Roel Janssen
2020-11-16 12:29     ` zimoun
2020-11-16 12:38       ` Roel Janssen [this message]
2020-11-16 12:59         ` zimoun
2020-11-17 22:58 ` zimoun
2020-11-18  9:31   ` Roel Janssen
2020-11-18 11:50     ` zimoun
2020-11-18 16:13       ` Roel Janssen
2020-11-18 16:23         ` zimoun
2020-11-18 16:33           ` Roel Janssen
2020-11-18 16:59             ` zimoun
2020-11-19 15:31               ` Roel Janssen
2020-11-19 15:36                 ` zimoun
2020-11-19 15:57                   ` Roel Janssen
2020-11-19 16:18                     ` zimoun
2020-11-19 16:25                       ` Roel Janssen
2020-11-19 16:36                         ` zimoun
2020-11-19 17:27                         ` zimoun
2020-11-19 19:03                           ` Roel Janssen
2020-11-19 19:18                             ` zimoun
2020-11-19 21:13                               ` Ricardo Wurmus
2020-11-20  9:16                                 ` Roel Janssen
2020-11-20 13:39                                   ` Ricardo Wurmus
2020-11-20 13:42                                     ` Ricardo Wurmus
2020-11-20 14:02                                       ` zimoun
2020-11-20 14:10                                       ` Roel Janssen
2020-11-20 13:59                                     ` zimoun
2020-11-20 14:28                                       ` Ricardo Wurmus
2020-11-20 15:20                                         ` zimoun

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=5b6c661babc4fbda5cda5c72a654e79b14b0bf67.camel@gnu.org \
    --to=roel@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=zimon.toutoune@gmail.com \
    /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).