Re: 7.4

2017-06-23 Thread Todd Chester 

On 06/23/2017 03:04 PM, Steven Haigh wrote:

On Saturday, 24 June 2017 3:32:02 AM AEST ToddAndMargo wrote:

On 06/23/2017 07:28 AM, Sean A wrote:

Are you all referring to RHEL 7.4 Beta?

Given recent history on the past 2 releases, I would put my money on 7.4
GA in Nov. 2017.  Scientific probably not until Jan 2018.

Just 7.4.  When Red Hat Bugzilla notifies me they
have fixed something, they say they fixed it in 7.4.

The way RH sounds, RHEL is already on 7.4, but I
haven't checked.


Nope:

$ cat /etc/redhat-release
Red Hat Enterprise Linux Server release 7.3 (Maipo)



Sounds to me like RH has lost interest in fixing anything in 7.3

Re: 7.4

2017-06-23 Thread Steven Haigh 
On Saturday, 24 June 2017 3:32:02 AM AEST ToddAndMargo wrote:
> On 06/23/2017 07:28 AM, Sean A wrote:
> > Are you all referring to RHEL 7.4 Beta?
> > 
> > Given recent history on the past 2 releases, I would put my money on 7.4
> > GA in Nov. 2017.  Scientific probably not until Jan 2018.
> Just 7.4.  When Red Hat Bugzilla notifies me they
> have fixed something, they say they fixed it in 7.4.
> 
> The way RH sounds, RHEL is already on 7.4, but I
> haven't checked.

Nope:

$ cat /etc/redhat-release
Red Hat Enterprise Linux Server release 7.3 (Maipo)

-- 
Steven Haigh

 net...@crc.id.au   http://www.crc.id.au
 +61 (3) 9001 6090  0412 935 897

signature.asc
Description: This is a digitally signed message part.

Re: 7.4

2017-06-23 Thread Jos Vos 
On Fri, Jun 23, 2017 at 10:32:02AM -0700, ToddAndMargo wrote:

> The way RH sounds, RHEL is already on 7.4, but I
> haven't checked.

Only 7.4 *beta* is out for a month now.  So the final 7.4 might still
take a few months from now.

-- 
--Jos Vos 
--X/OS Experts in Open Systems BV   |   Office: +31 20 6938364
--Amsterdam, The Netherlands|   Mobile: +31 6 26216181

Re: 7.4

2017-06-23 Thread ToddAndMargo 

On 06/23/2017 07:28 AM, Sean A wrote:

Are you all referring to RHEL 7.4 Beta?

Given recent history on the past 2 releases, I would put my money on 7.4 GA in 
Nov. 2017.  Scientific probably not until Jan 2018.



Just 7.4.  When Red Hat Bugzilla notifies me they
have fixed something, they say they fixed it in 7.4.

The way RH sounds, RHEL is already on 7.4, but I
haven't checked.

Re: Updateinfo file is not valid XML

2017-06-23 Thread Sean A 
Did you successfully update with EPEL disabled?

The post linked, regards problems with NSS being out of date, there were 
several other google results with similar info.  We update daily with yum-cron, 
and I still had this come up this week with the EPEL signatures not matching, 
the problem did not affect my CentOS 7 systems, only my SL7 systems.  That 
alone implied it was not an EPEL repo problem.

Anyway, after the yum clean, then updating with EPEL disabled, everything is 
fine, just as the post suggested.

Re: 7.4

2017-06-23 Thread Sean A 
Are you all referring to RHEL 7.4 Beta?  

Given recent history on the past 2 releases, I would put my money on 7.4 GA in 
Nov. 2017.  Scientific probably not until Jan 2018.

Re: Updateinfo file is not valid XML

2017-06-23 Thread Maarten 
I have already run yum clean all and that does not seem to help. All my
repos are all active including third party repos, I use protectbase to

protect the base system. So don't think that is a solution for everyone.
Will see if I get any more of those messages though, if not epel

probably has fixed something  on their side.


On 06/23/2017 04:21 PM, Sean A wrote:
> yum --disablerepo=epel upgrade -y

Re: Updateinfo file is not valid XML

2017-06-23 Thread Sean A 
From what I can tell this issue seems to be similar to the reasons given here: 
https://unix.stackexchange.com/questions/148144/unable-to-pull-epel-repository-metadata#163368
 and not in SL7 or EPEL repos.

My systems are not having that error message now that I've run:
yum clean all
yum --disablerepo=epel upgrade -y
yum upgrade -y