FS#65474 - [python-zipp] The built package uses version 0.0.0 in its metadata (despite building 2.0.0).

Attached to Project: Community Packages
Opened by Sean (GenuineXP) - Wednesday, 12 February 2020, 23:39 GMT
Last edited by Chih-Hsuan Yen (yan12125) - Thursday, 13 February 2020, 02:12 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Felix Yan (felixonmars)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
When installing the python-zipp at 2.0.0-1, the installed package at /usr/lib/python3.8/site-packages has version 0.0.0 in its metadata (its directory name and PKG-INFO file). This may be related to these issues on GitHub:

https://github.com/jaraco/zipp/issues/31
https://github.com/jaraco/configparser/issues/45

It seems that after a migration to setuptools_scm, some care must be taken when building packages to avoid version 0.0.0 being used in the build artifacts.

Additional info:
* package version(s): 2.0.0-1

Steps to reproduce:
Transitively install python-zipp and run a Python executable that depends on it with a non-trivial version spec. For example, the home-assistant package transitively requires python-zipp, but will fail to find a suitable version as specified in the package configuration.
This task depends upon

Closed by  Chih-Hsuan Yen (yan12125)
Thursday, 13 February 2020, 02:12 GMT
Reason for closing:  Duplicate
Additional comments about closing:  Thanks for the report. This is basically the same as https://bugs.archlinux.org/task/65348. Please follow updates there.

Loading...