Thursday 22 February 2024

Re: "Essential" DEP17 /usr move in progress

On Thu, Feb 22, 2024 at 07:32:29PM +0100, Julian Andres Klode wrote:
> Hello!
>
> as some might know I was about to look into moving the Essential
> set from / to /usr (bin, sbin, lib). This is now in full steam
> or rather almost done!
>
> Today, I spent the morning identifying packages, then uploading them
> to a PPA and testing bootstrapping with debootstrap and mmdebstrap,
> as well as upgrading my noble desktop.
>
> I then uploaded all packages except for glibc and base-files.
>
> We are trying to migrate the current -proposed glibc before uploading
> the new one such that we have a 2.39 in release pocket. But it fails
> with obscure britney messages:
>
> got: 41+0: a-3:a-7:a-1:i-26:p-1:r-1:s-2
> * arm64: libdsocksd0, libnss-db, libsocksd0, libsocksd0-dev,
> * unscd, zzuf
>
>
> base-files and glibc need to migrate in the same britney run or
> debootstrap breaks; see LP#2054719 for more details:
>
> https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2054719

This issue has now been resolved, glibc has migrated, and the
new glibc and base-files have been uploaded.

beware, here be dragons.

Thank you Graham for hinting and hinting and hinting.

--
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer i speak de, en

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

"Essential" DEP17 /usr move in progress

Hello!

as some might know I was about to look into moving the Essential
set from / to /usr (bin, sbin, lib). This is now in full steam
or rather almost done!

Today, I spent the morning identifying packages, then uploading them
to a PPA and testing bootstrapping with debootstrap and mmdebstrap,
as well as upgrading my noble desktop.

I then uploaded all packages except for glibc and base-files.

We are trying to migrate the current -proposed glibc before uploading
the new one such that we have a 2.39 in release pocket. But it fails
with obscure britney messages:

got: 41+0: a-3:a-7:a-1:i-26:p-1:r-1:s-2
* arm64: libdsocksd0, libnss-db, libsocksd0, libsocksd0-dev,
* unscd, zzuf


base-files and glibc need to migrate in the same britney run or
debootstrap breaks; see LP#2054719 for more details:

https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2054719

There's an autopkgtest regression in dash that I'll sort out
tomorrow. Let me know if you see any issues!

I hope this doesn't cause many inconveniences.

I'd like to thank Helmut Grohne for his assistance. Really
most of the patches come from him in the Debian bug tracker,
and he has been helpfully answering questions.

--
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer i speak de, en

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

Ubuntu 22.04.4 LTS released

The Ubuntu team is pleased to announce the release of Ubuntu 22.04.4 LTS
(Long-Term Support) for its Desktop, Server, and Cloud products, as well
as other flavours of Ubuntu with long-term support.

As usual, this point release includes many updates and updated
installation media has been provided so that fewer updates will need to
be downloaded after installation. These include security updates and
corrections for other high-severity bugs, with a focus on maintaining
stability and compatibility with Ubuntu 22.04 LTS.

22.04.4 also includes a new arm64+largemem ISO for ARM servers which provides
a 64k page size kernel. This can increase throughput at the cost of higher
memory usage. See here for more details:

https://ubuntu.com/server/docs/choosing-between-the-arm64-and-arm64-largemem-installer-options

Kubuntu 22.04.4 LTS, Ubuntu Budgie 22.04.4 LTS, Ubuntu MATE 22.04.4 LTS,
Lubuntu 22.04.4 LTS, Ubuntu Kylin 22.04.4 LTS, Ubuntu Studio 22.04.4 LTS,
and Xubuntu 22.04.4 LTS are also now available. More details can be found
in their individual release notes (see 'Official flavours'):

https://discourse.ubuntu.com/t/jammy-jellyfish-release-notes/24668

Maintenance updates will be provided for 5 years from the initial 22.04 LTS
release for Ubuntu Desktop, Ubuntu Server, Ubuntu Cloud, and Ubuntu Core.
All the remaining flavours will be supported for 3 years. Additional security
support is available with ESM (Expanded Security Maintenance).

To get Ubuntu 22.04.4 LTS
-------------------------

In order to download Ubuntu 22.04.4 LTS, visit:

https://ubuntu.com/download

Users of Ubuntu 20.04 LTS will be offered an automatic upgrade to
22.04.4 LTS via Update Manager.

We recommend that all users read the 22.04.4 LTS release notes, which
document caveats and workarounds for known issues, as well as more
in-depth notes on the release itself. They are available at:

https://discourse.ubuntu.com/t/jammy-jellyfish-release-notes/24668

If you have a question, or if you think you may have found a bug but
aren't sure, you can try asking in any of the following places:

#ubuntu on irc.libera.chat
https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
https://ubuntuforums.org
https://askubuntu.com


Help Shape Ubuntu
-----------------

If you would like to help shape Ubuntu, take a look at the list of ways
you can participate at:

https://discourse.ubuntu.com/contribute


About Ubuntu
------------

Ubuntu is a full-featured Linux distribution for desktops, laptops,
clouds and servers, with a fast and easy installation and regular
releases. A tightly-integrated selection of excellent applications is
included, and an incredible variety of add-on software is just a few
clicks away.

Professional services including support are available from Canonical and
hundreds of other companies around the world. For more information
about support, visit:

https://ubuntu.com/support


More Information
----------------

You can learn more about Ubuntu and about this release on our website
listed below:

https://ubuntu.com/

To sign up for future Ubuntu announcements, please subscribe to Ubuntu's
very low volume announcement list at:

https://lists.ubuntu.com/mailman/listinfo/ubuntu-announce

On behalf of the Ubuntu Release Team,
Ɓukasz 'sil2100' Zemczak


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

Tuesday 20 February 2024

New Kernel Uploader

On the 15th, the Kernel Uploaders Team[1] had an ad-hoc IRC meeting with
the following people in attendence:

Team Members:
Andrea Righi (~arighi)
Andrei Gherzan (~agherzan)
Bartlomiej Zolnierkiewicz (~bzolnier)
Dimitri Ledkov (~xnox)
Emil Renner Berthing (~esmil)
Ian May (~ian-may)
John Cabaj (~john-cabaj)
Joseph Salisbury (~jsalisbury)
Kleber Sacilotto de Souza (~kleber-souza)
Manuel Diewald (~diewald)
Marcelo Cerri (~mhcerri)
Phil Cox (~philcox)
Roxana Nicolescu (~roxanan)
Stefan Bader (~smb)

Applicants:
Jacob Martin (~jacobmartin)

Observers:
Kevin Becker (~kevinbecker)

[1] https://launchpad.net/~ubuntu-kernel-uploaders

We reviewed the application[2] by Jacob Martin (~jacobmartin)[3] for
Kernel Upload Rights. After representations by the applicant and
their sponsors a vote was held as below:

Andrea Righi +1
Andrei Gherzan +1
Bartlomiej Zolnierkiewicz +1
Dimitri Ledkov +1
Emil Renner Berthing +1
Ian May +1
John Cabaj +1
Joseph Salisbury +1
Kleber Sacilotto de Souza +1
Manuel Diewald +1
Marcelo Cerri +1
Phil Cox +1
Roxana Nicolescu +1
Stefan Bader +1

The application was unanimously approved; congratulations to Jacob
Martin.

[2] https://wiki.ubuntu.com/jacobmartin/KernelUploadRightsApplication
[3] https://launchpad.net/~jacobmartin

Congratulations to all of the successful applicants. Enjoy your new
rights. Andy Whitcroft (~apw) was tasked with adding them to the
~ubuntu-kernel-uploaders team and announcing these results.

-apw (on behalf of the ~ubuntu-kernel-uploaders team)

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

Monday 19 February 2024

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

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

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
<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.


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