Notice
Domoticz 2022.1
Domoticz 2022.1 is now possible to install in ClearOS 7.
EDIT April 13th 2022:
Thanks to some work from Nick, Domoticz 2022.1-4 is now available in clearos-contribs-testing. If you are eager to update from earlier versions you can do this from command line with the following command:
/Fred
OLD ORIGINAL POST (now obsolete):
But, things are not as smooth as they should be unfortunately. The koji build system does not want to play along, and Nick has a bit of a backlog to handle which has higher priority. So for now, the only thing I can do is to offer those of you who like to use the latest stable version of Domoticz is an fairly detailed description on how you can build the package yourself.
Hopefully Nick will have some time next month to look into the koji issue and fix it. In such case the instruction below is no longer needed. The instructions should be easy to follow even for someone that is not used to compile linux programs.
------------------------------
My recommendation is that unless you already have a ClearOS developer environment setup that you will create a virtual machine on your normal PC or laptop, dedicated for just building this package (and any other ClearOS application it that is the case). If you are running Windows, Oracles VirtualBox is a good alternative and that is what I have used in the example below:
On your PC/Laptop download the ClearOS installation iso: ClearOS-DVD-x86_64.iso
In Oracle VM Virutual Box:
Create new virtual machine, use the following settings:
Type: Linux
Version: Other Linux 64-bit
Memory: 4096MB (or more)
Storage size: Dynamic or Fixed at 8GB (minimum)
Go to settings and adjust number of processors to maximum of the green indicator
Under storage: "Attach" your downloaded ClearOS iso file to the virtual optical drive
Under Network I prefer to use "Bridged Adapter" which will give your virtual machine an IP address on your normal DHCP LAN so you easily can ssh to it later on etc.
Choose OK. Double click the new virtual machine to start it up. Select "Install ClearOS"
Set language, keyboard, minimal install, select harddrive, start the network adapter (make sure it gets an IP address).
Begin installation
Set root password
After the installation finish, reboot
Connect to your machine on the IP address you can see with a web browser. Please note that you connect to port 81 (for instance https://192.168.0.10:81)
Config:
Private Server Mode
Community edition is fine for this build-machine
Register the machine with your account at Clear
If it suggest you should update any package, do it.
Do not install any apps (for now at least), select "Skip Wizard"
Now, open a ssh terminal on your host computer or any other computer on your LAN (Putty is a good program on Windows) and connect to your build machine.
Login with user "root" and your admin password you defined in the installation process.
type the following commands:
your ssh connection will now be lost. After that the virtual machine is up and running again connect again with your ssh terminal
Enter your "normal" user-id that you want to use when you are working with the building machine
Now, let the root-ssh window be aside for a while and open another ssh login.
Login to your machine as the developer (non-root) user you configured in the clearos setup.
download the domoticz package from my github account:
Prepare a build directory, if you already have it since before, make sure it is empty:
copy the files into place:
download some other needed source files:
Now all needed files should be in place and you should be able to start building. Note the mock command can easily take more than one hour to execute depending on your CPU.
You now should have the domoticz rpm file available at: /var/lib/mock/clearos-7-x86_64/result/domoticz-2022.1-2.v7.x86_64.rpm
copy your domoticz installation file to the machine(s) where you want to install it. (Depending on transfer method you need to install ftp, samba etc on your build-machine)
For instance, from the web-interface you can access the Marketplace and install "Flexshares" and "Windows Networking(Samba)" and then use LDAP and "simple server". Then you need to add a user, my suggestion is to use the same name and password as you configured for the development user earlier. I tend to remember that the developer account should be setup before activating LDAP, so that is why I skiped to install these apps at the installation of the ClearOS operating system. However, I could be wrong.
When you have transfered to domoticz rpm file it is time to shut down the build-machine:
from the "root" ssh window to your build-machine, type "poweroff" to shut it down.
------------
On the machine where you want to install/update domoticz do the following:
login as root (command console, not the webinterface)
make sure you have your domoticz rpm file you have built in the same directory where you are.
Done!
EDIT April 13th 2022:
Thanks to some work from Nick, Domoticz 2022.1-4 is now available in clearos-contribs-testing. If you are eager to update from earlier versions you can do this from command line with the following command:
yum update --enable-repo=clearos-contribs-testing domoticz/Fred
OLD ORIGINAL POST (now obsolete):
But, things are not as smooth as they should be unfortunately. The koji build system does not want to play along, and Nick has a bit of a backlog to handle which has higher priority. So for now, the only thing I can do is to offer those of you who like to use the latest stable version of Domoticz is an fairly detailed description on how you can build the package yourself.
Hopefully Nick will have some time next month to look into the koji issue and fix it. In such case the instruction below is no longer needed. The instructions should be easy to follow even for someone that is not used to compile linux programs.
------------------------------
My recommendation is that unless you already have a ClearOS developer environment setup that you will create a virtual machine on your normal PC or laptop, dedicated for just building this package (and any other ClearOS application it that is the case). If you are running Windows, Oracles VirtualBox is a good alternative and that is what I have used in the example below:
On your PC/Laptop download the ClearOS installation iso: ClearOS-DVD-x86_64.iso
In Oracle VM Virutual Box:
Create new virtual machine, use the following settings:
Type: Linux
Version: Other Linux 64-bit
Memory: 4096MB (or more)
Storage size: Dynamic or Fixed at 8GB (minimum)
Go to settings and adjust number of processors to maximum of the green indicator
Under storage: "Attach" your downloaded ClearOS iso file to the virtual optical drive
Under Network I prefer to use "Bridged Adapter" which will give your virtual machine an IP address on your normal DHCP LAN so you easily can ssh to it later on etc.
Choose OK. Double click the new virtual machine to start it up. Select "Install ClearOS"
Set language, keyboard, minimal install, select harddrive, start the network adapter (make sure it gets an IP address).
Begin installation
Set root password
After the installation finish, reboot
Connect to your machine on the IP address you can see with a web browser. Please note that you connect to port 81 (for instance https://192.168.0.10:81)
Config:
Private Server Mode
Community edition is fine for this build-machine
Register the machine with your account at Clear
If it suggest you should update any package, do it.
Do not install any apps (for now at least), select "Skip Wizard"
Now, open a ssh terminal on your host computer or any other computer on your LAN (Putty is a good program on Windows) and connect to your build machine.
Login with user "root" and your admin password you defined in the installation process.
type the following commands:
yum update
rebootyour ssh connection will now be lost. After that the virtual machine is up and running again connect again with your ssh terminal
yum-config-manager --enable clearos-developer
yum upgrade
yum install clearos-devel app-devel vim-enhanced
clearos setupEnter your "normal" user-id that you want to use when you are working with the building machine
Now, let the root-ssh window be aside for a while and open another ssh login.
Login to your machine as the developer (non-root) user you configured in the clearos setup.
download the domoticz package from my github account:
git clone https://github.com/FredrikFornstad/domoticz-clearos.gitPrepare a build directory, if you already have it since before, make sure it is empty:
mkdir rpmbuild
cd rpmbuild
mkdir SOURCES
mkdir SPECScopy the files into place:
cp ../domoticz-clearos/* SOURCES/
mv SOURCES/domoticz.spec SPECS/download some other needed source files:
yum install python3-devel
cd SOURCES
grep -oh " http.*" sources.download | xargs -n1 wgetNow all needed files should be in place and you should be able to start building. Note the mock command can easily take more than one hour to execute depending on your CPU.
cd ../SPECS
rpmbuild -bs domoticz.spec
cd ../SRPMS
mock domoticz*You now should have the domoticz rpm file available at: /var/lib/mock/clearos-7-x86_64/result/domoticz-2022.1-2.v7.x86_64.rpm
copy your domoticz installation file to the machine(s) where you want to install it. (Depending on transfer method you need to install ftp, samba etc on your build-machine)
For instance, from the web-interface you can access the Marketplace and install "Flexshares" and "Windows Networking(Samba)" and then use LDAP and "simple server". Then you need to add a user, my suggestion is to use the same name and password as you configured for the development user earlier. I tend to remember that the developer account should be setup before activating LDAP, so that is why I skiped to install these apps at the installation of the ClearOS operating system. However, I could be wrong.
When you have transfered to domoticz rpm file it is time to shut down the build-machine:
from the "root" ssh window to your build-machine, type "poweroff" to shut it down.
------------
On the machine where you want to install/update domoticz do the following:
login as root (command console, not the webinterface)
make sure you have your domoticz rpm file you have built in the same directory where you are.
yum localinstall domoticz-2022.1-2.v7.x86_64.rpmDone!
Share this post:
Responses (21)
-
Accepted Answer
Fredrik Fornstad wrote:
Patrick,
Sorry, but I just cannot. I just checked my developer account in clearos.com and for some reason it is no longer connected to either app-servio nor app-domoticz. I have a feeling the backend is falling apart and there is just nobody home anymore. On top top of that the build system is broken and does not function without someone fixing it first.
Hate to say it, but I have given up and moved on six months ago.
/Fred
No Problem.
At least the information is findable.
Yes. I know COS is dead, but since my server is still running fine I keep it alive.
Moving to another distro with all the packages is difficult and a lot of work, so i postponing it -
Accepted Answer
Patrick,
Sorry, but I just cannot. I just checked my developer account in clearos.com and for some reason it is no longer connected to either app-servio nor app-domoticz. I have a feeling the backend is falling apart and there is just nobody home anymore. On top top of that the build system is broken and does not function without someone fixing it first.
Hate to say it, but I have given up and moved on six months ago.
/Fred -
Accepted Answer
Hi Fred,
Not sure if you are still around on the forum or are able to make a adustment to the app-domoticz
in /usr/clearos/apps/domoticz/libraries/Domoticz.php is a type in line 475
$file->add_lines("debig_level_txt= $debug_level_txt\n");
must be
$file->add_lines("debug_level_txt= $debug_level_txt\n");
Also since build 15170 of domoticz the debug logging changed
this modification in app-domoticz settles this correctly
libraries/Domoticz.php
public function validate_log_level_txt($log_level_txt)
{
clearos_profile(__METHOD__, __LINE__);
if (! preg_match('/(error|normal,error|normal,status,error|normal,status,error,debug)$/', $log_level_txt))
return lang('log_level_invalid');
}
public function validate_debug_level_txt($debug_level_txt)
{
clearos_profile(__METHOD__, __LINE__);
if (! preg_match('/(off|normal|normal,hardware,received,webserver,eventsystem,python,thread_id)$/', $debug_level_txt))
return lang('debug_setting_invalid');
}
views/setting.php
$debug_level_options_txt['normal'] = 'normal';
$debug_level_options_txt['normal,hardware,received,webserver,eventsystem,python,thread_id'] = 'all';
$debug_level_options_txt['normal'] = 'normal';
$debug_level_options_txt['normal,hardware,received,webserver,eventsystem,python,thread_id'] = 'all';
$debug_level_options_txt['off'] = 'off'; -
Accepted Answer
Fredrik Fornstad wrote:
Hint: Look at the History.txt.patch
Release builds will not accept xxxx.xxx if I remember right (translates into appversion)
I guess the history file looks different now and you will need to modify the patch file
Fred
You are a hero
I did a dirty change.
In the Domoticz package i changed manually in the history.txt file the line 2022.xxxx in 2022.3 (just a number) and the compile succeeded
Many thanks for your support !! -
Accepted Answer
-
Accepted Answer
The index.html patch is not critical (it disables two meny items (restart and sw upgrade if I remember right) that do not work anyway in Clearos). So disabling that in the spec file should not affect a successful build.
I tend to remember that one of the other patch files do however define appversion but I might be wrong. Look in my last post in the Serviio thread for some info on patches. You will have to go through the domoticz changes and adapt. This can take some time...
/Fred -
Accepted Answer
Hi Fred,
I was indeed lucky with the 2022.2 build.
I've tried with a newer beta version the compiling has not succeeded
The patch p6 for index.html is not working since this file has been changed.
Missing the knowledge to make a patch, so i exluded this patch in domoticz.spec
After a while i get a error:
[ 15%] Building CXX object CMakeFiles/domoticz.dir/main/CmdLine.cpp.o
[ 15%] Building CXX object CMakeFiles/domoticz.dir/main/Camera.cpp.o
[ 15%] Building CXX object CMakeFiles/domoticz.dir/main/domoticz.cpp.o
In file included from /builddir/build/BUILD/domoticz-14742/main/appversion.h:2,
from /builddir/build/BUILD/domoticz-14742/main/domoticz.cpp:32:
/builddir/build/BUILD/domoticz-14742/main/domoticz.cpp: In function 'void GetAppVersion()':
/builddir/build/BUILD/domoticz-14742/main/../appversion.h:1:20: error: 'xxxx' was not declared in this scope
1 | #define APPVERSION xxxx
| ^~~~
/builddir/build/BUILD/domoticz-14742/main/../appversion.h:1:20: note: in definition of macro 'APPVERSION'
1 | #define APPVERSION xxxx
| ^~~~
make[2]: *** [CMakeFiles/domoticz.dir/build.make:159: CMakeFiles/domoticz.dir/main/domoticz.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:238: CMakeFiles/domoticz.dir/all] Error 2
make: *** [Makefile:172: all] Error 2
error: Bad exit status from /var/tmp/rpm-tmp.b4NdAx (%build)
Not sure if this error is related to the excluded patch. -
Accepted Answer
Patrick,
The file "sources.download" is a special file needed for the Koji build system (it is the instruction to Koji where to download large sources). Your modification is not needed unless you are planning to use a similar build system (which I guess you do not have). Also, your suggested update is not complete, you need to generate a new SHA256 checksum (the "8282cb71c924b6ef92503976d50f966f2c785eab8f8cffa1136ac133f0241157" is for the old domoticz 2022.1 source).
You need to download the source and then calculate the checksum by doing something like this:
Then you copy the output and replace the old checksum in the sources.download. But as I said, when you build manually the file sources.download is not needed at all.wget https://github.com/domoticz/domoticz/archive/refs/tags/2022.2.tar.gz
sha256sum 2022.2.tar.gz
Everything else is OK. The "old" patches should be there unless Domoticz upstream have changed those parts. Without the patches it will not work as intended. In fact, If the old patches work, you were "lucky" this time. There will come a time when the upstream code have changed so much so that the patches will need to be modified. In fact, the Domoticz upstream is not intended to run on such old Linux version as ClearOS 7 so it is just a matter of time until it can't be fixed unless you run Domoticz in a virtualized environment on top of ClearOS if you still like to stick to it.
In addition, if you are running Z-wave: The upstream open-zwave is sort of dead, and even if it was not I do not think it is possible to compile newer version of it anylonger on ClearOS after they introduced the Supervision class last year. I have at least not been able to do it. That means that you will not find any support for new HW models that may enter the market. Domoticz and other home automation softwares have switched to ZwaveJS which have MUCH better support for the Z-wave protocol and is actively supported/developed. Unfortunately (if you ask me) it is not based on a "proper" programming language as C or C++ that can be compiled into a executable suitable for a rpm-package, but is based on Javascript/TypeScript which requires a NodeJS platform etc which in practice makes it a no go in a ClearOS environment (I tested it locally on clearOS and got it to work, but this is not the same thing as an uppgradable system ready for 24/7).
Finally, my recommendation for an alternative "all-in-one" home server would be TrueNAS. At least if you can keep it within your LAN and do not need firewall etc. One of the real advantages is the ZFS file system and the monitoring that goes with it. They have 2 versions "TrueNAS core" and "TrueNAS scale". The core version is based on FreeBSD and is old and very stable. The "scale" version is based on Linux and is almost "too new". The TrueNAS scale is what I personally would use, but I could not: TrueNAS is a "closed environment" which means that you need to install any apps as docker containers which has many advantages, but also some disadvantages. My motherboard do not support "VT-D" hardware virtualization pass through(Both CPU and motherboard need to support it) which means that I cannot assign physical HW directly to my docker containers. With Z-wave USB-dongles etc this was a stopper for me.
An alternative can be openmediavault as it is based on the normal Debian distribution which allows you to install applications such as Domoticz and openzwave directly on the host system. The operating system is also so modern that you can use the Domoticz installation files without the need for patches etc. Openmediavault also has the possibility to use ZFS through the omv-extras packages. However, any packages you install yourself on the host will not be maintained by the automated scripts etc, so this puts more responsibilities on the owner of the server...
/Fred -
Accepted Answer
Fredrik Fornstad wrote:
Patrick, good you got it working. I am afraid that from here on you will be on your own...
There is no way for me to maintain and update any of the ClearOS packages that I have created and supported for years (Domoticz, open-zwave, Serviio, ffmpeg, x264, x265, rtl433, frei0r-plugins, xvidcore, opencore-amr, lame, rtmpdump, vo-amrwbenc, vo-aacenc,vid.stab, dcadec and a few more) as since some time back the build system no longer recognizes my build requests and there is no one on the inside that can help me trigger the builds manually and release to the repos after Nick left.
Also, and this was a killer for me, after July 2022 no ClearOS packages at all have been built/updated, which means that from my perspective that the ClearOS platform is no longer suitable for my use. I have therefore taken the decision to move on and have now my own server up and running on a complete different platform. This was a painful step to take that involved many hours of work, but for me this was neccessary.
/Fred
I/m sorry to hear that you have switched to another OS and you are unfortunately unable to support the packages.
It's totally understandable and I'm afraid many will follow, but certainly many have already switched.
One more little question.
Can you say that what I've done is right?
I saw some patch files from previous versions.
Is it bad if they remain in the build?
Out of curiosity. Which package did you switch to?
Take care and i hope to see you back somewhere -
Accepted Answer
Patrick, good you got it working. I am afraid that from here on you will be on your own...
There is no way for me to maintain and update any of the ClearOS packages that I have created and supported for years (Domoticz, open-zwave, Serviio, ffmpeg, x264, x265, rtl433, frei0r-plugins, xvidcore, opencore-amr, lame, rtmpdump, vo-amrwbenc, vo-aacenc,vid.stab, dcadec and a few more) as since some time back the build system no longer recognizes my build requests and there is no one on the inside that can help me trigger the builds manually and release to the repos after Nick left.
Also, and this was a killer for me, after July 2022 no ClearOS packages at all have been built/updated, which means that from my perspective that the ClearOS platform is no longer suitable for my use. I have therefore taken the decision to move on and have now my own server up and running on a complete different platform. This was a painful step to take that involved many hours of work, but for me this was neccessary.
/Fred -
Accepted Answer
Hi,
Domoticz has released yesterday a new stable version 2022.2
I know it is good to wait a few weeks to see if there are any issues.
Since the development at Clear lately is lacking is have tried it myself to build new package
I've tweaked the build package of Fred and i succeeded
The 2 files "sources.download" and "domoticz.spec" needed to be updated and then just follow the building instruction made by fred
These changes needs to be made after this step:
copy the files into place:
cp ../domoticz-clearos/* SOURCES/
mv SOURCES/domoticz.spec SPECS/
-----------------------
In domoticz.spec the link to Boost-1.7.2 is not valid any more
Source1: https://dl.bintray.com/boostorg/release/1.72.0/source/boost_%{boostver}.tar.bz2
can be changed in
Source1: https://boostorg.jfrog.io/artifactory/main/release/1.72.0/source/boost_%{boostver}.tar.bz2
and
Version: 2022.1
Release: 3%{?dist}
into
Version: 2022.2
Release: 1%{?dist}
in sources.download
8282cb71c924b6ef92503976d50f966f2c785eab8f8cffa1136ac133f0241157 2022.1.tar.gz https://github.com/domoticz/domoticz/archive/refs/tags/2022.1.tar.gz
59c9b274bc451cf91a9ba1dd2c7fdcaf5d60b1b3aa83f2c9fa143417cc660722 boost_1_72_0.tar.bz2 https://phoenixnap.dl.sourceforge.net/project/boost/boost/1.72.0/boost_1_72_0.tar.bz2
into
8282cb71c924b6ef92503976d50f966f2c785eab8f8cffa1136ac133f0241157 2022.2.tar.gz https://github.com/domoticz/domoticz/archive/refs/tags/2022.2.tar.gz
59c9b274bc451cf91a9ba1dd2c7fdcaf5d60b1b3aa83f2c9fa143417cc660722 boost_1_72_0.tar.bz2 https://boostorg.jfrog.io/artifactory/main/release/1.72.0/source/boost_1_72_0.tar.bz2
-----------
Now continue with the next steps.
Good luck -
Accepted Answer
Fred, Nick,
On my VMware test setup i've made a clean install of v2021 and did a update to 2022.
All went smooth and looks like it is working.
SInce i've already made build of 2022 on my production server i'll not installed the package from the repos.
This is the output of the update on my VMware testserver for reference
============================================================================================================================================================================================================
Package Arch Versie Repository Grootte
============================================================================================================================================================================================================
Bijwerken:
domoticz x86_64 2022.1-4.v7 clearos-contribs-testing 11 M
Installeren vanwege afhankelijkheden:
python3-devel x86_64 3.6.8-18.el7 clearos-centos-verified 217 k
python3-rpm-generators noarch 6-2.el7 clearos-centos-verified 20 k
python3-rpm-macros noarch 3-34.el7 clearos-centos-verified 8.1 k
Transactie Samenvatting
============================================================================================================================================================================================================
Installeren ( 3 Afhankelijke pakketten)
Thanks both of you for the effort ! -
Accepted Answer
Fredrik Fornstad wrote:
Koji only. It built from what you committed to the repo unaltered.
Nick Howitt wrote:
Just to double check: Was it my spec file that you needed to tweak or was it Koji? If it was the Domoticz spec file (or any of the source files), then I rather do the change myself too, bump the revision and upload a new version...
It was not with the correct options so I've manually tagged it into clearos-contribs-testing. Hopefully it will build correctly next time without the manual tagging. I can't test until there is a version bump.
.
/Fred -
Accepted Answer
Nick Howitt wrote:
Just to double check: Was it my spec file that you needed to tweak or was it Koji? If it was the Domoticz spec file (or any of the source files), then I rather do the change myself too, bump the revision and upload a new version...
It was not with the correct options so I've manually tagged it into clearos-contribs-testing. Hopefully it will build correctly next time without the manual tagging. I can't test until there is a version bump.
.
/Fred -
Accepted Answer
I've played around a bit with koji and got domoticz to build. It was not with the correct options so I've manually tagged it into clearos-contribs-testing. Hopefully it will build correctly next time without the manual tagging. I can't test until there is a version bump.
I will always have to be contacted to get the package to build in koji in the first place but otherwise I hope it will be OK.
If you can, please test the build and I can then release it. -
Accepted Answer
-
Accepted Answer
That was a lot of python packages you pulled in... I think it was only the python3-devel that you actually needed.
OK, I have now made a domoticz-2022.1-3 release. The only change is that at installation time it now will make sure python3 (incl python3-devel) is installed instead of python34. python3 defaults to 3.6, so it will mean that domoticz now should run python 3.6 even on a complete new system instead of 3.4.
Since you have already installed python 3.6 (among other) in your system, there is no need to update.
If you do want to update anyway, you either follow the original build instructions (for a new build-machine), or if you still have your build-machine around you can do this on it:
cd domoticz-clearos
git pull
cd ../rpmbuild
cp ../domoticz-clearos/* SOURCES/
mv SOURCES/domoticz.spec SPECS/
cd SPECS
rm ../SRPMS/domoticz*
rpmbuild -bs domoticz.spec
cd ../SRPMS
mock domoticz*
After an hour or so the resulting file will be in /var/lib/mock/clearos-7-x86_64/
copy the domoticz-2022.1-3.v7.x86_64.rpm file to the ClearOS machine where you want domoticz installed and on that machine (as root) type:yum localinstall domoticz-2022.1-3.v7.x86_64.rpm -
Accepted Answer
Fredrik Fornstad wrote:
Patrick,
In ClearOS/Centos there is no package called libpython3 to my knowledge, instead I think you mean python3-libs...
Anyway, I will likely update my instruction above to do
in the build machine before doing the rpmbuild -bs domoticz.spec command. I am not sure if it is needed, but it will at least take care of an error message. Also, I will try to update the spec-file itself to make sure python 3.6 is installed together with domoticz.yum install python3-devel
Expect a domoticz-2022.1-3 update in a day or so.
/Fred
I did :yum install libpython3.*
And these package were then installed.
Mar 27 18:15:53 Installed: rh-python38-runtime-2.0-4.el7.x86_64
Mar 27 18:15:53 Installed: 1:tk-8.5.13-6.el7.x86_64
Mar 27 18:15:54 Installed: rh-python35-runtime-2.0-2.el7.x86_64
Mar 27 18:15:55 Installed: rh-python36-runtime-2.0-1.el7.x86_64
Mar 27 18:15:58 Installed: rh-python35-python-libs-3.5.1-13.el7.x86_64
Mar 27 18:15:58 Installed: rh-python35-python-3.5.1-13.el7.x86_64
Mar 27 18:15:58 Installed: rh-python35-python-setuptools-18.0.1-2.el7.noarch
Mar 27 18:15:58 Installed: rh-python35-python-pip-7.1.0-2.el7.noarch
Mar 27 18:15:58 Installed: rh-python35-python-tkinter-3.5.1-13.el7.x86_64
Mar 27 18:15:59 Installed: rh-python35-python-tools-3.5.1-13.el7.x86_64
Mar 27 18:15:59 Installed: python34-tkinter-3.4.10-8.el7.x86_64
Mar 27 18:15:59 Installed: python34-tools-3.4.10-8.el7.x86_64
Mar 27 18:15:59 Installed: python3-tkinter-3.6.8-18.el7.x86_64
Mar 27 18:15:59 Installed: python3-idle-3.6.8-18.el7.x86_64
Mar 27 18:16:01 Installed: python34-test-3.4.10-8.el7.x86_64
Mar 27 18:16:04 Installed: rh-python35-python-test-3.5.1-13.el7.x86_64
Mar 27 18:16:05 Installed: rh-python36-python-pip-9.0.1-5.el7.noarch
Mar 27 18:16:08 Installed: rh-python36-python-libs-3.6.12-1.el7.x86_64
Mar 27 18:16:08 Installed: rh-python36-python-3.6.12-1.el7.x86_64
Mar 27 18:16:08 Installed: rh-python36-python-setuptools-36.5.0-1.el7.noarch
Mar 27 18:16:08 Installed: rh-python36-python-tkinter-3.6.12-1.el7.x86_64
Mar 27 18:16:09 Installed: rh-python36-python-tools-3.6.12-1.el7.x86_64
Mar 27 18:16:12 Installed: rh-python36-python-test-3.6.12-1.el7.x86_64
Mar 27 18:16:12 Installed: rh-python38-python-setuptools-wheel-41.6.0-7.el7.noarch
Mar 27 18:16:12 Installed: rh-python38-python-pip-wheel-19.3.1-2.el7.noarch
Mar 27 18:16:12 Installed: rh-python38-python-setuptools-41.6.0-7.el7.noarch
Mar 27 18:16:12 Installed: rh-python38-python-3.8.11-2.el7.x86_64
Mar 27 18:16:15 Installed: rh-python38-python-libs-3.8.11-2.el7.x86_64
Mar 27 18:16:15 Installed: rh-python38-python-tkinter-3.8.11-2.el7.x86_64
Mar 27 18:16:16 Installed: rh-python38-python-idle-3.8.11-2.el7.x86_64
Mar 27 18:16:20 Installed: rh-python38-python-test-3.8.11-2.el7.x86_64
Mar 27 18:16:20 Installed: rh-python38-python-rpm-macros-3.8.11-2.el7.noarch
Mar 27 18:16:20 Installed: python3-rpm-macros-3-34.el7.noarch
Mar 27 18:16:20 Installed: xml-common-0.6.3-39.el7.noarch
Mar 27 18:16:20 Installed: iso-codes-3.46-2.el7.noarch
Mar 27 18:16:20 Installed: scl-utils-build-20130529-19.el7.x86_64
Mar 27 18:16:21 Installed: rh-python38-python-devel-3.8.11-2.el7.x86_64
Mar 27 18:16:21 Installed: rh-python35-python-devel-3.5.1-13.el7.x86_64
Mar 27 18:16:21 Installed: rh-python36-python-devel-3.6.12-1.el7.x86_64
Mar 27 18:16:24 Installed: python3-test-3.6.8-18.el7.x86_64
Mar 27 18:16:24 Installed: python3-rpm-generators-6-2.el7.noarch
Mar 27 18:16:24 Installed: python3-devel-3.6.8-18.el7.x86_64
Mar 27 18:16:24 Installed: python3-debug-3.6.8-18.el7.x86_64
Mar 27 18:16:25 Installed: rh-python36-python-debug-3.6.12-1.el7.x86_64
Mar 27 18:16:25 Installed: rh-python35-python-debug-3.5.1-13.el7.x86_64
Mar 27 18:16:26 Installed: rh-python38-python-debug-3.8.11-2.el7.x86_64
Mar 27 18:16:26 Installed: python34-debug-3.4.10-8.el7.x86_64
Fredrik Fornstad wrote:
Expect a domoticz-2022.1-3 update in a day or so.
Will there be a change in the build or is it just a cosmetic update ? -
Accepted Answer
Patrick,
In ClearOS/Centos there is no package called libpython3 to my knowledge, instead I think you mean python3-libs...
Anyway, I will likely update my instruction above to do
in the build machine before doing the rpmbuild -bs domoticz.spec command. I am not sure if it is needed, but it will at least take care of an error message. Also, I will try to update the spec-file itself to make sure python 3.6 is installed together with domoticz.yum install python3-devel
Expect a domoticz-2022.1-3 update in a day or so.
/Fred -
Accepted Answer
Hi Fred
I managed to build an rpm version and get Domoticz running on a VMware
Only Domoticz runs on Python 3.4 instead of 3.6.
Both versions of Python are installed and when I do Python --version I get " version 3.6.8"
Now do I aso have a spare server with a copy of an old ClearOS with Domoticz 2021.1 installed.
If I do the update, I just get Domoticz running on Python 3.6.
Now I don't remember if I ever updated anything on this, but do you know if I can get VMware (fresh install) to also run Domoticz with Python 3.6?
---------- UPDATE ----------
Found it!
You need to install libpython
yum install libpython3.*
-
Accepted Answer
Hi Fred,
Many thank you the explanation and works for this.
I'm trying it out now.
Below i've added a small markup in which i ran into following your instaction
If i've more i'll post it
Fredrik Fornstad wrote:
Domoticz 2022.1 is now possible to install in ClearOS 7.
Enter your "normal" user-id that you want to use when you are working with the building machine
Now, let the root-ssh window be aside for a while and open another ssh login.
Login to your machine as the developer (non-root) user you configured in the clearos setup.
download the domoticz package from my github account:
Small add-on.
You need to have the app " Shell Extension" installed from marketplace
https:/xxx.xxx.xxx.xxx/app/marketplace/view/shell_extension_core
After installing the app go to user acocunt and set for the non-root userlogin shell to : /bin/bash
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 »