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

[Scott Kostyshak]

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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <http://lists.lyx.org/pipermail/lyx-devel/attachments/20210522/89d75633/attachment-0001.asc>