All of lore.kernel.org
 help / color / mirror / Atom feed
From: Akira Yokosawa <akiyks@gmail.com>
To: "Дмитрий Дьяченко" <dimhen@gmail.com>
Cc: paulmck@kernel.org, perfbook@vger.kernel.org,
	Akira Yokosawa <akiyks@gmail.com>
Subject: Re: FYI, Second Edition Release Candidate 1 now available
Date: Thu, 31 Dec 2020 19:45:11 +0900	[thread overview]
Message-ID: <73d520b6-2686-c3b0-f9bc-07962ae1a259@gmail.com> (raw)
In-Reply-To: <f3fcbc29-c778-f882-d38e-242b9a9e75c9@gmail.com>

On Thu, 31 Dec 2020 16:22:22 +0900, Akira Yokosawa wrote:
> On Thu, 31 Dec 2020 11:05:34 +0900, Akira Yokosawa wrote:
>> On Thu, 31 Dec 2020 08:14:36 +0900, Akira Yokosawa wrote:
>>> On Wed, 30 Dec 2020 21:18:24 +0300, Дмитрий Дьяченко wrote:
>>>> Hi,
>>>>
>>>> a2ping is up to date
>>>> $ a2ping -v
>>>> a2ping.pl 2.84p, 2019-11-17
>>>> [..]
>>>>
>>>> My TexLive 2020 is not from Fedora packages but from TexArchive.
[...]
>> Switching back to TeX Live 2020 of Fedora package restored the successful build.
>>
>> This suggests something in upstream TeX Live 2020 has lost compatibility with
>> Fedora 32/33 since this September/October.
>> I have no idea what went wrong, though. Both Fedora and upstream TeX Live are
>> updated frequently, so...
> 
> Dmitry,
> 
> I have resolved a issue on my side (clash of $HOME/.texlive2020 with
> the Fedora's TeX Live) and now I see the same error as you have reported.
> 
> Now I can compare the .eps files on my own.

Dmitry,

This September saw updates in both GhostScript (9.53.0, now 9.53.3) and
pstricks-base (3.01).
It turned out this combination is the cause of the error you have encountered.

Update announcement of pstricks-base 3.01 [1] says:

    This version has a modified pstricks.tex|.pro for GhostScript versions > 9.52

However, it does not work with ghostscript 9.53.x in perfbook's use cases.

So, one workaround would be to downgrade ghostscript to 9.52 [2].

Another option would be to downgrade pstricks-base to 2.90 (2018/12/17)
(or similar [3]), which is the version in Fedora's current TeX Live package.
But note that an old version of pstricks-base might be incompatible with
the up-to-date upstream TeX Live.

It may sound strange but pstrics-base 2.90 works with ghostscript 9.53.x
as far as transparency composition is not concerned.
Perfbook's figures don't use transparency composition.

[1]: pstricks-base 3.01 update announcement on CTAN:
    https://www.ctan.org/ctan-ann/id/mailman.2839.1600699145.2548.ctan-ann@ctan.org

[2]: GhostScript release downloads:
    https://github.com/ArtifexSoftware/ghostpdl-downloads/releases

[3]: pstricks-base (as of 2019/02/27)
    https://www.texlive.info/tlnet-archive/2019/02/27/tlnet/archive/pstricks.tar.xz

GhostScript's compatibility-breaking "security" updates have caused a lot of
troubles these days...

Hopefully pstricks-base would catch up gs 9.53.x soon.

        Thanks, Akira

[...]


  reply	other threads:[~2020-12-31 10:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-30  5:37 FYI, Second Edition Release Candidate 1 now available Paul E. McKenney
2020-12-30 11:44 ` Akira Yokosawa
2020-12-30 16:13   ` Paul E. McKenney
2020-12-30 18:59     ` Paul E. McKenney
2020-12-30 23:21       ` Akira Yokosawa
2020-12-31  4:04         ` Paul E. McKenney
2020-12-31  4:43           ` Akira Yokosawa
2020-12-31 20:36             ` Paul E. McKenney
2021-01-01  1:30               ` Akira Yokosawa
2021-01-01 16:00                 ` Paul E. McKenney
2020-12-30 15:09 ` Дмитрий Дьяченко
2020-12-30 15:42   ` Akira Yokosawa
2020-12-30 18:18     ` Дмитрий Дьяченко
2020-12-30 23:14       ` Akira Yokosawa
2020-12-31  2:05         ` Akira Yokosawa
2020-12-31  7:22           ` Akira Yokosawa
2020-12-31 10:45             ` Akira Yokosawa [this message]
2020-12-31 13:51               ` Дмитрий Дьяченко

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=73d520b6-2686-c3b0-f9bc-07962ae1a259@gmail.com \
    --to=akiyks@gmail.com \
    --cc=dimhen@gmail.com \
    --cc=paulmck@kernel.org \
    --cc=perfbook@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.