On Mon, 18 May 2020, 14:18 Richard Shaw, <hobbes1...@gmail.com> wrote:
> I'm trying this for the first time (hadn't even noticed it was there!). > I've been using the src.fp.o github style forking from the web. > > I cloned a random project of mine and then tried: > $ fedpkg fork > Could not execute do_distgit_fork: The following error occurred while > creating a new fork: Invalid or expired token. Please visit > https://src.fedoraproject.org/settings#nav-api-tab to get or renew your > API token. > For invalid or expired token refer to "fedpkg fork -h" to set a token in > your user configuration. > > I checked src.fp.o/settings and even though my key was still valid, it was > going to expire this month so I went ahead and generated a new api token > and saved it in the specified location: > ~/.config/rpkg/fedpkg.conf > > But I still get the same message 10 minutes later. > I've got the same problem. I think it uses wrong remote path: a...@pkgs.fedoraproject.org Maybe it was working before, but then certain update happened. If you check clone options in UI in Pagure interface, the url will look like: ssh://book...@pkgs.fedoraproject.org/forks/bookwar/rpms/minetest.git There is no variant with "any". The API token is valid and works, as the fork is created. It is only the remote path which is broken. So I ended up calling git remote explicitly after the fork command to change the remote uri. And I think forking your own repo for pull-requests makes perfect sense, especially since distgit doesn't allow you to remove temporary branches from the main repo. -- Aleksandra Fedorova bookwar
_______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
