Bug 1744448 - Request to build meld for EPEL 8
Summary: Request to build meld for EPEL 8
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: meld
Version: epel8
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Lubomir Rintel
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1755295 1779921 1809457 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-22 08:24 UTC by Jens Kretschmer
Modified: 2020-04-08 00:35 UTC (History)
12 users (show)

Fixed In Version: meld-3.20.2-1.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-08 00:35:48 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jens Kretschmer 2019-08-22 08:24:27 UTC
Please build meld for EPEL 8

Comment 1 Dominic Hopf 2019-10-07 20:43:36 UTC
*** Bug 1755295 has been marked as a duplicate of this bug. ***

Comment 3 Dominic Hopf 2019-12-07 11:25:52 UTC
*** Bug 1779921 has been marked as a duplicate of this bug. ***

Comment 4 Dominic Hopf 2020-03-06 20:34:13 UTC
*** Bug 1809457 has been marked as a duplicate of this bug. ***

Comment 5 Thorsten Leemhuis 2020-03-25 06:37:14 UTC
What's the status here? el8 branches for meld got created, but it was never build?

Comment 6 Dominic Hopf 2020-03-26 22:45:05 UTC
Yep, branches have been created and my first thought was something like "let's merge epel7 into epel8 and see if it works". The result: it didn't: https://koji.fedoraproject.org/koji/taskinfo?taskID=42786237
As I'm currently struggling with some private issues I didn't get around to look further what the actual issue might be. Any support is heartily appreciated.

Comment 7 Leon Fauster 2020-03-27 00:05:03 UTC
Fedora31's version (meld-3.20.1-3) builds straight away with this little adaption of the spec file (EL8 ships python3-gobject):

--- meld-f31.spec	2020-03-27 00:54:17.979343655 +0100
+++ meld-el8.spec	2020-03-27 00:54:08.550349682 +0100
@@ -21,11 +21,7 @@
 Requires:	gtksourceview3 >= 3.6.0
 Requires:	patch
 Requires:	python3-cairo
-%if 0%{?rhel}
-Requires:   pygobject3
-%else
 Requires:	python3-gobject
-%endif
 
 Requires:	gsettings-desktop-schemas

Comment 8 Didier 2020-04-01 14:05:51 UTC
(In reply to Leon Fauster from comment #7)
> Fedora31's version (meld-3.20.1-3) builds straight away with this little
> adaption of the spec file (EL8 ships python3-gobject):

Confirmed ; meld-3.20.1-3dmn EL8 build for testing purposes available at COPR https://copr.fedorainfracloud.org/coprs/ifas/meld/

Comment 9 Levente Farkas 2020-04-01 15:07:26 UTC
tha could you add it to as epel8 source?

Comment 10 Thorsten Leemhuis 2020-04-01 15:18:35 UTC
Sorry, I'm out and can't help, too many software I needed was missing in EPEL8,  so I abandoned CentOS8 and went with Fedora instead

Comment 11 Didier 2020-04-02 11:49:15 UTC
Modified slightly to be somewhat better compliant : 

@@ -22,7 +22,9 @@
 Requires:	patch
 Requires:	python3-cairo
 %if 0%{?rhel}
+%if %{?rhel} < 8
 Requires:   pygobject3
+%endif
 %else
 Requires:	python3-gobject
 %endif


Now available at https://copr.fedorainfracloud.org/coprs/ifas/el8-missing/

Comment 12 Oliver Falk 2020-04-02 13:57:08 UTC
Thanks Didier for you work on that!

meld-3.20.1-4.el8 looks good and starts up fine on my RHEL 8 test system.
Shall we update the spec file in the fedora git and push for a "real" build?

Comment 13 Didier 2020-04-02 14:18:48 UTC
Dear Oliver,

Please, be my guest.

I tested the same spec for the fedora-31-x86_64 and fedora-32-x86_64 chroots.
F31 built just fine, F32 did not build (unrelated error, if I remember well).

Comment 14 Fedora Update System 2020-04-07 09:53:34 UTC
FEDORA-EPEL-2020-f8b75ecb7f has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-f8b75ecb7f

Comment 15 Fedora Update System 2020-04-08 00:35:48 UTC
FEDORA-EPEL-2020-f8b75ecb7f has been pushed to the Fedora EPEL 8 stable repository.
If problem still persists, please make note of it in this bug report.


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