#246 fedpkg request-branch requests branch in wrong repo
Closed: Fixed by onosek. Opened by jerboaa.

I've just tried to request a byteman branch for the objectweb-asm rpms repo. Here is what I did:

$ pwd
/home/sgehwolf/Documents/rpm_packaging/fedora/objectweb-asm
$ fedpkg --module-name byteman request-branch byteman --no-auto-module --sl rawhide:2018-12-01

That created a ticket like this:
https://pagure.io/releng/fedora-scm-requests/issue/7273

Note the "repo": "byteman" value in the json.

I'm not sure why. Some more info on the objectweb-asm repo clone:

$ git remote -v
origin  ssh://jerboaa@pkgs.fedoraproject.org/forks/jerboaa/rpms/objectweb-asm.git (fetch)
origin  ssh://jerboaa@pkgs.fedoraproject.org/forks/jerboaa/rpms/objectweb-asm.git (push)
upstream-ssh    ssh://jerboaa@pkgs.fedoraproject.org/rpms/objectweb-asm (fetch)
upstream-ssh    ssh://jerboaa@pkgs.fedoraproject.org/rpms/objectweb-asm (push)

Version info:
$ rpm -q fedpkg
fedpkg-1.33-2.fc28.noarch


Are you trying to request a branch for objectweb-asm?

Are you trying to request a branch for objectweb-asm?

Yes. Sorry, if that wasn't obvious. The above commands were run from a local clone of objectweb-asm rpms/objectweb-asm repo.

@jerboaa The problem should be you use fedpkg --module-name byteman, instead byteman should be replaced with objectweb-asm.

fedpkg has already have new option --repo for request-branch, hence that command to request a branch can be rewritten in this way:

fedpkg request-branch byteman --repo objectweb-asm --no-auto-module --sl rawhide:2018-12-01

Just to summarize, for the case above, all of the commands will work with the same result:

fedpkg --name objectweb-asm request-branch byteman --no-auto-module --sl rawhide:2020-12-01
fedpkg request-branch byteman --no-auto-module --sl rawhide:2020-12-01 --repo objectweb-asm

(for the next command, repo is detected as a current directory)

fedpkg request-branch byteman --no-auto-module --sl rawhide:2020-12-01

Metadata Update from @onosek:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

Metadata