glibc升级中遇到的小问题

线上用的glibc-2.17-78存在漏洞，需要升级到>glibc-2.17-106版本，yum仓库最新为196版本，直接使用yum update升级：

[root@192.168.0.1 batchuser]#yum -y update glibc
已加载插件：fastestmirror
Loading mirror speeds from cached hostfile
正在解决依赖关系
There are unfinished transactions remaining. You might consider running yum-complete-transaction, or "yum-complete-transaction --cleanup-only" and "yum history redo last", first to finish them. If those don't work you'll have to try removing/installing packages by hand (maybe package-cleanup can help).
程序 yum-complete-transaction 在 yum-utils 软件包中。
--> 正在检查事务
---> 软件包 glibc.x86_64.0.2.17-78.el7 将被 升级
--> 正在处理依赖关系 glibc = 2.17-78.el7，它被软件包 glibc-common-2.17-78.el7.x86_64 需要
---> 软件包 glibc.x86_64.0.2.17-196.el7 将被 更新
--> 解决依赖关系完成
错误：软件包：glibc-common-2.17-78.el7.x86_64 (@anaconda)
          需要：glibc = 2.17-78.el7
          正在删除: glibc-2.17-78.el7.x86_64 (@anaconda)
              glibc = 2.17-78.el7
          更新，由: glibc-2.17-196.el7.x86_64 (CTyueme-epel)
              glibc = 2.17-196.el7
 您可以尝试添加 --skip-broken 选项来解决该问题
** 发现 3 个已存在的 RPM 数据库问题， 'yum check' 输出如下：
glibc-common-2.17-196.el7.x86_64 是 glibc-common-2.17-78.el7.x86_64 的副本
glibc-common-2.17-196.el7.x86_64 有缺少的需求 glibc = ('0', '2.17', '196.el7')
libgcc-4.8.5-16.el7.x86_64 是 libgcc-4.8.3-9.el7.x86_64 的副本

查看当前服务器已安装的glibc包，发现glibc-common有新旧两个版本，将新版本删除

[root@192.168.0.1 batchuser]#rpm -qa | grep glibc
glibc-2.17-78.el7.x86_64
glibc-common-2.17-196.el7.x86_64
glibc-common-2.17-78.el7.x86_64

[root@192.168.0.1 batchuser]#yum remove glibc-common-2.17-196.el7.x86_64
已加载插件：fastestmirror
正在解决依赖关系
There are unfinished transactions remaining. You might consider running yum-complete-transaction, or "yum-complete-transaction --cleanup-only" and "yum history redo last", first to finish them. If those don't work you'll have to try removing/installing packages by hand (maybe package-cleanup can help).
程序 yum-complete-transaction 在 yum-utils 软件包中。
--> 正在检查事务
---> 软件包 glibc-common.x86_64.0.2.17-196.el7 将被 删除
--> 解决依赖关系完成

依赖关系解决

===&#