unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Roel Janssen <roel@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] import: Update Bioconductor release to 3.5.
Date: Fri, 28 Apr 2017 11:11:12 +0200	[thread overview]
Message-ID: <rbur30c5233.fsf@gnu.org> (raw)
In-Reply-To: <87pofyat7b.fsf@elephly.net>


Ricardo Wurmus writes:

> Roel Janssen <roel@gnu.org> writes:
>
>>> I’d be happy if you could take care of the mass update.  I should note
>>> that sometimes new inputs are required.  To find them I usually run the
>>> update in a separate branch where I’ve applied changes to import anew
>>> and compare with the existing package expression when updating.  It’s on
>>> my list to clean this all up and submit my changes for review.  It’s
>>> ugly but it works pretty well.  If you’re interested I could send you a
>>> patch.
>>
>> How do you test which inputs are required?  I built all the bioconductor
>> packages and fixed their builds by adding inputs wherever that was
>> needed.  This does not take care of inputs that are no longer needed (if
>> any..).  Any way I can test that in a convenient way?
>
> Attached is my rough patch set.  Apply this and run the update with
> “guix refresh -t bioconductor,cran -u”.  It will tell you to “consider”
> removing or adding inputs.  Some of the suggestions are wrong, but it
> really means well :)
>
> It’s terrible code in some places.  Don’t look too closely.

Thanks!  I think I've processed the mass-update now.  It looks like we
have only gained dependencies. (Not a lot though).

I kept the SVN repository URL for Bioconductor for now, instead of the
Github mirror.  AFAIU, Bioconductor is going to transition to Git (and
Github) before the next release, which deprecates the
'Bioconductor-mirror' repository.  Since package maintainers get the
heads-up and probably have to take some action when this transition
occurs, I will make sure we transition without service disruption. :)

Kind regards,
Roel Janssen

      reply	other threads:[~2017-04-28  9:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-26  9:13 [PATCH] import: Update Bioconductor release to 3.5 Roel Janssen
2017-04-27  6:51 ` Ricardo Wurmus
2017-04-27  7:44   ` Roel Janssen
2017-04-27 13:14     ` Ricardo Wurmus
2017-04-28  9:11       ` Roel Janssen [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

  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=rbur30c5233.fsf@gnu.org \
    --to=roel@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    /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).