Bug 1744587

Summary:	reptyr-0.7.0 is available
Product:	[Fedora] Fedora	Reporter:	barsnick
Component:	reptyr	Assignee:	Francisco Javier Tsao Santín <tsao>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	opensource, tsao
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	reptyr-0.7.0-1.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-11-26 14:58:12 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 barsnick 2019-08-22 13:51:26 UTC

Latest upstream release: 0.7.0
Current version/release in Fedora Rawhide: 0.6.2-14.fc30
URL: https://github.com/nelhage/reptyr/tags

Upstream release monitoring noticed this change, but failed to inform bugzilla. (Is anyone fixing this? I've seen dozens of missed updates.)

Comment 1 Francisco Javier Tsao Santín 2019-08-22 22:13:08 UTC

Thanks, in fact I recently saw there was a new release, and I'm working in the package upgrade.

Comment 2 Fedora Update System 2019-11-08 18:55:48 UTC

FEDORA-EPEL-2019-9a75ca995c has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-9a75ca995c

Comment 3 Fedora Update System 2019-11-10 00:16:11 UTC

reptyr-0.7.0-1.el8 has been pushed to the Fedora EPEL 8 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-9a75ca995c

Comment 4 Fedora Update System 2019-11-26 14:58:12 UTC

reptyr-0.7.0-1.el8 has been pushed to the Fedora EPEL 8 stable repository. If problems still persist, please make note of it in this bug report.