Displaying 20 results from an estimated 11000 matches similar to: "package vignettes build in the same R process?"
2017 Dec 06
2
FW: R-devel error
Interesting, yesterday I had exactly this problem, but today I solved it
(see the R-pkg-devel list) by _installing_ R-devel and
> update.packages(checkBuilt = TRUE)
I also tried it on Martin's Fedora 26 example below. Worked fine (had to
install some packages...)
On ubuntu 16.04.
G?ran Brostr?m
On 2017-12-06 11:29, Martin Maechler wrote:
>>>>>> Pearce, Robert
2017 Dec 05
2
FW: R-devel error
I am resubmitting this bug report but with additional information. I am running this with windows 10: w64-mingw32 with R Under development (unstable) (2017-12-04 r73829). I build 'httk' from the command prompt using 'R CMD build httk' after installing the required packages. Then when the vignettes are being created, it crashes. Today I installed the latest versions of Rtools,
2017 Dec 06
0
FW: R-devel error
>>>>> Pearce, Robert <Pearce.Robert at epa.gov>
>>>>> on Tue, 5 Dec 2017 21:31:09 +0000 writes:
> I am resubmitting this bug report but with additional information. I am running this with windows 10: w64-mingw32 with R Under development (unstable) (2017-12-04 r73829).
There is no such message (as you cite below) in the R-devel archives:
2013 Mar 13
1
Failed to locate 'weave' output file / vignette product does not have a known filename extension
Hello,
I'm seeing three different vignette-related errors with recent
versions of R-3.0.0 alpha.
First, with the package BitSeq
(http://bioconductor.org/packages/2.12/bioc/html/BitSeq.html), I get
the following when trying to build the package:
Error: processing vignette ?BitSeq.Rnw' failed with diagnostics:
Failed to locate the ?weave? output file (by engine ?utils::Sweave?)
for
2017 Dec 06
0
FW: R-devel error
Robert,
To expand a bit on Goran's point, is it possible that you have an old
library with packages installed that your R-devel is hitting. The R headers
changes relatively recently, so any packages with compiled code that were
built long enough ago (I don't have the exact date off the top of my head)
need to be rebuilt before they can be safely used.
If this is happening in a state
2013 Feb 15
1
Suggestion: Custom filename patterns for non-Sweave vignettes
Hi,
as far as I understand it, the new R devel feature of processing
non-Sweave vignettes will (a) locate any "[.][RrSs](nw|tex)$" or
".Rmd" files, (b) check for a registered vignette engine, (c) process
the file using the registered "weave" function, (d) and possibly post
process the generated weave artifact (e.g. a *.tex file).
I'd like to propose to extend
2013 Oct 08
1
"Failed to locate the 'texi2pdf' output file"
Just thought I would mention that the issue below (and in https://stat.ethz.ch/pipermail/r-devel/2013-April/066318.html) is still not resolved.
It hasn't been a big problem, but it potentially could be, if a critical package were to have this error on release day, then all its dependencies would fail to build, which would probably require us to postpone our release.
See the complete thread
2016 Aug 24
1
feature request for non-sweave vignettes
Currently Makefiles for vignettes are only supported for .tex files. Could
the tools package be modified to allow file extensions to be specified for
a vignette engine? Having the pandoc pdf conversion in a Makefile rather
than through R would be tidier in some cases.
If I specify my vignette engine as
```
tools::vignetteEngine(
'myengine',
pattern = '\\.[Rr](md|nw)$',
2013 Aug 23
2
packages with Sweave and knitr vignettes?
Now that R 3.0.0+ supports non-Sweave vignettes, R-exts \S 1.4.2 seems
to imply that
it is possible to include both Sweave and knitr vignettes in a single
package.
I'm wondering
if anyone has tried this and/or if there are some hidden gotchas putting
this into practice,
and concerned about creating problems with CRAN checks if I try this.
Consider two vignettes:
pkg/vignettes/vign1.Rnw,
2014 May 30
1
R CMD check for the R code from vignettes
Hi,
Recently I saw a couple of cases in which the package vignettes were
somewhat complicated so that Stangle() (or knitr::purl() or other
tangling functions) can fail to produce the exact R code that is
executed by the weaving function Sweave() (or knitr::knit(), ...). For
example, this is a valid document that can pass the weaving process
but cannot generate a valid R script to be source()d:
2013 Apr 12
2
"Failed to locate the 'texi2pdf' output file"
Hi,
Every day a few Bioconductor packages (different ones each day) fail
to build, on Windows only, with an error like this:
D:\biocbld\bbs-2.13-bioc\meat>D:\biocbld\bbs-2.13-bioc\R\bin\R.exe CMD
build --keep-empty-dirs --no-resave-data OrganismDbi
[...]
Error in find_vignette_product(name, by = "texi2pdf", engine = engine) :
Failed to locate the 'texi2pdf' output file (by
2016 Jun 18
1
vignette output: word_document problems
Hello:
Clicking "Knit Word" in RStudio 0.99.893 with R 3.3.0, works
fine with a vignette with "output: word_document". However, "R CMD
build" throws the following error:
$ R CMD build pkgW2vignettes
* checking for file ?pkgW2vignettes/DESCRIPTION? ... OK
* preparing ?pkgW2vignettes?:
* checking DESCRIPTION meta-information ... OK
* installing the
2016 May 03
2
vignette/knitr help
I need some help understanding a problem running the tests on the
'digest' package. Initially, I got the message that the 'knitr' package
was needed to run vignettes:
Running vignettes for package ?digest?
Error in loadVignetteBuilder(vigns$pkgdir) :
vignette builder 'knitr' not found
So I installed the knitr package and all its dependents (?mime?,
?stringi?,
2017 Feb 21
2
R CMD build error during vignettes build
Hello,
I'm trying to rebuild a package (using R version 3.3.2 (2016-10-31))
that has not seen any changes since it was last built without problems
in previous R versions. It fails during vignette building with:
---<--------------------cut here---------------start------------------->---
$ R CMD build diveMove
* checking for file ?diveMove/DESCRIPTION? ... OK
* preparing ?diveMove?:
*
2015 Mar 12
2
Requirement for pandoc 1.12.3 in R 3.1.3
Thanks Brian.
Indeed, the vignette is in markdown form. When I updated my system to
R 3.1.3 I ran update.packages() and this seems to have upset things
(including R-studio processing of markdown files).
I tried removing rmarkdown and reverting to an older version so that my
sessionInfo() is
Loading required package: rmarkdown
> sessionInfo()
R version 3.1.3 (2015-03-09)
Platform:
2013 Apr 01
1
missing exported methods when compiling vignettes in R 3.0.0 RC
A new problem has cropped up with compiling vignettes for my package BayesFactor. I'm not sure when it started, but I can tell you it didn't occur on R 2.15.3, and it does on 3.0.0 RC (2013-03-31 r62463) (session info is at the bottom of this message).
I have defined methods for which.min and which.max for a class (I've defined both S3 and S4 methods for the class
2017 Feb 22
0
R CMD build error during vignettes build
On 21/02/17 19:06, Sebastian P. Luque wrote:
> Hello,
>
> I'm trying to rebuild a package (using R version 3.3.2 (2016-10-31))
> that has not seen any changes since it was last built without problems
> in previous R versions. It fails during vignette building with:
>
> ---<--------------------cut here---------------start------------------->---
> $ R CMD build
2014 Feb 20
1
Where to put package vignettes
Dear R-devel list,
My name is Guillermo Vinu?. I have created an R package that includes a
vignette. Earlier on, to test my package, I tried to install it both in
Linux and Windows and it worked. My vignette was in /inst/doc.
Now, I have finished for good and before submitting my package to CRAN
I've tried to install it again first in Linux and then in Windows (I
removed that first
2020 Nov 01
2
vignettes present in 2 folders or won't work
Dear all,
I am struggling with an issue related to static vignettes: they work, but
only when present in double in the tarball -- in the folder inst/doc and
vignettes; see below for details.
Details:
I am pre-compiling heavy vignettes thanks to the vignette builder R.rsp.
So basically, I have PDF files which I want the package to use as Vignettes.
For this, I have the following in my
2007 May 14
3
RFC: allow packages to advertise vignettes on Windows
Hello,
The vignette concept, which started in Bioconductor, seems to be
catching on. They are supported by R CMD build/check and documented
in the Writing R Extensions manual. I think vignettes are a fantastic
way to introduce new users to a package. However, getting new users
to realize that a vignette is available can be challenging.
For some time now, we have had a function in Biobase that