Bug 916557 - vifm-0.7.5 is available
Summary: vifm-0.7.5 is available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: vifm
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ben Boeckel
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-28 10:14 UTC by Upstream Release Monitoring
Modified: 2013-06-09 03:28 UTC (History)
1 user (show)

Fixed In Version: vifm-0.7.5-1.fc19
Clone Of:
Environment:
Last Closed: 2013-05-31 02:38:04 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Upstream Release Monitoring 2013-02-28 10:14:44 UTC 
Latest upstream release: 0.7.4b
Current version in Fedora Rawhide: 0.7.4a
URL: http://sourceforge.net/api/file/index/project-name/vifm/mtime/desc/limit/100/rss

Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy

More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring
Comment 1 Upstream Release Monitoring 2013-05-13 08:39:33 UTC 
Latest upstream release: 0.7.5
Current version in Fedora Rawhide: 0.7.4a
URL: http://sourceforge.net/api/file/index/project-name/vifm/mtime/desc/limit/100/rss

Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy

More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring
Comment 2 Fedora Update System 2013-05-31 02:57:31 UTC 
vifm-0.7.5-1.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/vifm-0.7.5-1.fc19
Comment 3 Fedora Update System 2013-06-09 03:28:30 UTC 
vifm-0.7.5-1.fc19 has been pushed to the Fedora 19 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.