Subject: | |
From: | |
Reply To: | |
Date: | Mon, 26 Nov 2018 13:53:19 -0600 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
On 11/26/2018 01:15 PM, Adam Jensen wrote:
> Both of my SL-7.5 systems use the MATE desktop. Today, `yum update`
> gives some errors (below). Is there a good way to deal with this that
> won't result long-term maintenance problems?
>
>
> ---> Package libgtop2.x86_64 0:2.34.2-2.el7 will be updated
> --> Processing Dependency: libgtop-2.0.so.10()(64bit) for package:
> mate-system-monitor-1.16.0-1.el7.x86_64
> --> Processing Dependency: libgtop-2.0.so.10()(64bit) for package:
> mate-applets-1.16.0-1.el7.x86_64
> --> Processing Dependency: libgtop-2.0.so.10()(64bit) for package:
> marco-1.16.1-3.el7.x86_64
> --> Processing Dependency: libgtop-2.0.so.10()(64bit) for package:
> mate-disk-usage-analyzer-1.16.1-1.el7.x86_64
> --> Finished Dependency Resolution
> 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 (@sl)
> libgtop-2.0.so.10()(64bit)
> Updated By: libgtop2-2.38.0-3.el7.x86_64 (sl-security)
> ~libgtop-2.0.so.11()(64bit)
> Error: Package: marco-1.16.1-3.el7.x86_64 (@epel)
> Requires: libgtop-2.0.so.10()(64bit)
> Removing: libgtop2-2.34.2-2.el7.x86_64 (@sl)
> libgtop-2.0.so.10()(64bit)
> Updated By: libgtop2-2.38.0-3.el7.x86_64 (sl-security)
> ~libgtop-2.0.so.11()(64bit)
> Error: Package: mate-applets-1.16.0-1.el7.x86_64 (@epel)
> Requires: libgtop-2.0.so.10()(64bit)
> Removing: libgtop2-2.34.2-2.el7.x86_64 (@sl)
> libgtop-2.0.so.10()(64bit)
> Updated By: libgtop2-2.38.0-3.el7.x86_64 (sl-security)
> ~libgtop-2.0.so.11()(64bit)
> Error: Package: mate-disk-usage-analyzer-1.16.1-1.el7.x86_64 (@epel)
> Requires: libgtop-2.0.so.10()(64bit)
> Removing: libgtop2-2.34.2-2.el7.x86_64 (@sl)
> libgtop-2.0.so.10()(64bit)
> Updated By: libgtop2-2.38.0-3.el7.x86_64 (sl-security)
> ~libgtop-2.0.so.11()(64bit)
> You could try using --skip-broken to work around the problem
> You could try running: rpm -Va --nofiles --nodigest
>
Looks like EPEL wants to keep the old versions around. Either wait for
them to compile against the newer libraries or try checking/filing a bug
report to EPEL.
|
|
|