Bug 253117 - devel/py-anyio package incorrectly has 0.0.0 version number in PKG-INFO and directory name
Summary: devel/py-anyio package incorrectly has 0.0.0 version number in PKG-INFO and d...
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: arm64 Any
: --- Affects Some People
Assignee: Sunpoet Po-Chuan Hsieh
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-01-31 10:52 UTC by Robert Watson
Modified: 2021-03-03 18:39 UTC (History)
1 user (show)

See Also:
linimon: maintainer-feedback? (sunpoet)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Watson freebsd_committer 2021-01-31 10:52:13 UTC
On FreeBSD/arm64, running FreeBSD 13-ALPHA today:

root@raspberry-pi:~/cambridge-l41-aos-labs/2020-2021/Laboratories # pkg fetch py37-anyio
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
The following packages will be fetched:

New packages to be FETCHED:
	py37-anyio: 2.0.2 (93 KiB: 100.00% of the 93 KiB to download)

Number of packages to be fetched: 1

93 KiB to be downloaded.

Proceed with fetching packages? [y/N]: y
Fetching py37-anyio-2.0.2.txz: 100%   93 KiB  95.2kB/s    00:01    


But when I install, I get an incorrect directory name and PKG-INFO contents, showing a version of 0.0.0:

/usr/local/share/licenses/py37-anyio-2.0.2/catalog.mk
/usr/local/share/licenses/py37-anyio-2.0.2/LICENSE
/usr/local/share/licenses/py37-anyio-2.0.2/MIT
/usr/local/lib/python3.7/site-packages/anyio-0.0.0-py3.7.egg-info/PKG-INFO
/usr/local/lib/python3.7/site-packages/anyio-0.0.0-py3.7.egg-info/SOURCES.txt
/usr/local/lib/python3.7/site-packages/anyio-0.0.0-py3.7.egg-info/dependency_links.txt
/usr/local/lib/python3.7/site-packages/anyio-0.0.0-py3.7.egg-info/entry_points.txt
/usr/local/lib/python3.7/site-packages/anyio-0.0.0-py3.7.egg-info/not-zip-safe
/usr/local/lib/python3.7/site-packages/anyio-0.0.0-py3.7.egg-info/requires.txt
/usr/local/lib/python3.7/site-packages/anyio-0.0.0-py3.7.egg-info/top_level.txt


If I hand rename the directory in /usr/local/lib, and edit PKG-INFO to say 2.0.2, then it works. When I look in a ports build locally, I see that the downloaded distfile contains 2.0.2, but that the staging directory has 0.0.0 as above.

I'm afraid I don't understand the Python build/etc infrastructure, so can't debug this further easily.

This is an essential dependency for jupyter-lab, and without it, you cannot start jupyter-lab, making the dependent jupyter-lab package unusable.
Comment 1 commit-hook freebsd_committer 2021-02-01 19:47:51 UTC
A commit references this bug:

Author: sunpoet
Date: Mon Feb  1 19:47:21 UTC 2021
New revision: 563750
URL: https://svnweb.freebsd.org/changeset/ports/563750

Log:
  Fix version

  - Bump PORTREVISION for package change

  PR:		253117
  Reported by:	rwatson

Changes:
  head/devel/py-anyio/Makefile
  head/devel/py-anyio/files/
  head/devel/py-anyio/files/patch-setup.cfg
Comment 2 Sunpoet Po-Chuan Hsieh freebsd_committer 2021-02-01 19:53:33 UTC
(In reply to Robert Watson from comment #0)

I've checked the new package has correct version. Could you please confirm if it works for you? Thanks!
Comment 3 Robert Watson freebsd_committer 2021-02-04 12:48:31 UTC
It does. I'm having continuing issues with the Jupyterlabs port/package, however. The recent spate of upgrades seems to have left Matplotlib dysfunctional for me (possibly a local issue?). I noticed that py37-ipympl is not a run-time dependency of the Jupyterlabs ports, however, and I wonder if it should be.
Comment 4 Robert Watson freebsd_committer 2021-02-04 13:04:30 UTC
It appears that npm (or maybe just node) should also be a dependency of jupyterlab?

Once I install that, and ipympl, I then get:

[W 2021-02-04 05:08:52.157 LabApp] Build recommended
[W 2021-02-04 05:08:52.157 LabApp] jupyter-matplotlib needs to be included in build

It seems like there's a fairly severe regression with respect to Jupyterlab in the past couple of weeks -- it used to "just work", use Matplotlib, etc. Now key ports have been utterly broken (anyio), and so on.  Do basic jupyterlab notebooks using Matplotlib work for you currently?
Comment 5 commit-hook freebsd_committer 2021-03-03 18:10:19 UTC
A commit references this bug:

Author: sunpoet
Date: Wed Mar  3 18:08:39 UTC 2021
New revision: 567135
URL: https://svnweb.freebsd.org/changeset/ports/567135

Log:
  Revert r563750 and fix it in a better way

  PR:		253117

Changes:
  head/devel/py-anyio/Makefile
  head/devel/py-anyio/files/
Comment 6 Sunpoet Po-Chuan Hsieh freebsd_committer 2021-03-03 18:39:54 UTC
I tested anyio 2.0.2 on the box with setuptools-scm is installed, therefore I got the correct version (not anyio-0.0.0).