Hi All

Is it acceptable to specify a particular version of igraph for our package to 
use, even as a temporary fix?

Failing that, does anyone know of any way I can get R to tell me which 
functions in our package (CausalR) call which igraph functions?

Thanks
Glyn

-----Original Message-----
From: Bioc-devel [mailto:bioc-devel-boun...@r-project.org] On Behalf Of 
bioc-devel-requ...@r-project.org
Sent: 20 July 2015 11:00
To: bioc-devel@r-project.org
Subject: Bioc-devel Digest, Vol 136, Issue 20

Send Bioc-devel mailing list submissions to
        bioc-devel@r-project.org

To subscribe or unsubscribe via the World Wide Web, visit
        https://stat.ethz.ch/mailman/listinfo/bioc-devel
or, via email, send a message with subject or body 'help' to
        bioc-devel-requ...@r-project.org

You can reach the person managing the list at
        bioc-devel-ow...@r-project.org

When replying, please edit your Subject line so it is more specific than "Re: 
Contents of Bioc-devel digest..."


Today's Topics:

   1. changes to igraph break many Bioconductor packages (in
      release and devel) (Dan Tenenbaum)


----------------------------------------------------------------------

Message: 1
Date: Sun, 19 Jul 2015 14:38:39 -0700 (PDT)
From: Dan Tenenbaum <dtene...@fredhutch.org>
To: bioc-devel <bioc-devel@r-project.org>
Subject: [Bioc-devel] changes to igraph break many Bioconductor
        packages (in release and devel)
Message-ID:
        <622339655.4339608.1437341919035.javamail.r...@fredhutch.org>
Content-Type: text/plain; charset=utf-8

Hello,

The igraph package (in CRAN) recently had a major API change. The changes are 
detailed in its NEWS file:
https://cran.r-project.org/web/packages/igraph/news.html

The changes cause many Bioconductor packages to break in both release and 
devel. If you are the maintainer of one of the following packages, please see 
our build report (release: 
http://bioconductor.org/checkResults/release/bioc-LATEST/ ; devel: 
http://bioconductor.org/checkResults/devel/bioc-LATEST/ ) for a report of the 
error and fix it right away in release (if your package is in release) and 
devel. You should increment the package version number as well in order to 
cause your changes to propagate.


BioNet
CausalR
facopy
FEM *
FGNet *
geNetClassifier
GenomicInteractions
GenoView
HTSanalyzeR
netbiov



* - these packages also need to be sure to import (in DESCRIPTION and 
NAMESPACE) the graph package.


If you have any questions, please send them to the bioc-devel mailing list.

Thanks,
Dan



------------------------------

Subject: Digest Footer

_______________________________________________
Bioc-devel mailing list
Bioc-devel@r-project.org
https://stat.ethz.ch/mailman/listinfo/bioc-devel


------------------------------

End of Bioc-devel Digest, Vol 136, Issue 20
*******************************************

________________________________

This e-mail was sent by GlaxoSmithKline Services Unlimited
(registered in England and Wales No. 1047315), which is a
member of the GlaxoSmithKline group of companies. The
registered address of GlaxoSmithKline Services Unlimited
is 980 Great West Road, Brentford, Middlesex TW8 9GS.

_______________________________________________
Bioc-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/bioc-devel

Reply via email to