https://github.com/clearos/clearsync/tags contains tags for 1.5 and 1.6, but the spec file refers to 2.0. It looks like the later version tags were not pushed to github.
Share this post:
Responses (9)
-
Accepted Answer
Nick Howitt wrote:
As far as I am aware, ClearOS does not make use of tags in github. The latest built version should be in the clear7 branch (although the build could have failed ....).
Correct. The ClearOS 7 build system uses branches for production builds. It's not a very good workflow for traditional software releases, but it's a limitation that we have to live with! -
Accepted Answer
Sergej Pupykin wrote:
Regarding webconfig, probably I asked incorrectly: if contents of webconfig repo is not going to be installed using rpm it is ok. But may be I miss something and there is some way to pack it using rpm.
The webconfig is a git super-project that doesn't contain anything new. It's just a convenient way to "git clone" the core ClearOS apps in one place. -
Accepted Answer
-
Accepted Answer
I am rebuilding clearos packages for arm architecture. check-password sources are needed by openldap, yasm source rpm is needed by gconsole (actually by firefox engine I think)
Regarding webconfig, probably I asked incorrectly: if contents of webconfig repo is not going to be installed using rpm it is ok. But may be I miss something and there is some way to pack it using rpm. -
Accepted Answer
I can't see why you want an el5 package. yasm comes from EPEL so you'd have to go there for their sources. If you just want it installed, install it with yum. You should have clearos-epel enabled and it will pull from there.
check_password is an OpenLDAP package so is installed with the openldap-servers package via yum. This appears to be a ClearOS package and I'm not sure where you would go to get the sources.
Why do you need to compile the webconfig? If you are trying to add your own package you don't need to recompile it at all. You'd need to follow the developer guide to see how to do that. I am also not sure where the sources are. A lot is migrating to BitBucket at the moment so you could have a look there. I notice the packages in Github now have the archived flag set so BitBucket is probably a better place to look. -
Accepted Answer
Thank you, I was able to go further. But I have some more questions regarding sources:
I cannot google following source archives:
- yasm-1.2.0-3.el5.src.rpm
- ltb-project-openldap-ppolicy-check-password-1.1.tar.gz (was able to find https://github.com/ltb-project/openldap-ppolicy-check-password/archive/v1.1.tar.gz but it needs to modify rpm spec)
Do you have any source cache?
Also it is not clear how to build https://github.com/clearos/webconfig. There is only clearos6 branch and broken for anonymous users submodule links (needs to switch ssh:// to https://) I was not able to build it using "make local" command. Could you please provide some more information on this package? -
Accepted Answer
I'm missing a stage in my set up notes, but I think it goes like this:
Do a git clone of "clearos/common" from github - this is a one off task.
Clone the package you want to build. I have ssh keys set up so:
This assumes the "clearos/common" is in a folder "common", parallel to clearos-base. You are just symlinking to the Makefile in clearos/common.cd /usr/src
git clone git@github.com:clearos/clearos-base.git
cd clearos-base
ln -s ../common/Makefile Makefile
At this point you can do a:
to build the srpm ormake srpm
to build the final rpm (although mine fails as I need to install pam-devel).make local
-
Accepted Answer
-
Accepted Answer
Please login to post a reply
You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here.
Register Here »