Created attachment 1681048 [details] Patch for 0.9.10 spec file --> 0.15 release Description of problem: 0.15 has been released for some time. However, 0.9.10 is only available in Fedora (and EPEL). I have modified the spec file in order to build 0.15. But for EPEL there seem to be core dependencies missing, such as buildah and docker are too old in EPEL7. I expect this is the reason why charliecloud has not been updated for EPEL7? Is there also a reason why it is not updated for Fedora? My changed spec file for the 0.15 version did not build due to the recent security hardening defaults in Fedora (and EPEL8), namely PIE. I did not pursue this further, but changing build flags will fix that of course. But my goal oriented towards updating the package in EPEL. In a nutshell: Why is the latest version of charliecloud not available in Fedora and EPEL 7/8? I suppose it is because of these core dependencies missing, but I would like to double check. Version-Release number of selected component (if applicable): charliecloud-0.9.10-12.fc31 Steps to Reproduce: 1. Patch the current 0.9.10 spec file with the attached patch 2. Run in Mock a build with the 0.15 source for Fedora 31, EPEL7 and EPEL8 Additional info: Errors while configuring on EPEL7 mock build: checking for buildah... buildah checking if buildah version >= 1.11.2... too old (1.9.0) checking for docker... docker checking if docker version >= 17.03... too old (1.13.1) Changes I made to the spec file are included in the attached file charliecloud_version_bump.patch
Greetings, We do plan on updating the charliecloud package for EPEL 7/8, you can see the spec file here: https://github.com/hpc/charliecloud/blob/9a2053964ee07335640fa6d2727eb82954113203/packaging/fedora/charliecloud.spec. 0.15 was released 17 days ago, however, you are correct in that the Charliecloud package on EPEL 7/8 has been slow to receive updates. There are a few reasons for this: 1) Charliecloud undergoes rapid development and frequent releases; we want to make sure what we put in EPEL is stable and reliable, 2) version 0.10, the version after 0.9.10, introduced a dependency on umoci that couldn't be resolved, and 3) Charliecloud switched over from a manual Makefile build process to utilizing autotools. 0.15 has ironed out many of the autotools issues and removed the skopeo and umoci dependencies (although still requires two patches). It is a good candidate for EPEL 7 and 8. The spec file linked above is more or less what I will upload to src.fedoraproject.org in the near future. Thank you for patience.
Update: I've identified a runtime bug when compiling with the flag '-Wp,-D_FORTIFY_SOURCE=2`. The ch-run executable hangs on line 141 (ch-run.c) when calling realpath(3). I'm investigating, however, this bug will need to be addressed before we update to 0.15.
Update: The issues have been resolved and I am staging 0.15 builds on fedora and epel 7.
FEDORA-2020-6755f39727 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2020-6755f39727
FEDORA-2020-1bb107e5e5 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-1bb107e5e5
FEDORA-2020-434c6877aa has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-434c6877aa
FEDORA-EPEL-2020-4de27ea34b has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-4de27ea34b
FEDORA-2020-6755f39727 has been pushed to the Fedora 30 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-6755f39727` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-6755f39727 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-434c6877aa 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-434c6877aa` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-434c6877aa See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-1bb107e5e5 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-1bb107e5e5` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-1bb107e5e5 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2020-4de27ea34b 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-4de27ea34b See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-434c6877aa has been pushed to the Fedora 31 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2020-1bb107e5e5 has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2020-6755f39727 has been pushed to the Fedora 30 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2020-4de27ea34b has been pushed to the Fedora EPEL 7 stable repository. If problem still persists, please make note of it in this bug report.