Bug 1656991
| Summary: | update Singularity packages in EPEL to 3.x | ||
|---|---|---|---|
| Product: | [Fedora] Fedora EPEL | Reporter: | Paul Stauffer <paulds> |
| Component: | singularity | Assignee: | Dave Dykstra <dwd> |
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | epel7 | CC: | bbockelm, dave.love, dwd |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-04-12 19:59:29 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
Paul Stauffer
2018-12-06 19:42:56 UTC
I have started to work on it. The version of golang in rhel7 was too old until today when the latest version was released in epel7 (because RHEL 7.6 removed golang except in devtoolset). Beyond that, since singularity-3 is such a major update, it's going to require a lot of testing before I'll be willing to let it replace singularity-2.6.0 as the default. I think there are some things that will break current users and I want to avoid that as much as possible. I expect it will take at least one more release of singularity 3.x. Meanwhile I think I'll put it in the testing repositories. I'd rather avoid a singularity3 package. singularity-3 does attempt to be mostly compatible with singularity-2, it's just going to take a little more work before it is close enough. Dave singularity-3.0.3 is now the default for f28 and f29. However I still want to see more improvements and testing before putting singularity-3 in EPEL, to make sure that it doesn't break use cases of people using it in production. I know of one issue that does break a production use case, in https://github.com/sylabs/singularity/issues/2588, so I need to wait at least until that is fixed. Meanwhile I don't want to put it into epel-testing either, in case there's another security release like 2.6.1; I wouldn't want a singularity-3 version in testing to get in the way of a 2.6.2. This is to be done in bug #1693909. singularity-3.1.1 is now in epel-testing. Please give karma. *** This bug has been marked as a duplicate of bug 1693909 *** |