GNU bug report logs - #70281
Incorrect python-portend output version

Previous Next

Package: guix;

Reported by: Sergio Pastor Pérez <sergio.pastorperez <at> outlook.es>

Date: Mon, 8 Apr 2024 15:47:01 UTC

Severity: normal

To reply to this bug, email your comments to 70281 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#70281; Package guix. (Mon, 08 Apr 2024 15:47:02 GMT) Full text and rfc822 format available.
Acknowledgement sent to Sergio Pastor Pérez <sergio.pastorperez <at> outlook.es>:
New bug report received and forwarded. Copy sent to bug-guix <at> gnu.org. (Mon, 08 Apr 2024 15:47:02 GMT) Full text and rfc822 format available.

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

From: Sergio Pastor Pérez <sergio.pastorperez <at> outlook.es>
To: bug-guix <at> gnu.org
Subject: Incorrect python-portend output version
Date: Mon, 08 Apr 2024 17:41:03 +0200

Hello.

I've noticed that `python-portend' does not have a correct version
number in the output derivation. This will create failures during the
`python-build-system' `sanity-check' phase.

The following command demonstrates the issue:
--8<---------------cut here---------------start------------->8---
$ guix shell --pure grep python python-portend -- pip3 list portend | grep 'portend'
portend          0.0.0
...
--8<---------------cut here---------------end--------------->8---

Have a great day,
Sergio.
This bug report was last modified 26 days ago.

Previous Next

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