Terminator doesn't seem to be branched already for epel8 : (https://src.fedoraproject.org/rpms/terminator/branches?branchname=master) Is that possible to branch it, and then build/provide it through epel8 ? Thanks a lot !
Unfortunately it's not as easy as just creating a Git branch. This also needs to be (successfully!) build and tested on RHEL8 or CentOS 8. I have no possibility to do that currently. Any support on this is welcome!
*** Bug 1741774 has been marked as a duplicate of this bug. ***
That's true, it needs other pkgs. I was able to get it to build in my copr repo : https://copr.fedorainfracloud.org/coprs/arrfab/not-in-epel8/build/1043574/ I just patched .spec with this : @@ -12,7 +12,7 @@ BuildRequires: python2-devel gettext desktop-file-utils intltool Requires: vte291 python2-gobject keybinder3 desktop-file-utils -%if 0%{?rhel} +%if 0%{?rhel} <= 7 The real issue is for the other Requires, especially python2-gobject I had to use a ugly hack like this to be able to install terminator on my .el8 laptop : use the f28 rpms for it https://archives.fedoraproject.org/pub/archive/fedora/linux/releases/28/Everything/x86_64/os/Packages/p/python2-gobject-3.28.2-1.fc28.x86_64.rpm https://archives.fedoraproject.org/pub/archive/fedora/linux/releases/28/Everything/x86_64/os/Packages/p/python2-gobject-base-3.28.2-1.fc28.x86_64.rpm Those packages, on Fedora are built from pygobject3 src.rpm. But on .el8, the .spec is so trimmed that it doesn't build those pkgs anymore (see https://koji.mbox.centos.org/koji/buildinfo?buildID=411) Compare the .spec between Fedora and .el8 : Fedora : https://src.fedoraproject.org/rpms/pygobject3/blob/f28/f/pygobject3.spec#_58 .el8 (as pushed to centos) : https://git.centos.org/rpms/pygobject3/blob/c8/f/SPECS/pygobject3.spec Was wondering if introducing in epel8 a -compat pkg that would build what was trimmed from .spec (to build python2-gobject* pkgs) wouldn't be the way to go. Apart from that, once the F28 pkgs are installed on laptop, terminator (built with that minor .spec change for python-psutil) works fine (and I need on my .el8 laptop to be able to be productive) :)
Hi all, any update on this? it would be really useful to have in RHEL8... thanks
Currently Terminator is in a weird state. A few of us have been working on Terminator to update it to python3 and we actually have a branch that looks like it's in pretty good shape but the upstream maintainers have gone incommunicado and so it's proving hard to get the updates into an official release. I'll try to put up a copr repository with the code and update the bug in the next week or so Bug is here: https://bugs.launchpad.net/terminator/+bug/1662544 Branch is here: https://code.launchpad.net/~hellodeargrandma/terminator/python3
copr updated with python3 code for those of you interested: dnf copr enable mattrose/python3-terminator I think we have all the technical bugs worked out, now it's just a matter of sorting out the politics, I think :(
(In reply to Matt Rose from comment #6) > copr updated with python3 code for those of you interested: > > dnf copr enable mattrose/python3-terminator > > I think we have all the technical bugs worked out, now it's just a matter of > sorting out the politics, I think :( It works for me on RHEL8.1! Thanks Matt!
I almost got tears in my eyes from seeing terminator (v3, no less) on EL8 ... Thank you so much.
dmaphy has packaged up the new release of terminator for epel8 dnf -y --enable-repo=updates-testing terminator Try it out and show it some love on bodhi.
FEDORA-EPEL-2020-6850774286 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-6850774286
FEDORA-EPEL-2020-6850774286 has been pushed to the Fedora EPEL 8 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-6850774286 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2020-6850774286 has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report.