Opened 6 years ago
Closed 4 years ago
#58133 closed defect (fixed)
texlive-pstricks may need an update
Reported by: | diochnos | Owned by: | drkp (Dan Ports) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.5.4 |
Keywords: | Cc: | ||
Port: | texlive-pstricks |
Description
Hi,
I bumped into this issue: https://tex.stackexchange.com/questions/469005/pstricks-newly-introduced-error-in-package
Per the suggestion, I commented
\def\ProvidesPackageRCS{\@ifnextchar[\ProvidesPackageRCS@i{\ProvidesPackageRCS@i[] }}%$
and replaced it with
\def\ProvidesPackageRCS#1{}
in the file macports_directory/share/texmf-texlive/generic/pstricks/pstricks.tex
This indeed worked for my installation. Then I went to ctan to see the contents of that file in the pstricks package (https://ctan.org/pkg/pstricks-base?lang=en) and indeed the file is different. Now, in the critical lines (around line 70), it reads:
\def\ProvidesPackageRCS#1{\typeout{Loading #1}}% %\@ifnextchar[\ProvidesPackageRCS@i{\ProvidesPackageRCS@i[] }}%$ %\def\ProvidesPackageRCS@i[#1]#2{}
Just wanted to let you know because it appears that the package needs an update. I am attaching a tex file that replicates the initial issue. Interestingly, while the error is thrown during the compilation using the latex command and compilation is paused, nevertheless, pressing enter to bypass the issue and then using dvipdf corrects a pdf file with the image as expected.
Attachments (1)
Change History (4)
Changed 6 years ago by diochnos
Attachment: | pstricks_issue.tex added |
---|
comment:1 Changed 6 years ago by mf2k (Frank Schima)
In the future, please fill in the Port field and add the port maintainer(s) to Cc (port info --maintainers texlive-pstricks
), if any.
comment:2 Changed 6 years ago by mf2k (Frank Schima)
Owner: | set to drkp |
---|---|
Port: | texlive-pstricks added |
Status: | new → assigned |
comment:3 Changed 4 years ago by drkp (Dan Ports)
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
This has been updated by now (and, based on the stackexchange thread, it may have been an issue with pgf, which is now replaced with texlive also)
TeX file replicating the issue