Bug 1253909 - rubygem-compass-rails-3.1.0 is available
Summary: rubygem-compass-rails-3.1.0 is available
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: rubygem-compass-rails
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Troy Dawson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-15 12:11 UTC by Upstream Release Monitoring
Modified: 2018-04-28 00:10 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:


Attachments (Terms of Use)
[patch] Update to 3.0.0 (#1253909) (1.02 KB, patch)
2016-01-23 12:11 UTC, Upstream Release Monitoring
no flags Details | Diff
[patch] Update to 3.0.1 (#1253909) (1.17 KB, patch)
2016-02-16 00:11 UTC, Upstream Release Monitoring
no flags Details | Diff
[patch] Update to 3.0.2 (#1253909) (1.17 KB, patch)
2016-03-03 12:12 UTC, Upstream Release Monitoring
no flags Details | Diff

Description Upstream Release Monitoring 2015-08-15 12:11:30 UTC
Latest upstream release: 2.0.5
Current version/release in rawhide: 2.0.4-1.fc24
URL: http://rubygems.org/gems/compass-rails

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

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.

Comment 1 Upstream Release Monitoring 2015-08-15 12:11:37 UTC
Failed to kick off scratch build.

cmd:  sha256sum /var/tmp/thn-FCowbV/100.0%
return code:  1
stdout:

stderr:
sha256sum: /var/tmp/thn-FCowbV/100.0%: No such file or directory

Comment 2 Upstream Release Monitoring 2016-01-23 12:11:43 UTC
Latest upstream release: 3.0.0
Current version/release in rawhide: 2.0.4-1.fc24
URL: http://rubygems.org/gems/compass-rails

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

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.

Comment 3 Upstream Release Monitoring 2016-01-23 12:11:54 UTC
Created attachment 1117445 [details]
[patch] Update to 3.0.0 (#1253909)

Comment 4 Upstream Release Monitoring 2016-01-23 12:13:58 UTC
Scratch build completed http://koji.fedoraproject.org/koji/taskinfo?taskID=12662399

Comment 5 Upstream Release Monitoring 2016-02-16 00:11:27 UTC
Latest upstream release: 3.0.1
Current version/release in rawhide: 2.0.4-2.fc24
URL: http://rubygems.org/gems/compass-rails

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

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.

Comment 6 Upstream Release Monitoring 2016-02-16 00:11:36 UTC
Created attachment 1127465 [details]
[patch] Update to 3.0.1 (#1253909)

Comment 7 Upstream Release Monitoring 2016-02-16 00:14:54 UTC
Scratch build completed http://koji.fedoraproject.org/koji/taskinfo?taskID=13000038

Comment 8 Upstream Release Monitoring 2016-03-03 12:12:11 UTC
Latest upstream release: 3.0.2
Current version/release in rawhide: 2.0.4-2.fc24
URL: http://rubygems.org/gems/compass-rails

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

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.

Comment 9 Upstream Release Monitoring 2016-03-03 12:12:20 UTC
Created attachment 1132740 [details]
[patch] Update to 3.0.2 (#1253909)

Comment 10 Upstream Release Monitoring 2016-03-03 12:14:33 UTC
Scratch build completed http://koji.fedoraproject.org/koji/taskinfo?taskID=13213137

Comment 11 Upstream Release Monitoring 2018-04-28 00:10:17 UTC
Latest upstream release: 3.1.0
Current version/release in rawhide: 2.0.4-5.fc28
URL: http://rubygems.org/gems/compass-rails

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

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


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