Bug 1860744
| Summary: | Version 1.0.5 is out, please update the package. | ||
|---|---|---|---|
| Product: | [Fedora] Fedora EPEL | Reporter: | Frank Büttner <bugzilla> |
| Component: | R-Rcpp | Assignee: | Mattias Ellert <mattias.ellert> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | epel7 | CC: | mattias.ellert |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | R-Rcpp-1.0.5-1.fc32 R-Rcpp-1.0.5-1.fc31 R-Rcpp-1.0.5-1.el6 R-Rcpp-1.0.5-1.el8 R-Rcpp-1.0.5-1.el7 | Doc Type: | --- |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-08-05 01:20:17 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Frank Büttner
2020-07-27 04:27:26 UTC
FEDORA-EPEL-2020-9a5aab0395 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-9a5aab0395 FEDORA-2020-be01d597f1 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-be01d597f1 FEDORA-EPEL-2020-580e14ab60 has been submitted as an update to Fedora EPEL 6. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-580e14ab60 FEDORA-2020-be01d597f1 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-be01d597f1` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-be01d597f1 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-EPEL-2020-580e14ab60 has been pushed to the Fedora EPEL 6 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-580e14ab60 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-EPEL-2020-e5fe8a00a5 has been pushed to the Fedora EPEL 8 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-e5fe8a00a5 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2020-0fdf9db89b 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-0fdf9db89b` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-0fdf9db89b See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-EPEL-2020-9a5aab0395 has been pushed to the Fedora EPEL 7 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-9a5aab0395 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2020-be01d597f1 has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2020-0fdf9db89b has been pushed to the Fedora 31 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-EPEL-2020-580e14ab60 has been pushed to the Fedora EPEL 6 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-EPEL-2020-e5fe8a00a5 has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-EPEL-2020-9a5aab0395 has been pushed to the Fedora EPEL 7 stable repository. If problem still persists, please make note of it in this bug report. |