This bug was fixed in the package systemd - 249.11-0ubuntu3.6
---
systemd (249.11-0ubuntu3.6) jammy; urgency=medium
* Deny-list TEST-58-REPART on ppc64el (LP: #1988994)
File: debian/patches/lp1988994-Deny-list-TEST-58-REPART-on-ppc64el.patch
https://git.launchpad.net/~ubunt
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
Hello Iain, or anyone else affected,
Accepted systemd into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/249.11-0ubuntu3.5 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://w
After the discussion on the mailing list (ubuntu-devel@) has settled, and
@bluca provided an updated MP#427557 to ship systemd-repart as an additional
binary package in Jammy (universe, not installed by default), I've moved ahead
and staged the changes to provide an upgrade path (removal of syst
** Description changed:
[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 i
** Description changed:
[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 i
** Description changed:
[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 i
> In addition to that though, I notice that mkosi in Jammy does refer to
/usr/bin/systemd-repart. Will the Jammy packaged mkosi therefore change
behaviour if you start shipping it in Ubuntu?
Those references are for the dracut configuration, i.e. to get those
files from the target image to the tar
There's further discussion in the ubuntu-devel ML thread.
In addition to that though, I notice that mkosi in Jammy does refer to
/usr/bin/systemd-repart. Will the Jammy packaged mkosi therefore change
behaviour if you start shipping it in Ubuntu?
--
You received this bug notification because you
We got some response from the SRU team (@racb):
https://lists.ubuntu.com/archives/ubuntu-devel/2022-August/042250.html
Basically he suggests doing this change in a PPA/jammy-backports, or as
a entirely new package:
* "what if you were to put systemd-repart as a new package into a PPA, or into
j
** Merge proposal linked:
https://code.launchpad.net/~bluca/ubuntu/+source/systemd/+git/systemd/+merge/427557
--
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
Titl
** Description changed:
[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 i
** Tags added: rls-jj-incoming
--
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 Releas
** Description changed:
[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 our new raspberry pi images
+ The bug reporter would like to use i
debdiff enabling systemd repart in the jammy/devel branch
** Patch added: "systemd_repart.debdiff"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1897932/+attachment/5605761/+files/systemd_repart.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch s
The upstream systemd developers team would like to request to enable
systemd-repart in Jammy in the next proposed-updates. MR:
https://code.launchpad.net/~bluca/ubuntu/+source/systemd/+git/systemd/+merge/427557
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
I was asked to add a Jammy task, I did so - the details and if that will
be done is up to your consideration/discussion/decision.
--
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/bu
** Changed in: systemd (Ubuntu)
Status: Triaged => Fix Released
** Changed in: systemd (Ubuntu Jammy)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.laun
** Also affects: systemd (Ubuntu Jammy)
Importance: Undecided
Status: New
--
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 packag
** Description changed:
+ [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?
- I'd like to use it in our new raspberry pi images where we don't have
- cloud-init installed. We're already
Any chance it could be enabled now that Jammy shipped? It's really fine
to enable it in 249 for 20.10, there's really no reason to wait for a
new version
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https
This was enabled in Debian's systemd v250.1-2
https://salsa.debian.org/systemd-team/systemd/-/commit/4a93ec2f56969e11c73ef346a342e7e552faae75
We're shipping the more stable systemd v249 in Ubuntu Jammy LTS, and are
already post feature freeze, so we cannot enable new features anymore.
This will m
** Changed in: systemd (Debian)
Status: New => Fix Released
--
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 sys
** Changed in: systemd (Debian)
Status: Unknown => New
--
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
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
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.n
** Bug watch added: Debian Bug tracker #976959
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976959
** Also affects: systemd (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976959
Importance: Unknown
Status: Unknown
--
You received this bug notification because
26 matches
Mail list logo
