Tonight (17/12/19-18/12/19) the following updated packages are being released:
* = the package is also being released to Business at the same time.
Packages available for testing
app-network - code merge complete. Seems to work for everything except external VLANs.
Unless detailed otherwise, packages available for testing can be installed with:
Packages being worked on:
Big updates scheduled - fingers crossed
18th Dec - Kopano 8.7.5 - delayed for one day to sort out a repo issue.
- app-configuration-backup - reduce samba and netify files backed up, and add one OpenLDAP files
- app-nextcloud-extension - To get unlimited quotas working.
* = the package is also being released to Business at the same time.
Packages available for testing
- app-kopano - update underlying Kopano package to 8.7.5. Because of a dependency issue I have not pushed kopano 8.7.7, but, when correctly available from upstream, it should just drop in.
The update is complete and available for testing for anyone with a valid kopano licence only. To update, please do a:
yum update *kopano* --enablerepo=clearos-paid-testing- Now allows you to set up Wireless and Cellular interfaces. You will also need app-wireless to configure a NIC as an access point. Otherwise manual configuration is then needed for WiFi and Cellular devices.
- I've tweaked it for kernel mode PPPoE (much faster and lower resoures). For the moment we are not forcibly converting PPPoE interfaces over, but if you edit an interface it will switch to kernel mode.
- Hides irrelevant interfaces from app-network-report such as docker0, veth* and ifb*.
- Numerous other changes since last 2.6.0
- Do not use the the update if you use VLAN's on external interfaces.
Unless detailed otherwise, packages available for testing can be installed with:
yum update --enablerepo=clearos-updates-testing {package-name}Packages being worked on:
- app-storage
- app-sia - In theory it worked but does not. Fixes needed. I have an idea to get it working in Gateway mode but it is deathly slow.
- app-openvpn to add three configuration parameters (client-to-client, "push block-outside-dns" and to force all traffic through the VPN). This is being worked on by an external contributor.
- app-attack-detector to add a button beside each banned IP to you can unban it. This is being worked on by an external contributor.
Big updates scheduled - fingers crossed
18th Dec - Kopano 8.7.5 - delayed for one day to sort out a repo issue.
Share this post:
Responses (18)
-
Accepted Answer
We bring down all EPEL updated every week on Tuesdays into the Community repos and the following week we copy them into the paid Verified EPEL repos the following week. I skipped doing it last week - Christmas Eve. All EPEL packages should be immediately available from epel-unverified and epel-unverified-testing which are disabled by default.
Certain packages are excluded from yum - have a look in /etc/yum.repos.d/clearos-epel.repo. -
Accepted Answer
-
Accepted Answer
-
Accepted Answer
That is my mistake. Because of repo issues I had to generate an app-kopano-basic-extras file and that meant I had to go outside process and manually update the spec file so I forgot to change the string in /usr/clearos/apps/kopano_basic/deploy/info.php, the file usually used to create the spec file.
The good news is that Peter has updated the spec file generator to create the extras package if required and I'll be re-spinning the app in January to get round the repo issues that we spoke about in the Community Meeting earlier today. Because of the the issue left over from original update script it is important that I fix that first and thoroughly test before releasing again. -
Accepted Answer
There is an updated app-kopano-basic in clearos-paid-testing. This will fix the version numbering (but it bumps it to 2.3.10). It will also prepare for all the auxiliary packages from kopano to become available such as xapian-core and xapian-core-libs. At the moment I've left the auxiliary packages paid-testing. -
Accepted Answer
Nick Howitt wrote:
There is an updated app-kopano-basic in clearos-paid-testing. This will fix the version numbering (but it bumps it to 2.3.10). It will also p
repare for all the auxiliary packages from kopano to become available such as xapian-core and xapian-core-libs. At the moment I've left the auxiliary packages paid-testing.
Done !
yum update --enablerepo=clearos-paid-testing app-kopano*
Dependencies Resolved
==============================================================================================================================================================================================
Package Arch Version Repository Size
==============================================================================================================================================================================================
Updating:
app-kopano-basic noarch 1:2.3.10-1.v7 clearos-paid-testing 9.5 k
app-kopano-basic-core noarch 1:2.3.10-1.v7 clearos-paid-testing 13 k
Transaction Summary
==============================================================================================================================================================================================
Upgrade 2 Packages
Total download size: 22 k
Is this ok [y/d/N]: y
Downloading packages:
No Presto metadata available for clearos-paid-testing
(1/2): app-kopano-basic-2.3.10-1.v7.noarch.rpm | 9.5 kB 00:00:00
(2/2): app-kopano-basic-core-2.3.10-1.v7.noarch.rpm | 13 kB 00:00:00
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Total 83 kB/s | 22 kB 00:00:00
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
Updating : 1:app-kopano-basic-core-2.3.10-1.v7.noarch 1/4
Connecting to ClearCenter...
kopano_basic OK
owncloud OK
Subscription update complete
/usr/bin/mkdir: cannot create directory ‘/etc/kopano/license’: File exists
Updating : 1:app-kopano-basic-2.3.10-1.v7.noarch 2/4
Cleanup : 1:app-kopano-basic-2.3.9-1.v7.noarch 3/4
Cleanup : 1:app-kopano-basic-core-2.3.9-1.v7.noarch 4/4
Verifying : 1:app-kopano-basic-2.3.10-1.v7.noarch 1/4
Verifying : 1:app-kopano-basic-core-2.3.10-1.v7.noarch 2/4
Verifying : 1:app-kopano-basic-core-2.3.9-1.v7.noarch 3/4
Verifying : 1:app-kopano-basic-2.3.9-1.v7.noarch 4/4
Updated:
app-kopano-basic.noarch 1:2.3.10-1.v7 app-kopano-basic-core.noarch 1:2.3.10-1.v7
-
Accepted Answer
Nick,
Any chanche there will come a OpenVPN-core update
Currently COS is on verison 2.4.6 (released on 2018.04.24), but the current stable release is 2.4.8 (released 2019.10.31)
Looks like there some nice improvements done in the new releases (https://openvpn.net/community-downloads/
I know about there current situation at COS, but i it just a question....
Maybe the repos of OpenVPN are usable -
Accepted Answer
We don't maintain OpenVPN. We get the package direct from EPEL. They are at 2.4.8 now so you can install it from epel-unverified if you want. If I do updates next Tuesday, it should go to Community then and to Home/Business the following week.
Having said that, I don't think it will give you much. Most of the improvements seem to be for Windows. -
Accepted Answer
Nick Howitt wrote:
We don't maintain OpenVPN. We get the package direct from EPEL. They are at 2.4.8 now so you can install it from epel-unverified if you want. If I do updates next Tuesday, it should go to Community then and to Home/Business the following week.
Having said that, I don't think it will give you much. Most of the improvements seem to be for Windows.
Thanks. Good to know
How are the EPEL repos maintaned towards the COS repos ?
For example if there are other packages updates available. -
Accepted Answer
-
Accepted Answer
Nick Howitt wrote:
It looks like openvpn is on the exclude list from Epel, so I'll have to download it first and test it. This means I cannot push the release through today.
This is the output of my Epel.
Is this the same as with you ?
yum update --enablerepo=epel-unverified
====================================================================================================================
Package Arch Version Repository Size
====================================================================================================================
Updating:
certbot noarch 1.0.0-1.el7 epel-unverified 41 k
fail2ban-server noarch 0.10.4-1.el7 epel-unverified 404 k
openvpn x86_64 2.4.8-1.el7 epel-unverified 523 k
python2-acme noarch 1.0.0-1.el7 epel-unverified 74 k
python2-certbot noarch 1.0.0-1.el7 epel-unverified 358 k
python2-certbot-apache noarch 1.0.0-1.el7 epel-unverified 107 k
Transaction Summary
====================================================================================================================
Upgrade 6 Packages
yum update --enablerepo=clearos-epel
Dependencies Resolved
================================================================================
Package Arch Version Repository Size
================================================================================
Updating:
certbot noarch 1.0.0-1.el7 clearos-epel 41 k
python2-acme noarch 1.0.0-1.el7 clearos-epel 74 k
python2-certbot noarch 1.0.0-1.el7 clearos-epel 358 k
python2-certbot-apache noarch 1.0.0-1.el7 clearos-epel 107 k
Transaction Summary
================================================================================
Upgrade 4 Packages
-
Accepted Answer
I'll release fail2ban next week. I did the prep for that months ago and it looks like we forgot to remove the block on the update. I just was not going to do it yesterday at short notice. I've asked why other packages are being blocked from EPEL and I have been promised an answer today. There are quite a few more packages blocked from updating, but many of them are ones which we compile our own versions.
I've upgraded my OpenVPN to 2.4.8 and it seems to be running OK. I just want to test another couple of connections. If that is OK, and depending on comments coming back from the devs, I'll release it into Community next week. -
Accepted Answer
-
Accepted Answer
Shad must have pushed it through to try and get a working 7.7 iso. All it does is add the webconfig service to /usr/lib/systemd/system-preset/90-default.preset as the webconfig was not starting on a new install. It will have no effect on any existing installations, but installing 7.7 without the webconfig is a bad user experience. It has also been pushed to business as the iso is built off the paid repos. -
Accepted Answer
Wednesday January 8 2020
================================================================================
Package Arch Version Repository Size
================================================================================
Updating:
app-base noarch 1:2.8.11-1.v7 clearos-updates 31 k
app-base-core noarch 1:2.8.11-1.v7 clearos-updates 455 k
Transaction Summary
================================================================================
Upgrade 2 Packages
Total download size: 487 k
Background downloading packages, then exiting:
No Presto metadata available for clearos-updates
--------------------------------------------------------------------------------
Total 235 kB/s | 487 kB 00:02
exiting because "Download Only" specified
More updates to enable creation of an ISO? -
Accepted Answer
No. When intiscripts updated it introduced an problem (have a look at resolv.conf - if it starts with "; generated by /usr/sbin/dhclient-script" you have the problem) and exposed a bug in app-network. It is not possible to release an updated app-network because there is too much work-in-progress to back it out and I don't understand the reasoning behind the code that is already there. It has not changed got 6 to 7 years. As an expedient, the issue can be fixed by running /var/clearos/events/network_peerdns/network_resolver, so I picked on a package and adjusted its post-install script.. -
Accepted Answer
have a look at resolv.conf
Here's one of mine from ClearOS 7.x - they are all similar
[code]
domain sraellis.com
search sraellis.com
nameserver 127.0.0.1
nameserver 192.168.1.17
nameserver 192.168.2.35
nameserver 1.1.1.1
[/quote]
Don't use dnsmasq as it lacks vital function. nor the ClearOS modifications. Use bind and ISC dhcpd instead. Require a master/slave dns/dhcp setup to provide the ability to take down one server and not loose dns/dhcp. Full synchronisation so only the master needs updates. Multiwan provides an alternate gateway, imapsync provides mail backup and redundancy while rsync copies share data. This is the function (though not the identical software) enjoyed at work before retirement. Something that any business where availabilty is important would mandate as a minimum.
It is not possible to release an updated app-network because there is too much work-in-progress to back it out and I don't understand the reasoning behind the code that is already there. It has not changed got 6 to 7 years.
ClearOS certainly digs itself into some holes...
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 »