------------ Original Message ------------ > Date: Thursday, March 26, 2015 16:32:12 -0500 > From: Les Mikesell <lesmikesell at gmail.com> > > On Thu, Mar 26, 2015 at 4:27 PM, Richard > <lists-centos at listmail.innovate.net> wrote: >> >> >> ------------ Original Message ------------ >>> Date: Thursday, March 26, 2015 16:18:45 -0500 >>> From: Les Mikesell <lesmikesell at gmail.com> >>> >>> On Thu, Mar 26, 2015 at 4:09 PM, Richard >>> <lists-centos at listmail.innovate.net> wrote: >>>> >>>>> >>>>> Does anyone know what's up with: >>>>> >>>>> Error: Package: marco-1.8.3-1.el7.x86_64 (epel) >>>>> Requires: libgtop-2.0.so.10()(64bit) >>>>> >>>>> Isn't the EPEL package built against stock Centos? >>>> >>>> >>>> Check epel-testing, that's where it (still) was a few days ago I >>>> believe. [I don't have my C7 laptop on so can't confirm things >>>> quickly.] >>>> >>> >>> Thanks, but it doesn't help to --enablerepo=epel-testing. The >>> libgtop2 package should be from the base repo anyway. >> >> Sorry, just checked. It looks to be in "cr". > > So... the right thing to do for someone who just wants to update a > system today would be??? Probably depends on your view of CR. Here's the announcement for it the other day: <http://lists.centos.org/pipermail/centos-announce/2015-March/020980.html> I updated a machine the other day with a combination of CR and epel-testing (key MATE things were there still) and it seems fine, though I haven't tested it heavily yet. The epel things that were in -testing may have moved to epel base by now.