Bug 1967528

Summary: pipewire-0.3.29 is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: pipewireAssignee: Wim Taymans <wtaymans>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: brunovern.a, joepesco2020, wtaymans
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: pipewire-0.3.32-1.fc34 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-07-22 01:14:09 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
[patch] Update to 0.3.29 (#1967528) none

Description Upstream Release Monitoring 2021-06-03 10:15:37 UTC 
Latest upstream release: 0.3.29
Current version/release in rawhide: 0.3.28-1.fc35
URL: https://pipewire.org

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from anitya: https://release-monitoring.org/project/57357/
Comment 1 Upstream Release Monitoring 2021-06-03 10:15:42 UTC 
One or more of the new sources for this package are identical to the old sources. This is most likely caused either by identical source files between releases, for example service files, or the specfile does not use version macro in its source URLs. If this is the second case, then please update the specfile to use version macro in its source URLs.
Comment 2 Upstream Release Monitoring 2021-06-03 10:15:45 UTC 
Created attachment 1788823 [details]
[patch] Update to 0.3.29 (#1967528)
Comment 3 Upstream Release Monitoring 2021-06-03 10:25:15 UTC 
the-new-hotness/release-monitoring.org's scratch build of pipewire-0.3.29-1.fc32.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=69226159
Comment 4 Fedora Update System 2021-06-03 10:34:59 UTC 
FEDORA-2021-4bd6fdd9d3 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-4bd6fdd9d3
Comment 5 Fedora Update System 2021-06-04 01:18:46 UTC 
FEDORA-2021-4bd6fdd9d3 has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-4bd6fdd9d3`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-4bd6fdd9d3

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 6 Fedora Update System 2021-07-20 14:38:57 UTC 
FEDORA-2021-f3a65aee6b has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-f3a65aee6b
Comment 7 Fedora Update System 2021-07-21 01:54:38 UTC 
FEDORA-2021-f3a65aee6b has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-f3a65aee6b`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-f3a65aee6b

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 8 Fedora Update System 2021-07-22 01:14:09 UTC 
FEDORA-2021-f3a65aee6b has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.