Using git FAQ for package maintainers

How do I update an existing package?
Refer to How to update a package.

How do I import a SRPM package?
As an alternative, you can import a complete SRPM (.src.rpm) package to update an existing package, using a similar procedure to the initial package import.

The fedpkg tool (from the package) can commit entire src.rpm contents in one step. It uploads new tarballs into lookaside cache, updates a working copy of the last version found in git, and commits all changes. In case you prepare your update packages in an ordinary rpmbuild tree, you can use the script to import a finished update src.rpm in one step. Examples: fedpkg import ~/rpm/SRPMS/foo-1.0-2.src.rpm fedpkg import -b f14 ~/bar-2.1-1.src.rpm Run the command fedpkg import --help for the options it understands. It can also update modules in branch directories other than the default master.

Be careful, since fedpkg can also create non-existing git modules in the master branch on-the-fly. According to current policies, the creation of new modules needs approval. (Changed names here only -- is this accurate? --pfrields 21:33, 31 July 2010 (UTC))

Example for this method
fedpkg clone foo cd foo fedpkg srpm cd foo fedpkg import -b  ~/rpmbuild/SRPM/- - .src.rpm fedpkg switch-branch  git pull fedpkg build
 * 1) You're on the master branch right now.
 * 1) 
 * 2) commit your changes:

How do I add a new package?
Please refer to the new package process for existing contributors and the 'Import of complete src.rpm packages' section above.

How do I add a new branch?
Refer to Package SCM Admin Requests.

How do I remove a branch?
(Would this use git branch -d? --pfrields 21:33, 31 July 2010 (UTC))

How do I make changes to an older branch?
Here is the scenario: you've build your package successfully on the f14 branch, but there is a problem keeping your package from building on f13.

Solution: make your changes in the branch and then add a digit to the very right of the release tag. There is no need to change the release in the other branches. This allows upgrades to work smoothly if the user upgrades to a newer release of Fedora.

Name:   foo Version: 1.0 Release: 1%{?dist}

Name:   foo Version: 1.0 Release: 1%{?dist}.1

Then tag and build as usual.

Refer to https://www.redhat.com/archives/fedora-extras-list/2006-May/msg00083.html for more information.

How do I request a build?
Use the fedpkg build command.

Detailed information about the Fedora build system is at Using the Koji build system.

I have an account but I can't connect to git via ssh
The fedpkg tool clones repositories using the ssh:// protocol, so this should not be a problem normally. If you cloned using the git utility itself, check the file to ensure the remote repository is being accessed via an ssh:// protocol, and not git://.

Please write to accounts at fedora.redhat.com and include all details. There has not been any IP address ACL anymore for months now, so your problem is likely a client configuration issue, private/public key mismatch, or some network problem. (Is this still needed? --pfrields 21:33, 31 July 2010 (UTC))

How do I update/import a new branch?
If a new branch is created on the server side,  should be able to pull the new branch.

Reusing the changelog
fedpkg clog fedpkg commit -F clog
 * Use fedpkg clog to extract the last spec changelog entry and store it in a local "clog" file. Include this file as the git commit log message. This can be done with the following commands:

Expired Certificates (Error 255 or OpenSSL.SSL.Error)
This error usually means that your client certificate (~/.fedora.cert) has expired, so you need to visit the account system and retrieve a new one.

You may need to rerun from the  package, especially if you get the error: : [('SSL routines', 'SSL3_READ_BYTES', 'sslv3 ]alert certificate expired'), ('SSL routines', 'SSL3_WRITE_BYTES', 'ssl handshake failure')

Remove your ~/.fedora-server*ca.cert and rerun  if you get the error: Error: [('SSL routines', 'SSL3_GET_SERVER_CERTIFICATE', 'certificate verify failed')]