Dear all,
I hope this isn't a duplicate of another question. Here goes:
- I would like to update my swfdr package, which is already on
Bioconductor. It is also on Github and my submission process was via
opening an issue at https://github.com/Bioconductor/Contributions/issues/213
- At this point
Hi Levi,
The external_data_store.txt file is not needed anymore.
The current git.bioconductor.org server does not store files in the LFS mode,
so you can just add a file, commit and push. But for Github, you might have to
use LFS for such large files. I’ll look into this more and get back to yo
Also, can I now remove external_data_store.txt?
$ cat external_data_store.txt
data
inst/extdata
On Tue, Sep 5, 2017 at 4:38 PM, Levi Waldron
wrote:
> Are a couple extra commands needed at https://www.bioconductor.
> org/developers/how-to/git/maintain-github-bioc/ for experimental data
> packag
Are a couple extra commands needed at
https://www.bioconductor.org/developers/how-to/git/maintain-github-bioc/
for experimental data packages? I followed the instructions here for
curatedOvarianData, but got GitHub warnings on push:
remote: warning: GH001: Large files detected. You may want to try
Hi Nitesh --
Thanks very much for the help on this last week. I've been investigating
the build problem displayed on the page you linked rather slowly but have
reached a point where I now have a question:
- The error appears to be due to an example data set not being found.
This data set ap
If you go to the github issue (#375), I believe there is an option at the
bottom to reopen issue.
Lori Shepherd
Bioconductor Core Team
Roswell Park Cancer Institute
Department of Biostatistics & Bioinformatics
Elm & Carlton Streets
Buffalo, New York 14263
F
Hi,
I submitted my package (MetaCyto) to bioconductor a few months ago. At that
time, the package was not accepted and the issue was closed. I would like to
re-submit my package. However, the system terminated my submission with the
following message: You cannot post the same repository more th
Hi Andrzej,
Thank you for replies and looking into this!
Thank you for the detailed explanation about the beta workflow build
system and the use of rmarkdown::render with a custom template. Does
it support \@ref() calls?
Now that the Windows build is solved, I believe that the Mac one is
related
Hey Kasper,
- I really appreciate your help. Although it didn't help answer the
question directly, I think it would still be necessary to clarify
some facts:
1. I agree that using "non-standard fonts" could bring better aesthetics
for a particular group of people -- maybe not everyone. But
Build errors like these (related to processing of vignettes) happens
occasionally. I _strongly_ suggests not not using non-standard fonts or
advanced layout features. The small advantage of this (better aesthetics
according to the package writer, but not always according to everyone who
reads it)
Dear BioC,
- I see some very recent build errors for my packages (vignettes) which
use Google Fonts:
pandoc: Could not fetch
https://fonts.googleapis.com/css?family=Alegreya+Sans:400,400i,700
TlsExceptionHostPort (HandshakeFailed Error_EOF) "fonts.googleapis.com"
443
For example
https://biocondu
11 matches
Mail list logo
