Forums

Resolved
0 votes
Hi,

Have you any idea when 6.8 will be released?

For months now I've had yum update failing because of krb5-libs, libselinux and openssl packages are behind their devel versions. I know I can remove the devel packages but there have been no other updates since around May/June so the failing packages are not blocking anything. I'm hoping 6.8 will sort things.

TIA,

Nick
Tuesday, September 20 2016, 04:53 PM
Share this post:
Responses (16)
  • Accepted Answer

    Friday, December 09 2016, 09:55 AM - #Permalink
    Resolved
    0 votes
    Looks like some of ClearOS 6.8 has been hanging around right from early July according to my log... see below

    CentOS 6.8, on which ClearOS 6.8 is based, was released on May 25 2016...
    https://lists.centos.org/pipermail/centos-announce/2016-May/021895.html
    https://linux.slashdot.org/story/16/05/25/2132241/centos-linux-68-released

    It has now taken Clear over 7 months to do the update... and we are still waiting for the official release...

    [root@danda ~]# cat /etc/*release*
    ClearOS Community release 6.8.0 (Final)
    ClearOS Community release 6.8.0 (Final)
    ClearOS Community release 6.8.0 (Final)
    cpe:/o:redhat:enterprise_linux:6:ga:community
    [root@danda ~]# ls -lad /etc/*release*
    -rw-r--r-- 1 root root 40 Jul 7 02:37 /etc/clearos-release
    lrwxrwxrwx 1 root root 15 Jul 7 13:24 /etc/redhat-release -> clearos-release
    lrwxrwxrwx 1 root root 15 Jul 7 13:24 /etc/system-release -> clearos-release
    -rw-r--r-- 1 root root 46 Jul 7 02:37 /etc/system-release-cpe
    [root@danda ~]# rpm -q --whatprovides /etc/redhat-release
    clearos-release-community-6-6.8.0.2.v6.noarch
    [root@danda ~]# grep "clearos-release-community-6-6.8.0.2.v6.noarch" /var/log/yum.log
    Jul 07 13:24:39 Updated: clearos-release-community-6-6.8.0.2.v6.noarch
    [root@danda ~]#


    To date have not had any problems with 6.8 - wish 7.2 was as good...
    The reply is currently minimized Show
  • Accepted Answer

    Friday, December 09 2016, 09:34 AM - #Permalink
    Resolved
    0 votes
    This is what I got from COS support

    These updates are coming soon and will hit your system automatically. You can pre-empt this by updating using the updates-testing repos but this effectively downgrade your subscription to community.


    This was on 7 November - so not sure what soon means!
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, December 08 2016, 08:54 PM - #Permalink
    Resolved
    0 votes
    I bit the bullet and went for 7.2. Now I'm waiting for 7.3 :S
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, December 08 2016, 08:38 PM - #Permalink
    Resolved
    0 votes
    Any news on the release of 6.8? the end of support is coming up, not sure how much effort will be put into making this version available so late in the game, but I still like to have it.
    The reply is currently minimized Show
  • Accepted Answer

    Monday, October 24 2016, 09:13 PM - #Permalink
    Resolved
    0 votes
    Hi All,

    I will be on hiatus from ClearOS until December 1. Hopefully, ClearOS 6.8 will be released before my return!
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, October 20 2016, 06:06 PM - #Permalink
    Resolved
    0 votes
    Nick Howitt wrote:

    7.2 was harder than expected and I began to think about abandoning it because of a major gotcha. My installation was done by prepping the disk on an old PC then moving the disk. As such the interfaces were going to change. I was happy with this, expecting to configure them at the console. Unfortunately, to identify the interfaces easily, I left one connected and one disconnected. It turns out that in this state you cannot get onto the graphical console. It just hangs. Other symptoms are that LDAP won't start, nor will other bits. I tore my hair out on this one for a long while and nearly abandoned it. Finally as the interface I'd left connected was the WAN and it was already configured for OpenVPN, I managed to get to the webconfig using a data connection to my phone and OpenVPN!

    There are some more bugs:
    1 - Config back up from 6.x and restore to 7.x does not bring in the cyrus-imap certificate and my clients complained about the new certificate
    2 - the samba start up script does not correct the "interfaces" line in smb.conf, so the new (LAN) interface was not found and smb and nmb failed
    3 - fail2ban defaults to firewall-cmd and not iptables. This should possibly be fixed in the clearos-epel repo.


    Sorry to hear you are having problms with 7.2.
    I'd the same experience with 7.2 which was installed on a different PC and then moved to another with the NIC
    The DHCP server could get connect properly and i'd load of WAN warnings (see my post) and did not had a WAN connection......
    I've solved by putting the server on a static IP, which is not logic but it works for now
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, October 20 2016, 01:06 PM - #Permalink
    Resolved
    0 votes
    7.2 was harder than expected and I began to think about abandoning it because of a major gotcha. My installation was done by prepping the disk on an old PC then moving the disk. As such the interfaces were going to change. I was happy with this, expecting to configure them at the console. Unfortunately, to identify the interfaces easily, I left one connected and one disconnected. It turns out that in this state you cannot get onto the graphical console. It just hangs. Other symptoms are that LDAP won't start, nor will other bits. I tore my hair out on this one for a long while and nearly abandoned it. Finally as the interface I'd left connected was the WAN and it was already configured for OpenVPN, I managed to get to the webconfig using a data connection to my phone and OpenVPN!

    There are some more bugs:
    1 - Config back up from 6.x and restore to 7.x does not bring in the cyrus-imap certificate and my clients complained about the new certificate
    2 - the samba start up script does not correct the "interfaces" line in smb.conf, so the new (LAN) interface was not found and smb and nmb failed
    3 - fail2ban defaults to firewall-cmd and not iptables. This should possibly be fixed in the clearos-epel repo.
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, October 18 2016, 11:42 PM - #Permalink
    Resolved
    0 votes
    Tony Ellis is indeed running 6.8 - on 7 machines - a mixture of 32 and 64 bit - since shortly after 6.8 went into test. No problems encountered except on the 64 bit machines where the 32-bit and 64 bit rpms upgrades have gotten out of sync. The 64 bit machines need to run some 32-bit binaries, hence both rpm upgrades must be at the same level. Note that I only run a subset of ClearOS apps - no flexshares, no dnsmasq, no paid apps, no BackupPC, no Serviio etc and on one machine no ldap (though it is running ClearOS!)

    As for the comment "Just switch to 7.2 ;-) 6.x is old fashion" - I do have a 7.x test machine and when I decide it is stable enough, and I have upgraded all the apps I have written, I will migrate... fashion has not to do with it :-) suitability for purpose is... My year 2000 VW Golf still performs admirably the reason for owning it!
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, October 18 2016, 05:41 PM - #Permalink
    Resolved
    0 votes
    Patrick de Brabander wrote:
    Just switch to 7.2 ;-)
    6.x is old fashion :D :D
    I know the theory. I was struggling with the idea until the backup and restore of configs was created as I needed to get OpenVPN certificates across to support my mother and mother-in-law. I also had no real solution for e-mails while taking the e-mail server down. That is all sorted now. All that is needed now is time when the kids and wife aren't at home so I can pull the server down.
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, October 18 2016, 04:49 PM - #Permalink
    Resolved
    0 votes
    Nick Howitt wrote:

    I was waiting for the official release, but I'm hoping to switch to 7.2 on Thursday so I may never get as far as 6.8.

    I believe Tony Ellis is running 6.8.


    Just switch to 7.2 ;-)
    6.x is old fashion :D :D
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, October 18 2016, 03:07 PM - #Permalink
    Resolved
    0 votes
    I was waiting for the official release, but I'm hoping to switch to 7.2 on Thursday so I may never get as far as 6.8.

    I believe Tony Ellis is running 6.8.
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, October 18 2016, 02:59 PM - #Permalink
    Resolved
    0 votes
    Does anyone have feedback on the upgrade to 6.8?

    *bump*
    The reply is currently minimized Show
  • Accepted Answer

    Friday, September 23 2016, 04:49 PM - #Permalink
    Resolved
    0 votes
    Nick, just join the 7.2 party! :)
    Like
    1
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, September 22 2016, 04:14 PM - #Permalink
    Resolved
    0 votes
    Thanks for the reply. I'm happy to wait a bit longer. Who knows, I may even get my 7.x server going and completely skip 6.8.
    Like
    1
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, September 22 2016, 01:46 PM - #Permalink
    Resolved
    0 votes
    I hope to see 6.8.0 officially released in the next couple of weeks.
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, September 22 2016, 01:45 PM - #Permalink
    Resolved
    0 votes
    Hi Nick,

    I'm not going to get into the reasons why the release is ridiculously late (too political), but the 6.8.0 release is staged in "updates-testing" (and has been since mid-June). Here are the instructions for upgrading a ClearOS 6 system to 6.8.0:

    Step 1 -- Enable the test repositories:

    yum-config-manager --enable clearos-updates,clearos-updates-testing


    Step 2 -- If you have enabled CentOS repositories for installing other packages, you should also enable the CentOS 6.8 repositories:

    yum-config-manager --enable centos-unverified,centos-updates-unverified


    Step 3 -- Upgrade to ClearOS 6.8.0

    yum upgrade


    Step 4 -- The upgrade may disable the yum testing repositories, so you should run the above yum-config-manager commands again.
    The reply is currently minimized Show
Your Reply