[R-pkg-devel] LaTeX issues on r-devel-windows-x86_64-gcc10-UCRT?
Dear all, lately, an error and two warnings occurred for our package dataquieR on the platform r-devel-windows-x86_64-gcc10-UCRT (https://cran.r-project.org/web/checks/check_results_dataquieR.html). Unfortunately, error messages/warnings are likely related to the test system’s configuration/setup: - Missing file /msys64/home/tomas/ucrt3/svn/ucrt3/r_packages/patches_idx.rds - "LaTeX errors“ without further specification, rather unspecific. I have now re-built this environment as close as I could according to the platform description and given my infrastructure. In this setup, I had a missing font in the end in my test installation. After I had applied this: https://tex.stackexchange.com/a/129523 (setup configuration for the font ts1-zi4r), the pdf could be created. The warning about missing patches_idx.rds, I could not reproduce, but this may be less relevant anyway. The setup, I used (hopefully close to r-devel-windows-x86_64-gcc10-UCRT) was - Microsoft Windows 10 Enterprise LTSC, 10.0.17763 Build 17763 - R 4.2.0 Pre Release UCRT3 downloaded today from r-project.org as the only R installation - Rtools 4.0.2.0.1 downloaded today from r-project.org as the only Rtools installation - For TeX, I installed MiKTeX 21.6 as the only TeX installation. - all binaries were put on the PATH environment variable —— Now my question: Is this related to CRAN’s r-devel-windows-x86_64-gcc10-UCRT and can that be fixed there? Whom should I contact at CRAN? Thank you in advance, Stephan -- Dr. Stephan Struckmann stephan.struckm...@uni-greifswald.de Biomathematiker/Informatiker/Apotheker Tel. +49 (0) 3834 - 86 77 83 Institut für Community Medicine Walther-Rathenau-Str. 48 17475 Greifswald __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
Re: [R-pkg-devel] LaTeX issues on r-devel-windows-x86_64-gcc10-UCRT?
Dear Tomas, > thanks. The new results are now available and the patches issue was resolved. geat work, thank you! > > These results are still with MiKTeX 21.8, with some crashes (e.g. when > building the documentation for R), but it seems dataquieR is not affected. I > will downgrade to 21.6, which should resolve these - I've tested that in the > automated VM setup at > https://svn.r-project.org/R-dev-web/trunk/WindowsBuilds/winutf8/ucrt3/vm.html Indeed, dataquieR now doesn’t show any errors any more. If I find the time, I’ll try MikTeX 21.8 later today, maybe, I can examine the issues a bit deeper then. Have a great day, Stephan signature.asc Description: Message signed with OpenPGP __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
[R-pkg-devel] r-oldrel-windows-ix86+x86_64 -- bioconductor links?
Dear list members, thank you for reading. For a few weeks, I have a WARNING on CRAN package checks for our dataquieR package, which does not even indirectly use Bioconductor nor cites anything from there. The warning states, that an old bioconductor release is not available any more: > Check: for unstated dependencies in ‘tests’ > Result: WARN > Warning: unable to access index for repository > https://bioconductor.org/packages/3.14/bioc/src/contrib: > cannot open URL > 'https://bioconductor.org/packages/3.14/bioc/src/contrib/PACKAGES' > Warning: unable to access index for repository > https://bioconductor.org/packages/3.14/data/annotation/src/contrib: > cannot open URL > 'https://bioconductor.org/packages/3.14/data/annotation/src/contrib/PACKAGES' > Warning: unable to access index for repository > https://bioconductor.org/packages/3.14/data/experiment/src/contrib: > cannot open URL > 'https://bioconductor.org/packages/3.14/data/experiment/src/contrib/PACKAGES' > Flavor: r-oldrel-windows-ix86+x86_64 I suspect, this WARNING is related with the test infrastructure somehow. Since I also have to fix two NOTEs within the next two weeks, I should comment on this WARNING too. What would you propose to do about the WARNING — I cannot address it, because dataquieR is not using Bioconductor at all (I’m rather sure about this, because `grep -ir bioc *` returns nothing, and because the BiocManager package does not list https://CRAN.R-project.org/package=BiocManager in its reverse dependencies). I expected the WARNING to disappear once someone fixes the suspected problems on r-oldrel-windows-ix86+x86_64, but this has not yet happened. Any hints how to handle this are appreciated, thank you in advance, Stephan signature.asc Description: Message signed with OpenPGP __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
