attachment
0001-Use-the-correct-remote-when-listing-revs.patch

Otherwise, someone downstream may end up in the following situation:

{{{
Traceback (most recent call last):
File "/usr/bin/fedpkg", line 959, in
args.command(args)
File "/usr/bin/fedpkg", line 319, in build
url, chain)
File "/usr/lib/python2.6/site-packages/pyfedpkg/init.py", line 796, in build
if self.repo.git.rev_list('%s...%s' % (branch, remote)):
File "/usr/lib/python2.6/site-packages/git/cmd.py", line 127, in
return lambda args, kwargs: self._call_process(name, args, kwargs)
File "/usr/lib/python2.6/site-packages/git/cmd.py", line 342, in _call_process
return self.execute(call, _kwargs)
File "/usr/lib/python2.6/site-packages/git/cmd.py", line 249, in execute
raise GitCommandError(command, status, stderr_value)
git.errors.GitCommandError: 'git rev-list el5/custom-kolabsys.com...origin/el5/custom-kolabsys.com' \
returned exit status 128: fatal: ambiguous argument \
'el5/custom-kolabsys.com...origin/el5/custom-kolabsys.com': \
unknown revision or path not in the working tree.
Use '--' to separate paths from revisions
}}}

Applied. Thanks.