Open TristanCacqueray opened 2 years ago
Currently I think it mostly works for repos cloned over ssh. (There might be some unreleased tweaks for this in git - not sure have to check the logs.)
Here is the clone's .git/config:
[core]
repositoryformatversion = 0
filemode = true
bare = false
logallrefupdates = true
[remote "origin"]
url = https://src.fedoraproject.org/rpms/supercollider
fetch = +refs/heads/*:refs/remotes/origin/*
[branch "rawhide"]
remote = origin
merge = refs/heads/rawhide
I would recommend though to use fbrnch clone
or at least fedpkg clone
, which both default to ssh.
You are correct that https does work too apparently - whereas I was simplifying/assuming a https repo to be an anonymous checkout.
Maybe some user config could be added: like "prefer-https-to-ssh". I probably won't get it that soon though.
It is also useful to have support for "anonymous checkouts" (eg if you are working on a host without your ssh keys or not a Fedora packager), and https: is probably the main way to do that currently (maybe git: also works).
And perhaps the tool could have reminded me that:
* run `fedpkg scratch-build --srpm` to build in koji
(You mean fbrnch scratch
* then run `fedpkg push` to submit the update
and fbrnch build
? ;o)
But I do like your idea of suggesting next steps... that would be friendly - let me see later...
Just noting this page here: https://fedoraproject.org/wiki/Infrastructure/HTTPS-commits
Hi, it seems like the update command does not work with package cloned over http.
Here is what I did:
fbrnch update
Here is what I got:
Here is what I expected:
And perhaps the tool could have reminded me that:
fedpkg scratch-build --srpm
to build in kojifedpkg push
to submit the update