Bug 1560983 - rubygem-apipie-rails-0.5.18 is available
Summary: rubygem-apipie-rails-0.5.18 is available
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: rubygem-apipie-rails
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: 2018-03-27 12:10 UTC by Upstream Release Monitoring
Modified: 2020-08-13 09:41 UTC (History)
2 users (show)

Fixed In Version: rubygem-apipie-rails-0.5.18-1.fc34
Clone Of:
Environment:
Last Closed: 2020-08-13 09:41:28 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
[patch] Update to 0.5.17 (#1560983) (1.10 KB, patch)
2020-01-10 16:37 UTC, Upstream Release Monitoring
no flags Details | Diff
[patch] Update to 0.5.18 (#1560983) (1.10 KB, patch)
2020-05-21 14:36 UTC, Upstream Release Monitoring
no flags Details | Diff

Description Upstream Release Monitoring 2018-03-27 12:10:15 UTC
Latest upstream release: 0.5.7
Current version/release in rawhide: 0.5.5-2.fc28
URL: http://github.com/Apipie/apipie-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/4684/

Comment 1 Upstream Release Monitoring 2018-04-27 12:10:15 UTC
Latest upstream release: 0.5.8
Current version/release in rawhide: 0.5.5-2.fc28
URL: http://github.com/Apipie/apipie-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/4684/

Comment 2 Upstream Release Monitoring 2018-06-29 12:10:19 UTC
Latest upstream release: 0.5.9
Current version/release in rawhide: 0.5.5-2.fc28
URL: http://github.com/Apipie/apipie-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/4684/

Comment 3 Upstream Release Monitoring 2018-07-25 00:10:15 UTC
Latest upstream release: 0.5.10
Current version/release in rawhide: 0.5.5-3.fc29
URL: http://github.com/Apipie/apipie-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/4684/

Comment 4 Upstream Release Monitoring 2019-05-22 17:00:52 UTC
Latest upstream release: 0.5.16 Current version/release in rawhide: 0.5.5-4.fc30 URL: http://github.com/Apipie/apipie-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_monitoringPlease 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/4684/

Comment 5 Upstream Release Monitoring 2019-05-22 17:00:53 UTC
Skipping the scratch build because an SRPM could not be built: ['git', 'clone', 'https://src.fedoraproject.org/cgit/rpms/rubygem-apipie-rails.git', '/var/tmp/thn-3dcm2wwb'] returned 128: b"Cloning into '/var/tmp/thn-3dcm2wwb'...\nfatal: repository 'https://src.fedoraproject.org/cgit/rpms/rubygem-apipie-rails.git/' not found\n"

Comment 6 Upstream Release Monitoring 2020-01-10 16:37:51 UTC
Latest upstream release: 0.5.17
Current version/release in rawhide: 0.5.5-5.fc31
URL: http://github.com/Apipie/apipie-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/4684/

Comment 7 Upstream Release Monitoring 2020-01-10 16:37:54 UTC
Created attachment 1651339 [details]
[patch] Update to 0.5.17 (#1560983)

Comment 8 Upstream Release Monitoring 2020-01-10 16:39:32 UTC
the-new-hotness/release-monitoring.org's scratch build of rubygem-apipie-rails-0.5.17-1.fc29.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=40374665

Comment 9 Upstream Release Monitoring 2020-05-21 14:36:27 UTC
Latest upstream release: 0.5.18
Current version/release in rawhide: 0.5.5-6.fc32
URL: http://github.com/Apipie/apipie-rails

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/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/4684/

Comment 10 Upstream Release Monitoring 2020-05-21 14:36:30 UTC
Created attachment 1690665 [details]
[patch] Update to 0.5.18 (#1560983)

Comment 11 Upstream Release Monitoring 2020-05-21 14:39:53 UTC
the-new-hotness/release-monitoring.org's scratch build of rubygem-apipie-rails-0.5.18-1.fc30.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=44773416


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