Bug 1744587 - reptyr-0.7.0 is available
Summary: reptyr-0.7.0 is available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: reptyr
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Francisco Javier Tsao Santín
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-22 13:51 UTC by barsnick
Modified: 2019-11-26 14:58 UTC (History)
2 users (show)

Fixed In Version: reptyr-0.7.0-1.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-26 14:58:12 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.