681
edits
Changes
Jump to navigation
Jump to search
Line 4:
Line 4: − + Line 12:
Line 12: − + Line 24:
Line 24: − + + + + + + + + + + + + + + + + + + + + + + + + +
How to create Smeserver RPM using the gitea repository (view source)
Revision as of 13:30, 19 February 2024
, 19 February→Add into Bugzilla
=== Detailed Instructions ===
=== Detailed Instructions ===
# Create a new repository as follows:
# [[File:Screenshot from 2024-01-30 11-53-07.png|thumb|Parameters to Gitea create new repo]]Create a new repository as follows:
## Fill in name (typically smeserver-<specific name>
## Fill in name (typically smeserver-<specific name>
## Add a description (this will be used on the readme.MD)
## Add a description (this will be used on the readme.MD)
# Return to your build system
# Return to your build system
# Clone the new repo
# Clone the new repo
# Run the "git-post-create-repo.sh <organisation> repo-name". This will rename the spec file and fill in the bugzilla and wiki entries readme.MD and the repo data relating to the Wiki and Bugzillaa..
# Run the "git-post-create-repo.sh <organisation> repo-name". This will rename the spec file and fill in the bugzilla and wiki entries readme.MD and the repo data relating to the Wiki and Bugzilla..
# Add in files / directories etc required under the "root" directory.
# Add in files / directories etc required under the "root" directory.
# Edit the spec file.
# Edit the spec file.
In the interim before we move completely to the gitea repo, then you should be able to take the src rpm and import it into CVS.
In the interim before we move completely to the gitea repo, then you should be able to take the src rpm and import it into CVS.
I'll fill in how to do that when I get it done!
I did this successfully, but not until a lot of fiddling - the next time I have to do it, I may be able to define the necessary steps.
It involves the helper script /usr/bin/importNew which is part of the smeserver-mock package.
However it requires the presence of the "common" directory and "CVSROOT" in the correct place - in Parallel with ~/smecontribs/rpm. They can be checked out of CVS.
I am not clear if it requires to be run on the koozali infastructure build server or can be run on your own build server (with ssh access to the buildserver). Hopefully the latter.
I also note that calls to the CVS while on the infra build server only work if the connection is made locally, eg
cvs -z3 -d /cvs/smecontribs co -P common
[[File:Screenshot from 2024-02-19 10-13-15.png|thumb|Final confirmation of package added]]
=== Add into Bugzilla ===
# Log into Bugzilla
# Click on Administration on the top of the page (if you do not have this, then you do not have enough permissions to do the job).
# Click on Products
# Click on Which ever "products of..." is the one you want.
# Choose the next area
# Click on "Edit Components"
# Then "Add"
# Add in details of new package and submit.
[[Category:Developer]]