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, 2
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 in
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
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 h
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
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
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 C
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
_
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
> shahris
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 m
Developers,
The release of Bioconductor 3.9 is less than a week out. Today marks the
'feature freeze' of 3.9 where we ask that all commits are limited to bug fixes
and documentation (no more API changes).
Thanks.
Lori Shepherd
Bioconductor Core Team
Roswell Park Cancer Institute
Departmen
Please see
http://bioconductor.org/developers/how-to/git/
and
#17 of the FAQ http://bioconductor.org/developers/how-to/git/faq/
You personally can create as many branches as you like for your own use.
We recommend the following and these are the upstream branches to link to:
Bioconductor
12 matches
Mail list logo
