Call for testing: first set of 22.04.4 images ready!
Hello everyone! On Friday last week we built our first batch of test .4 images! As always, those can be found on the respective isotracker milestone here: https://iso.qa.ubuntu.com/qatracker/milestones/451/builds There are still some images that we need to get building, but those are RISC-V related. All others should be more-or-less release-candidate worthy (we hope). Please pick up your favorite flavor and start testing! Progress of the whole milestone can be tracked on the tracking post here: https://discourse.ubuntu.com/t/jammy-jellyfish-22-04-4-lts-point-release-status-tracking/42115 Thank you! Cheers, -- Łukasz 'sil2100' Zemczak Foundations Team Tools Squad Engineering Manager lukasz.zemc...@canonical.com www.canonical.com -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
early +1 maintenance: jupyter-notebook FTBFS, jupyter-client update ahead of debian
Hi, 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. 1. https://launchpad.net/ubuntu/+source/jupyter-notebook 2. https://bugs.launchpad.net/ubuntu/+source/jupyter-notebook/+bug/2054342 3. https://launchpad.net/ubuntu/+source/jupyter-client 4. https://launchpad.net/ubuntu/+source/jupyter-client/8.6.0-0ubuntu1 -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: early +1 maintenance: jupyter-notebook FTBFS, jupyter-client update ahead of debian
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? See also https://bugs.debian.org/1059658 -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: PGP signature -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: early +1 maintenance: jupyter-notebook FTBFS, jupyter-client update ahead of debian
Hi, On Mon, Feb 19, 2024 at 5:11 PM Steve Langasek 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. 1. https://launchpad.net/~ahasenack/+archive/ubuntu/plusoneweek/+packages -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
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 wrote: > > Hi, > > On Mon, Feb 19, 2024 at 5:11 PM Steve Langasek > 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 from .asynchronous import AsyncKernelClient # noqa jupyter_client/asynchronous/__init__.py:1: in from .client import AsyncKernelClient # noqa jupyter_client/asynchronous/client.py:6: in from jupyter_client.channels import HBChannel jupyter_client/channels.py:15: in from .session import Session jupyter_client/session.py:54: in from jupyter_client.jsonutil import extract_dates jupyter_client/jsonutil.py:15: in from dateutil.parser import parse as _dateutil_parse # type: ignore /usr/lib/python3/dist-packages/dateutil/parser/__init__.py:2: in from ._parser import parse, parser, parserinfo, ParserError /usr/lib/python3/dist-packages/dateutil/parser/_parser.py:50: in from .. import tz /usr/lib/python3/dist-packages/dateutil/tz/__init__.py:2: in from .tz import * /usr/lib/python3/dist-packages/dateutil/tz/tz.py:37: in 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
Re: PSA: proposed-migration for arm64
On 09.02.24 18:51, Brian Murray wrote: Additionally, we've increased the default instance size from 1 CPU and 1536MB to 2 CPUs and 4096MB. Subsequently, the Ubuntu QA team will also be testing all the packages hinted to run on the big flavor to see if the hint is still necessary. is this just for arm64, or for all architectures? -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
