[Debcrafters-packages] [Bug 2109800] Re: systemd-fsckd functionality should be in plymouth directly

2025-06-10 Thread Launchpad Bug Tracker
This bug was fixed in the package systemd - 257.6-1ubuntu1

---
systemd (257.6-1ubuntu1) questing; urgency=medium

  * Merge with Debian unstable (LP: #2112075). Remaining changes:
- debian/tests/boot-and-services: skip apparmor tests on armhf
- debian/systemd.postinst:
  + manually call systemd-tmpfiles --create in postinst
  + Do not create /etc/tmpfiles.d/tmp.conf on upgrades
- debian/control:
  + Add Recommends: networkd-dispatcher systemd-resolved to systemd package
  + Make systemd-cryptsetup Priority: important
  + Give systemd-resolved Priority: important
  + Add Recommends: systemd-hwe-hwdb to udev package
  + Drop Recommends: libnss-myhostname libnss-resolve from systemd-resolved
  + Do not build systemd-boot-efi-{amd64,arm64}-signed-template
- switch-root: use MS_MOVE for /run when switchig from initrd
- resolve,wait-online: backport wait-online DNS patches
- test-network: add handling for Ubuntu FAN patches (LP #2104943)
- d/rules: disable bpf support on riscv64 for now (LP #2099864)
- d/extra/dbus-1: remove SetLocale restriction from dbus policy (LP 
#2102028)
- d/extra/polkit-1: let root ignore inhibitors on reboot etc (LP #2092438)
- Fix d/extra/initramfs-tools/hooks/udev, so that udev rules that are
  specific to s390x ccw devices are only prevented from being copied if
  zdev_early=0 is set, but copy rules in case of zdev_early=1 or if
  zdev_early is not specified at all. (LP #2102236)
- Delta for i386:
  + debian/systemd.install: exclude files that are not built for i386
  + debian/systemd.manpages: do not ship un-built manpages on i386
  + debian/rules,debian/control,debian/tests/control:
Do not build with tpm libraries on i386
  + debian/rules,debian/control,debian/tests/control:
Do not build with libqrencode on i386
  + debian/rules: Remove unneeded efi artifacts on i386 to avoid debugedit 
errors
  * Dropped, no longer needed:
- debian/patches: drop systemd-fsckd patch (LP: #2109800, LP: #1970069)

systemd (257.6-1) unstable; urgency=medium

  [ Luca Boccassi ]
  * d/copyright: use GPL URL instead of old FSF postal address.
  * d/signing-template/copyright: use GPL URL instead of old FSF postal
address.
  * d/control: bump Standards-Version to 4.7.2, no changes
  * Add version to systemd-boot-efi-signed virtual package. Otherwise
dependency on systemd-boot-efi-signed (>= 257.5-2) is not satisfiable
(Closes: #1104663)
  * systemd-homed: add dependency on polkitd (Closes: #1105743)
  * systemd-boot: fix BOOT.CSV usage (Closes: #1106024)
  * Update upstream source from tag 'upstream/257.6' Update to upstream
version '257.6' with Debian dir
907f7fd2ae07adbab0ffd7b9235fc25435f12bab
(Fixes CVE-2025-4598)
  * Drop patches, merged upstream

  [ Tim Small ]
  * document requirement to sync *.link files with initrd (Closes:
#1005282)

  [ Kirill Rekhov ]
  * Set upstream metadata fields: Security-Contact

systemd (257.5-2) unstable; urgency=medium

  * Backport new patch to workaround /lib64 symlink incompatibility
(Closes: #1079329)

systemd (257.5-1) unstable; urgency=medium

  * Add NEWS entry to warn about network connectivity loss due to mDNS,
and workaround
  * Use Conflicts instead of Breaks/Replaces for file move (Closes:
#1101965)
  * Update upstream source from tag 'upstream/257.5' Update to upstream
version '257.5' with Debian dir
2218d137fd911b8d5c2849535b066d27f01406b2
  * Drop backports, included in 257.5
  * Remove conflicts with dracut:arm64 and build nspawn:arm64 again. A
mutually satisfactory solution for #1079329 has been agreed and is
being worked on, so temporarily reintroduce #1079329 until it's ready
in a few days as per agreement with ctte.

systemd (257.4-9) unstable; urgency=medium

  * resolved: break mDNS, remove conflict with avahi. Feedback from users
is to prefer breaking mDNS rather than avoiding avahi. Ship a drop-in
to disable mDNS by default, so that users relying on mDNS for
reachability can hopefully notice it and mask it before upgrading
(Closes: #1098914)

systemd (257.4-8) unstable; urgency=medium

  [ Luca Boccassi ]
  * systemd.preinst: do not use systemctl libsystemd-shared might not be
unpacked yet, so check things manually (Closes: #1101698)
  * systemd.preinst: fix shellcheck warnings
  * d/t/boot-and-services: skip gdm3 test in nested LXD run. It is flaky
and fails half the times, not much value in checking a desktop session
inside a nested container
  * reintroduce systemd-resolved, with conflict on avahi-daemon. It turns
out the cloud images have a hard dependency on resolved. In order to
avoid having to change them, reintroduce the package, with a hard
conflict on avahi-daemon to avoid reintroducing #1098914 (Closes:
#1101532)

  [ Yu Watanabe ]
  * d/rules: drop nscd meson option. The meson option was de

[Debcrafters-packages] [Bug 2109800] Re: systemd-fsckd functionality should be in plymouth directly

2025-06-03 Thread Daniel van Vugt
Please consider upstreaming when ready:
https://gitlab.freedesktop.org/plymouth/plymouth/-/issues/62

** Bug watch added: gitlab.freedesktop.org/plymouth/plymouth/-/issues #62
   https://gitlab.freedesktop.org/plymouth/plymouth/-/issues/62

** Also affects: plymouth via
   https://gitlab.freedesktop.org/plymouth/plymouth/-/issues/62
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of
Debcrafters packages, which is subscribed to plymouth in Ubuntu.
https://bugs.launchpad.net/bugs/2109800

Title:
  systemd-fsckd functionality should be in plymouth directly

Status in Plymouth:
  Fix Released
Status in plymouth package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Committed

Bug description:
  When systemd-fsckd was removed from upstream systemd, a small
  helper/compatibility feature was left behind. When systemd-fsck is
  running, it will connect to /run/systemd/fsck.progress, if it exists,
  and point fsck to that fd for progress updates. The systemd-fsckd patch
  in Ubuntu currently utilizes that, and then sends updates to plymouth.
  This means that we currently have a situation like this:

   systemd-fsck@dev1.service -
   ...|-> systemd-fsckd.service -> plymouthd
   systemd-fsck@devN.service -

  In other words, systemd-fsckd.service is a middleware. But, plymouthd
  could simply listen on /run/systemd/fsck.progress itself.

  There is already very similar logic for this in Ubuntu's plymouth via
  debian/patches/ubuntu-spinner-fsck.patch. Instead of carrying the
  large systemd-fsckd patch in systemd, we should consolidate the
  functionality into the existing plymouth patches.

To manage notifications about this bug go to:
https://bugs.launchpad.net/plymouth/+bug/2109800/+subscriptions


-- 
Mailing list: https://launchpad.net/~debcrafters-packages
Post to : debcrafters-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~debcrafters-packages
More help   : https://help.launchpad.net/ListHelp