Bug 781429 - rubygem-fssm-0.2.10 is available
Summary: rubygem-fssm-0.2.10 is available
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: rubygem-fssm
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Vít Ondruch
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-13 11:59 UTC by Upstream Release Monitoring
Modified: 2014-03-31 14:35 UTC (History)
1 user (show)

Fixed In Version: rubygem-fssm-0.2.10-1.fc21
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-03-31 14:35:28 UTC
Type: ---


Attachments (Terms of Use)

Description Upstream Release Monitoring 2012-01-13 11:59:37 UTC
Latest upstream release: 0.2.8.1
Current version in Fedora Rawhide: 0.2.7
URL: http://rubygems.org/api/v1/gems/fssm.json

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 2012-04-10 10:56:08 UTC
Latest upstream release: 0.2.9
Current version in Fedora Rawhide: 0.2.7
URL: http://rubygems.org/api/v1/gems/fssm.json

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 Upstream Release Monitoring 2013-01-27 15:34:17 UTC
Latest upstream release: 0.2.10
Current version in Fedora Rawhide: 0.2.7
URL: http://rubygems.org/api/v1/gems/fssm.json

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


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