Bug 2104341 - Please update geany to latest version, currently 1.38
Summary: Please update geany to latest version, currently 1.38
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: geany
Version: epel7
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Dominic Hopf
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-07-06 02:34 UTC by agents
Modified: 2023-06-20 09:40 UTC (History)
5 users (show)

Fixed In Version: geany-1.37-1.el7
Clone Of:
Environment:
Last Closed: 2022-07-17 01:00:28 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description agents 2022-07-06 02:34:06 UTC

Comment 1 Fedora Update System 2022-07-08 11:47:51 UTC
FEDORA-EPEL-2022-d21f0b3572 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-d21f0b3572

Comment 2 Dominic Hopf 2022-07-08 11:49:31 UTC
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.

Comment 3 Fedora Update System 2022-07-09 01:30:45 UTC
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.

Comment 4 agents 2022-07-09 03:08:51 UTC
(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!

Comment 5 Fedora Update System 2022-07-17 01:00:28 UTC
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.

Comment 6 agents 2022-08-13 18:12:51 UTC
(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.

Comment 7 Fedora Update System 2022-08-16 10:31:09 UTC
FEDORA-EPEL-2022-8a29188f03 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-8a29188f03

Comment 8 Fedora Update System 2022-08-17 01:44:08 UTC
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.

Comment 9 Fedora Update System 2022-08-24 21:17:03 UTC
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.

Comment 10 agents 2023-06-19 14:29:10 UTC
Can I ask why geany 1.38 could not be built for CentOS 7? What is/are the specific failure(s)?

Comment 11 Dominic Hopf 2023-06-20 09:35:16 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.