-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test fails with TeXLive 2023 #105
Comments
Ah actually my previously reported issue seems to be more directly related to this! ☝️
|
@grimbough any thoughts on how to resolve this? |
With the patch described in Debian bug #1050807 the Bioconductor.sty becomes incompatible to ragged2e < v3.5. On the one hand one could make sure not to use the old ragged2e (if this is possible somehow) after applying the patch. On the other hand one could try to improve the patch by doing something like:
This suggestion is untested. P.S.: this style file contains lots of |
Just confirming we also see this on our CI runs at: https://github.com/Bioconductor/BiocStyle/actions/runs/6185247528/job/16790480792 |
Aha, this is super helpful, it seems the pandoc version plays a big role here. Let me add |
Those tests aren't comprehensive. They confound both tinytex & pandoc versions. Given the other reports here I'm sure it's the latest Tinytex (or texlive) version that is the issue |
Oh OK I see, pandoc 2.17 uses the tinytex 2022.01, thanks for pointing that out. |
Hopefully this is now solved in 0858890 I've no idea whether the issue the patch was trying to solve is still around, so for now I've elected to only apply they patch if we're using ragged2e version 3.5 or older. We'll see if anyone complains of unexpected rendering going forwards. This fix should be available in both release and devel version of the package (2.28.1 and 2.29.2 respectively). Thank you all for the pointers, please report here if it continues to be an issue. |
Isn't that what this line is doing? BiocStyle/inst/resources/tex/Bioconductor.sty Line 529 in 3ae5fa0
If ragged2e is later than 2023-06-01 then it enters |
You are correct, sorry I missed that |
Hi,
there is a bug report in Debian about a failure with TeXLive 2023. Just see the bug log and the attached workaround (which probably needs enhancement).
Kind regards, Andreas.
The text was updated successfully, but these errors were encountered: