Perhaps I'm eating my words from earlier today, but in order to get yum update to work I've had to remove bind-devel and pam-devel because of a multilib error. Presumably they were loaded when installing the development system. I've now got the update through and trying to reinstall them and I get:
[edit]
nss-devel is in the same state and possibly nss-softokn-devel and nss-softokn-freebl-devel
[/edit]
[root@server ~]# yum update
Loaded plugins: clearcenter-marketplace, fastestmirror
Setting up Update Process
ClearCenter Marketplace: fetching repositories...
Loading mirror speeds from cached hostfile
* clearos: clearos.mirrors.ovh.net
* clearos-addons: clearos.mirrors.ovh.net
* clearos-contribs: clearos.mirrors.ovh.net
* clearos-core: clearos.mirrors.ovh.net
* clearos-extras: clearos.mirrors.ovh.net
* clearos-fast-updates: download1.clearsdn.com
* clearos-updates: clearos.mirrors.ovh.net
* contribs: download1.clearsdn.com
* private-clearcenter-dyndns: download1.clearsdn.com:80
* private-clearcenter-plex: download3.clearsdn.com:80
* private-clearcenter-roundcubemail: download3.clearsdn.com:80
* private-clearcenter-smart-monitor: download2.clearsdn.com:80
* private-clearcenter-static-vpn: download2.clearsdn.com:80
Resolving Dependencies
--> Running transaction check
---> Package bind-libs.x86_64 32:9.8.2-0.37.rc1.el6_7.2 will be updated
--> Processing Dependency: bind-libs = 32:9.8.2-0.37.rc1.el6_7.2 for package: 32:bind-devel-9.8.2-0.37.rc1.el6_7.2.x86_64
---> Package bind-libs.x86_64 32:9.8.2-0.37.rc1.el6_7.4 will be an update
---> Package bind-utils.x86_64 32:9.8.2-0.37.rc1.el6_7.2 will be updated
---> Package bind-utils.x86_64 32:9.8.2-0.37.rc1.el6_7.4 will be an update
---> Package pam.x86_64 0:1.1.1-20.el6 will be updated
--> Processing Dependency: pam = 1.1.1-20.el6 for package: pam-devel-1.1.1-20.el6.x86_64
---> Package pam.x86_64 0:1.1.1-20.el6_7.1 will be an update
--> Running transaction check
---> Package bind-libs.i686 32:9.8.2-0.37.rc1.el6_7.2 will be installed
--> Processing Dependency: libcap.so.2 for package: 32:bind-libs-9.8.2-0.37.rc1.el6_7.2.i686
--> Processing Dependency: libcrypto.so.10 for package: 32:bind-libs-9.8.2-0.37.rc1.el6_7.2.i686
--> Processing Dependency: libcrypto.so.10(libcrypto.so.10) for package: 32:bind-libs-9.8.2-0.37.rc1.el6_7.2.i686
--> Processing Dependency: libdl.so.2 for package: 32:bind-libs-9.8.2-0.37.rc1.el6_7.2.i686
--> Processing Dependency: libdl.so.2(GLIBC_2.0) for package: 32:bind-libs-9.8.2-0.37.rc1.el6_7.2.i686
--> Processing Dependency: libdl.so.2(GLIBC_2.1) for package: 32:bind-libs-9.8.2-0.37.rc1.el6_7.2.i686
--> Processing Dependency: libgssapi_krb5.so.2 for package: 32:bind-libs-9.8.2-0.37.rc1.el6_7.2.i686
--> Processing Dependency: libgssapi_krb5.so.2(gssapi_krb5_2_MIT) for package: 32:bind-libs-9.8.2-0.37.rc1.el6_7.2.i686
--> Processing Dependency: libm.so.6 for package: 32:bind-libs-9.8.2-0.37.rc1.el6_7.2.i686
--> Processing Dependency: libpthread.so.0 for package: 32:bind-libs-9.8.2-0.37.rc1.el6_7.2.i686
--> Processing Dependency: libpthread.so.0(GLIBC_2.0) for package: 32:bind-libs-9.8.2-0.37.rc1.el6_7.2.i686
--> Processing Dependency: libpthread.so.0(GLIBC_2.1) for package: 32:bind-libs-9.8.2-0.37.rc1.el6_7.2.i686
--> Processing Dependency: libpthread.so.0(GLIBC_2.3.2) for package: 32:bind-libs-9.8.2-0.37.rc1.el6_7.2.i686
--> Processing Dependency: libxml2.so.2 for package: 32:bind-libs-9.8.2-0.37.rc1.el6_7.2.i686
--> Processing Dependency: libxml2.so.2(LIBXML2_2.6.0) for package: 32:bind-libs-9.8.2-0.37.rc1.el6_7.2.i686
--> Processing Dependency: libz.so.1 for package: 32:bind-libs-9.8.2-0.37.rc1.el6_7.2.i686
--> Processing Dependency: libc.so.6(GLIBC_2.4) for package: 32:bind-libs-9.8.2-0.37.rc1.el6_7.2.i686
---> Package bind-libs.x86_64 32:9.8.2-0.37.rc1.el6_7.2 will be updated
---> Package pam.i686 0:1.1.1-20.el6 will be installed
--> Processing Dependency: libaudit.so.1 for package: pam-1.1.1-20.el6.i686
--> Processing Dependency: libcrack.so.2 for package: pam-1.1.1-20.el6.i686
--> Processing Dependency: libdb-4.7.so for package: pam-1.1.1-20.el6.i686
--> Processing Dependency: libselinux.so.1 for package: pam-1.1.1-20.el6.i686
---> Package pam.x86_64 0:1.1.1-20.el6 will be updated
--> Running transaction check
---> Package audit-libs.i686 0:2.3.7-5.el6 will be installed
---> Package cracklib.i686 0:2.8.16-4.el6 will be installed
---> Package db4.i686 0:4.7.25-19.el6_6 will be installed
---> Package glibc.i686 0:2.12-1.166.el6_7.1 will be installed
--> Processing Dependency: libfreebl3.so for package: glibc-2.12-1.166.el6_7.1.i686
--> Processing Dependency: libfreebl3.so(NSSRAWHASH_3.12.3) for package: glibc-2.12-1.166.el6_7.1.i686
---> Package krb5-libs.i686 0:1.10.3-42.el6 will be installed
--> Processing Dependency: libcom_err.so.2 for package: krb5-libs-1.10.3-42.el6.i686
--> Processing Dependency: libkeyutils.so.1 for package: krb5-libs-1.10.3-42.el6.i686
--> Processing Dependency: libkeyutils.so.1(KEYUTILS_0.3) for package: krb5-libs-1.10.3-42.el6.i686
---> Package libcap.i686 0:2.16-5.5.el6 will be installed
--> Processing Dependency: libattr.so.1 for package: libcap-2.16-5.5.el6.i686
--> Processing Dependency: libattr.so.1(ATTR_1.0) for package: libcap-2.16-5.5.el6.i686
---> Package libselinux.i686 0:2.0.94-5.8.el6 will be installed
---> Package libxml2.i686 0:2.7.6-20.el6 will be installed
---> Package openssl.i686 0:1.0.1e-42.el6 will be installed
---> Package zlib.i686 0:1.2.3-29.el6 will be installed
--> Running transaction check
---> Package keyutils-libs.i686 0:1.4-5.el6 will be installed
---> Package libattr.i686 0:2.4.44-7.el6 will be installed
---> Package libcom_err.i686 0:1.41.12-22.el6 will be installed
---> Package nss-softokn-freebl.i686 0:3.14.3-22.el6_6 will be installed
--> Finished Dependency Resolution
Error: Multilib version problems found. This often means that the root
cause is something else and multilib version checking is just
pointing out that there is a problem. Eg.:
1. You have an upgrade for bind-libs which is missing some
dependency that another package requires. Yum is trying to
solve this by installing an older version of bind-libs of the
different architecture. If you exclude the bad architecture
yum will tell you what the root cause is (which package
requires what). You can try redoing the upgrade with
--exclude bind-libs.otherarch ... this should give you an error
message showing the root cause of the problem.
2. You have multiple architectures of bind-libs installed, but
yum can only see an upgrade for one of those arcitectures.
If you don't want/need both architectures anymore then you
can remove the one with the missing update and everything
will work.
3. You have duplicate versions of bind-libs installed already.
You can use "yum check" to get yum show these errors.
...you can also use --setopt=protected_multilib=false to remove
this checking, however this is almost never the correct thing to
do as something else is very likely to go wrong (often causing
much more problems).
Protected multilib versions: 32:bind-libs-9.8.2-0.37.rc1.el6_7.2.i686 != 32:bind-libs-9.8.2-0.37.rc1.el6_7.4.x86_64
Error: Protected multilib versions: pam-1.1.1-20.el6_7.1.x86_64 != pam-1.1.1-20.el6.i686
Error: Protected multilib versions: nss-softokn-freebl-3.14.3-22.el6_6.i686 != nss-softokn-freebl-3.14.3-23.el6_7.x86_64
[edit]
nss-devel is in the same state and possibly nss-softokn-devel and nss-softokn-freebl-devel
[/edit]
Share this post:
Responses (12)
-
Accepted Answer
Nick Howitt wrote:
It is still the same. Can't install pam-devel and bind-devel without downgrading packages etc.
When is 6.7 likely to be released?
Hi Nick. Unfortunately, I don't have an answer to that question and it is one that I have asked repeatedly. I have asked those with the power to pull the trigger to answer your post. -
Accepted Answer
-
Accepted Answer
Hi Nick, on my system which just updated to 6.7.0 beta 1 it has new clearos-centos repo and clearos-centos-updates rather than clearos-core. These new repos have the x86_64 version of bind-libs? perhaps clearos-core is still default for users who haven't upgraded to the beta yet
[root@leonardo ~]# yum list bind-libs
Loaded plugins: clearcenter-marketplace, fastestmirror
ClearCenter Marketplace: fetching repositories...
Loading mirror speeds from cached hostfile
* clearos: www.mirrorservice.org
* clearos-addons: www.mirrorservice.org
* clearos-centos: mirror.ukhost4u.com
* clearos-centos-updates: centos.mirroring.pulsant.co.uk
* clearos-extras: www.mirrorservice.org
* clearos-fast-updates: download1.clearsdn.com
* clearos-updates: www.mirrorservice.org
* clearos-updates-testing: www.mirrorservice.org
* contribs: download1.clearsdn.com
* private-clearcenter-dyndns: download2.clearsdn.com:80
* zarafa-community-71: download2.clearsdn.com
Installed Packages
bind-libs.x86_64 32:9.8.2-0.37.rc1.el6_7.4 @clearos-centos-updates
Available Packages
bind-libs.i686 32:9.8.2-0.37.rc1.el6_7.4 clearos-centos-updates -
Accepted Answer
I've rolled back nss-softokn* which has allowed me to install nss-devel. I cannot install pam-devel or bind-devel. If I exclude the clearos-updates repo, as that tries to update nss-softokn* to an incompatible version I get a multilib error where it seems to be trying to install i686 packages:
If I leave clearos-updates enabled then the versions of nss-softokn* are in a mess:[root@server ~]# yum install pam-devel --disablerepo=clearos-updates Loaded plugins: clearcenter-marketplace, fastestmirror
Setting up Install Process
ClearCenter Marketplace: fetching repositories...
Loading mirror speeds from cached hostfile
* clearos: clearos.mirrors.ovh.net
* clearos-addons: clearos.mirrors.ovh.net
* clearos-contribs: clearos.mirrors.ovh.net
* clearos-core: clearos.mirrors.ovh.net
* clearos-extras: clearos.mirrors.ovh.net
* clearos-fast-updates: download3.clearsdn.com
* contribs: download3.clearsdn.com
* private-clearcenter-dyndns: download1.clearsdn.com:80
* private-clearcenter-plex: download2.clearsdn.com:80
* private-clearcenter-roundcubemail: download3.clearsdn.com:80
* private-clearcenter-smart-monitor: download3.clearsdn.com:80
* private-clearcenter-static-vpn: download1.clearsdn.com:80
Resolving Dependencies
--> Running transaction check
---> Package pam-devel.x86_64 0:1.1.1-20.el6 will be installed
--> Processing Dependency: pam = 1.1.1-20.el6 for package: pam-devel-1.1.1-20.el6.x86_64
--> Running transaction check
---> Package pam.i686 0:1.1.1-20.el6 will be installed
--> Processing Dependency: libaudit.so.1 for package: pam-1.1.1-20.el6.i686
--> Processing Dependency: libcrack.so.2 for package: pam-1.1.1-20.el6.i686
--> Processing Dependency: libcrypt.so.1 for package: pam-1.1.1-20.el6.i686
--> Processing Dependency: libcrypt.so.1(GLIBC_2.0) for package: pam-1.1.1-20.el6.i686
--> Processing Dependency: libdb-4.7.so for package: pam-1.1.1-20.el6.i686
--> Processing Dependency: libdl.so.2 for package: pam-1.1.1-20.el6.i686
--> Processing Dependency: libdl.so.2(GLIBC_2.0) for package: pam-1.1.1-20.el6.i686
--> Processing Dependency: libdl.so.2(GLIBC_2.1) for package: pam-1.1.1-20.el6.i686
--> Processing Dependency: libnsl.so.1 for package: pam-1.1.1-20.el6.i686
--> Processing Dependency: libnsl.so.1(GLIBC_2.0) for package: pam-1.1.1-20.el6.i686
--> Processing Dependency: libselinux.so.1 for package: pam-1.1.1-20.el6.i686
--> Processing Dependency: libutil.so.1 for package: pam-1.1.1-20.el6.i686
--> Processing Dependency: libutil.so.1(GLIBC_2.0) for package: pam-1.1.1-20.el6.i686
--> Processing Dependency: libc.so.6(GLIBC_2.9) for package: pam-1.1.1-20.el6.i686
--> Running transaction check
---> Package audit-libs.i686 0:2.3.7-5.el6 will be installed
---> Package cracklib.i686 0:2.8.16-4.el6 will be installed
---> Package db4.i686 0:4.7.25-19.el6_6 will be installed
---> Package glibc.i686 0:2.12-1.166.el6_7.1 will be installed
--> Processing Dependency: libfreebl3.so for package: glibc-2.12-1.166.el6_7.1.i686
--> Processing Dependency: libfreebl3.so(NSSRAWHASH_3.12.3) for package: glibc-2.12-1.166.el6_7.1.i686
---> Package libselinux.i686 0:2.0.94-5.8.el6 will be installed
--> Running transaction check
---> Package nss-softokn-freebl.i686 0:3.14.3-22.el6_6 will be installed
--> Finished Dependency Resolution
Error: Multilib version problems found. This often means that the root
cause is something else and multilib version checking is just
pointing out that there is a problem. Eg.:
1. You have an upgrade for pam which is missing some
dependency that another package requires. Yum is trying to
solve this by installing an older version of pam of the
different architecture. If you exclude the bad architecture
yum will tell you what the root cause is (which package
requires what). You can try redoing the upgrade with
--exclude pam.otherarch ... this should give you an error
message showing the root cause of the problem.
2. You have multiple architectures of pam installed, but
yum can only see an upgrade for one of those arcitectures.
If you don't want/need both architectures anymore then you
can remove the one with the missing update and everything
will work.
3. You have duplicate versions of pam installed already.
You can use "yum check" to get yum show these errors.
...you can also use --setopt=protected_multilib=false to remove
this checking, however this is almost never the correct thing to
do as something else is very likely to go wrong (often causing
much more problems).
Protected multilib versions: pam-1.1.1-20.el6.i686 != pam-1.1.1-20.el6_7.1.x86_64
[root@server ~]# yum install pam-devel
Loaded plugins: clearcenter-marketplace, fastestmirror
Setting up Install Process
ClearCenter Marketplace: fetching repositories...
Loading mirror speeds from cached hostfile
* clearos: clearos.mirrors.ovh.net
* clearos-addons: clearos.mirrors.ovh.net
* clearos-contribs: clearos.mirrors.ovh.net
* clearos-core: clearos.mirrors.ovh.net
* clearos-extras: clearos.mirrors.ovh.net
* clearos-fast-updates: download1.clearsdn.com
* clearos-updates: clearos.mirrors.ovh.net
* contribs: download1.clearsdn.com
* private-clearcenter-dyndns: download1.clearsdn.com:80
* private-clearcenter-plex: download3.clearsdn.com:80
* private-clearcenter-roundcubemail: download1.clearsdn.com:80
* private-clearcenter-smart-monitor: download1.clearsdn.com:80
* private-clearcenter-static-vpn: download3.clearsdn.com:80
Resolving Dependencies
--> Running transaction check
---> Package pam-devel.x86_64 0:1.1.1-20.el6 will be installed
--> Processing Dependency: pam = 1.1.1-20.el6 for package: pam-devel-1.1.1-20.el6.x86_64
--> Running transaction check
---> Package pam.i686 0:1.1.1-20.el6 will be installed
--> Processing Dependency: libaudit.so.1 for package: pam-1.1.1-20.el6.i686
--> Processing Dependency: libcrack.so.2 for package: pam-1.1.1-20.el6.i686
--> Processing Dependency: libcrypt.so.1 for package: pam-1.1.1-20.el6.i686
--> Processing Dependency: libcrypt.so.1(GLIBC_2.0) for package: pam-1.1.1-20.el6.i686
--> Processing Dependency: libdb-4.7.so for package: pam-1.1.1-20.el6.i686
--> Processing Dependency: libdl.so.2 for package: pam-1.1.1-20.el6.i686
--> Processing Dependency: libdl.so.2(GLIBC_2.0) for package: pam-1.1.1-20.el6.i686
--> Processing Dependency: libdl.so.2(GLIBC_2.1) for package: pam-1.1.1-20.el6.i686
--> Processing Dependency: libnsl.so.1 for package: pam-1.1.1-20.el6.i686
--> Processing Dependency: libnsl.so.1(GLIBC_2.0) for package: pam-1.1.1-20.el6.i686
--> Processing Dependency: libselinux.so.1 for package: pam-1.1.1-20.el6.i686
--> Processing Dependency: libutil.so.1 for package: pam-1.1.1-20.el6.i686
--> Processing Dependency: libutil.so.1(GLIBC_2.0) for package: pam-1.1.1-20.el6.i686
--> Processing Dependency: libc.so.6(GLIBC_2.9) for package: pam-1.1.1-20.el6.i686
--> Running transaction check
---> Package audit-libs.i686 0:2.3.7-5.el6 will be installed
---> Package cracklib.i686 0:2.8.16-4.el6 will be installed
---> Package db4.i686 0:4.7.25-19.el6_6 will be installed
---> Package glibc.i686 0:2.12-1.166.el6_7.1 will be installed
--> Processing Dependency: libfreebl3.so for package: glibc-2.12-1.166.el6_7.1.i686
--> Processing Dependency: libfreebl3.so(NSSRAWHASH_3.12.3) for package: glibc-2.12-1.166.el6_7.1.i686
---> Package libselinux.i686 0:2.0.94-5.8.el6 will be installed
--> Running transaction check
---> Package nss-softokn-freebl.i686 0:3.14.3-22.el6_6 will be installed
---> Package nss-softokn-freebl.x86_64 0:3.14.3-22.el6_6 will be updated
--> Processing Dependency: nss-softokn-freebl(x86-64) = 3.14.3-22.el6_6 for package: nss-softokn-freebl-devel-3.14.3-22.el6_6.x86_64
---> Package nss-softokn-freebl.x86_64 0:3.14.3-23.el6_7 will be an update
--> Finished Dependency Resolution
Error: Package: nss-softokn-freebl-devel-3.14.3-22.el6_6.x86_64 (@clearos-core)
Requires: nss-softokn-freebl(x86-64) = 3.14.3-22.el6_6
Removing: nss-softokn-freebl-3.14.3-22.el6_6.x86_64 (@clearos)
nss-softokn-freebl(x86-64) = 3.14.3-22.el6_6
Updated By: nss-softokn-freebl-3.14.3-23.el6_7.x86_64 (clearos-updates)
nss-softokn-freebl(x86-64) = 3.14.3-23.el6_7
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
Has ClearOS 6.6 been abandoned in favour of the pending 6.7 as this problem has been around for a while and it seems that only upgrading to 6.7beta fixes it?
Oh, and having rolled back nss-softokn* to get nss-devel installed, of course yum update is now broken because it tries to update nss-softokn* but is not allowed to because of the dependencies from nss-devel. -
Accepted Answer
-
Accepted Answer
No chance for me. I do not even have the i686 package installed. I can get nss-softokn* (v3.14.3-23.el6_7) installed on their own and they come from clearos-updates. If I install that I cannot install nss-devel (v3.19.1-3.el6_6.x86_64 from clearos-core).
If I leave nss-devel installed I cannot run yum update as it tries and fails to update nss-sortokn*
I do not have a combination which allows me to install bind-devel and pam-devel.
Fortunately all these packages were installed with the development environment and I don't need them right now, but I will when I next need to compile libreswan.
I really wish the devs would sort this out without me having to raise another bug report but so far they show little interest. -
Accepted Answer
Nick Howitt wrote:
I really wish the devs would sort this out without me having to raise another bug report but so far they show little interest.
Hi Nick. It's a basic flaw in the way the build/repo system was put together in ClearOS 6. Add in the chaos created from the CentOS 6.0 organizational issues (which forced our hand to rebuild RHEL ourselves) and voila -- a mess. Fortunately, it really only impacts command line hackers. Starting with ClearOS 6.7, we are migrating from "ClearOS Core" to "CentOS", so that will remove one problematic area. Regardless, the underlying build system flaws in 6 remain and it's just something we're just going to have to live with in 6.
The new build system and repo policies for ClearOS 7 are much more sane. The "xyz-devel" packages will now land in the same repo as the "xyz" parent package and we won't see much library mismatching any more. See? We showed some interest As for the 32-bit library shenanigans, that will continue to be a pain. I wish CentOS would just drop 32-bit support in 64-bit systems... it's just not worth it. It's just way too easy to accidentally install 32-bit binaries. I NEVER WANT 32-bit binaries on my systems... ever.
Hmmm... I wonder if there's an option in yum. -
Accepted Answer
@Peter,
Thanks for a bit of interest although the issue has been going on for over 2 weeks now.
Another little play. It seems you can ignore 32bit packages by adding "--exclude=*.i386,*.i686" to your yum command. You can add this to the basic yum configuration in the same way I exclude all kernel updates (until I want them). Add this to yum.conf:
This fixes the multilib problem and should probably be pushed into all x64 installations.exclude=kernel,kernel-devel,kernel-firmware,kernel-headers,*.i386,*.i686
Unfortunately gets you back into the same problems as nss where the -devel packages in clearos-core are lagging the installed packages in clearos-updates:[root@server ~]# yum install bind-devel pam-devel
<snip>
Resolving Dependencies
--> Running transaction check
---> Package bind-devel.x86_64 32:9.8.2-0.37.rc1.el6_7.2 will be installed
--> Processing Dependency: bind-libs = 32:9.8.2-0.37.rc1.el6_7.2 for package: 32:bind-devel-9.8.2-0.37.rc1.el6_7.2.x86_64
---> Package pam-devel.x86_64 0:1.1.1-20.el6 will be installed
--> Processing Dependency: pam = 1.1.1-20.el6 for package: pam-devel-1.1.1-20.el6.x86_64
--> Finished Dependency Resolution
Error: Package: 32:bind-devel-9.8.2-0.37.rc1.el6_7.2.x86_64 (clearos-core)
Requires: bind-libs = 32:9.8.2-0.37.rc1.el6_7.2
Installed: 32:bind-libs-9.8.2-0.37.rc1.el6_7.4.x86_64 (@clearos-updates)
bind-libs = 32:9.8.2-0.37.rc1.el6_7.4
Available: 32:bind-libs-9.8.2-0.30.rc1.el6_6.1.x86_64 (clearos)
bind-libs = 32:9.8.2-0.30.rc1.el6_6.1
Available: 32:bind-libs-9.8.2-0.37.rc1.el6_7.2.x86_64 (clearos-core)
bind-libs = 32:9.8.2-0.37.rc1.el6_7.2
Error: Package: pam-devel-1.1.1-20.el6.x86_64 (clearos-core)
Requires: pam = 1.1.1-20.el6
Installed: pam-1.1.1-20.el6_7.1.x86_64 (@clearos-updates)
pam = 1.1.1-20.el6_7.1
Available: pam-1.1.1-20.el6.x86_64 (clearos)
pam = 1.1.1-20.el6
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
Also, why are there "rc1" packages in clearos, clearos-core and clearos-updates? -
Accepted Answer
-
Accepted Answer
Nick Howitt wrote:
When is 6.7 likely to be released?
Good morning Nick. ClearOS 6.7 has been in the works for a while now, but we've found some issues that we've been coding through and resolving.
This Saturday we'll be building an internal ISO for testing and if all goes well, we hope to release next week.
More to come! -
Accepted Answer
Devin Johnson wrote:
That's good news. Judging by Tim's posts it will fix the repo issue.
Nick Howitt wrote:
When is 6.7 likely to be released?
Good morning Nick. ClearOS 6.7 has been in the works for a while now, but we've found some issues that we've been coding through and resolving.
This Saturday we'll be building an internal ISO for testing and if all goes well, we hope to release next week.
More to come! -
Accepted Answer
Please login to post a reply
You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here.
Register Here »