some commonly seen fedpkg errors and solutions

1. fedpkg clone publickey error.

[test@NUC-UEFI fedora-scm]$ fedpkg clone tpm2-tss
Cloning into 'tpm2-tss'...
Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
Could not execute clone: Command '['git', 'clone', 'ssh://test@pkgs.fedoraproject.org/rpms/tpm2-tss', '--origin', 'origin']' returned non-zero exit status 128

Causee:

git clone is using user "test" instead of the FAS account username.

Solution:

$ fedpkg  --user <FAS_USERNAME> clone tpm2-tss

Preconditions(MUST to have before doing "fedpkg clone"):

a) user must get the membership for Fedora packager group.

b) ssh public key of local must be added to FAS account.

2. fedpkg build error - "No credential cache found"

Cause:

The user's credential cache is incorrect ordoes not exist.

Solution:

The user should run kinit beforetrying to start the service.

$ kinit <fas_username>@FEDORAPROJECT.ORG

3, "fedpkg build" hang for long time, "fedpkg -v build" prints some "authentication failure" and "failed connecting to proxy" messages.

Cause: network problem under proxy. "echo $http_proxy" and "echo $https_proxy" to check whether you are using proxies.

Solution: Try not using proxy by "unset http_proxy" and "unset https_proxy".

4.

I updated SPEC, and did a build in Mar:
https://koji.fedoraproject.org/koji/buildinfo?buildID=863183

But when doing "fedpkg update", always get error:
Invalid tag: tpm2-tools-1.1.0-6.fc26 not tagged with any of the following tags [u'f22-updates-candidate', u'dist-6E-epel-testing-candidate', u'f21-updates-candidate', u'f24-updates-candidate', u'f26-updates-candidate', u'epel7-testing-candidate', u'f25-updates-candidate', u'f23-updates-candidate', u'dist-5E-epel-testing-candidate']
Unable to determine release from build: tpm2-tools-1.1.0-6.fc26

Cause:

The tag of build:
https://koji.fedoraproject.org/koji/buildinfo?buildID=863183
is set to fc27, instead of fc26. 

Fix:

Increase release version, do another "fedpkg build" & "fedpkg update".

5. fedpkg update error:

ServerError: ServerError(https://bodhi.fedoraproject.org/updates/, 403, Error returned from json module while processing https://bodhi.fedoraproject.org/updates/: No JSON object could be decoded

It looks like a bug in bodhi. Bug 1445294 - bodhi client cannot submit a new update" 

and workaround is
$ rm ~/.fedora/openidbaseclient-sessions.cache

This will be fixed by python-fedora-0.9 for bodhi-0.9 users, and will be fixed by the combination of python-fedora-0.9 and bodhi-2.6.2 for bodhi-2 users.

More info please refer to:
https://bugzilla.redhat.com/show_bug.cgi?id=1446575
https://bugzilla.redhat.com/show_bug.cgi?id=1445294