Bug 2026807

Summary:	obs-build-20211125 is available
Product:	[Fedora] Fedora	Reporter:	Upstream Release Monitoring <upstream-release-monitoring>
Component:	obs-build	Assignee:	Neal Gompa <ngompa13>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	dan.cermak, ngompa13
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	obs-build-20211125-376.1.1.fc36 obs-build-20211125-376.1.1.fc35 obs-build-20211125-376.1.1.fc34	Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-11-26 07:07:47 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:

Description Upstream Release Monitoring 2021-11-25 23:16:10 UTC

Latest upstream release: 20211125
Current version/release in rawhide: 20211025-374.2.1.fc36
URL: https://github.com/openSUSE/obs-build

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/12343/

Comment 1 Upstream Release Monitoring 2021-11-25 23:16:16 UTC

An unexpected error occurred while creating the scratch build and has been automatically reported. Sorry!

Comment 2 Fedora Update System 2021-11-26 07:06:48 UTC

FEDORA-2021-ec0b49fc50 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2021-ec0b49fc50

Comment 3 Fedora Update System 2021-11-26 07:07:47 UTC

FEDORA-2021-ec0b49fc50 has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 4 Fedora Update System 2021-11-26 07:30:50 UTC

FEDORA-2021-487b6d04b1 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-487b6d04b1

Comment 5 Fedora Update System 2021-11-26 07:31:15 UTC

FEDORA-2021-d5e9ad999c has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2021-d5e9ad999c

Comment 6 Fedora Update System 2021-11-27 01:27:14 UTC

FEDORA-2021-487b6d04b1 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-487b6d04b1`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-487b6d04b1

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

Comment 7 Fedora Update System 2021-11-27 21:58:07 UTC

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

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

Comment 8 Fedora Update System 2021-12-05 01:06:29 UTC

FEDORA-2021-d5e9ad999c has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 9 Fedora Update System 2021-12-05 01:37:40 UTC

FEDORA-2021-487b6d04b1 has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.