Add version metadata check to Python sanity-check

  • Open
  • quality assurance status badge
Details
One participant
  • Maxim Cournoyer
Owner
unassigned
Submitted by
Maxim Cournoyer
Severity
normal
M
M
Maxim Cournoyer wrote on 13 Apr 2022 04:15
(name . bug-guix)(address . bug-guix@gnu.org)
87y209wwx3.fsf@gmail.com
Hello Guix,

Many Python packages rely on third party packages such as
python-setuptools-scm or python-versioneer to compute the version string
used as part of the packaging.

When these tools are missing, the version string ends up being '0.0.0'
in the resulting PKG-INFO package metadata file, which is wrong and
breaks Python build systems dependency verification.

This issue is about adding a check to our already existing sanity-check
phase/script so that it ensure the version string in the built package
metadata is not 0.0.0 (unless defined as such at the level of the Guix
package).

Thanks,

Maxim
?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 54899@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 54899
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch