(Created page with "{{shortcut|RSOP:BRANCH}} == Description == <!-- Put a description of the task here. --> This SOP covers how to make git and pkgdb branches for packages, either for new packages t...") |
(→Normal Action (automated): The script has been moved to the releng repo) |
||
(One intermediate revision by one other user not shown) | |||
Line 17: | Line 17: | ||
3) Clone the fedora-infrastructure tools repository: | 3) Clone the fedora-infrastructure tools repository: | ||
<pre> | <pre> | ||
git clone ssh://git.fedorahosted.org/git/ | git clone ssh://git.fedorahosted.org/git/releng.git | ||
</pre> | </pre> | ||
Line 24: | Line 24: | ||
== Manual Action == | == Manual Action == | ||
=== Creating a new branch for an existing package === | |||
1) ssh into pkgs.fedoraproject.org | |||
2) pkgdb-client edit -u $YOURUSERNAME -b $NEWBRANCH --master=devel $NAMEOFPACKAGE | |||
3) pkgdb2branch.py $NAMEOFPACKAGE | |||
[[Category:Release Engineering SOPs]] | [[Category:Release Engineering SOPs]] |
Revision as of 13:01, 22 August 2014
Description
This SOP covers how to make git and pkgdb branches for packages, either for new packages that have passed review, or for existing packages that need a new branch (e.g. EPEL). Release Engineering has written a script to automate this process.
Normal Action (automated)
1) On your local system (not on an infrastructure hosted system), be sure you have the following packages installed:
- python-bugzilla
- python-configobj
- python-fedora
2) Run "bugzilla login" and successfully receive an Authorization cookie.
3) Clone the fedora-infrastructure tools repository:
git clone ssh://git.fedorahosted.org/git/releng.git
4) In scripts/process-git-requests, run "process-git-requests". Answer the prompts.
Manual Action
Creating a new branch for an existing package
1) ssh into pkgs.fedoraproject.org
2) pkgdb-client edit -u $YOURUSERNAME -b $NEWBRANCH --master=devel $NAMEOFPACKAGE
3) pkgdb2branch.py $NAMEOFPACKAGE