I have verified that systemd-repart is available in jammy-proposed, and
that the upgrade path to kinetic works as expected:
root@jammy:~# apt-cache policy systemd-repart
systemd-repart:
Installed: 249.11-0ubuntu3.6
Candidate: 249.11-0ubuntu3.6
Version table:
*** 249.11-0ubuntu3.6 500
500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages
100 /var/lib/dpkg/status
root@jammy:~# do-release-upgrade -d
[ upgrade... ]
[ reboot... ]
root@jammy:~# lsb_release -cs
kinetic
root@jammy:~# apt-cache policy systemd-repart
systemd-repart:
Installed: (none)
Candidate: (none)
Version table:
root@jammy:~# apt-cache policy systemd
systemd:
Installed: 251.4-1ubuntu4
Candidate: 251.4-1ubuntu4
Version table:
*** 251.4-1ubuntu4 500
500 http://archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
100 /var/lib/dpkg/status
root@jammy:~# dpkg -S /bin/systemd-repart
systemd: /bin/systemd-repart
** Tags removed: rls-jj-incoming verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1897932
Title:
systemd-repart not packaged
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Jammy:
Fix Committed
Status in systemd package in Debian:
Fix Released
Bug description:
[Impact]
systemd-repart is not (as of 246.6-1ubuntu1) packaged in the
Ubuntu/Debian packages of systemd - probably because it has an extra
dependency?
The bug reporter would like to use it in their new raspberry pi images
where they don't have cloud-init installed. The reporter is already
using systemd-growfs, but they are missing the nice partition resizing
part (so are using cloud-initramfs-growroot).
Furthermore, in the mkosi image builder
(https://github.com/systemd/mkosi), the systemd/mkosi developers would
like to start using systemd-repart for partitioning. Unfortunately,
they're currently blocked on this because 22.04 doesn't ship systemd-
repart. The upstream CI uses Github Actions which runs on Ubuntu Jammy
and will do so until the next Ubuntu LTS is released. If we have to
wait for the next LTS to be released, we'll have to wait for a
considerable amount of time before we're able to start using systemd-
repart.
Being able to use systemd-repart will allow the systemd/mkosi developers to
take advantage of its improved interface compared to sfdisk,
as well as its builtin protections against race conditions surrounding the
use of loop devices. The systemd/mkosi developers expect to
be able to get rid of some nasty loop device failure in mkosi by using
systemd-repart.
[Test Plan]
This is a missing extra executable. Once enabled it has self-tests in the
build-time unit tests, and also a regression test in the autopkgtest 'upstream'
suite.
* Attach (local) build-log showing the systemd-repart self-tests passing, as
found in build-deb/meson-logs/testlog.txt
* Attach autopkgtest logs showing the regression tests passing (especially
TEST-58-REPART from "upstream-2" testsuite)
* Test upgrade-path Jammy->Kinetic to make sure systemd-repart is properly
replaced by Kinetic's "systemd" binary package
[Where problems could occur]
Shipping systemd-repart will come with no additional risk. While there is a
systemd-repart.service that runs on boot, it's configured to not do anything if
no config files are shipped with the system or provided by the user. As such,
the service, if enabled, will effectively be a noop. Aside from the service,
there's the CLI tool systemd-repart and the accompanying man pages that will be
shipped as part of the systemd package.
Given that there's no risk involved with enabling systemd-repart, and
given the useful features it provides, the systemd/mkosi developers
would like to request that systemd-repart be enabled in Ubuntu and
backported to Jammy so that they can start adopting it in mkosi.
Runtime behavior of existing components is not affected by the build
config change.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1897932/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
