Bug 943

Summary: Cannot access libreriscv.git via ssh
Product: Libre-SOC Website Reporter: Jacob Lifshay <programmerjake>
Component: websiteAssignee: Luke Kenneth Casson Leighton <lkcl>
Status: RESOLVED FIXED    
Severity: blocker CC: libre-soc-bugs, lkcl, programmerjake
Priority: Highest    
Version: unspecified   
Hardware: PC   
OS: Linux   
NLnet milestone: --- total budget (EUR) for completion of task and all subtasks: 0
budget (EUR) for this task, excluding subtasks' budget: 0 parent task for budget allocation:
child tasks for budget allocation: The table of payments (in EUR) for this task; TOML format:

Description Jacob Lifshay 2022-10-05 02:56:35 BST 
git pull on my existing repo failed, I didn't change anything. cloning via https works.

(libre-soc-venv-3.7) jacob@jacob-desktop:~/projects/libreriscv/libreriscv$ git fetch
FATAL: R any libreriscv jacob1 DENIED by fallthru
(or you mis-spelled the reponame)
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

jacob@jacob-desktop:~$ ssh -p 922 gitolite3@git.libre-soc.org
PTY allocation request failed on channel 0
hello jacob1, this is gitolite3@libre-soc running gitolite3 3.6.12-1 (Debian) on git 2.30.2

 R W	SymbiYosys
 R W	benchmarks
<snip>
 R  	kvm-minippc
 R  	lambdasoc
 R W	libresoc-isa-manual
 R W	libresoc-litex
 R W	litex
 R W	llvm
 R  	ls2
 R  	mesa
 R W	microwatt
<snip>
 R W	yosys
Connection to git.libre-soc.org closed.
jacob@jacob-desktop:~$
Comment 1 Luke Kenneth Casson Leighton 2022-10-05 04:14:03 BST 
keys 1 and 2 (desktop and probook) are definitely there.
Comment 2 Luke Kenneth Casson Leighton 2022-10-05 04:43:36 BST 
(In reply to Luke Kenneth Casson Leighton from comment #1)
> keys 1 and 2 (desktop and probook) are definitely there.

frickin upgrade to 3.6.12 fricked things up.
Comment 3 Jacob Lifshay 2022-10-05 06:50:56 BST 
(In reply to Luke Kenneth Casson Leighton from comment #2)
> (In reply to Luke Kenneth Casson Leighton from comment #1)
> > keys 1 and 2 (desktop and probook) are definitely there.
> 
> frickin upgrade to 3.6.12 fricked things up.

thanks, I verified it's fixed!