Hi, I'm more of a follower than a contributor, but I've kind of followed the seabios project for awhile.
I like to keep my git repos up to date. However, when I run:
$ git pull fatal: unable to update url base from redirection: asked for: https://git.seabios.org/cgit/seabios.git/info/refs?service=git-upload-pack redirect: https://review.coreboot.org/plugins/gitiles/seabios/
Now, mind you, my remote was set to git.seabios.org/cgit/seabios.git. So seeing the error, I opted to go to the repository myself to see what the matter was. My browser redirected me to https://review.coreboot.org/plugins/gitiles/seabios/ which included a directive to "git clone ssh://review.coreboot.org:29418/seabios" to clone the repo. So I tried it. However, this failed with:
$ git clone ssh://review.coreboot.org:29418/seabios Cloning into 'seabios'... xxxxxxxx@review.coreboot.org: Permission denied (publickey). fatal: Could not read from remote repository.
Obviously my pubkey isn't going to be in any authorized_keys file, nor would I expect it to be. So my question is: how do I keep my seabios repo up-to-date, as the repo seems to have moved and something is possibly fubar. Is anonymous read-only access even a thing for seabios anymore?
Dear Pvt,
Am 22.05.21 um 10:48 schrieb Pvt Snafu via SeaBIOS:
Hi, I'm more of a follower than a contributor, but I've kind of followed the seabios project for awhile.
I like to keep my git repos up to date. However, when I run:
$ git pull fatal: unable to update url base from redirection: asked for: https://git.seabios.org/cgit/seabios.git/info/refs?service=git-upload-pack redirect: https://review.coreboot.org/plugins/gitiles/seabios/
Now, mind you, my remote was set to git.seabios.org/cgit/seabios.git. So seeing the error, I opted to go to the repository myself to see what the matter was. My browser redirected me to https://review.coreboot.org/plugins/gitiles/seabios/ which included a directive to "git clone ssh://review.coreboot.org:29418/seabios" to clone the repo. So I tried it. However, this failed with:
$ git clone ssh://review.coreboot.org:29418/seabios Cloning into 'seabios'... xxxxxxxx@review.coreboot.org: Permission denied (publickey). fatal: Could not read from remote repository.
Obviously my pubkey isn't going to be in any authorized_keys file, nor would I expect it to be. So my question is: how do I keep my seabios repo up-to-date, as the repo seems to have moved and something is possibly fubar. Is anonymous read-only access even a thing for seabios anymore?
Please use
git clone https://git.seabios.org/seabios.git
as described on the Web site on the page *Download* [1].
Kind regards,
Paul
-
Paul Menzel -
Pvt Snafu