Spec URL: https://qulogic.fedorapeople.org//R-pkgcache.spec SRPM URL: https://qulogic.fedorapeople.org//R-pkgcache-1.1.0-1.fc32.src.rpm Description: Metadata and package cache for CRAN-like repositories. This is a utility package to be used by package management tools that want to take advantage of caching.
Rebuilding the package fails because in the testing stage the build is offline: ... Running 'testthat.R' ERROR Running the tests in 'tests/testthat.R' failed. Last 13 lines of output: 13. update_or_add, cache is too old (@test-5-cache.R#147) - Reason: offline 14. update_or_add, cache is current (@test-5-cache.R#179) - Reason: offline 15. bioconductor$get_repos (@test-metadata-utils.R#5) - Reason: offline 16. bioconductor$.internal$get_matching_bioc_version (@test-metadata-utils.R#16) - Reason: offline == Failed ====================================================================== -- 1. Failure: download_file, errors (@test-4-async-http.R#62) ---------------- `ret` inherits from `async_rejected/async_http_error/simpleError/error/condition` not `async_http_404`. == DONE ======================================================================== Error: Test failures Execution halted * checking PDF version of manual ... OK * DONE Status: 1 ERROR, 3 WARNINGs
Ah, it must have cached something somewhere while I was testing out builds. Spec URL: https://qulogic.fedorapeople.org/reviews/R-pkgcache.spec SRPM URL: https://qulogic.fedorapeople.org/reviews/R-pkgcache-1.1.0-2.fc32.src.rpm
The license is correct and appropriated for Fedora. The spec file follows the Fedora package guidelines. In this cases these are the fedora-review complaints: Issues: ======= - Package have the default element marked as %%doc :DESCRIPTION - Package requires R-core. I need to take some time to fix these reports from fedora-review as they are not issues. The package is approved. 
(fedscm-admin): The Pagure repository was created at https://src.fedoraproject.org/rpms/R-pkgcache
FEDORA-2020-7d3e8189f1 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-7d3e8189f1
FEDORA-2020-e15eb4fc79 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-e15eb4fc79
FEDORA-2020-6e5f3336b7 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-6e5f3336b7
FEDORA-2020-7d3e8189f1 has been pushed to the Fedora 33 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-7d3e8189f1` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-7d3e8189f1 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-6e5f3336b7 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-6e5f3336b7` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-6e5f3336b7 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-e15eb4fc79 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-e15eb4fc79` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-e15eb4fc79 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-7d3e8189f1 has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2020-e15eb4fc79 has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2020-6e5f3336b7 has been pushed to the Fedora 31 stable repository. If problem still persists, please make note of it in this bug report.