Bug 1309667 - nodejs-is-my-json-valid-2.20.5 is available
Summary: nodejs-is-my-json-valid-2.20.5 is available
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: nodejs-is-my-json-valid
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Orphan Owner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-18 12:13 UTC by Upstream Release Monitoring
Modified: 2020-08-18 16:18 UTC (History)
0 users

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-08-18 16:18:23 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Rebase-helper rebase-helper-debug.log log file. See for details and report the eventual error to rebase-helper https://github.com/phracek/rebase-helper/issues. (16.38 KB, patch)
2016-09-20 00:21 UTC, Upstream Release Monitoring
no flags Details | Diff
Rebase-helper rebase-helper-debug.log log file. See for details and report the eventual error to rebase-helper https://github.com/phracek/rebase-helper/issues. (15.22 KB, patch)
2016-10-03 00:18 UTC, Upstream Release Monitoring
no flags Details | Diff
[patch] Update to 2.20.1 (#1309667) (1.08 KB, patch)
2020-06-26 14:34 UTC, Upstream Release Monitoring
no flags Details | Diff
[patch] Update to 2.20.2 (#1309667) (1.08 KB, patch)
2020-06-29 09:46 UTC, Upstream Release Monitoring
no flags Details | Diff
[patch] Update to 2.20.4 (#1309667) (1.08 KB, patch)
2020-06-30 00:19 UTC, Upstream Release Monitoring
no flags Details | Diff

Description Upstream Release Monitoring 2016-02-18 12:13:11 UTC
Latest upstream release: v2.13.0
Current version/release in rawhide: 2.12.4-2.fc24
URL: https://github.com/mafintosh/is-my-json-valid

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 2016-02-18 12:13:17 UTC
Failed to kick off scratch build.

cmd:  spectool -g /var/tmp/thn-Pgh606/nodejs-is-my-json-valid.spec
return code:  22
stdout:
Getting https://registry.npmjs.org/is-my-json-valid/-/is-my-json-valid-v2.13.0.tgz to ./is-my-json-valid-v2.13.0.tgz

stderr:
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
curl: (22) The requested URL returned error: 500 Internal Server Error

Comment 2 Upstream Release Monitoring 2016-02-23 00:14:37 UTC
Latest upstream release: v2.13.1
Current version/release in rawhide: 2.12.4-2.fc24
URL: https://github.com/mafintosh/is-my-json-valid

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-02-23 00:14:42 UTC
Failed to kick off scratch build.

cmd:  spectool -g /var/tmp/thn-W8EDzW/nodejs-is-my-json-valid.spec
return code:  22
stdout:
Getting https://registry.npmjs.org/is-my-json-valid/-/is-my-json-valid-v2.13.1.tgz to ./is-my-json-valid-v2.13.1.tgz

stderr:
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
curl: (22) The requested URL returned error: 500 Internal Server Error

Comment 4 Upstream Release Monitoring 2016-09-20 00:20:59 UTC
Latest upstream release: v2.14.0
Current version/release in rawhide: 2.12.4-2.fc24
URL: https://github.com/mafintosh/is-my-json-valid

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

Comment 5 Upstream Release Monitoring 2016-09-20 00:21:06 UTC
Patching or scratch build for nodejs-is-my-json-valid-2.12.4 failed.

Comment 6 Upstream Release Monitoring 2016-09-20 00:21:07 UTC
Created attachment 1202653 [details]
Rebase-helper rebase-helper-debug.log log file.
See for details and report the eventual error to rebase-helper https://github.com/phracek/rebase-helper/issues.

Comment 7 Upstream Release Monitoring 2016-09-20 00:21:08 UTC
Patches were not touched. All were applied properly

Comment 8 Upstream Release Monitoring 2016-10-03 00:18:13 UTC
Latest upstream release: v2.15.0
Current version/release in rawhide: 2.12.4-2.fc24
URL: https://github.com/mafintosh/is-my-json-valid

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

Comment 9 Upstream Release Monitoring 2016-10-03 00:18:20 UTC
Patching or scratch build for nodejs-is-my-json-valid-2.12.4 failed.

Comment 10 Upstream Release Monitoring 2016-10-03 00:18:21 UTC
Created attachment 1206719 [details]
Rebase-helper rebase-helper-debug.log log file.
See for details and report the eventual error to rebase-helper https://github.com/phracek/rebase-helper/issues.

Comment 11 Upstream Release Monitoring 2016-10-03 00:18:23 UTC
Patches were not touched. All were applied properly

Comment 12 Upstream Release Monitoring 2017-02-27 00:16:55 UTC
Latest upstream release: v2.16.0
Current version/release in rawhide: 2.12.4-3.fc26
URL: https://github.com/mafintosh/is-my-json-valid

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

Comment 13 Upstream Release Monitoring 2017-02-27 00:16:59 UTC
An unexpected error occured creating the scratch build: please report this issue to the-new-hotness issue tracker at https://github.com/fedora-infra/the-new-hotness/issues

Comment 14 Upstream Release Monitoring 2017-08-24 00:16:29 UTC
Latest upstream release: v2.16.1
Current version/release in rawhide: 2.12.4-4.fc27
URL: https://github.com/mafintosh/is-my-json-valid

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

Comment 15 Upstream Release Monitoring 2017-08-24 00:16:33 UTC
An HTTP error occurred downloading the package's new Source URLs: Getting https://registry.npmjs.org/is-my-json-valid/-/is-my-json-valid-v2.16.1.tgz to ./is-my-json-valid-v2.16.1.tgz

Comment 16 Upstream Release Monitoring 2017-12-19 12:17:26 UTC
Latest upstream release: v2.17.1
Current version/release in rawhide: 2.12.4-4.fc27
URL: https://github.com/mafintosh/is-my-json-valid

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

Comment 17 Upstream Release Monitoring 2017-12-19 12:17:30 UTC
An HTTP error occurred downloading the package's new Source URLs: Getting https://registry.npmjs.org/is-my-json-valid/-/is-my-json-valid-v2.17.1.tgz to ./is-my-json-valid-v2.17.1.tgz

Comment 18 Upstream Release Monitoring 2018-02-15 00:16:38 UTC
Latest upstream release: v2.17.2
Current version/release in rawhide: 2.12.4-4.fc27
URL: https://github.com/mafintosh/is-my-json-valid

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

Comment 19 Upstream Release Monitoring 2018-08-10 00:19:33 UTC
Latest upstream release: v2.18.0
Current version/release in rawhide: 2.12.4-6.fc29
URL: https://github.com/mafintosh/is-my-json-valid

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

Comment 20 Upstream Release Monitoring 2018-08-13 12:18:31 UTC
Latest upstream release: v2.19.0
Current version/release in rawhide: 2.12.4-6.fc29
URL: https://github.com/mafintosh/is-my-json-valid

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

Comment 21 Upstream Release Monitoring 2020-06-26 14:34:00 UTC
Latest upstream release: 2.20.1
Current version/release in rawhide: 2.12.4-10.fc32
URL: https://github.com/mafintosh/is-my-json-valid

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

Comment 22 Upstream Release Monitoring 2020-06-26 14:34:02 UTC
Created attachment 1698934 [details]
[patch] Update to 2.20.1 (#1309667)

Comment 23 Upstream Release Monitoring 2020-06-26 14:36:04 UTC
the-new-hotness/release-monitoring.org's scratch build of nodejs-is-my-json-valid-2.20.1-1.fc32.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=46207216

Comment 24 Upstream Release Monitoring 2020-06-29 09:46:51 UTC
Latest upstream release: 2.20.2
Current version/release in rawhide: 2.12.4-10.fc32
URL: https://github.com/mafintosh/is-my-json-valid

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

Comment 25 Upstream Release Monitoring 2020-06-29 09:46:54 UTC
Created attachment 1699107 [details]
[patch] Update to 2.20.2 (#1309667)

Comment 26 Upstream Release Monitoring 2020-06-29 09:50:59 UTC
the-new-hotness/release-monitoring.org's scratch build of nodejs-is-my-json-valid-2.20.2-1.fc32.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=46319574

Comment 27 Upstream Release Monitoring 2020-06-30 00:19:43 UTC
Latest upstream release: 2.20.4
Current version/release in rawhide: 2.12.4-10.fc32
URL: https://github.com/mafintosh/is-my-json-valid

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

Comment 28 Upstream Release Monitoring 2020-06-30 00:19:45 UTC
Created attachment 1699219 [details]
[patch] Update to 2.20.4 (#1309667)

Comment 29 Upstream Release Monitoring 2020-06-30 00:23:15 UTC
the-new-hotness/release-monitoring.org's scratch build of nodejs-is-my-json-valid-2.20.4-1.fc32.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=46358161

Comment 30 Upstream Release Monitoring 2020-07-23 05:22:27 UTC
Latest upstream release: 2.20.5
Current version/release in rawhide: 2.12.4-10.fc32
URL: https://github.com/mafintosh/is-my-json-valid

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

Comment 31 Upstream Release Monitoring 2020-07-23 05:22:30 UTC
An unexpected error occurred while creating the scratch build and has been automatically reported. Sorry!

Comment 32 Miro Hrončok 2020-08-18 16:18:23 UTC
Automation has figured out the package is retired in rawhide.

If you like it to be unretired, please open a ticket at https://pagure.io/releng/new_issue?template=package_unretirement


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