Re: Anyone on TeX Live 2021 pretest ? (to confirm a regression for ja LilyPond)
On Tue, Jun 15, 2021 at 02:45:41PM +0200, Pavel Sanda wrote: > On Mon, Jun 14, 2021 at 10:19:20AM -0400, Scott Kostyshak wrote: > > > > > > > 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 > > > > > > > > > > > > Huh, this would be painful if true in general. > > > > > > > > > > Indeed it does seem annoying, but is only relevant for a few of our > > > > > documents. > > > > > > > > > > > What exact version of ghostscript do you have? > > > > > > > > > > $ gs --version > > > > > 9.53.3 > > > > > > > > If interested, see also: https://www.lyx.org/trac/ticket/12303 > > > > > > According to > > > https://tex.stackexchange.com/questions/597980/ghostscript-requires-dallowpstransparency-when-compiling-pstricks-figures > > > "An up-to-date TeX installation, such as TeXLive-2021, should already > > > have the GS call configured with -dALLOWPSTRANSPARENCY" > > > Is this actually true? > > > > I have an up-to-date TL21 installation and still get the issue. I'm not > > sure if the quoted statement was meant to be only about pdflatex. > > Ok, we'll need to figure out whether there are security implications with > dALLOWPSTRANSPARENCY and hopefully add it to defaults. > If not then we should at least parse error output to catch this particular > case and issue some informed warning. Sounds good. Let's discuss further at #12303. I don't think I will spend time on a patch. But I'm happy to provide feedback if anyone else is interested. Scott signature.asc Description: PGP signature -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Anyone on TeX Live 2021 pretest ? (to confirm a regression for ja LilyPond)
On Mon, Jun 14, 2021 at 10:19:20AM -0400, Scott Kostyshak wrote: > > > > > > 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 > > > > > > > > > > Huh, this would be painful if true in general. > > > > > > > > Indeed it does seem annoying, but is only relevant for a few of our > > > > documents. > > > > > > > > > What exact version of ghostscript do you have? > > > > > > > > $ gs --version > > > > 9.53.3 > > > > > > If interested, see also: https://www.lyx.org/trac/ticket/12303 > > > > According to > > https://tex.stackexchange.com/questions/597980/ghostscript-requires-dallowpstransparency-when-compiling-pstricks-figures > > "An up-to-date TeX installation, such as TeXLive-2021, should already have > > the GS call configured with -dALLOWPSTRANSPARENCY" > > Is this actually true? > > I have an up-to-date TL21 installation and still get the issue. I'm not sure > if the quoted statement was meant to be only about pdflatex. Ok, we'll need to figure out whether there are security implications with dALLOWPSTRANSPARENCY and hopefully add it to defaults. If not then we should at least parse error output to catch this particular case and issue some informed warning. Pavel -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Anyone on TeX Live 2021 pretest ? (to confirm a regression for ja LilyPond)
On Mon, Jun 14, 2021 at 11:40:13AM +0200, Pavel Sanda wrote: > On Sun, Jun 13, 2021 at 11:09:12AM -0400, Scott Kostyshak wrote: > > On Mon, May 31, 2021 at 02:19:26PM -0400, Scott Kostyshak wrote: > > > On Mon, May 31, 2021 at 04:57:49PM +0200, Pavel Sanda wrote: > > > > On Sat, May 29, 2021 at 01:45:24PM -0400, Scott Kostyshak wrote: > > > > > 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 > > > > > > > > Huh, this would be painful if true in general. > > > > > > Indeed it does seem annoying, but is only relevant for a few of our > > > documents. > > > > > > > What exact version of ghostscript do you have? > > > > > > $ gs --version > > > 9.53.3 > > > > If interested, see also: https://www.lyx.org/trac/ticket/12303 > > According to > https://tex.stackexchange.com/questions/597980/ghostscript-requires-dallowpstransparency-when-compiling-pstricks-figures > "An up-to-date TeX installation, such as TeXLive-2021, should already have > the GS call configured with -dALLOWPSTRANSPARENCY" > Is this actually true? I have an up-to-date TL21 installation and still get the issue. I'm not sure if the quoted statement was meant to be only about pdflatex. Scott signature.asc Description: PGP signature -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Anyone on TeX Live 2021 pretest ? (to confirm a regression for ja LilyPond)
Am Mon, 14 Jun 2021 11:40:13 +0200 schrieb Pavel Sanda : > On Sun, Jun 13, 2021 at 11:09:12AM -0400, Scott Kostyshak wrote: > > On Mon, May 31, 2021 at 02:19:26PM -0400, Scott Kostyshak wrote: > > > On Mon, May 31, 2021 at 04:57:49PM +0200, Pavel Sanda wrote: > > > > On Sat, May 29, 2021 at 01:45:24PM -0400, Scott Kostyshak wrote: > > > > > 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 > > > > > > > > Huh, this would be painful if true in general. > > > > > > Indeed it does seem annoying, but is only relevant for a few of our > > > documents. > > > > > > > What exact version of ghostscript do you have? > > > > > > $ gs --version > > > 9.53.3 > > > > If interested, see also: https://www.lyx.org/trac/ticket/12303 > > According to > https://tex.stackexchange.com/questions/597980/ghostscript-requires-dallowpstransparency-when-compiling-pstricks-figures > "An up-to-date TeX installation, such as TeXLive-2021, should already have > the GS call > configured with -dALLOWPSTRANSPARENCY" Is this actually true? > > Pavel Since gs is not part of texlive21, this seems unlikely. On ubuntu: $ dpkg -S /usr/bin/gs ghostscript: /usr/bin/gs Kornel pgpCYpjPWn4Xq.pgp Description: Digitale Signatur von OpenPGP -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Anyone on TeX Live 2021 pretest ? (to confirm a regression for ja LilyPond)
On Sun, Jun 13, 2021 at 11:09:12AM -0400, Scott Kostyshak wrote: > On Mon, May 31, 2021 at 02:19:26PM -0400, Scott Kostyshak wrote: > > On Mon, May 31, 2021 at 04:57:49PM +0200, Pavel Sanda wrote: > > > On Sat, May 29, 2021 at 01:45:24PM -0400, Scott Kostyshak wrote: > > > > 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 > > > > > > Huh, this would be painful if true in general. > > > > Indeed it does seem annoying, but is only relevant for a few of our > > documents. > > > > > What exact version of ghostscript do you have? > > > > $ gs --version > > 9.53.3 > > If interested, see also: https://www.lyx.org/trac/ticket/12303 According to https://tex.stackexchange.com/questions/597980/ghostscript-requires-dallowpstransparency-when-compiling-pstricks-figures "An up-to-date TeX installation, such as TeXLive-2021, should already have the GS call configured with -dALLOWPSTRANSPARENCY" Is this actually true? Pavel -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Anyone on TeX Live 2021 pretest ? (to confirm a regression for ja LilyPond)
On Mon, May 31, 2021 at 02:19:26PM -0400, Scott Kostyshak wrote: > On Mon, May 31, 2021 at 04:57:49PM +0200, Pavel Sanda wrote: > > On Sat, May 29, 2021 at 01:45:24PM -0400, Scott Kostyshak wrote: > > > 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 > > > > Huh, this would be painful if true in general. > > Indeed it does seem annoying, but is only relevant for a few of our documents. > > > What exact version of ghostscript do you have? > > $ gs --version > 9.53.3 If interested, see also: https://www.lyx.org/trac/ticket/12303 Scott signature.asc Description: PGP signature -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Anyone on TeX Live 2021 pretest ? (to confirm a regression for ja LilyPond)
On Mon, May 31, 2021 at 04:57:49PM +0200, Pavel Sanda wrote: > On Sat, May 29, 2021 at 01:45:24PM -0400, Scott Kostyshak wrote: > > 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 > > Huh, this would be painful if true in general. Indeed it does seem annoying, but is only relevant for a few of our documents. > What exact version of ghostscript do you have? $ gs --version 9.53.3 Scott signature.asc Description: PGP signature -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Anyone on TeX Live 2021 pretest ? (to confirm a regression for ja LilyPond)
On Sat, May 29, 2021 at 01:45:24PM -0400, Scott Kostyshak wrote: > 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 Huh, this would be painful if true in general. What exact version of ghostscript do you have? Pavel -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Anyone on TeX Live 2021 pretest ? (to confirm a regression for ja LilyPond)
Am Sun, 30 May 2021 13:21:18 -0400 schrieb Scott Kostyshak : > On Sun, May 30, 2021 at 09:12:35AM +0200, Kornel Benko wrote: > > Am Sun, 30 May 2021 08:56:17 +0200 > > schrieb Kornel Benko : > > > > > > 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. > > > > > > > and here the patch. > > Tested and works great. Thank you! Please commit. > > Scott Committed at bc01f509. Kornel pgpWsOxLxPkim.pgp Description: Digitale Signatur von OpenPGP -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Anyone on TeX Live 2021 pretest ? (to confirm a regression for ja LilyPond)
On Sun, May 30, 2021 at 09:12:35AM +0200, Kornel Benko wrote: > Am Sun, 30 May 2021 08:56:17 +0200 > schrieb Kornel Benko : > > > > 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. > > > > and here the patch. Tested and works great. Thank you! Please commit. Scott signature.asc Description: PGP signature -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Anyone on TeX Live 2021 pretest ? (to confirm a regression for ja LilyPond)
Am Sun, 30 May 2021 08:56:17 +0200
schrieb Kornel Benko :
> > 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.
>
and here the patch.
Kornel
diff --git a/lib/scripts/prefTest.pm b/lib/scripts/prefTest.pm
index e98ac4ad2f..8e25b7986b 100644
--- a/lib/scripts/prefTest.pm
+++ b/lib/scripts/prefTest.pm
@@ -85,21 +85,28 @@ sub getConverter($$)
{
my ($l, $add) = @_;
chomp($l);
my ($from, $to, $cmd, $par);
($l, $from) = getNext($l);
- return undef if ($from !~ /(tex|dvi)$/);
+ return undef if ($from !~ /(ps|tex|dvi)$/);
($l, $to) = getNext($l);
return undef if ($to !~ /^((dvi3?|pdf[23456]?)(log)?)$/);
- my ($checkfor, $substitute);
+ my ($checkfor, $substitute, $extrapar);
if ($from =~ /tex/) {
$checkfor = qr/\s+\-shell\-(escape|restricted)/;
$substitute = "-shell-escape";
+$extrapar = qr/^latex/;
+ }
+ elsif ($from =~ /ps$/) {
+$checkfor = qr/\s+\-dALLOWPSTRANSPARENCY/;
+$substitute = "-dALLOWPSTRANSPARENCY";
+$extrapar = qr/hyperref-driver=dvips/;
}
else {
$checkfor = qr/\s+-i\s+dvipdfmx-unsafe.cfg/;
$substitute = "-i dvipdfmx-unsafe.cfg";
+$extrapar = qr/^hyperref-driver=dvipdfm/;
}
($l, $cmd) = getNext($l);
if ($add) {
if ($cmd !~ $checkfor) {
if ($cmd =~ /^(\S+)\s*(.*)$/) {
@@ -110,11 +117,11 @@ sub getConverter($$)
}
else {
$cmd =~ s/$checkfor//;
}
($l, $par) = getNext($l);
- return undef if ($par !~ /^(latex|hyperref-driver=dvipdfm)/);
+ return undef if ($par !~ $extrapar);
my $key = "\"$from\" \"$to\"";
if ($add) {
return([$key, [$cmd, $par]]);
}
else {
pgpkybCsF_b0n.pgp
Description: Digitale Signatur von OpenPGP
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Anyone on TeX Live 2021 pretest ? (to confirm a regression for ja LilyPond)
Am Sat, 29 May 2021 13:45:24 -0400 schrieb Scott Kostyshak : > 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 : > > > > > 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 : > > > > > > > > > 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 > > $ ./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 pgpi48CtLL0f2.pgp Description: Digitale Signatur von OpenPGP -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Anyone on TeX Live 2021 pretest ? (to confirm a regression for ja LilyPond)
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 : > > > 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 : > > > > > > > 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 > $ ./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 signature.asc Description: PGP signature -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Anyone on TeX Live 2021 pretest ? (to confirm a regression for ja LilyPond)
Am Sat, 22 May 2021 21:43:18 -0400 schrieb 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 : > > > > > 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 $ ./prefTest.pl test Kornel Kornel pgpPABJCKipk6.pgp Description: Digitale Signatur von OpenPGP -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Anyone on TeX Live 2021 pretest ? (to confirm a regression for ja LilyPond)
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 : > > > 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 signature.asc Description: PGP signature -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Anyone on TeX Live 2021 pretest ? (to confirm a regression for ja LilyPond)
Am Sat, 22 May 2021 16:51:43 +0200 schrieb Jürgen Spitzmüller : > 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. Kornel pgpLdyvHWpIat.pgp Description: Digitale Signatur von OpenPGP -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Anyone on TeX Live 2021 pretest ? (to confirm a regression for ja LilyPond)
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). 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 signature.asc Description: This is a digitally signed message part -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Anyone on TeX Live 2021 pretest ? (to confirm a regression for ja LilyPond)
Am Sat, 22 May 2021 16:07:17 +0200 schrieb Jürgen Spitzmüller : > Am Samstag, dem 22.05.2021 um 15:13 +0200 schrieb Kornel Benko: > > > what is the behavior on the released TexLive 2021? > > > > Still same. Does not compile due to error from dvipdfmx. > > The issue I have linked to has been fixed, so this must be something > else and should be reported to the dvipdfmx list. > > Jürgen > 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. From the POV of dvipdfmx devels, the input-data changed somehow. That makes it not unlikely that also platex creates wrong output. Kornel pgpsU2DnLMOQX.pgp Description: Digitale Signatur von OpenPGP -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Anyone on TeX Live 2021 pretest ? (to confirm a regression for ja LilyPond)
Am Samstag, dem 22.05.2021 um 16:23 +0200 schrieb Kornel Benko: > > Who is "we"? > > Peoples running the tests? But if this just hides a real bug, what is the purpose of changing the tests? Jürgen signature.asc Description: This is a digitally signed message part -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Anyone on TeX Live 2021 pretest ? (to confirm a regression for ja LilyPond)
Am Sat, 22 May 2021 16:06:26 +0200 schrieb Jürgen Spitzmüller : > Am Samstag, dem 22.05.2021 um 14:37 +0200 schrieb Kornel Benko: > > Is there any reason why we have to compile with platex? > > Who is "we"? Peoples running the tests? > > Selecting non-text fonts, the compilation succeeds (with lualatex and > > also with xetex). > > Fine, but I suppose some people still prefer to use platex. So even if > we change the example file, the bug is there. > > Jürgen Kornel pgpdvZ4ilzMkn.pgp Description: Digitale Signatur von OpenPGP -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Anyone on TeX Live 2021 pretest ? (to confirm a regression for ja LilyPond)
Am Samstag, dem 22.05.2021 um 15:13 +0200 schrieb Kornel Benko: > > what is the behavior on the released TexLive 2021? > > Still same. Does not compile due to error from dvipdfmx. The issue I have linked to has been fixed, so this must be something else and should be reported to the dvipdfmx list. Jürgen signature.asc Description: This is a digitally signed message part -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Anyone on TeX Live 2021 pretest ? (to confirm a regression for ja LilyPond)
Am Samstag, dem 22.05.2021 um 14:37 +0200 schrieb Kornel Benko: > Is there any reason why we have to compile with platex? Who is "we"? > Selecting non-text fonts, the compilation succeeds (with lualatex and > also with xetex). Fine, but I suppose some people still prefer to use platex. So even if we change the example file, the bug is there. Jürgen signature.asc Description: This is a digitally signed message part -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Anyone on TeX Live 2021 pretest ? (to confirm a regression for ja LilyPond)
Am Sat, 22 May 2021 14:56:58 +0200 schrieb Dr Eberhard W Lisse : > And, > > what is the behavior on the released TexLive 2021? Still same. Does not compile due to error from dvipdfmx. > el > > On 2021-05-22 14:37 , Kornel Benko wrote: > > Am Tue, 23 Mar 2021 10:50:16 -0400 > > schrieb Scott Kostyshak : > > > >> On Mon, Mar 22, 2021 at 11:52:49AM +0100, Jürgen Spitzmüller wrote: > >>> Am Montag, dem 22.03.2021 um 10:51 +0100 schrieb Kornel Benko: > Same here. Error in running > dvipdfmx -o ... > >>> > >>> Maybe https://tug.org/pipermail/tex-live/2021-March/046609.html > >> > >> Thanks for confirming Kornel, and for the relevant link Jürgen. > >> > >> Scott > > > > Is there any reason why we have to compile with platex? > > Selecting non-text fonts, the compilation succeeds (with lualatex and also > > with > > xetex). > > Kornel pgpU8BW0L3yT_.pgp Description: Digitale Signatur von OpenPGP -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Anyone on TeX Live 2021 pretest ? (to confirm a regression for ja LilyPond)
And, what is the behavior on the released TexLive 2021? el On 2021-05-22 14:37 , Kornel Benko wrote: Am Tue, 23 Mar 2021 10:50:16 -0400 schrieb Scott Kostyshak : On Mon, Mar 22, 2021 at 11:52:49AM +0100, Jürgen Spitzmüller wrote: Am Montag, dem 22.03.2021 um 10:51 +0100 schrieb Kornel Benko: Same here. Error in running dvipdfmx -o ... Maybe https://tug.org/pipermail/tex-live/2021-March/046609.html Thanks for confirming Kornel, and for the relevant link Jürgen. Scott Is there any reason why we have to compile with platex? Selecting non-text fonts, the compilation succeeds (with lualatex and also with xetex). Kornel -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Anyone on TeX Live 2021 pretest ? (to confirm a regression for ja LilyPond)
Am Tue, 23 Mar 2021 10:50:16 -0400 schrieb Scott Kostyshak : > On Mon, Mar 22, 2021 at 11:52:49AM +0100, Jürgen Spitzmüller wrote: > > Am Montag, dem 22.03.2021 um 10:51 +0100 schrieb Kornel Benko: > > > Same here. Error in running > > > dvipdfmx -o ... > > > > Maybe https://tug.org/pipermail/tex-live/2021-March/046609.html > > Thanks for confirming Kornel, and for the relevant link Jürgen. > > Scott Is there any reason why we have to compile with platex? Selecting non-text fonts, the compilation succeeds (with lualatex and also with xetex). Kornel pgpDqOc72C4gF.pgp Description: Digitale Signatur von OpenPGP -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Anyone on TeX Live 2021 pretest ? (to confirm a regression for ja LilyPond)
On Mon, Mar 22, 2021 at 11:52:49AM +0100, Jürgen Spitzmüller wrote: > Am Montag, dem 22.03.2021 um 10:51 +0100 schrieb Kornel Benko: > > Same here. Error in running > > dvipdfmx -o ... > > Maybe https://tug.org/pipermail/tex-live/2021-March/046609.html Thanks for confirming Kornel, and for the relevant link Jürgen. Scott signature.asc Description: PGP signature -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Anyone on TeX Live 2021 pretest ? (to confirm a regression for ja LilyPond)
Am Montag, dem 22.03.2021 um 10:51 +0100 schrieb Kornel Benko: > Same here. Error in running > dvipdfmx -o ... Maybe https://tug.org/pipermail/tex-live/2021-March/046609.html Jürgen signature.asc Description: This is a digitally signed message part -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Anyone on TeX Live 2021 pretest ? (to confirm a regression for ja LilyPond)
Am Wed, 17 Mar 2021 22:44:24 -0400 schrieb Scott Kostyshak : > The ctests for the Japanese LilyPond example file are failing on TeX > Live 2021 pretest. Attached is a minimal example. It compiles for me on > TeX Live 2020 but not TeX LIve 2021 pretest. Is anyone using the pretest > and can confirm it fails for you? > > Scott Same here. Error in running dvipdfmx -o ... Kornel pgpds096ZMoF1.pgp Description: Digitale Signatur von OpenPGP -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Anyone on TeX Live 2021 pretest ? (to confirm a regression for ja LilyPond)
That is the archetypical question for comp.text.tex el On 18/03/2021 04:44, Scott Kostyshak wrote: The ctests for the Japanese LilyPond example file are failing on TeX Live 2021 pretest. Attached is a minimal example. It compiles for me on TeX Live 2020 but not TeX LIve 2021 pretest. Is anyone using the pretest and can confirm it fails for you? Scott -- To email me replace 'nospam' with 'el' -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Anyone on TeX Live 2021 pretest ? (to confirm a regression for ja LilyPond)
The ctests for the Japanese LilyPond example file are failing on TeX Live 2021 pretest. Attached is a minimal example. It compiles for me on TeX Live 2020 but not TeX LIve 2021 pretest. Is anyone using the pretest and can confirm it fails for you? Scott LilyPond_Book.lyx Description: application/lyx signature.asc Description: PGP signature -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
