Now don't go bugging people asking when CentOS 6.7 will be out. "When it's ready."
In upgrading from RHEL 6.6 to 6.7, I did find that I had to disable my 3rd party repos (elrepo and epel) in order to avoid yum erroring out. Plus I did the usual "yum clean all". (I don't use the PackageKit GUI as it's been unable to complete for quite a few months without dumping core.)
Devin
On Thu, Jul 23, 2015 at 8:02 PM, Devin Reade gdr@gno.org wrote:
In upgrading from RHEL 6.6 to 6.7, I did find that I had to disable my 3rd party repos (elrepo and epel) in order to avoid yum erroring out.
Can you elaborate on this? What yum error(s) did you see? I updated a RHEL 6.6 system with ELRepo enabled (but no EPEL packages) to RHEL 6.7 using 'yum update' without any issue.
Akemi
On 24/07/15 07:40, Akemi Yagi wrote:
On Thu, Jul 23, 2015 at 8:02 PM, Devin Reade gdr@gno.org wrote:
In upgrading from RHEL 6.6 to 6.7, I did find that I had to disable my 3rd party repos (elrepo and epel) in order to avoid yum erroring out.
Can you elaborate on this? What yum error(s) did you see? I updated a RHEL 6.6 system with ELRepo enabled (but no EPEL packages) to RHEL 6.7 using 'yum update' without any issue.
Akemi
Same here - I updated RHEL 6.6 systems yesterday with elrepo enabled with no issues whatsoever. I don't have EPEL installed so perhaps that was the issue rather than elrepo?
--On Thursday, July 23, 2015 11:40:21 PM -0700 Akemi Yagi amyagi@gmail.com wrote:
On Thu, Jul 23, 2015 at 8:02 PM, Devin Reade gdr@gno.org wrote:
In upgrading from RHEL 6.6 to 6.7, I did find that I had to disable my 3rd party repos (elrepo and epel) in order to avoid yum erroring out.
Can you elaborate on this? What yum error(s) did you see? I updated a RHEL 6.6 system with ELRepo enabled (but no EPEL packages) to RHEL 6.7 using 'yum update' without any issue.
Unfortunately I no longer have the specific messages available, but it was one of those ones where something didn't like the specific versions of available dependent packages. Whether or not it would impact a given system would likely depend exactly on what was installed.
It's also possible that there is some left over cruft somewhere on the system that feeds into the problem. It's been updated regularly since the first RHEL 6.0 came out and at time has had epel, elrepo, and at one point rpmforge RPMs installed.
Reenabling the 3rd party repos after the update was not an issue.
Mostly the email was a heads-up with a simple solution should anyone else run into problems.
Devin
Am 05.08.2015 um 17:19 schrieb Alan McKay alan.mckay@gmail.com:
Any ETA on when CentOS 6.7 will exit the CR phase?
fourth paragraph: http://lists.centos.org/pipermail/centos/2015-July/153859.html
-- LF
-
Akemi Yagi -
Alan McKay -
Devin Reade -
Leon Fauster -
Ned Slider