Community Packages

Please read this before reporting a bug:
http://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#67182 - [python-pillow6] [python2-pillow6] should not exist, please remove/rename back to "pillow"

Attached to Project: Community Packages
Opened by Eli Schwartz (eschwartz) - Friday, 03 July 2020, 12:30 GMT
Last edited by Eli Schwartz (eschwartz) - Sunday, 13 September 2020, 04:32 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Kyle Keen (keenerd)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Nothing needs python3 PIL version 6.x, so there really is no reason to provide an old package.

The usual way to provide old versions of a python2 package when upstream drops python2 support is to create a new PKGBUILD for e.g. python2-pillow only, and package it at the latest version.

e.g. astroid, cairo, isort, numpy, pylint, setuptools, cherrypy, pygments, pyxattr, sphinx...

NOT to create a new PKGBUILD for e.g. python2-pillow only, and package it at the latest version, but then also change the package name.

python2-pillow6 causes unnecessary confusion, and due to the lack of the "replaces" keyword, also does not get installed on users' machines, causing even greater confusion when they notice that programs depend on a package that has disappeared from the repos.
This task depends upon

Closed by  Eli Schwartz (eschwartz)
Sunday, 13 September 2020, 04:32 GMT
Reason for closing:  Fixed
Comment by loqs (loqs) - Sunday, 13 September 2020, 04:31 GMT

Loading...