Bug 1644519

I'm getting the same result, with these additional installed packages also preventing the update to RHEL 7.6 from succeeding because of the same libgtop dependency:

mate-disk-usage-analyzer-1.16.1-1.el7.x86_64 (@epel)
mate-applets-1.16.0-1.el7.x86_64 (@epel)
mate-system-monitor-1.16.0-1.el7.x86_64 (@epel)

We have to wait. Build root is broken for epel7.
https://koji.fedoraproject.org/koji/taskinfo?taskID=30574743
https://pagure.io/releng/issue/7898

*** Bug 1644590 has been marked as a duplicate of this bug. ***

Any chance to upgrade to a newer version of mate while this is in progress?

As i said before, i can't rebuild the packages because build root for epel7 is broken at koji build server.
10 minutes ago....
https://koji.fedoraproject.org/koji/taskinfo?taskID=30595598

mate-utils-1.16.1-2.el7 mate-applets-1.16.0-2.el7 marco-1.16.1-4.el7 caja-actions-1.8.2-2.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-417249babc

I guess you're all rhel users.
You can use epel-updates-testing for fixing your update when the update is available.
As most MATE users use centos7 i will wait with a push to stable until 7.6 upgrade is available in centos7.

caja-actions-1.8.2-2.el7, marco-1.16.1-4.el7, mate-applets-1.16.0-2.el7, mate-utils-1.16.1-2.el7 has been pushed to the Fedora EPEL 7 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-417249babc

All working fine now. Thanks.

I'm still getting an error for mate-system monitor.

(The updates for marco, mate-disk-use-analyzer, and mate-applets are working.)

Running

yum update --enablerepo=epel-testing

results in 

Error: Package: mate-system-monitor-1.16.0-1.el7.x86_64 (@epel)
           Requires: libgtop-2.0.so.10()(64bit)
           Removing: libgtop2-2.34.2-2.el7.x86_64 (@rhel-7-server-rpms)
               libgtop-2.0.so.10()(64bit)
           Updated By: libgtop2-2.38.0-3.el7.x86_64 (rhel-7-server-rpms)
              ~libgtop-2.0.so.11()(64bit)
           Available: libgtop2-2.28.4-7.el7.x86_64 (rhel-7-server-rpms)
               libgtop-2.0.so.10()(64bit)
           Available: libgtop2-2.34.2-1.el7.x86_64 (rhel-7-server-rpms)
               libgtop-2.0.so.10()(64bit)
           Available: libgtop2-2.28.4-6.el7.i686 (rhel-7-server-rpms)
               Not found

caja-actions-1.8.2-2.el7 marco-1.16.1-4.el7 mate-applets-1.16.0-2.el7 mate-system-monitor-1.16.0-2.el7 mate-utils-1.16.1-2.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-417249babc

opps, i forgot system-monitor

https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-417249babc

is updated.

caja-actions-1.8.2-2.el7, marco-1.16.1-4.el7, mate-applets-1.16.0-2.el7, mate-system-monitor-1.16.0-2.el7, mate-utils-1.16.1-2.el7 has been pushed to the Fedora EPEL 7 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-417249babc

The update went through fine now.  Thank you for your help.

*** Bug 1647961 has been marked as a duplicate of this bug. ***

Hi Team

I downloaded the RHEL 7.6 from website today and tried installing MATE. I got the same dependency issue. Is this fix available in the downloaded iso or still in development/testing stage?

Regards,
Abhishek Thakur

Sorry my bad, I am new to this bugzilla and redhat environment so still learning my way around. Seems this fix is in QA . Any idea when can I expect its release ?

Regards,
Abhishek Thakur

enable epel-testing repo.

(In reply to Wolfgang Ulbrich from comment #12)
> opps, i forgot system-monitor
> 

Looks as though mate-netspeed also got missed.

When should we expect the packages in testing to be promoted to stable?

Some folks with large environments aren't keen to enable epel-testing.

ok, i will take a look at mate-netspeed.

I will push it to stable when centos7 is updated.
Most Mate users using Centos7 as it is a free distro ;)

mate-netspeed is part of mate-applets which is already rebuilt.

Just a heads up (you probably already know) -- CentOS 7.6.1810 released today and is being synced to mirrors - which should mean promotion from epel-testing is now possible

Scientific Linux 7.6 was also released today.

(In reply to Pat Riehecky from comment #4)
> Any chance to upgrade to a newer version of mate while this is in progress?

This would be a duplicate of Bug #1436260 but I believe you're already part of that conversation.  :-)

(In reply to Greg Bailey from comment #24)
> (In reply to Pat Riehecky from comment #4)
> > Any chance to upgrade to a newer version of mate while this is in progress?
> 
> This would be a duplicate of Bug #1436260 but I believe you're already part
> of that conversation.  :-)

No, because
1. mate-1.16 is the last gtk3 version of Mate and this means a switch to gtk3 during runtime of a distro.
2. I don't have any interest/time any more to maintain Mate for rhel7 and future rhel release for free.
3. Feel free to become a fedora maintainer and takeover Mate for for epel7 branch

> 1. mate-1.16 is the last gtk3 version of Mate and this means a switch to gtk3 d
> uring runtime of a distro.

Typo, i mean Mate-1.16 is the last gtk2 version of Mate.

(In reply to Greg Smith from comment #22)
> Just a heads up (you probably already know) -- CentOS 7.6.1810 released
> today and is being synced to mirrors - which should mean promotion from
> epel-testing is now possible


Hi, do we have an eta on when will it be elevated ?

caja-actions-1.8.2-2.el7, marco-1.16.1-4.el7, mate-applets-1.16.0-2.el7, mate-system-monitor-1.16.0-2.el7, mate-utils-1.16.1-2.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, please make note of it in this bug report.