Bug 2271623

Summary:	rebuild F40 pipewire
Product:	[Fedora] Fedora	Reporter:	Germano Massullo <germano.massullo>
Component:	pipewire	Assignee:	Wim Taymans <wtaymans>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	40	CC:	brunovern.a, information, wtaymans
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	pipewire-1.0.4-2.fc40	Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-03-29 00:19:38 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Germano Massullo 2024-03-26 15:02:32 UTC

Fedora 39 and 42 have version pipewire-1.0.4-2, but Fedora 40 has an older pipewire-1.0.4-1

According to changelog [1], this is the difference
- Configure server, client and rlimit priorities to be the same as JACK.

[1]: https://src.fedoraproject.org/rpms/pipewire/blob/rawhide/f/pipewire.spec#_832

Comment 1 Fedora Update System 2024-03-27 15:07:22 UTC

FEDORA-2024-5ae64512a0 (pipewire-1.0.4-2.fc40) has been submitted as an update to Fedora 40.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-5ae64512a0

Comment 2 Fedora Update System 2024-03-28 02:18:56 UTC

FEDORA-2024-5ae64512a0 has been pushed to the Fedora 40 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-5ae64512a0`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-5ae64512a0

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 3 Fedora Update System 2024-03-29 00:19:38 UTC

FEDORA-2024-5ae64512a0 (pipewire-1.0.4-2.fc40) has been pushed to the Fedora 40 stable repository.
If problem still persists, please make note of it in this bug report.