Bug 267161 - devel/py-ipykernel 6.16.0 fails to run: No module named ipykernel_launcher
Summary: devel/py-ipykernel 6.16.0 fails to run: No module named ipykernel_launcher
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Many People
Assignee: Yuri Victorovich
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-10-17 20:06 UTC by p5B2EA84B3
Modified: 2022-10-17 23:07 UTC (History)
2 users (show)

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


Attachments
Poudriere build log (47.05 KB, text/plain)
2022-10-17 20:06 UTC, p5B2EA84B3
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description p5B2EA84B3 2022-10-17 20:06:37 UTC
Created attachment 237425 [details]
Poudriere build log

Trying to run a jupyter notebook fails:

[I 21:51:56.581 NotebookApp] Jupyter Notebook 6.4.12 is running at:
[I 21:51:56.581 NotebookApp] http://localhost:8888/
[I 21:51:56.582 NotebookApp] Use Control-C to stop this server and shut down all kernels (twice to skip confirmation).
[I 21:52:26.329 NotebookApp] Kernel started: 139bae2f-cf77-4145-9331-86bab9880f5c, name: python3
/usr/local/bin/python3.9: No module named ipykernel_launcher
[W 21:52:28.491 NotebookApp] 404 GET /nbextensions/widgets/notebook/js/extension.js?v=20221017215155 (127.0.0.1) 55.280000ms referer=None
[I 21:52:29.254 NotebookApp] KernelRestarter: restarting kernel (1/5), new random ports
/usr/local/bin/python3.9: No module named ipykernel_launcher
[I 21:52:32.490 NotebookApp] KernelRestarter: restarting kernel (2/5), new random ports
/usr/local/bin/python3.9: No module named ipykernel_launcher
[I 21:52:36.128 NotebookApp] KernelRestarter: restarting kernel (3/5), new random ports
/usr/local/bin/python3.9: No module named ipykernel_launcher
[I 21:52:39.447 NotebookApp] KernelRestarter: restarting kernel (4/5), new random ports
/usr/local/bin/python3.9: No module named ipykernel_launcher
[I 21:52:42.500 NotebookApp] KernelRestarter: restarting kernel (5/5), new random ports
/usr/local/bin/python3.9: No module named ipykernel_launcher
[W 21:52:45.559 NotebookApp] KernelRestarter: restart failed
[W 21:52:45.560 NotebookApp] Kernel 139bae2f-cf77-4145-9331-86bab9880f5c died, removing from map.
[W 21:52:49.311 NotebookApp] Replacing stale connection: 139bae2f-cf77-4145-9331-86bab9880f5c:248ee85eb94c4e619e03ad08694bec92

Searching for the missing ipykernel_launcher:
# find /usr/local/lib/python3.9/site-packages -name "ipykernel_launcher*"
finds nothing.
Searching in poudriere build log for ipykernel_launcher also results to nothing found.

See https://github.com/jupyter/notebook/issues/5738

Remark: py39-ipykernel5 worked.
Comment 1 p5B2EA84B3 2022-10-17 21:04:04 UTC
(In reply to p5B2EA84B3 from comment #0)
> Remark: py39-ipykernel5 worked.

/root/tmp/All # tar -xpv -f py39-ipykernel5-5.5.6.pkg -C / '*ipykernel_launcher.*' 
tar: Removing leading '/' from member names
x usr/local/lib/python3.9/site-packages/__pycache__/ipykernel_launcher.cpython-39.opt-1.pyc
x usr/local/lib/python3.9/site-packages/__pycache__/ipykernel_launcher.cpython-39.pyc
x usr/local/lib/python3.9/site-packages/ipykernel_launcher.py

Extracting missing ipykernel_launcher files from py39-ipykernel5-5.5.6.pkg fixed the problem here as a workaround.
Comment 2 commit-hook freebsd_committer freebsd_triage 2022-10-17 23:04:34 UTC
A commit in branch main references this bug:

URL: https://cgit.FreeBSD.org/ports/commit/?id=2477c5015da7a468251e6ec1dccbf2e18ddd172d

commit 2477c5015da7a468251e6ec1dccbf2e18ddd172d
Author:     Yuri Victorovich <yuri@FreeBSD.org>
AuthorDate: 2022-10-17 23:01:50 +0000
Commit:     Yuri Victorovich <yuri@FreeBSD.org>
CommitDate: 2022-10-17 23:03:27 +0000

    devel/py-ipykernel: Unbreak: fix bug that the launcher submodule wasn't installed

    PR:             267161
    Approved by:    portmgr (unbreak)

 devel/py-ipykernel/Makefile       | 1 +
 devel/py-ipykernel/files/setup.py | 1 +
 2 files changed, 2 insertions(+)
Comment 3 Yuri Victorovich freebsd_committer freebsd_triage 2022-10-17 23:04:57 UTC
It should be fixed now. Thanks for reporting.