SCIENTIFIC-LINUX-USERS Archives

January 2018

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:
Nico Kadel-Garcia <[log in to unmask]>
Reply To:
Nico Kadel-Garcia <[log in to unmask]>
Date:
Fri, 5 Jan 2018 10:29:20 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (70 lines)
On Fri, Jan 5, 2018 at 5:35 AM, Jean-Michel Barbet
<[log in to unmask]> wrote:
> Hello all,
>
> Trying to update to recent kernel, in the list of updated package
> there are 4 device-mapper updated packages and it looks like that
> the new device-mapper-event.x86_64 0:1.02.117-12.el6 conflicts with
> the installed lvm2-libs-2.02.100-8.el6.x86_64 :

A bit of phase lag among the mirrors and the cache for the mirrors is
unsurprising. "yum clean all" is my friend for this, as is:doing a
smaller set of updates at a time. For example:

    yum update "glib*" # to get glibc updates
    yum update "[A-Z]* # to get those pesky capitalized name packages

etc., etc.



> yum update
> Loaded plugins: priorities, security
> Setting up Update Process
> 715 packages excluded due to repository priority protections
> Resolving Dependencies
> --> Running transaction check
> ---> Package device-mapper.x86_64 0:1.02.79-8.el6 will be updated
> ---> Package device-mapper.x86_64 0:1.02.117-12.el6 will be an update
> ---> Package device-mapper-event.x86_64 0:1.02.79-8.el6 will be updated
> ---> Package device-mapper-event.x86_64 0:1.02.117-12.el6 will be an update
> ---> Package device-mapper-event-libs.x86_64 0:1.02.79-8.el6 will be updated
> ---> Package device-mapper-event-libs.x86_64 0:1.02.117-12.el6 will be an
> update
> ---> Package device-mapper-libs.x86_64 0:1.02.79-8.el6 will be updated
> ---> Package device-mapper-libs.x86_64 0:1.02.117-12.el6 will be an update
> ---> Package kernel.x86_64 0:2.6.32-696.18.7.el6 will be installed
> ---> Package kernel-firmware.noarch 0:2.6.32-696.10.3.el6 will be updated
> ---> Package kernel-firmware.noarch 0:2.6.32-696.18.7.el6 will be an update
> ---> Package kernel-headers.x86_64 0:2.6.32-696.10.3.el6 will be updated
> ---> Package kernel-headers.x86_64 0:2.6.32-696.18.7.el6 will be an update
> ---> Package kpartx.x86_64 0:0.4.9-72.el6 will be updated
> ---> Package kpartx.x86_64 0:0.4.9-100.el6 will be an update
> ---> Package microcode_ctl.x86_64 1:1.17-17.el6 will be updated
> ---> Package microcode_ctl.x86_64 1:1.17-25.2.el6_9 will be an update
> ---> Package nagios-common.x86_64 0:4.3.2-5.el6 will be updated
> ---> Package nagios-common.x86_64 0:4.3.4-7.el6 will be an update
> ---> Package nrpe.x86_64 0:3.1.1-1.el6 will be updated
> ---> Package nrpe.x86_64 0:3.2.0-6.el6 will be an update
> ---> Package tzdata.noarch 0:2017b-1.el6 will be updated
> ---> Package tzdata.noarch 0:2017c-1.el6 will be an update
> --> Processing Conflict: device-mapper-event-1.02.117-12.el6.x86_64
> conflicts lvm2-libs < 2.02.111
> --> Finished Dependency Resolution
> Error: device-mapper-event conflicts with lvm2-libs-2.02.100-8.el6.x86_64
>
>
> This is not a new story but I am wondering if someting has been
> forgotten upstream and if other sites are seeing the same...
>
> Thank you.
>
> JM
>
> --
> ------------------------------------------------------------------------
> Jean-michel BARBET                    | Tel: +33 (0)2 51 85 84 86
> Laboratoire SUBATECH Nantes France    | Fax: +33 (0)2 51 85 84 79
> CNRS-IN2P3/IMT-Atlantique/Univ.Nantes | E-Mail: [log in to unmask]
> ------------------------------------------------------------------------

ATOM RSS1 RSS2