[LON-CAPA-users] YUM problem with tre-common on CentOS 7

D G Teed donald.teed at gmail.com
Tue Aug 20 08:22:12 EDT 2019


Hello,

I've just migrated our Redhat 6 Lon-Capa to CentOS 7.

It seems the site is working OK.  When I did a yum update recently there is
a conflict with tre-common being provided by both epel and loncapa-updates

I tried exclude=tre-common within /etc/yum.repos.d/epel.repo
and did yum clean all followed by yum update. Same error as previously.

This package wasn't part of the R dependencies on the previous OS version
so I can't compare to how it was satisfied on the previous server.

I  think the problem is that tre comes from epel and lists a dependency and
version found only
on epel of tre-common,  while loncapa-updates provides tre-common but not
the matching tre so
it isn't possible to make epel not provide tre packages.

# yum list tre-common
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
* base: mirror.calgah.com
* epel: epel.mirror.constant.com
* extras: mirror.its.dal.ca
* updates: mirror.calgah.com
Installed Packages
tre-common.noarch                          0.8.0-18.20140228gitc2f5d13.el7
                                 @epel
Available Packages
tre-common.noarch
                         0.8.0-18.20140228gitc2f5d13.el7.centos
                          loncapa-updates-noarch

# yum list tre
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
* base: mirror.its.dal.ca
* epel: epel.mirror.constant.com
* extras: mirror.its.dal.ca
* updates: mirror.its.dal.ca
Installed Packages
tre.x86_64
                                         0.8.0-18.20140228gitc2f5d13.el7
                                         @epel


# yum update
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
epel/x86_64/metalink

               |
 14 kB  00:00:00
* base: mirror.calgah.com
* epel: epel.mirror.constant.com
* extras: mirror.its.dal.ca
* updates: mirror.calgah.com
Resolving Dependencies
--> Running transaction check
---> Package tre-common.noarch 0:0.8.0-18.20140228gitc2f5d13.el7 will be
updated
--> Processing Dependency: tre-common = 0.8.0-18.20140228gitc2f5d13.el7 for
package: tre-0.8.0-18.20140228gitc2f5d13.el7.x86_64
---> Package tre-common.noarch 0:0.8.0-18.20140228gitc2f5d13.el7.centos
will be an update
--> Finished Dependency Resolution
Error: Package: tre-0.8.0-18.20140228gitc2f5d13.el7.x86_64 (@epel)
          Requires: tre-common = 0.8.0-18.20140228gitc2f5d13.el7
          Removing: tre-common-0.8.0-18.20140228gitc2f5d13.el7.noarch
(@epel)
              tre-common = 0.8.0-18.20140228gitc2f5d13.el7
          Updated By:
tre-common-0.8.0-18.20140228gitc2f5d13.el7.centos.noarch
(loncapa-updates-noarch)
              tre-common = 0.8.0-18.20140228gitc2f5d13.el7.centos
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
[root at sirius ~]# yum clean all
Loaded plugins: fastestmirror
Cleaning repos: base epel extras loncapa-updates-basearch
loncapa-updates-noarch updates
Cleaning up list of fastest mirrors
Other repos take up 115 M of disk space (use --verbose for details)
[root at sirius ~]# yum update
Loaded plugins: fastestmirror
Determining fastest mirrors
epel/x86_64/metalink

               |
 14 kB  00:00:00
* base: mirror.its.dal.ca
* epel: epel.mirror.constant.com
* extras: mirror.its.dal.ca
* updates: mirror.its.dal.ca
base

                               |
3.6 kB  00:00:00
epel

                               |
5.3 kB  00:00:00
extras

                             |
3.4 kB  00:00:00
loncapa-updates-basearch

           |
 951 B  00:00:00
loncapa-updates-noarch

             |
 951 B  00:00:00
updates

                            |
3.4 kB  00:00:00
(1/7): base/7/x86_64/group_gz
                                                                             |
166 kB  00:00:00
(2/7): epel/x86_64/group_gz

        |
 88 kB  00:00:00
(3/7): epel/x86_64/updateinfo
                                                                             |
999 kB  00:00:00
(4/7): extras/7/x86_64/primary_db
                                                                         |
215 kB  00:00:00
(5/7): epel/x86_64/primary_db
                                                                             |
6.8 MB  00:00:00
(6/7): base/7/x86_64/primary_db
                                                                           |
6.0 MB  00:00:00
(7/7): updates/7/x86_64/primary_db
                                                                        |
7.4 MB  00:00:00
(1/2): loncapa-updates-noarch/7/primary
                                                                   |  32 kB
 00:00:00
(2/2): loncapa-updates-basearch/7/x86_64/primary
                                                          |  31 kB
 00:00:00
loncapa-updates-basearch

                            81/81

loncapa-updates-noarch

                              65/65

Resolving Dependencies
--> Running transaction check
---> Package tre-common.noarch 0:0.8.0-18.20140228gitc2f5d13.el7 will be
updated
--> Processing Dependency: tre-common = 0.8.0-18.20140228gitc2f5d13.el7 for
package: tre-0.8.0-18.20140228gitc2f5d13.el7.x86_64
---> Package tre-common.noarch 0:0.8.0-18.20140228gitc2f5d13.el7.centos
will be an update
--> Finished Dependency Resolution
Error: Package: tre-0.8.0-18.20140228gitc2f5d13.el7.x86_64 (@epel)
          Requires: tre-common = 0.8.0-18.20140228gitc2f5d13.el7
          Removing: tre-common-0.8.0-18.20140228gitc2f5d13.el7.noarch
(@epel)
              tre-common = 0.8.0-18.20140228gitc2f5d13.el7
          Updated By:
tre-common-0.8.0-18.20140228gitc2f5d13.el7.centos.noarch
(loncapa-updates-noarch)
              tre-common = 0.8.0-18.20140228gitc2f5d13.el7.centos
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest

What do you suggest I try to resolve that issue?  I have not tried the
exclude on the lon-capa repo, but assumed
there was a reason the package exists there.

Regards,

--Donald Teed
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.lon-capa.org/pipermail/lon-capa-users/attachments/20190820/3cdaf3ee/attachment-0001.html>


More information about the LON-CAPA-users mailing list