debcrafters-packages team mailing list archive

[Julian Andres Klode <2112491@xxxxxxxxxxxxxxxxxx>]

This should be worked around in coreutils-from 0.0.0~ubuntu10. I'm
closing that task to keep the list of coreutils-from bugs relevant to
actual remaining build failures.

** Changed in: coreutils-from (Ubuntu)
       Status: Triaged => Fix Committed

** Changed in: coreutils-from (Ubuntu)
       Status: Fix Committed => Fix Released

** Summary changed:

- mutter & gnome-shell: FTBFS with coreutils-from: pipewire stuck in an accept4 loop
+ rust-coreutils: env(1) forks, but must exec() directly

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

Title:
  rust-coreutils: env(1) forks, but must exec() directly

Status in coreutils-from package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in pipewire package in Ubuntu:
  Invalid
Status in rust-coreutils package in Ubuntu:
  Triaged

Bug description:
  Seen in the test rebuild with coreutils-from 0.0.0~ubuntu8
  https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20250530-questing-coreutils-questing.html

  but not in the reference rebuild
  https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20250530-questing-questing.html

  
  mutter 48.1-1ubuntu4 has failed multiple times with no log against coreutils-from 0.0.0~ubuntu8.
  It built successfully on first attempt in questing -release.

  I'm not sure if this link is helpful:

  https://launchpad.net/ubuntu/+archive/test-rebuild-20250530-questing-
  coreutils/+build/30875360

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils-from/+bug/2112491/+subscriptions