Bug 1850392
| Summary: | rubygem-jekyll-feed-0.15.0 is available | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Upstream Release Monitoring <upstream-release-monitoring> | ||||||
| Component: | rubygem-jekyll-feed | Assignee: | Fabio Valentini <decathorpe> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | rawhide | CC: | decathorpe | ||||||
| Target Milestone: | --- | Keywords: | FutureFeature, Triaged | ||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | rubygem-jekyll-feed-0.15.0-1.fc32 rubygem-jekyll-feed-0.15.0-1.fc31 | Doc Type: | --- | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2020-07-22 01:05:33 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
|
Description
Upstream Release Monitoring
2020-06-24 08:39:45 UTC
Created attachment 1698545 [details]
[patch] Update to 0.14.0 (#1850392)
the-new-hotness/release-monitoring.org's scratch build of rubygem-jekyll-feed-0.14.0-1.fc32.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=46080895 Latest upstream release: 0.15.0 Current version/release in rawhide: 0.13.0-3.fc32 URL: https://github.com/jekyll/jekyll-feed 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/17331/ Created attachment 1700640 [details]
[patch] Update to 0.15.0 (#1850392)
the-new-hotness/release-monitoring.org's scratch build of rubygem-jekyll-feed-0.15.0-1.fc32.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=46950456 FEDORA-2020-a2c6d7eda0 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-a2c6d7eda0 FEDORA-2020-ca0be1d034 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-ca0be1d034 FEDORA-2020-a2c6d7eda0 has been pushed to the Fedora 32 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-a2c6d7eda0` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-a2c6d7eda0 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2020-ca0be1d034 has been pushed to the Fedora 31 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-ca0be1d034` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-ca0be1d034 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2020-a2c6d7eda0 has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2020-ca0be1d034 has been pushed to the Fedora 31 stable repository. If problem still persists, please make note of it in this bug report. |