Forums

Resolved
0 votes
ClearOS 7.6.0 for Community has been release. You can read more about this release on the release notes page here:

https://www.clearos.com/resources/documentation/clearos/content:en_us:announcements_releases_clearos_7.6.0_community_release_information

Please post any issues related to this release here. There are early reports of issues with Samba which was resolved by rebooting the system. If you have a Samba issue and can tolerate leaving it in the broken condition, please work with Nick who is chasing a general bug that exists in Samba.

If your update get's stuck, you want to manually install and not wait for automated updates and you want to fast track the process, run the following:

yum update app-base
yum clean all
yum update

[edit]
For all users with systems booting with UEFI (not BIOS)
Do not reboot your server until you get an updated grub2 package. You need grub2-2.02.1-0.76.v7.1 (or later) which should be installed overnight on Saturday 6th Apr/Sunday 7th Apr. You can check your version with:
rpm -q grub2

You can update manually with:
yum update grub2 --enablerepo=clearos-updates*

If you do reboot without the updated package, please follow the procedure in this post to make your system bootable again.
[/edit]
Thursday, April 04 2019, 08:33 PM
Share this post:
Responses (37)
  • Accepted Answer

    Thursday, April 04 2019, 08:45 PM - #Permalink
    Resolved
    0 votes
    For now, we've withdrawn the kernel. It creates a chicken and egg problem that we are working through. Updates are set to work automatically, this typically works like this:

    - ClearOS 7.5 - currently pointing to ClearOS-CentOS 7.5.1804
    - Day1 auto-update: the ClearOS Community systems would be updated with many files, including app-base which points the users to the core CentOS 7.6.1810 packages
    - Day2 auto-update: the rest of the updates from CentOS 7.6.1810 would be upgraded

    This is how a system would typically update. The issue this morning was that the kernel causes a conflict with some of the packages included in the first phase of packages. If you did not get app-base manually, you should get it tonight. If you have any issue (or even notice anything) you can run the update manually:

    yum update app-base
    yum clean all
    yum update
    The reply is currently minimized Show
  • Accepted Answer

    Friday, April 05 2019, 05:07 PM - #Permalink
    Resolved
    0 votes
    It looks like there is a Windows Networking issue after the upgrade. Samba may restart successfully during the upgrade, but won't restart again after that. If this happens to you, you can restart winbind with a:
    service winbind restart
    You can then restart Windows Networking or do a:
    service smb start


    [edit]
    I have removed the suggestion to restart because unless you have a further update to grub2 to grub2-2.02.1-0.76.v7.1 or later ("rpm -q grub2" to check) and you do a UEFI boot, you will hit another issue which will stop ClearOS from booting. If this happens, please see this post for a workaround.
    [/edit]
    The reply is currently minimized Show
  • Accepted Answer

    Sunday, April 07 2019, 03:41 PM - #Permalink
    Resolved
    0 votes
    The samba issue (actually it is an old one) should be fixed in http://koji.clearos.com/koji/buildinfo?buildID=2610
    The reply is currently minimized Show
  • Accepted Answer

    Sunday, April 07 2019, 03:43 PM - #Permalink
    Resolved
    0 votes
    I've built a test ISO for ClearOS 7.6 that can be found at:

    http://mirror.clearos.com/clearos/testing/7.6.0.253848/x86_64/iso/ClearOS-DVD-x86_64-7.iso

    Since 7.6 ISOs support Business, Home, and Community with support for upgrade, it is still flagged as beta.
    The reply is currently minimized Show
  • Accepted Answer

    Monday, April 08 2019, 05:02 PM - #Permalink
    Resolved
    0 votes
    I guess it will take a couple of weeks till ClearOS 7.6 reaches Home/Business?
    The reply is currently minimized Show
  • Accepted Answer

    Friday, April 12 2019, 03:54 PM - #Permalink
    Resolved
    0 votes
    Perhaps,

    You can see the burndown of the 'ClearOS 7.6' project here: https://gitlab.com/groups/clearos/-/milestones/4 (Currently at 77%)

    Once this gets to 100% you can expect for Home/Business to be pushed on the Tuesday having reached 100% (which can be on a Tuesday). Updates should flow over the next two nights (we are working to fix that two night thingy as well see - https://gitlab.com/clearos/clearfoundation/app-software-updates/issues/4).
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, April 16 2019, 07:47 PM - #Permalink
    Resolved
    0 votes
    As mentioned in some of the threads, we have had to release some aspect of the ClearOS 7.6 Community in stages. The next phase sees a resolution to the kernel issue that is outstanding and a re-merger with upstream certbot with Nick's fix to the app-lets-encrypt module. We will also be pushing a feature to the marketplace soon that will allow for more automated installs.

    To get a jump on the automated updates and to validate that your system works well with the new kernel, make sure that you either:

    1) Do nothing and let the system resolve the updates and cross your fingers that if you need to reboot at some later date that the kernel is ok. (not recommended)
    2) Let the updates happen, probably not a problem. Reboot sometime this weekend or in the evening in a few days just to make sure it comes up ok. (good)
    3) Do the updates now (yum update), reboot Report problems, if any. (better)
    3) Do the updates now (yum update), reboot Report problems or successes. (best)

    Thanks all !!!
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, April 17 2019, 06:28 AM - #Permalink
    Resolved
    0 votes
    Updated two machines with the latest 7.6 updates as of Wed Apr 17 16:20:00 AEST 2019 (Sydney Local) including kernel 3.10.0-957.10.1.v7.x86_64. Both rebooted OK and running OK (All CPUS running at 100% 24/7 courtesy of BOINC and medical research from WCG - so some stress testing...)

    These are the two machines, the test machine will be powered off if no problems over next 24 hrs...

    Glenis-Test
    May-Production-Backup
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, April 17 2019, 04:48 PM - #Permalink
    Resolved
    0 votes
    Dave Loper wrote:

    Perhaps,

    You can see the burndown of the 'ClearOS 7.6' project here: https://gitlab.com/groups/clearos/-/milestones/4 (Currently at 77%)

    Once this gets to 100% you can expect for Home/Business to be pushed on the Tuesday having reached 100% (which can be on a Tuesday). Updates should flow over the next two nights (we are working to fix that two night thingy as well see - https://gitlab.com/clearos/clearfoundation/app-software-updates/issues/4).


    Thank you Dave for the answer. Checking your links at the moment..
    The reply is currently minimized Show
  • Accepted Answer

    Mansoor
    Mansoor
    Offline
    Wednesday, April 17 2019, 10:08 PM - #Permalink
    Resolved
    0 votes
    Updated one machine, running clearOS community, to 7.6 (kernel 3.10.0-957.10.1.v7.x86_64). The machine rebooted without any issue.
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, April 18 2019, 06:21 AM - #Permalink
    Resolved
    0 votes
    Updated on 2 machines with new kernel, so far working all pretty well!
    The reply is currently minimized Show
  • Accepted Answer

    Friday, April 19 2019, 01:22 PM - #Permalink
    Resolved
    1 votes
    I installed Community in a VM. I registered the install and it did the first updates during the installation wizard. After I successfully finished the wizard I'll try to do a "yum update" I'll get this error:


    <snip>
    ---> Package xorg-x11-server-common.x86_64 0:1.19.5-5.el7 will be updated
    ---> Package xorg-x11-server-common.x86_64 0:1.19.5-5.1.el7_5.0.1 will be an update
    ---> Package yum-plugin-fastestmirror.noarch 0:1.1.31-45.el7 will be updated
    ---> Package yum-plugin-fastestmirror.noarch 0:1.1.31-46.el7_5 will be an update
    ---> Package yum-utils.noarch 0:1.1.31-45.el7 will be updated
    ---> Package yum-utils.noarch 0:1.1.31-46.el7_5 will be an update
    --> Running transaction check
    ---> Package emacs-filesystem.noarch 1:24.3-20.el7_4 will be installed
    ---> Package shim-x64.x86_64 0:12-2.el7 will be an update
    --> Processing Dependency: mokutil = 12-2.el7 for package: shim-x64-12-2.el7.x86_64
    --> Finished Dependency Resolution
    Error: Package: shim-x64-12-2.el7.x86_64 (clearos-centos-verified)
    Requires: mokutil = 12-2.el7
    Installed: mokutil-12-1.v7.x86_64 (@anaconda/7.5.0.228724)
    mokutil = 12-1.v7
    You could try using --skip-broken to work around the problem
    You could try running: rpm -Va --nofiles --nodigest
    [root@VM-Community-01 ~]#


    Going to try to fix this issue..
    Like
    1
    The reply is currently minimized Show
  • Accepted Answer

    Friday, April 19 2019, 01:25 PM - #Permalink
    Resolved
    1 votes
    I did:


    yum update app-base
    yum clean all
    yum update


    It didn't fix the issue. I'm now going to do what is suggested by yum:


    Error: Package: shim-x64-12-2.el7.x86_64 (clearos-centos-verified)
    Requires: mokutil = 12-2.el7
    Installed: mokutil-12-1.v7.x86_64 (@anaconda/7.5.0.228724)
    mokutil = 12-1.v7
    You could try using --skip-broken to work around the problem
    You could try running: rpm -Va --nofiles --nodigest
    Like
    1
    The reply is currently minimized Show
  • Accepted Answer

    Friday, April 19 2019, 01:53 PM - #Permalink
    Resolved
    0 votes
    I did what yum suggested and used:


    You could try using --skip-broken to work around the problem


    Installation goes fine now when we skip the broken packages.

    It seems that "shim-x64-12-2.el7.x86_64" need version "mokutil = 12-2.el7" but installed is " mokutil-12-1.v7.x86_64".
    The reply is currently minimized Show
  • Accepted Answer

    Friday, April 19 2019, 02:09 PM - #Permalink
    Resolved
    0 votes
    When I check "System reports" it shows still version 7.5 (see screenshot).

    With the kernel I'm on:

    [root@VM-Community-01 ~]# uname -r
    3.10.0-862.11.6.v7.x86_64
    Attachments:
    The reply is currently minimized Show
  • Accepted Answer

    Friday, April 19 2019, 02:33 PM - #Permalink
    Resolved
    0 votes
    @Marcel, the repos always give this issue as the Community version goes ahead of the Business version. The problem is that in the first 30 days of a trial licence, the Community repos don't get enabled as there is still an option to upgrade to Home or Business. You should be able to force the issue if you enable clearos-updates, clearos-centos and clearos-centos-updates either in the yum command or permanently. Dave was hoping to release Business next week, in which case it will resolve itself, but there is a lingering update issue in app-base (which no one has noticed so far), and he also wants to crack the issue of updating in one night or he will have to hold the kernel back again from Business.

    [edit]
    If it still fails, try clearos-epel as well.
    [/edit]
    The reply is currently minimized Show
  • Accepted Answer

    Friday, April 19 2019, 02:45 PM - #Permalink
    Resolved
    0 votes
    @Nick, I installed community Edition to do some testing (I registered it as community edition). You never now maybe I encounter some problems which then can be debugged... :)
    The reply is currently minimized Show
  • Accepted Answer

    Friday, April 19 2019, 06:46 PM - #Permalink
    Resolved
    0 votes
    @Nick, do I understand correctly that if you register ClearOS as Community you still have the 30 days trail? I did what you suggested and the VM is now updating.

    Update:

    The system updated okay after the suggested steps!

    After update I'm on kernel:

    3.10.0-957.10.1.v7.x86_64


    So I guess that the trail is also active after registration of the version...
    The reply is currently minimized Show
  • Accepted Answer

    Friday, April 19 2019, 08:31 PM - #Permalink
    Resolved
    0 votes
    I'll try and clarify this trial thing. There is no such thing as a trial Community Edition **but** during the first thirty days it is possible you like it so much you can relatively easily move to the Home or Business edition. In order for this to happen, ClearOS is kept on the paid-for repos and not the community repos. Much of the time the packages are the same, but different versions get slightly different access to some apps. After 30 days, if you are still on the Community Edition, the paid-for repos get disabled and the community repos get enabled.

    Your version was in this horrible period there the Community and paid-for versions were out of sync so you were trying to install some 7.6 apps without having access to the full 7.6 Community repos and it was not able to find some of the 7.6 packages it needed.
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, April 20 2019, 10:27 AM - #Permalink
    Resolved
    0 votes
    Thanks Nick! Good and clear explanation.
    The reply is currently minimized Show
  • Accepted Answer

    Sunday, April 21 2019, 04:49 PM - #Permalink
    Resolved
    0 votes
    Dave Loper wrote:

    I've built a test ISO for ClearOS 7.6 that can be found at:

    http://mirror.clearos.com/clearos/testing/7.6.0.253848/x86_64/iso/ClearOS-DVD-x86_64-7.iso

    Since 7.6 ISOs support Business, Home, and Community with support for upgrade, it is still flagged as beta.


    Tried to install this iso in KVM but after an succesfull install in won't boot. I've made a screenshot of the error.
    The reply is currently minimized Show
  • Accepted Answer

    Monday, April 22 2019, 04:01 AM - #Permalink
    Resolved
    0 votes
    This is that bad grub error that was fix. I'll see why it isn't working soon.
    The reply is currently minimized Show
  • Accepted Answer

    Monday, April 22 2019, 12:28 PM - #Permalink
    Resolved
    0 votes
    Dave, did you get rid of the suggestion page because you're releasing 7.6? I think an 'Acknowledge All' button on the anti* signature pages would be fantastic. I've not kept up on acknowledging all the updates and now I'm having to spend forever acknowledging them individually to clear the page. Thanks for all your work. ClearOS is such a great distro.
    The reply is currently minimized Show
  • Accepted Answer

    Monday, April 22 2019, 01:13 PM - #Permalink
    Resolved
    0 votes
    Dirk Albring wrote:

    Dave, did you get rid of the suggestion page because you're releasing 7.6? I think an 'Acknowledge All' button on the anti* signature pages would be fantastic. I've not kept up on acknowledging all the updates and now I'm having to spend forever acknowledging them individually to clear the page. Thanks for all your work. ClearOS is such a great distro.


    You mean this page? That are feature requests for ClearOS 8! Dave has now released ClearOS Community 7.6.

    Regarding the "Acknowledge All" button I made a feature request for you!

    Feature request on Gitlab
    Like
    1
    The reply is currently minimized Show
  • Accepted Answer

    Monday, April 22 2019, 03:26 PM - #Permalink
    Resolved
    0 votes
    Thanks for reporting that feature Dirk and thanks Marcel for submitting the feature request. The feature request page was temporary to raise awareness of the new method of reporting in GitLab. Literally any feature you care about and want to promote can be made there. GitLab has allowed us to consolidate a number of things including the Feature request process which is now more open and participatory. We used to maintain internal spreadsheets, polls, documents, some features were posted to the other tracker. All of these are being migrated to this new process. Feel free to add anything you care about or you can even jump in and help now in more participatory ways. We have some documentation that makes this easy and are working to make even more of it easier to consume. From the old tracker we have moved all issues that were 'pegged' to a specific release target. What remains is a large list of 'unsorted' items. Feel free to add those to feature requests if you like.

    Make sure to like (thumbs up) any feature request you feel passionate about. It helps to inform us of what is important to our users. To do this,

    1) log into GitLab
    2) go to the features request or issue you care about
    3) click the thumbs up or thumbs down

    Thanks for your feedback.
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, April 25 2019, 03:39 AM - #Permalink
    Resolved
    1 votes
    Updates for 7.6 have become broken. On all systems previously upgraded to 7.6 OK

    [root@may ~]# yum clean all && yum update
    Loaded plugins: clearcenter-marketplace, fastestmirror, verify
    ClearCenter Marketplace: fetching repositories...
    Cleaning repos: clearos clearos-centos clearos-centos-sclo-rh clearos-centos-updates clearos-contribs clearos-epel clearos-fast-updates clearos-infra clearos-updates
    : private-clearcenter-dyndns
    Cleaning up list of fastest mirrors
    Loaded plugins: clearcenter-marketplace, fastestmirror, verify
    ClearCenter Marketplace: fetching repositories...
    Determining fastest mirrors
    * clearos: clearos.uberglobalmirror.com
    ...
    ... snipped
    ...
    Resolving Dependencies
    --> Running transaction check
    ---> Package app-base.noarch 1:2.6.5-1.v7 will be updated
    ---> Package app-base.noarch 1:2.6.9-2.v7 will be an update
    ---> Package app-base-core.noarch 1:2.6.5-1.v7 will be updated
    ---> Package app-base-core.noarch 1:2.6.9-2.v7 will be an update
    --> Processing Dependency: system-base >= 7.6.5 for package: 1:app-base-core-2.6.9-2.v7.noarch
    ---> Package csplugin-filewatch.x86_64 0:1.1-1.v7 will be updated
    ---> Package csplugin-filewatch.x86_64 0:1.2-1.v7 will be an update
    --> Finished Dependency Resolution
    Error: Package: 1:app-base-core-2.6.9-2.v7.noarch (clearos-updates)
    Requires: system-base >= 7.6.5
    Installed: system-base-7.6.3-1.v7.x86_64 (@clearos-updates)
    system-base = 7.6.3-1.v7
    Available: system-base-7.4.2-1.v7.x86_64 (clearos)
    system-base = 7.4.2-1.v7
    You could try using --skip-broken to work around the problem

    Attempts to just update app-base result in the same error... :-(
    Like
    1
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, April 25 2019, 06:41 AM - #Permalink
    Resolved
    0 votes
    @Tony,
    Thanks. I'd forgotten that Dave had added the dependency when I promoted app-base yesterday. system-base-7.6.5-1.v7 is just syncing to the mirrors. Until it sync's, it is in clearos-updates-testing and is safe to install independently.
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, April 25 2019, 07:43 AM - #Permalink
    Resolved
    -1 votes
    Thanks Nick - will try again tomorrow...

    However, does the present process really rely on casual conversation between staff and one's memory? If so, that's a recipe for continuing problems. Surely there should be a written procedure whereby numerous checks are made before making an update/addition to a repository, e.g. dependencies are met. Also a test install conducted to confirm the updates will not cause issues. From an outsider looking in it gives the appearance it's a rather haphazard modus operandi at best with no change management/control. It certainly doesn't engender confidence in the product.
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, April 25 2019, 08:29 AM - #Permalink
    Resolved
    0 votes
    Point taken. I am still learning this side of things. I know, for example, if you promote an app, the core package automatically gets promoted. Similarly, if you promote samba, all the packages compiled at the same time also get promoted.

    Doing a trial after a promotion is problematic as you have to wait for the repos to sync before you can test and, at any point prior to the sync, people using other mirrors which may have already sync'd will hit the issue. If an issue is found it will take a further round of sync's to fix, but you have given me an idea.
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, April 25 2019, 09:51 AM - #Permalink
    Resolved
    0 votes

    I am still learning this side of things

    Started using ClarkConnect about 1998 and no idea how long it had being in operation before that. Are you saying that in all that 21 years or more no written procedures have been created, and kept updated, for essential tasks within the company? Each new person learns by trial and error? Nothing passed on from one person to the next so every change in personnel results in being back to almost square one :( Not your problem per se. "Seat of the pants" culture? Hope none are pilots :p

    Brings to mind this aphorism from George Santayana (1905) Reason in Common Sense, p. 284, volume 1 of The Life of Reason

    "Those who cannot remember the past are condemned to repeat it"

    When in a former life I worked in IT/Company Change Management-Control - that was one of our mottos... The same is true for those unaware of the past. The problem you mentioned re. rpm updates syncing to repositories has been well known for many many years - so why should it still be a recurring problem... Other distributions I use mitigate it pretty well... Cannot remember the last time it happened to me with Ubuntu/CentOS/Fedora (just a sample of one person I realize).

    Anyway - this is now OT - sorry.
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, April 25 2019, 02:55 PM - #Permalink
    Resolved
    0 votes
    Tony,

    Thank you for your bug report. Hopefully, Nick's fix addressed your principal concern. If you would like business quality updates, please use the business version. I'm quite confident that this last error caused no issues for Business or Home users and that the impact on Community was simply to cease the flow of new updates until this was resolved (ie. not critical). If you want better quality Community releases, documentation, and processes for your community production boxes, please participate in QA/Updates-Testing, documentation, and processes. I thank everyone in the community that has helped with feedback during this release. We recognize that there have been bumps. Nick's only error was to apologize for being new at this. His fixes did not cause any catastrophic error and having no reports from the community to the fitness of the package, it was decided to be pushed. Nick is doing a great job. We are actively seeking QA testers that can help approve releases to the community. Part of the goal for last Saturday's meeting with the community was to address concerns and to give free advice on ClearOS and training to community members who want to participate more. We will do this again this weekend.

    In the past this upgrade process was in the realm of a single person who was very good at checking many things (he had learned through his own experiences and even had his own mistakes along the way). Nick is stepping into this role with the mandate of involving the community in the community updates. This includes community documentation which, as you may have seen, Nick is very good at. Nick and I have only have been meeting almost daily during this update cycle to review fixes that have needed to occur. I signed off on the package that was pushed and so it is my fault as well. I did not perform the unit test that would have detected this because the old test system is not applicable to our new process. What I didn't miss was putting the requirement in there for it to require the dependency. Had that packaged pushed without that version of system-base as a requirement, bad things would have happened. So you are welcome. I've only known Nick to push 1 package without a consensus of a plurality of participants in the QA process and that package was done yesterday at your request and insistence to fix this issue and in an effort to please you with a quick response. The community is grateful for his years of support both on and off the ClearCenter team. It is likely that you didn't mean or intend any disrespect.
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, April 25 2019, 03:16 PM - #Permalink
    Resolved
    0 votes
    Dave - all the best with ClearOS, hope things work out for all at ClearOS and its users. I see steps are starting to be taken in the right direction but has been rather slow coming. For me this is the parting of the ways as I hinted before, ClearOS 7.6 will be my last version before moving to a more stable platform As a retired person on a fixed income there is no way I am going to pay for Home or Business Editions for the number of systems I control. It's been fun at times - frustrating at others. Good luck.
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, May 04 2019, 08:07 AM - #Permalink
    Resolved
    0 votes
    Hi All,

    On one of my machines i got this errors:

    ---> Package app-php-engines-core.noarch 1:1.2.0-1.v7 will be an update
    --> Processing Dependency: rh-php72-php-bcmath for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-cli for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-common for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-fpm for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-gd for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-gmp for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-intl for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-json for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-ldap for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-mbstring for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-mysqlnd for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-opcache for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-pdo for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-pear for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-process for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-soap for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-xml for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-zip for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    ---> Package cairo-gobject.x86_64 0:1.15.12-3.el7 will be installed
    ---> Package centos-indexhtml.noarch 0:7-9.el7.centos will be installed
    ---> Package dejavu-sans-fonts.noarch 0:2.33-6.el7 will be installed
    ---> Package fribidi.x86_64 0:1.0.2-1.el7 will be installed
    ---> Package gtk3.x86_64 0:3.22.30-3.el7 will be installed
    --> Processing Dependency: libwayland-cursor(x86-64) >= 1.9.91 for package: gtk3-3.22.30-3.el7.x86_64
    --> Processing Dependency: libxkbcommon.so.0(V_0.5.0)(64bit) for package: gtk3-3.22.30-3.el7.x86_64
    --> Processing Dependency: dconf(x86-64) for package: gtk3-3.22.30-3.el7.x86_64
    --> Processing Dependency: adwaita-icon-theme for package: gtk3-3.22.30-3.el7.x86_64
    --> Processing Dependency: libxkbcommon.so.0()(64bit) for package: gtk3-3.22.30-3.el7.x86_64
    --> Processing Dependency: libwayland-egl.so.1()(64bit) for package: gtk3-3.22.30-3.el7.x86_64
    --> Processing Dependency: libwayland-cursor.so.0()(64bit) for package: gtk3-3.22.30-3.el7.x86_64
    --> Processing Dependency: librest-0.7.so.0()(64bit) for package: gtk3-3.22.30-3.el7.x86_64
    --> Processing Dependency: libjson-glib-1.0.so.0()(64bit) for package: gtk3-3.22.30-3.el7.x86_64
    --> Processing Dependency: libatk-bridge-2.0.so.0()(64bit) for package: gtk3-3.22.30-3.el7.x86_64
    ---> Package libglvnd-egl.x86_64 1:1.0.1-0.8.git5baa1e5.el7 will be installed
    --> Processing Dependency: libglvnd(x86-64) = 1:1.0.1-0.8.git5baa1e5.el7 for package: 1:libglvnd-egl-1.0.1-0.8.git5baa1e5.el7.x86_64
    --> Processing Dependency: libGLdispatch.so.0()(64bit) for package: 1:libglvnd-egl-1.0.1-0.8.git5baa1e5.el7.x86_64
    ---> Package libglvnd-glx.x86_64 1:1.0.1-0.8.git5baa1e5.el7 will be installed
    ---> Package libsmartcols.x86_64 0:2.23.2-59.el7_6.1 will be installed
    --> Running transaction check
    ---> Package adwaita-icon-theme.noarch 0:3.28.0-1.el7 will be installed
    --> Processing Dependency: adwaita-cursor-theme = 3.28.0-1.el7 for package: adwaita-icon-theme-3.28.0-1.el7.noarch
    ---> Package app-php-engines-core.noarch 1:1.2.0-1.v7 will be an update
    --> Processing Dependency: rh-php72-php-bcmath for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-cli for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-common for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-fpm for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-gd for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-gmp for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-intl for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-json for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-ldap for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-mbstring for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-mysqlnd for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-opcache for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-pdo for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-pear for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-process for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-soap for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-xml for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-zip for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    ---> Package at-spi2-atk.x86_64 0:2.26.2-1.el7 will be installed
    --> Processing Dependency: at-spi2-core(x86-64) >= 2.25.3 for package: at-spi2-atk-2.26.2-1.el7.x86_64
    --> Processing Dependency: libatspi.so.0()(64bit) for package: at-spi2-atk-2.26.2-1.el7.x86_64
    ---> Package dconf.x86_64 0:0.28.0-4.el7 will be installed
    ---> Package json-glib.x86_64 0:1.4.2-2.el7 will be installed
    ---> Package libglvnd.x86_64 1:1.0.1-0.8.git5baa1e5.el7 will be installed
    ---> Package libwayland-cursor.x86_64 0:1.15.0-1.el7 will be installed
    ---> Package libwayland-egl.x86_64 0:1.15.0-1.el7 will be installed
    ---> Package libxkbcommon.x86_64 0:0.7.1-1.el7 will be installed
    ---> Package rest.x86_64 0:0.8.1-2.el7 will be installed
    --> Processing Dependency: libsoup-gnome-2.4.so.1()(64bit) for package: rest-0.8.1-2.el7.x86_64
    --> Processing Dependency: libsoup-2.4.so.1()(64bit) for package: rest-0.8.1-2.el7.x86_64
    --> Running transaction check
    ---> Package adwaita-cursor-theme.noarch 0:3.28.0-1.el7 will be installed
    ---> Package app-php-engines-core.noarch 1:1.2.0-1.v7 will be an update
    --> Processing Dependency: rh-php72-php-bcmath for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-cli for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-common for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-fpm for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-gd for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-gmp for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-intl for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-json for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-ldap for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-mbstring for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-mysqlnd for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-opcache for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-pdo for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-pear for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-process for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-soap for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-xml for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-zip for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    ---> Package at-spi2-core.x86_64 0:2.28.0-1.el7 will be installed
    ---> Package libsoup.x86_64 0:2.62.2-2.el7 will be installed
    --> Processing Dependency: glib-networking(x86-64) >= 2.38.0 for package: libsoup-2.62.2-2.el7.x86_64
    --> Running transaction check
    ---> Package app-php-engines-core.noarch 1:1.2.0-1.v7 will be an update
    --> Processing Dependency: rh-php72-php-bcmath for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-cli for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-common for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-fpm for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-gd for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-gmp for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-intl for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-json for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-ldap for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-mbstring for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-mysqlnd for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-opcache for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-pdo for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-pear for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-process for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-soap for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-xml for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-zip for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    ---> Package glib-networking.x86_64 0:2.56.1-1.el7 will be installed
    --> Processing Dependency: gsettings-desktop-schemas for package: glib-networking-2.56.1-1.el7.x86_64
    --> Processing Dependency: libproxy.so.1()(64bit) for package: glib-networking-2.56.1-1.el7.x86_64
    --> Running transaction check
    ---> Package app-php-engines-core.noarch 1:1.2.0-1.v7 will be an update
    --> Processing Dependency: rh-php72-php-bcmath for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-cli for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-common for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-fpm for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-gd for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-gmp for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-intl for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-json for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-ldap for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-mbstring for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-mysqlnd for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-opcache for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-pdo for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-pear for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-process for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-soap for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-xml for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-zip for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    ---> Package gsettings-desktop-schemas.x86_64 0:3.28.0-2.el7 will be installed
    ---> Package libproxy.x86_64 0:0.4.11-11.el7 will be installed
    --> Processing Dependency: libmodman.so.1()(64bit) for package: libproxy-0.4.11-11.el7.x86_64
    --> Running transaction check
    ---> Package app-php-engines-core.noarch 1:1.2.0-1.v7 will be an update
    --> Processing Dependency: rh-php72-php-bcmath for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-cli for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-common for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-fpm for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-gd for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-gmp for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-intl for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-json for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-ldap for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-mbstring for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-mysqlnd for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-opcache for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-pdo for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-pear for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-process for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-soap for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-xml for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-zip for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    ---> Package libmodman.x86_64 0:2.0.1-8.el7 will be installed
    --> Finished Dependency Resolution
    --> Running transaction check
    ---> Package app-php-engines-core.noarch 1:1.2.0-1.v7 will be an update
    --> Processing Dependency: rh-php72-php-bcmath for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-cli for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-common for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-fpm for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-gd for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-gmp for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-intl for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-json for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-ldap for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-mbstring for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-mysqlnd for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-opcache for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-pdo for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-pear for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-process for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-soap for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-xml for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    --> Processing Dependency: rh-php72-php-zip for package: 1:app-php-engines-core-1.2.0-1.v7.noarch
    ---> Package kernel.x86_64 0:3.10.0-693.2.2.v7 will be erased
    --> Finished Dependency Resolution
    Error: Package: 1:app-php-engines-core-1.2.0-1.v7.noarch (clearos-contribs)
    Requires: rh-php72-php-ldap
    Error: Package: 1:app-php-engines-core-1.2.0-1.v7.noarch (clearos-contribs)
    Requires: rh-php72-php-pear
    Error: Package: 1:app-php-engines-core-1.2.0-1.v7.noarch (clearos-contribs)
    Requires: rh-php72-php-bcmath
    Error: Package: 1:app-php-engines-core-1.2.0-1.v7.noarch (clearos-contribs)
    Requires: rh-php72-php-opcache
    Error: Package: 1:app-php-engines-core-1.2.0-1.v7.noarch (clearos-contribs)
    Requires: rh-php72-php-mysqlnd
    Error: Package: 1:app-php-engines-core-1.2.0-1.v7.noarch (clearos-contribs)
    Requires: rh-php72-php-intl
    Error: Package: 1:app-php-engines-core-1.2.0-1.v7.noarch (clearos-contribs)
    Requires: rh-php72-php-mbstring
    Error: Package: 1:app-php-engines-core-1.2.0-1.v7.noarch (clearos-contribs)
    Requires: rh-php72-php-process
    Error: Package: 1:app-php-engines-core-1.2.0-1.v7.noarch (clearos-contribs)
    Requires: rh-php72-php-cli
    Error: Package: 1:app-php-engines-core-1.2.0-1.v7.noarch (clearos-contribs)
    Requires: rh-php72-php-zip
    Error: Package: 1:app-php-engines-core-1.2.0-1.v7.noarch (clearos-contribs)
    Requires: rh-php72-php-xml
    Error: Package: 1:app-php-engines-core-1.2.0-1.v7.noarch (clearos-contribs)
    Requires: rh-php72-php-soap
    Error: Package: 1:app-php-engines-core-1.2.0-1.v7.noarch (clearos-contribs)
    Requires: rh-php72-php-gmp
    Error: Package: 1:app-php-engines-core-1.2.0-1.v7.noarch (clearos-contribs)
    Requires: rh-php72-php-common
    Error: Package: 1:app-php-engines-core-1.2.0-1.v7.noarch (clearos-contribs)
    Requires: rh-php72-php-fpm
    Error: Package: 1:app-php-engines-core-1.2.0-1.v7.noarch (clearos-contribs)
    Requires: rh-php72-php-pdo
    Error: Package: 1:app-php-engines-core-1.2.0-1.v7.noarch (clearos-contribs)
    Requires: rh-php72-php-json
    Error: Package: 1:app-php-engines-core-1.2.0-1.v7.noarch (clearos-contribs)
    Requires: rh-php72-php-gd
    --nodigest
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, May 04 2019, 08:42 AM - #Permalink
    Resolved
    0 votes
    Please see the first post for the manual update procedure.
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, May 07 2019, 01:56 PM - #Permalink
    Resolved
    0 votes
    Nick Howitt wrote:

    Please see the first post for the manual update procedure.

    Hi Nick,
    Sorry for late response!
    A few hours later it worked..... mirror not in sync?
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, May 07 2019, 01:57 PM - #Permalink
    Resolved
    0 votes
    Hi guys,
    What is the yum upgrade procedure for Business editions? Same?

    Regards, Gerard
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, May 07 2019, 02:18 PM - #Permalink
    Resolved
    0 votes
    Yes because of a circular dependency issue. The automatic updates resolve this by doing a partial update one night which effectively updates app-base so the rest of the update goes through the following night.
    The reply is currently minimized Show
Your Reply