[Bioc-devel] Don't have git access to my newly submitted git package

Steve Lianoglou @||@nog|ou @end|ng |rom gm@||@com
Sat Oct 2 05:52:52 CEST 2021

Hello folks,

I think I may have a similar problem accessing the git repos as was
reported by Henrik back in August:

My recently submitted package (sparrow) was just accepted for review:

I added the upstream bioc git repos, and have activated my account under:

I have also confirmed that the public ssh-rsa key under my bioc profile is
the one I have in ~/.ssh/id_rsa.pub

I want to start whacking away at the code so that the package passes on the
bioc build servers, but when I try to push a small change to the upstream
repo, I get this:

$ git push upstream main
FATAL: W any packages/sparrow s.lianoglou 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.

I went in to see what's cooking via ssh and see that I only have read
access to the sparrow repository:

$ ssh -T git using git.bioconductor.org | grep -E "sparrow"
 R   packages/sparrow

But I can also see that I have write access to some repositories I
contributed to back in the day when I was a graduate student (ohhh good

$ ssh -T git using git.bioconductor.org | grep -E "^ R W"
 R W packages/GenomicRanges
 R W packages/Gviz
 R W packages/IRanges

Is this likely something going wrong on my side, or is there something
cooking on the bioc side?

Lastly, I would also like to submit a second "sibling" package along
sparrow that (only) enhances sparrow by adding shiny modules and a full
shiny app to explore GSEA results.

I planned on doing that following the instructions here:

But maybe I should wait until the next cycle (happy to do that)?

There is a package in bioc (gCrisprTools) with an update that relies on
some mojo in my sparrow package and don't want to jeopardize sparrow's
consideration for this release cycle by adding another package for review
on top of that.


Thanks in advance for your time and guidance,

	[[alternative HTML version deleted]]

More information about the Bioc-devel mailing list