Bug 1783964 - Python 2 version incorrectly tagged as Python 3
Summary: Python 2 version incorrectly tagged as Python 3
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: texlive
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tom "spot" Callaway
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-12-16 10:48 UTC by Silas S. Brown
Modified: 2020-01-19 01:00 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-01-13 02:20:05 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Silas S. Brown 2019-12-16 10:48:08 UTC
In the package texlive-latex-papersize-7:20180414-35.fc30.noarch (installed via dnf install texlive-latex-papersize on Fedora Core 30), /usr/bin/latex-papersize is a Python 2 script incorrectly set to run under the Python 3 interpreter.  It contains "print" statements in Python 2 syntax, among other things.  Thus:

    [silasbrown@localhost ~]$ latex-papersize 
      File "/usr/bin/latex-papersize", line 156
        print __doc__.strip() ; raise SystemExit
                    ^
    SyntaxError: invalid syntax

There does now exist an upstream version which is compatible with Python 3, so the fix would be to simply get the upstream version from CTAN, or indeed from my personal website at http://ssb22.user.srcf.net/notes/latex-papersize.py

Since this is similar to what happened in bug 1748462 with the git-tools package, I can't help wondering if some good chap at Red Hat thought it was an idea to simply mark all Python 2 scripts as Python 3, across all packages, without actually converting any of them (not even with the automated 2to3 tool), without testing anything (not even checking that the script still prints its help text), and without sending any courtesy emails upstream to find out if upstream developers might be able to provide real Python 3 versions.  Are we just counting on affected users figuring out how to report bugs that random scripts have stopped working all over the distro?

Comment 1 Tom "spot" Callaway 2020-01-10 15:50:06 UTC
Apologies. I'll patch in your newer version to resolve this issue.

Comment 2 Fedora Update System 2020-01-11 01:25:16 UTC
texlive-base-20190410-7.fc31 has been pushed to the Fedora 31 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-acf8c538b5

Comment 3 Fedora Update System 2020-01-11 01:48:55 UTC
texlive-base-20180414-36.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-e86cf4559b

Comment 4 Fedora Update System 2020-01-13 02:20:05 UTC
texlive-base-20190410-7.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report.

Comment 5 Fedora Update System 2020-01-19 01:00:53 UTC
texlive-base-20180414-36.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.