Bug 1955841

Summary:	R-R.cache-0.15.0 is available
Product:	[Fedora] Fedora	Reporter:	Upstream Release Monitoring <upstream-release-monitoring>
Component:	R-R.cache	Assignee:	Elliott Sales de Andrade <quantum.analyst>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	quantum.analyst
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	R-R.cache-0.15.0-1.fc35 R-R.cache-0.15.0-2.fc34 R-R.cache-0.15.0-2.fc33	Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-06-17 23:12:54 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-05-01 00:09:45 UTC

Latest upstream release: 0.15.0
Current version/release in rawhide: 0.14.0-5.fc34
URL: https://github.com/HenrikBengtsson/R.cache

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

Comment 1 Upstream Release Monitoring 2021-05-01 00:09:48 UTC

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

Comment 2 Fedora Update System 2021-06-17 23:12:54 UTC

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

Comment 3 Fedora Update System 2021-06-17 23:15:53 UTC

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

Comment 4 Fedora Update System 2021-09-19 03:06:29 UTC

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

Comment 5 Fedora Update System 2021-09-19 03:06:30 UTC

FEDORA-2021-6cc05bad0b has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-6cc05bad0b

Comment 6 Fedora Update System 2021-09-19 05:42:44 UTC

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

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

Comment 7 Fedora Update System 2021-09-19 05:50:09 UTC

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

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

Comment 8 Fedora Update System 2021-09-27 01:22:51 UTC

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

Comment 9 Fedora Update System 2021-09-27 01:25:07 UTC

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