GNU bug report logs - #54899
Add version metadata check to Python sanity-check

Previous Next

Package: guix;

Reported by: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>

Date: Wed, 13 Apr 2022 02:17:02 UTC

Severity: normal

To reply to this bug, email your comments to 54899 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox

Report forwarded to bug-guix <at> gnu.org:
bug#54899; Package guix. (Wed, 13 Apr 2022 02:17:02 GMT) Full text and rfc822 format available.
Acknowledgement sent to Maxim Cournoyer <maxim.cournoyer <at> gmail.com>:
New bug report received and forwarded. Copy sent to bug-guix <at> gnu.org. (Wed, 13 Apr 2022 02:17:02 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
To: bug-guix <bug-guix <at> gnu.org>
Subject: Add version metadata check to Python sanity-check
Date: Tue, 12 Apr 2022 22:15:52 -0400

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
This bug report was last modified 2 years and 13 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.