Hi,
Recently my package (universalmotif) has suddenly started timing out on both
release and devel builds for all platforms
(https://bioconductor.org/checkResults/devel/bioc-LATEST/universalmotif/),
stopping at the "creating vignettes" stage. I've determined that the issue is
this particular l
Dear Bioc-devel,
For a little while now I've been getting a couple of odd Rd warnings in the
Windows check of the devel branch of my package:
Found the following significant warnings:
Rd warning: Previous alias or file overwritten by alias:
convert_motifs,PWM-method
Rd warning: cannot open
Hi,
Recently I've been having several examples fail on the tokay2 test machine,
specifically the i386 examples. Unfortunately I don't have access to a
windows machine to diagnose these failures right now, and the output that I
can see shows no errors; the examples just end abruptly. I don't see th
ait for the upstream fix.
>
> Martin
>
>
> On 1/2/20, 7:06 AM, "Bioc-devel on behalf of Benjamin Jean-Marie Tremblay"
> benjamin.tremb...@uwaterloo.ca> wrote:
>
>Dear bioc-devel,
>
>My package has been getting a strange error on merida1 (als
Dear bioc-devel,
My package has been getting a strange error on merida1 (also celaya2)
during the initial install phase. I've pasted it at the bottom of this message.
My question is: what can I do to figure out what the problem is? I already work
on a Mac currently, and R CMD check runs fine. I'v
; > and the release branch. The fix addresses vignette build errors
> > > >
> > > > occurring
> > > > > with rmarkdown v1.18, these should clear up within the next build
> >
> > cycle.
> > > > > Cheers,
> > > > > Andrzej
>
doc_date() : could not find function "doc_date"
> Calls: ... inline_exec -> hook_eval -> withVisible -> eval -> eval
> Execution halted
>
> Should I wait until BiocStyle is updated?
>
> Best,
> Ioannis
>
> Fra: Martin Morgan
> Sendt: sønd
I’ve been getting the exact same error for compiling the Rmarkdown
vignettes in my own package. Some partial testing before the weekend
revealed that in my case the error could be circumvented simply by not
using
output: BiocStyle::pdf_document
but instead
output: pdf_document
in the ya
