Re: [Bioc-devel] How can I print a message on console with library("myPackage")?

2019-04-24 Thread Martin Morgan
Yes I strongly second Robert's suggestion. Also be sure that you are registered at https://support.bioconductor.org and that you enter your package name in the 'Watched tags' field of the user Profile, so that you are notified by email whenever a question is posted there. Martin On 4/24/19,

Re: [Bioc-devel] Unable to reproduce chimeraviz 3.9 build failure (test failure)

2019-04-24 Thread Pages, Herve
Hi Stian, This is likely related to an issue with the recently updated org.Hs.eg.db package. The issue was reported on this list 2 days ago: https://stat.ethz.ch/pipermail/bioc-devel/2019-April/014956.html A fix for org.Hs.eg.db is on its way. Hopefully it will make the current test failure

Re: [Bioc-devel] How can I print a message on console with library("myPackage")?

2019-04-24 Thread Robert M. Flight
Instead of putting the message in the startup, perhaps make use of the BugReports field in the package DESCRIPTION, and maybe use a GitHub issues page with a good template This way you avoid annoying your users with startup messages, for something that should be accessible in the DESCRIPTION

[Bioc-devel] Unable to reproduce chimeraviz 3.9 build failure (test failure)

2019-04-24 Thread Stian Lågstad
Hi, The most recent build of chimeraviz failed due to a test failure: https://master.bioconductor.org/checkResults/3.9/bioc-LATEST/chimeraviz/malbec2-checksrc.html. That the test in question should suddenly fail surprises me, and I'm unable to reproduce this locally. Does anyone have ideas as to

Re: [Bioc-devel] No build report today (April 24, 2019)

2019-04-24 Thread Pages, Herve
On 4/24/19 10:48, Pages, Herve wrote: > Hi developers, > > Due to some technical problems with the build system, there will be no > new build report today for the BioC 3.10 software builds. I meant for the BioC 3.9 builds sorry. (There won't be a report for the BioC 3.10 builds either but these

Re: [Bioc-devel] How can I print a message on console with library("myPackage")?

2019-04-24 Thread Arman Shahrisa
Thank you very much for your kind help. That fixed my issue. Best regards, Arman From: Shepherd, Lori Sent: Wednesday, April 24, 2019 9:59:40 PM To: Arman Shahrisa; Martin Morgan; bioc-devel; szwj...@gmail.com Subject: Re: [Bioc-devel] How can I print a message

[Bioc-devel] No build report today (April 24, 2019)

2019-04-24 Thread Pages, Herve
Hi developers, Due to some technical problems with the build system, there will be no new build report today for the BioC 3.10 software builds. Sorry for the inconvenience. H. -- Hervé Pagès Program in Computational Biology Division of Public Health Sciences Fred Hutchinson Cancer Research

Re: [Bioc-devel] How can I print a message on console with library("myPackage")?

2019-04-24 Thread Shepherd, Lori
I assume your package is the cbaf package? Don't forget the new zzz.R file to the collate field in the DESCRIPTION Lori Shepherd Bioconductor Core Team Roswell Park Cancer Institute Department of Biostatistics & Bioinformatics Elm & Carlton Streets Buffalo, New York 14263

Re: [Bioc-devel] How can I print a message on console with library("myPackage")?

2019-04-24 Thread Arman Shahrisa
I really appreciate your kind answers. I created the zzz.R file in the same folder as the rest of my R files. I tried both .onAttach and .onLoad functions as follow: > .onAttach <- function(libname, pkgname){ >packageStartupMessage("Please send bug reports and suggestions to >

Re: [Bioc-devel] failing package nucleoSim

2019-04-24 Thread Turaga, Nitesh
Hi Astrid Your package should be good to go now as far as the "master" (devel) branch goes. Don't worry about the RELEASE_3_8 having duplicate commit issues, it doesn't need to be fixed since it's been frozen (i.e you cannot issue changes to it anymore). But from the upcoming release, please