Yes we are aware. We are looking into the issue and are trying to have it
resolve shortly.
Lori Shepherd
Bioconductor Core Team
Roswell Park Cancer Institute
Department of Biostatistics & Bioinformatics
Elm & Carlton Streets
Buffalo, New York 14263
From: Bioc-deve
Hi,
I assume you are already aware of it, but there's a problem with the builder
for the new packages. It works fine in Windows but Mac and Linux cannot access
CRAN
checking package dependencies ...Warning: unable to access index for repository
https://CRAN.R-project.org/src/contrib:
cannot
Okay, thank you very much!
On Fri, 12 Apr 2019 at 12:25, Shepherd, Lori
wrote:
> That is not correct. The webhook was only for the package submission
> process.
>
> See the link provided on linking to Bioconductor.
>
> Other helpful github links can be found here:
> http://bioconductor.org/deve
That is not correct. The webhook was only for the package submission process.
See the link provided on linking to Bioconductor.
Other helpful github links can be found here:
http://bioconductor.org/developers/how-to/git/
Lori Shepherd
Bioconductor Core Team
Roswell Park Cancer Institute
Thank you for the instructions!
Can I just clarify -- I was pushing changes to my Github repository that
has a webhook set up (as per instructions from when I first submitted the
package to Bioconductor). I thought that pushes to master branch with
version bump should trigger package builds. Am I
We are not seeing the changes pushed to the git.bioconductor server. I am
assuming you are referring to the RELEASE_3_8 branch since you are referencing
1.6.1.
Have set up the remote upstream to point to Bioconductor,
http://bioconductor.org/developers/how-to/git/sync-existing-repositories/
Hi,
Sorry, I think I must have done something wrong as the build report is not
showing the updates to my package from 2 days ago. Could you please help me
with this? I thought I updated the version of BUMHMM correctly (from 1.6.1
to 1.6.2 and 1.6.3) but it is not been picked up?
Thanks,
Alina
On
Your configure outsmarts the check system, so your options are to omit the
flags or to live with the warning. Either solution is fine with Bioconductor.
Martin
On 4/12/19, 4:17 AM, "Bioc-devel on behalf of Jochen Knaus"
wrote:
Hi everybody,
for our new R package "Netboost" we ha
Hi everybody,
for our new R package "Netboost" we have a problem about non portable
compiler flags. Basically we support AVX in our own C++ code (using
compiler intrinsics to use the AVX units). Of course we have a non-AVX
code path.
For building we use autotools and configure to determine at
