Anyone on TeX Live 2021 pretest ? (to confirm a regression for ja LilyPond)

[Kornel Benko]

Am Sat, 29 May 2021 13:45:24 -0400
schrieb Scott Kostyshak <skostysh at lyx.org>:

> On Sun, May 23, 2021 at 10:24:15AM +0200, Kornel Benko wrote:
> > Am Sat, 22 May 2021 21:43:18 -0400
> > schrieb Scott Kostyshak <skostysh at lyx.org>:
> >   
> > > On Sat, May 22, 2021 at 05:26:10PM +0200, Kornel Benko wrote:  
> > > > Am Sat, 22 May 2021 16:51:43 +0200
> > > > schrieb Jürgen Spitzmüller <spitz at lyx.org>:
> > > >     
> > > > > Am Samstag, dem 22.05.2021 um 16:33 +0200 schrieb Kornel Benko:    
> > > > > > Fine. But how to explain that running with 2020-dvipdfmx compiles on
> > > > > > TL20, but the same dvipdfmx (copied from TL20) fails if using TL20 env.      
> > > > > 
> > > > > Stricter security measures have been introduced with TL 21 [1].
> > > > > 
> > > > > The produced DVI is fine, but dvipdfmx does not produce a PDF due to
> > > > > access restrictions (when attempting to access fonts).
> > > > > 
> > > > > When processing the DVI with
> > > > > 
> > > > > dvipdfmx -i dvipdfmx-unsafe.cfg
> > > > > 
> > > > > it works, i.e., after changing the converter DVI > PDF (dvipdfm) to
> > > > > dvipdfmx -i dvipdfmx-unsafe.cfg -o $$o $$i
> > > > > 
> > > > > dvipdfmx-unsafe.cfg makes dvipdfmx call gs (rungs) with -dNOSAFER
> > > > > rather than with -DSAFER (as in the default dvipdfmx.cfg of TL21).    
> > > > 
> > > > Thanks.
> > > >     
> > > > > However, this change should definitely only be applied to trustworthy
> > > > > files, so changing the converter generally is certainly not such a good
> > > > > idea.
> > > > > 
> > > > > Jürgen
> > > > > 
> > > > > [1] The explicit call of -DSAFER has been introduced for TL 21:
> > > > > https://tug.org/pipermail/tex-live-commits/2021-March/017216.html
> > > > >     
> > > > 
> > > > That means that we could use this setting for our tests.    
> > > 
> > > Thanks for following up on this, Kornel. I think I stopped looking into
> > > this issue because I thought it was due to a known bug with a fix in
> > > progress.
> > > 
> > > Scott  
> > 
> > Committed change to prefTest.pm to add "-i dvipdfmx-unsafe.cfg" as
> > parameter for dvipdfmx in our test environment.
> > 
> > To use:
> > 	$ cd <build_dir>
> > 	$ ./prefTest.pl test  
> 
> I think there is a related issue: Some exports that use ps2pdf now seem
> to need the flag "-dALLOWPSTRANSPARENCY" on TL21. Adding the following
> line to my preferences file fixes some tests:
> 
> \converter "ps" "pdf" "ps2pdf -dALLOWPSTRANSPARENCY $$i $$o" "hyperref-driver=dvips
> 
> I believe that this fixes the failures in the following tests:
> 
> export/examples/Presentations/Powerdot_lyx22 (Failed)
> export/examples/Presentations/Powerdot_lyx23 (Failed)
> DEFAULTOUTPUT_export/examples/Presentations/Powerdot_pdf (Failed)
> export/examples/Articles/Chess/Game_2_lyx22 (Failed)
> export/examples/Articles/Chess/Game_2_lyx23 (Failed)
> DEFAULTOUTPUT_export/examples/Articles/Chess/Game_2_pdf (Failed)
> export/examples/Graphics_and_Insets/Instant_Preview_lyx22 (Failed)
> export/examples/Graphics_and_Insets/Instant_Preview_lyx23 (Failed)
> DEFAULTOUTPUT_export/examples/Graphics_and_Insets/Instant_Preview_pdf (Failed)
> 
> Interestingly, the flag fixes the English Powerdot tests but not the
> French ones. I think the failures in the French document might be
> additionally related to 441c6a93. I've started some discussion on that
> commit.
> 
> I took a look at sub getConverter($$) but I'm not sure my Perl skills
> are good enough to create a non-hackish patch. Kornel, are you
> interested?
> 
> Scott

I will have a look.

	Kornel
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: Digitale Signatur von OpenPGP
URL: <http://lists.lyx.org/pipermail/lyx-devel/attachments/20210530/28194a84/attachment.asc>