Re: [Bioc-devel] Removal of Information in OrgDb generated from NCBI -- Feedback needed.

2020-04-29 Thread Stadler, Michael
Hi Lori Just my two-cents: I would not miss UNIGENE. I am using org.db's mostly to annotate primary gene identifiers (ENTERZID, ENSEMBL) with additional human readable information (SYMBOL, GENENAME), and to map between different primary identifiers. I mostly use, in decreasing order of importan

[Bioc-devel] How to change version number in release

2020-04-29 Thread Xu, Zongli (NIH/NIEHS) [E] via Bioc-devel
I accidently changed the second number (y) of a version number (x.y.z, in release version), from an even number to an odd number. Now I seems can not update my package anymore. Is anyone know how to change it back to an even number? Thanks, Zongli __

Re: [Bioc-devel] LazyData in DESCRIPTION file

2020-04-29 Thread Vincent Carey
I see this is guideline 7 at https://bioconductor.org/developers/package-guidelines/ I have used LazyData: TRUE so that [pkgname]::[entity] can be used instead of data(). The claim that it is "rarely a good thing" and slows down package loading can be weighed against convenience. I am not sure y

[Bioc-devel] LazyData in DESCRIPTION file

2020-04-29 Thread Vinh Tran
Dear Bioc members, I have just encountered a warning during the CHECK that some data objects are used in the documents but not in code (e.g. “Variables with usage in documentation object ‘ppTree’ but not in code"). They are the demo data, that I am using only in the examples for demonstrate the

[Bioc-devel] Removal of Information in OrgDb generated from NCBI -- Feedback needed.

2020-04-29 Thread Shepherd, Lori
Hello Bioconductor maintainers The core team was made aware of an issue with one of the make orgDb functions in AnnotationForge: https://github.com/Bioconductor/AnnotationForge/issues/13 Investigating further, NCBI will no longer be updating the gene2unigene file. The url has moved to an ARC

Re: [Bioc-devel] No build report

2020-04-29 Thread Cao, Quy
Thank you Lori! From: Shepherd, Lori Sent: Wednesday, April 29, 2020 11:50 AM To: Cao, Quy ; Herv� Pag�s ; Nitesh Turaga ; Bioc-devel Subject: Re: [Bioc-devel] No build report There are only automatic emails when a package fails. You can get the daily build reports by going to http://biocon

Re: [Bioc-devel] No build report

2020-04-29 Thread Shepherd, Lori
There are only automatic emails when a package fails. You can get the daily build reports by going to http://bioconductor.org/checkResults/ That has the devel (3.12) and release (3.11) build reports updated daily. Lori Shepherd Bioconductor Core Team Roswell Park Comprehensive Cancer Cente

Re: [Bioc-devel] No build report

2020-04-29 Thread Cao, Quy
Hi Herve, I definitely didn't look into the right place. I was waiting for an email about my package build report. Thank you so much for pointing this out. Regards, Quy -Original Message- From: Hervé Pagès Sent: Wednesday, April 29, 2020 11:44 AM To: Cao, Quy ; Shepherd, Lori ; Nite

Re: [Bioc-devel] No build report

2020-04-29 Thread Hervé Pagès
Hi Quy, Are you looking at the right place? Build report for BioC 3.11 is here https://bioconductor.org/checkResults/3.11/bioc-LATEST/ and I see PERFect there, since at least Monday. Best, H. On 4/29/20 08:01, Cao, Quy wrote: Dear Lori, I haven't seen a build report for the package yet.

Re: [Bioc-devel] No build report

2020-04-29 Thread Cao, Quy
Dear Lori, I haven't seen a build report for the package yet. Should I be waiting for a little bit more? Thanks, Quy From: Shepherd, Lori Sent: Monday, April 27, 2020 11:00 AM To: Cao, Quy ; Nitesh Turaga ; Bioc-devel Subject: Re: No build report It looks like you had merge conflicts with

Re: [Bioc-devel] Bioconductor 3.11 is Released!

2020-04-29 Thread Shepherd, Lori
Thank you for letting us know. I'll look into your NEWS file and see why it wasn't included. If there was an issue with formatting I will contact you off the bioc mailing list. Cheers, Lori Shepherd Bioconductor Core Team Roswell Park Comprehensive Cancer Center Department of Biostatistic