SCIENTIFIC-LINUX-USERS Archives

September 2017

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Lofgren, Eric" <[log in to unmask]>
Reply To:
Lofgren, Eric
Date:
Wed, 20 Sep 2017 00:25:06 +0000
Content-Type:
multipart/signed
Parts/Attachments:
text/plain (6 kB) , smime.p7s (6 kB)
That does indeed seem to have resolved the issue. Thank you.

Eric

> On Sep 19, 2017, at 4:03 PM, Alan Bartlett <[log in to unmask]> wrote:
> 
> On 19 September 2017 at 23:09, Lofgren, Eric <[log in to unmask]> wrote:
>> We’ve got a seldom-used workstation running SL7, which I try to update whenever I’m on the machine.
>> 
>> This last time, I encountered an error running sudo yum update, I got the following error:
>> 
>> ---> Package libplist.x86_64 0:1.10-4.el7 will be updated
>> --> Processing Dependency: libplist.so.1()(64bit) for package: libgpod-0.8.3-14.el7.x86_64
>> ---> Package usbmuxd.x86_64 0:1.0.8-11.el7 will be obsoleted
>> --> Processing Dependency: libusbmuxd.so.2()(64bit) for package: libgpod-0.8.3-14.el7.x86_64
>> --> Finished Dependency Resolution
>> Error: Package: libgpod-0.8.3-14.el7.x86_64 (@epel)
>>           Requires: libusbmuxd.so.2()(64bit)
>>           Removing: usbmuxd-1.0.8-11.el7.x86_64 (@base/$releasever)
>>               libusbmuxd.so.2()(64bit)
>>           Obsoleted By: usbmuxd-1.1.0-1.el7.x86_64 (sl-security)
>>               Not found
>> Error: Package: libgpod-0.8.3-14.el7.x86_64 (@epel)
>>           Requires: libimobiledevice.so.4()(64bit)
>>           Removing: libimobiledevice-1.1.5-6.el7.x86_64 (@base/$releasever)
>>               libimobiledevice.so.4()(64bit)
>>           Updated By: libimobiledevice-1.2.0-1.el7.x86_64 (sl-security)
>>              ~libimobiledevice.so.6()(64bit)
>> Error: Package: libgpod-0.8.3-14.el7.x86_64 (@epel)
>>           Requires: libplist.so.1()(64bit)
>>           Removing: libplist-1.10-4.el7.x86_64 (@base/$releasever)
>>               libplist.so.1()(64bit)
>>           Updated By: libplist-1.12-3.el7.x86_64 (sl-security)
>>              ~libplist.so.3()(64bit)
>> You could try using --skip-broken to work around the problem
>> ** Found 4 pre-existing rpmdb problem(s), 'yum check' output follows:
>> ipa-client-4.4.0-14.sl7_3.7.x86_64 has installed conflicts freeipa-client: ipa-client-4.4.0-14.sl7_3.7.x86_64
>> ipa-client-common-4.4.0-14.sl7_3.7.noarch has installed conflicts freeipa-client-common: ipa-client-common-4.4.0-14.sl7_3.7.noarch
>> ipa-common-4.4.0-14.sl7_3.7.noarch has installed conflicts freeipa-common: ipa-common-4.4.0-14.sl7_3.7.noarch
>> ipa-python-compat-4.4.0-14.sl7_3.7.noarch has installed conflicts freeipa-python-compat: ipa-python-compat-4.4.0-14.sl7_3.7.noarch
>> 
>> Trying yum update —skip-broken yields an error as well…
>> 
>> -> Finished Dependency Resolution
>> 
>> Packages skipped because of dependency problems:
>>    1:NetworkManager-1.8.0-9.el7.x86_64 from sl-security
>>    1:NetworkManager-adsl-1.8.0-9.el7.x86_64 from sl-security
>>    1:NetworkManager-glib-1.8.0-9.el7.i686 from sl-security
>>    1:NetworkManager-glib-1.8.0-9.el7.x86_64 from sl-security
>>    1:NetworkManager-libnm-1.8.0-9.el7.x86_64 from sl-security
>>    NetworkManager-libreswan-1.2.4-2.el7.x86_64 from sl-security
>>    NetworkManager-libreswan-gnome-1.2.4-2.el7.x86_64 from sl-security
>>    1:NetworkManager-ppp-1.8.0-9.el7.x86_64 from sl-security
>>    1:NetworkManager-team-1.8.0-9.el7.x86_64 from sl-security
>>    1:NetworkManager-tui-1.8.0-9.el7.x86_64 from sl-security
>>    1:NetworkManager-wifi-1.8.0-9.el7.x86_64 from sl-security
>>    PackageKit-1.1.5-1.sl7.x86_64 from sl-security
>>    PackageKit-command-not-found-1.1.5-1.sl7.x86_64 from sl-security
>>    PackageKit-glib-1.1.5-1.sl7.x86_64 from sl-security
>> 
>> …snip a huge number of packages…
>> 
>>    webkitgtk3-2.4.11-2.el7.x86_64 from sl-security
>>    webkitgtk4-2.14.7-2.el7.x86_64 from sl-security
>>    webkitgtk4-jsc-2.14.7-2.el7.x86_64 from sl-security
>>    webkitgtk4-plugin-process-gtk2-2.14.7-2.el7.x86_64 from sl-security
>>    webrtc-audio-processing-0.3-1.el7.x86_64 from sl-security
>>    xkeyboard-config-2.20-1.el7.noarch from sl-security
>>    xorg-x11-apps-7.7-7.el7.x86_64 from sl-security
>>    xorg-x11-drv-ati-7.7.1-3.20160928git3fc839ff.el7.x86_64 from sl-security
>>    xorg-x11-drv-dummy-0.3.7-1.el7.x86_64 from sl-security
>>    xorg-x11-drv-evdev-2.10.5-2.1.el7.x86_64 from sl-security
>>    xorg-x11-drv-fbdev-0.4.3-25.el7.x86_64 from sl-security
>>    xorg-x11-drv-intel-2.99.917-26.20160929.el7.x86_64 from sl-security
>>    1:xorg-x11-drv-nouveau-1.0.13-3.el7.x86_64 from sl-security
>>    xorg-x11-drv-qxl-0.1.5-3.el7.x86_64 from sl-security
>>    xorg-x11-drv-synaptics-1.9.0-1.el7.x86_64 from sl-security
>>    xorg-x11-drv-v4l-0.2.0-47.el7.x86_64 from sl-security
>>    xorg-x11-drv-vesa-2.3.2-25.1.el7.x86_64 from sl-security
>>    xorg-x11-drv-vmmouse-13.1.0-1.el7.x86_64 from sl-security
>>    xorg-x11-drv-vmware-13.2.1-1.el7.x86_64 from sl-security
>>    xorg-x11-drv-void-1.4.1-2.el7.x86_64 from sl-security
>>    xorg-x11-drv-wacom-0.34.2-2.el7.x86_64 from sl-security
>>    xorg-x11-proto-devel-7.7-20.el7.noarch from sl-security
>>    xorg-x11-server-Xorg-1.19.3-11.el7.x86_64 from sl-security
>>    xorg-x11-server-common-1.19.3-11.el7.x86_64 from sl-security
>>    xorg-x11-server-utils-7.7-20.el7.x86_64 from sl-security
>>    xorg-x11-utils-7.5-22.el7.x86_64 from sl-security
>>    xz-libs-5.2.2-1.el7.i686 from sl
>>    1:yelp-3.22.0-1.el7.x86_64 from sl-security
>>    1:yelp-libs-3.22.0-1.el7.x86_64 from sl-security
>>    yelp-xsl-3.20.1-1.el7.noarch from sl-security
>>    zenity-3.22.0-1.el7.x86_64 from sl-security
>> Error:  Multilib version problems found. This often means that the root
>>       cause is something else and multilib version checking is just
>>       pointing out that there is a problem. Eg.:
>> 
>>         1. You have an upgrade for libcurl which is missing some
>>            dependency that another package requires. Yum is trying to
>>            solve this by installing an older version of libcurl of the
>>            different architecture. If you exclude the bad architecture
>>            yum will tell you what the root cause is (which package
>>            requires what). You can try redoing the upgrade with
>>            --exclude libcurl.otherarch ... this should give you an error
>>            message showing the root cause of the problem.
>> 
>>         2. You have multiple architectures of libcurl installed, but
>>            yum can only see an upgrade for one of those architectures.
>>            If you don't want/need both architectures anymore then you
>>            can remove the one with the missing update and everything
>>            will work.
>> 
>>         3. You have duplicate versions of libcurl installed already.
>>            You can use "yum check" to get yum show these errors.
>> 
>>       ...you can also use --setopt=protected_multilib=false to remove
>>       this checking, however this is almost never the correct thing to
>>       do as something else is very likely to go wrong (often causing
>>       much more problems).
>> 
>>       Protected multilib versions: libcurl-7.29.0-42.el7.x86_64 != libcurl-7.29.0-35.el7.i686
>> 
>> Does anyone know what’s going on, or how to fix this?
>> 
>> Thanks,
>> 
>> Eric
> 
> Try --
> 
> sudo yum downgrade libgpod
> sudo yum update
> 
> Alan.



ATOM RSS1 RSS2