Tinytex: Custom packages update (resolving error on pdftexcmds or kvoptions)

Created on 2 Dec 2019  路  7Comments  路  Source: yihui/tinytex

Hello, first of all, thank you so much for creating and hosting this setup.

It appears that the meta package oberdiek has recently dropped two packages that are necessary for building R manual pages: kvoptions and pdftexcmds.

I noticed this using github action's and it stumped me for a while, but I found that if I ensured that those two packages were installed, everything was fine.

I've made an incredibly minimal (and useless!) package to show the issue at https://github.com/jonkeane/simple-package see the error in the action around https://github.com/jonkeane/simple-package/runs/329317228#step:7:71 The setup-tinytex stage completes fine, but when R CMD check is run, the manual isn't able to be built because it can't find pdftexcmds.sty

I'm not fully certain the intent of the custom packages yaml in TinyTeX is to be able to build package docs, but if it is, I've submitted a PR (#157) including those two packages which should clear this up.


By filing an issue to this repo, I promise that

  • [x] I have fully read the issue guide at https://yihui.name/issue/.
  • [x] I have provided the necessary information about my issue.

    • If I'm asking a question, I have already asked it on Stack Overflow or RStudio Community, waited for at least 24 hours, and included a link to my question there.

    • If I'm filing a bug report, I have included a minimal, self-contained, and reproducible example, and have also included xfun::session_info('tinytex'). I have upgraded all my packages to their latest versions (e.g., R, RStudio, and R packages), and also tried the development version: remotes::install_github('yihui/tinytex').

    • If I have posted the same issue elsewhere, I have also mentioned it in this issue.

  • [x] I have learned the Github Markdown syntax, and formatted my issue correctly.

I understand that my issue may be closed if I don't fulfill my promises.

Most helpful comment

The process of the oberdiek CTAN package restructuring seems to be ongoing - see series of commits here moving packages to their own repositories.

We are currently seeing failures on GitHub actions where pdfescape is not found. @yihui would you like me/us to submit a PR as we come across these, or is there way to handle it more holistically?

cc @boshek

All 7 comments

Thank you so much for the so careful investigation and useful information! A colleague of mine actually asked me this question a couple of days ago but I didn't know what went wrong. Now it is clear to me after I read the announcement in the CTAN list.

Issues like this have reminded me how fragile and spaghetti-y the latex world is.
you will 钀ㄦ硶锛寉ou will all 钀ㄦ硶

It appears there's a new one: letltxmacro I can't find a CTAN announcement about this one moving, but I'm seeing the same behavior: https://github.com/jonkeane/simple-package/runs/336725908 I've submitted a PR again: #160

Perfect! Thanks again!

The process of the oberdiek CTAN package restructuring seems to be ongoing - see series of commits here moving packages to their own repositories.

We are currently seeing failures on GitHub actions where pdfescape is not found. @yihui would you like me/us to submit a PR as we come across these, or is there way to handle it more holistically?

cc @boshek

@ateucher I have added pdfescape this time. If you find more in the future, please feel free to submit PRs. FYI, you can find the package names by passing the LaTeX error to tinytex::parse_packages():

> tinytex::parse_packages(text = "! LaTeX Error: File `pdfescape.sty' not found.")
tlmgr search --file --global '/pdfescape.sty'
[1] "pdfescape"

Thank you!

Perfect, thanks @yihui!

Was this page helpful?
0 / 5 - 0 ratings