Bug 2401012
| Summary: | Please branch and build SuperLUMT in epel10/epel10.1/epel10.0 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora EPEL | Reporter: | Orion Poplawski <orion> |
| Component: | SuperLUMT | Assignee: | Antonio T. sagitter <trpost> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | epel10 | CC: | trpost |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | SuperLUMT-4.0.1-6.el10_2 | Doc Type: | --- |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2025-11-01 01:32:18 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 2391476 | ||
|
Description
Orion Poplawski
2025-10-02 13:57:25 UTC
Will you be able to branch and build SuperLUMT in epel10? I would be happy to be a co-maintainer if you do not wish to build it on epel10 (FAS: orion). I'm going to upgrade sundials to the 7.5.0 soon, and i will build it on epel10 too. FEDORA-EPEL-2025-7e69d51408 (MUMPS-5.7.3-5.el10_2, petsc-3.24.0-7.el10_2, and 2 more) has been submitted as an update to Fedora EPEL 10.2. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-7e69d51408 FEDORA-EPEL-2025-7e69d51408 has been pushed to the Fedora EPEL 10.2 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-7e69d51408 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-EPEL-2025-7e69d51408 (MUMPS-5.7.3-5.el10_2, petsc-3.24.0-7.el10_2, and 2 more) has been pushed to the Fedora EPEL 10.2 stable repository. If problem still persists, please make note of it in this bug report. |