This bug was fixed in the package systemd - 257.3-1ubuntu3

---------------
systemd (257.3-1ubuntu3) plucky; urgency=medium

  * d/control: remove other bpf deps for riscv64

systemd (257.3-1ubuntu2) plucky; urgency=medium

  * d/t/tests-in-lxd: skip test on any setup error
  * d/rules: disable bpf support on riscv64 for now (LP: #2099864)

systemd (257.3-1ubuntu1) plucky; urgency=medium

  * Merge with Debian unstable. 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
      + Build-Depends: linux-tools-generic
      + 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
    - initramfs-tools: copy hwdb.bin to initramfs
    - d/rules: fix bpftool path discovery on ubuntu
    - 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

systemd (257.3-1) unstable; urgency=medium

  * d/t/control: do not pull in gdm3 on loong64. Not installable, skip it
    like s390x/riscv/armel
  * systemd-boot: warn if efibootmgr is not installed. As it means the
    boot entry won't be created, since it's a recommends
  * systemd-boot: fix creating bootvar on arm64
  * systemd-boot: check that bootvar really points to sd-boot. Otherwise
    it could be a leftover with another second stage. Check both encoded
    and decoded strings.
  * Drop fallback for missing linux-bpf-dev package
  * ukify: depend on python3-zstandard and recommend python3-lz4 arm64
    kernels are getting zboot+zstd so zstandard will be required for uname
    probing. lz4 might be used externally so just recommend it.
  * Update upstream source from tag 'upstream/257.3' Update to upstream
    version '257.3' with Debian dir
    1531e0bcaea1d2bf600be6d542bae876d1829da9
  * autopkgtest: fix mkosi config section

 -- Nick Rosbrook <en...@ubuntu.com>  Mon, 24 Feb 2025 10:36:52 -0500

** Changed in: systemd (Ubuntu)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2099864

Title:
  [p-m] depwait on riscv64 due to missing linux-bpf-dev in Ubuntu

Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  It seems as if Ubuntu doesn't build this package on riscv64:
  https://packages.ubuntu.com/plucky/linux-bpf-dev

  This discrepancy is causing systemd to FTBFS due to depwait in plucky-
  proposed, blocking migration.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2099864/+subscriptions


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

Reply via email to