Skip to content
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

TeX Live 2016 test breaks #1199

Closed
henryso opened this issue Aug 6, 2016 · 16 comments
Closed

TeX Live 2016 test breaks #1199

henryso opened this issue Aug 6, 2016 · 16 comments
Milestone

Comments

@henryso
Copy link
Contributor

henryso commented Aug 6, 2016

Under TeX Live 2016 (but not TeX Live 2015), the plain-tex/PopulusSion/PopulusSion.tex, plain-tex/braces/over_braces.tex, and plain-tex/text-styles/text-styles.tex tests fail with:

infwarerr: The package is already loaded, stopped
) (/usr/local/texlive/2016/texmf-dist/tex/generic/oberdiek/ltxcmds.sty
ltxcmds: The package is already loaded, stopped
)
! Undefined control sequence.
<argument> ...degraphics \@undefined \else \@ifpackageloaded 
                                                  {pst-pdf}{}{\@ifpackageloa...
\AtBeginDocument #1->#1

l.1271   }

? 
! Emergency stop.
<argument> ...degraphics \@undefined \else \@ifpackageloaded 
                                                  {pst-pdf}{}{\@ifpackageloa...
\AtBeginDocument #1->#1

l.1271   }

End of file on the terminal!

!  ==> Fatal error occurred, no output PDF file produced!

The custom spaces also appear to be broken under TeX Live 2016. See the gabc-output/glyphs/spaces.gabc test:

image

@henryso henryso added this to the 4.2 milestone Aug 6, 2016
@rpspringuel
Copy link
Contributor

The plain-tex tests are failing due to some sort of package loading error with graphicx and xcolor. I can reproduce them with the following simple document:

%%%%%%%%%%%%%%%%%%
%% TeXLive 2016 compatibility
\ifdefined\pagewidth                   \let\pdfpagewidth       \pagewidth                  \fi
\ifdefined\pageheight                  \let\pdfpageheight      \pageheight                 \fi
%%%%%%%%%%%%%%%%%%

\pdfpagewidth210mm
\pdfpageheight297mm

\edef\greoldcatcode{\the\catcode`@}
\catcode`\@=11

\input graphicx.tex % for \resizebox
\input color.sty%

\catcode`\@=\greoldcatcode

\color{red}
Hello!
\bye

This only occurs under LuaTeX. pdfTeX handles the above document fine. We're thus probably looking at a LuaTeX bug. @eroux, where was it that we were supposed to report such bugs again?

@eroux
Copy link
Contributor

eroux commented Aug 15, 2016

Do you have an up to date TeXLive 2016? A similar problem was reported here but it seems to have been fixed... if it's not, I think the mailing list of the thread is the correct one...

@rpspringuel
Copy link
Contributor

I'm fully up to date (just checked).

After some more experimenting I've discovered that I can work around the issue as follows:

%%%%%%%%%%%%%%%%%%
%% TeXLive 2016 compatibility
\ifdefined\pagewidth                   \let\pdfpagewidth       \pagewidth                  \fi
\ifdefined\pageheight                  \let\pdfpageheight      \pageheight                 \fi
%%%%%%%%%%%%%%%%%%

\pdfpagewidth210mm
\pdfpageheight297mm

\edef\greoldcatcode{\the\catcode`@}
\catcode`\@=11

\input miniltx.tex
\input color.sty%
\input graphicx.tex %

\catcode`\@=\greoldcatcode

\color{red}
Hello!
\bye

@eroux
Copy link
Contributor

eroux commented Aug 15, 2016

Well, this still looks like a bug, so I think it would be best to report it to tex-live mailing-list

@rpspringuel
Copy link
Contributor

Well, it doesn't appear to me to be a TeXLive packaging problem, so I'm not sure that's the right place. Since the problem appears related to graphicx and color, I just reported it to the LaTeX project using their bug reporting form (as they are the maintainers of those packages).

@eroux
Copy link
Contributor

eroux commented Aug 15, 2016

Ok thanks

@rpspringuel
Copy link
Contributor

For future reference, bug reports on the PlainTeX interface of color and graphicx should go to one of the following places:

https://github.com/davidcarlisle/dpctex/tree/master/plain-graphics

or

https://github.com/latex3/graphics-def

rpspringuel added a commit to rpspringuel/gregorio that referenced this issue Aug 16, 2016
There's a bug that causes documents to fail in TeXLive 2016 when graphix is loaded before color.  It is easily avoided by loading color first (the change I make here so that gregorio-project#1199 is resolved), but I've also reported the bug to the appropriate people.
@rpspringuel
Copy link
Contributor

The PlainTeX problems are addressed in #1207. Even without those changes, however, they should be solved when the fix (which has already been pushed to CTAN) makes it to the download mirrors in 24 hours or so.

The problem with the custom spacings remains.

@rpspringuel
Copy link
Contributor

I just did some experimenting and it seems that adding a tex.setskip command into gregoriotex.lua in the appropriate place fixes the issue with the custom spacings. My guess is that the scaling in Lua is no longer being communicated implicitly back to TeX, so we have to do it explicitly ourselves.

I've made the fix locally, I'm just debating which release to push it to.

@henryso
Copy link
Contributor Author

henryso commented Aug 18, 2016

Is setting tex.setskip backward compatible to at least TeX Live 2015? It seems like that should go into 4.1.x, along with @anthonyfok's change, if that can be vetted.

@rpspringuel
Copy link
Contributor

I'm in the process of checking backwards compatibility. I'll let you know the results when I have them.

@rpspringuel
Copy link
Contributor

The change is backwards compatible with TL2015.

@henryso
Copy link
Contributor Author

henryso commented Aug 21, 2016

Any clues to the cause of the custom spacing issue?

@rpspringuel
Copy link
Contributor

I have my suspicion (given above), but nothing more at the moment. I just sent an email to the LuaTeX list asking about the change to see if my suspicions are correct.

@rpspringuel
Copy link
Contributor

The reply I got from the LuaTeX list:

skips (glue) is kind of special in the sense that it's something indirect (glue specs)

in the current luatex the glue nodes no longer use these specs (so no indirectness) but the registers are still 'specs' so, what you get with
tex.getskip is a gluespec (node) that you can then mess with (independently) and you set a skip by passing a gluespec node

(the old model also shared specs with ref counts and such which could be quite tricky and have side effects when messing with these specs)

you can use tex.setglue to set the width (or more values)

If I understand the jargon correctly, then my suspicion is correct and the fix I applied is the appropriate one.

@henryso
Copy link
Contributor Author

henryso commented Aug 22, 2016

... and since you confirmed earlier that this is backwards-compatible, it's all good. Thanks for following up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants