Monday, 19 February 2024

Re: early +1 maintenance: jupyter-notebook FTBFS, jupyter-client update ahead of debian

Hi,

On Mon, Feb 19, 2024 at 5:30 PM Andreas Hasenack <andreas@canonical.com> wrote:
>
> Hi,
>
> On Mon, Feb 19, 2024 at 5:11 PM Steve Langasek
> <steve.langasek@ubuntu.com> wrote:
> >
> > Hi Andreas,
> >
> > On Mon, Feb 19, 2024 at 05:05:00PM -0300, Andreas Hasenack wrote:
> > > I started working on my +1 maintenance shift with the goal of
> > > trailblazing the python 3.12 migration. A few packages sorted already,
> > > but jupyter-notebook has me stumped, and I thought I would share this
> > > now instead of at the end of the shift.
> >
> > > src:jupyter-notebook[1] is FTBFS[2] due to a test failure in
> > > noble-proposed with src:jupyter-client[3] >= 8. I filed a bug[2] with
> > > my findings.
> >
> > > Upstream and other projects I could find all seem to have settled on
> > > pinning jupyter-client to a version < 8. And indeed, if we build
> > > jupyter-notebook with jupyter-client from noble
> > > release (version 7.4.9-2, same as in debian), then it succeeds.
> >
> > > I don't know why jupyter-client was updated to 8.6.0[4] ahead of
> > > debian. So far, I have exhausted my troubleshooting on this issue. I
> > > suppose we could remove src:jupyter-client 8.6.0-0ubuntu1 from
> > > noble-proposed, as that could help with the python3 migration.
> >
> > Given the uploader and the timing, I suspect this was done to get
> > jupyter-client itself to be sorted for the python3.12 transition.
> >
> > Can you verify that the previous version of the package in Ubuntu builds in
> > noble?
>
> Both locally and in a ppa with noble-proposed enabled[1],
> jupyter-client 7.4.9-2 built, but build-time tests are disabled in
> this package.
>
> > See also https://bugs.debian.org/1059658
>
> I'll try a dep8 run, see what happens with today's archive.

These tests fail with the same error as reported in the bug, with python 3.12:

Testing with python3.12:
/usr/lib/python3/dist-packages/_pytest/config/__init__.py:331:
PluggyTeardownRaisedWarning: A plugin raised an exception during an
old-style hookwrapper teardown.
Plugin: helpconfig, Hook: pytest_cmdline_parse
ConftestImportFailure: DeprecationWarning:
datetime.datetime.utcfromtimestamp() is deprecated and scheduled for
removal in a future version. Use timezone-aware objects to represent
datetimes in UTC: datetime.datetime.fromtimestamp(timestamp,
datetime.UTC). (from
/tmp/autopkgtest.BaOJPJ/build.m7g/real-tree/jupyter_client/tests/conftest.py)
For more information see
https://pluggy.readthedocs.io/en/stable/api_reference.html#pluggy.PluggyTeardownRaisedWarning
config = pluginmanager.hook.pytest_cmdline_parse(
ImportError while loading conftest
'/tmp/autopkgtest.BaOJPJ/build.m7g/real-tree/jupyter_client/tests/conftest.py'.
jupyter_client/__init__.py:8: in <module>
from .asynchronous import AsyncKernelClient # noqa
jupyter_client/asynchronous/__init__.py:1: in <module>
from .client import AsyncKernelClient # noqa
jupyter_client/asynchronous/client.py:6: in <module>
from jupyter_client.channels import HBChannel
jupyter_client/channels.py:15: in <module>
from .session import Session
jupyter_client/session.py:54: in <module>
from jupyter_client.jsonutil import extract_dates
jupyter_client/jsonutil.py:15: in <module>
from dateutil.parser import parse as _dateutil_parse # type: ignore
/usr/lib/python3/dist-packages/dateutil/parser/__init__.py:2: in <module>
from ._parser import parse, parser, parserinfo, ParserError
/usr/lib/python3/dist-packages/dateutil/parser/_parser.py:50: in <module>
from .. import tz
/usr/lib/python3/dist-packages/dateutil/tz/__init__.py:2: in <module>
from .tz import *
/usr/lib/python3/dist-packages/dateutil/tz/tz.py:37: in <module>
EPOCH = datetime.datetime.utcfromtimestamp(0)
E DeprecationWarning: datetime.datetime.utcfromtimestamp() is
deprecated and scheduled for removal in a future version. Use
timezone-aware objects to represent datetimes in UTC:
datetime.datetime.fromtimestamp(timestamp, datetime.UTC).
autopkgtest [17:49:30]: test command1: -----------------------]

Maybe that's easier to fix than the jupyter-notebook failure?

--
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel