Bug 2104341
| Summary: | Please update geany to latest version, currently 1.38 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora EPEL | Reporter: | agents |
| Component: | geany | Assignee: | Dominic Hopf <dmaphy> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | epel7 | CC: | dmaphy, egolov, josef, oliver, pingou |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | geany-1.37-1.el7 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-07-17 01:00:28 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
agents
2022-07-06 02:34:06 UTC
FEDORA-EPEL-2022-d21f0b3572 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-d21f0b3572 Unfortunately it was not possible to build 1.38 without failures for EPEL7. Here is 1.37 for now, probably I'm able to point out the issue and also build a newer version of the Geany plugins. Stay tuned for those. FEDORA-EPEL-2022-d21f0b3572 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-2022-d21f0b3572 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. (In reply to Dominic Hopf from comment #2) > Unfortunately it was not possible to build 1.38 without failures for EPEL7. > Here is 1.37 for now, probably I'm able to point out the issue and also > build a newer version of the Geany plugins. Stay tuned for those. Can I ask why 1.38 fails for EPEL7? Will you be able to build geany-themes in addition to geany-plugins? Thank you for your work! FEDORA-EPEL-2022-d21f0b3572 has been pushed to the Fedora EPEL 7 stable repository. If problem still persists, please make note of it in this bug report. (In reply to Fedora Update System from comment #5) > FEDORA-EPEL-2022-d21f0b3572 has been pushed to the Fedora EPEL 7 stable > repository. > If problem still persists, please make note of it in this bug report. I have been running 1.37 for a couple of weeks and it seems to work fine. However, the plugins also need to be updated from 1.36 to 1.37 as there may be inconsistencies. For example, I am using the Project plugin for 1.36 and when closing a project it no longer closes the project files under Geany 1.37. This worked fine when both were 1.36 wherefore I suspect some inconsistencies between editor and plugins. Thanks in advance. FEDORA-EPEL-2022-8a29188f03 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-8a29188f03 FEDORA-EPEL-2022-8a29188f03 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-2022-8a29188f03 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-EPEL-2022-8a29188f03 has been pushed to the Fedora EPEL 7 stable repository. If problem still persists, please make note of it in this bug report. Can I ask why geany 1.38 could not be built for CentOS 7? What is/are the specific failure(s)? From the Geany Mailinglist: > So I did a quick try to build Geany 1.38 for EPEL7, right now the problem is that `./configure` already fails with this message: > > configure: error: *** A compiler with support for C++17 language features is required. > error: Bad exit status from /var/tmp/rpm-tmp.X4sTL9 (%build) > Bad exit status from /var/tmp/rpm-tmp.X4sTL9 (%build) > Ok, thats not one that is fixable in a practical sense, Scintilla versions after the 3.x.x stable versions do require C++17, and the changes between the old version and the new versions (two major versions after all) have too many changes to be practical to support both. > I'm afraid this is not possible to build without immense effort unless anyone else has an idea? > Does one of you guys know if it's possible to install flatpaks on CentOS 7? Probably that could be an idea then? > Well, I guess Flatsnaps, dockers or other containerised mechanisms would maybe allow for a newer C++ compiler to build against a newer runtime. Docker is used to do the Windows cross compiles and CI now. Would need to run in the container too so the newer C++ runtime library was available I guess. But I am no container expert. |