[Bioc-devel] denied access to git

Dear admin,
I re-submit my ssh key to the google form.
Maybe I need to wait to get approved.

Actually I do not have access to push updates for bioCancer package.

bioCancer Mezhoud$  git remote -v
origin    https://github.com/Bioconductor-mirror/bioCancer (fetch)

Notice when you visit the github link that it is 'read only' and further 
(from https://github.com/Bioconductor-mirror) no longer current.

Remove the 'origin' remote, and don't push there

   git remote remove origin
   git push upstream master

Can you help us to understand why you added the Bioconductor-mirror 
remote, so that we can help others avoid the same problem?

Other developers maintain a version of their repository on github, and 
might have added an 'origin' remote pointing there; this is appropriate.

Martin

origin    https://github.com/Bioconductor-mirror/bioCancer (push)
upstream    git at git.bioconductor.org:packages/bioCancer.git (fetch)
upstream    git at git.bioconductor.org:packages/bioCancer.git (push)

git checkout master
Already on 'master'
Your branch is ahead of 'origin/master' by 1 commit.
   (use "git push" to publish your local commits)

git push origin master
remote: Permission to Bioconductor-mirror/bioCancer.git denied to kmezhoud.
fatal: unable to access 'https://github.com/Bioconductor-mirror/bioCancer/':
The requested URL returned error: 403


Thanks,
Karim

	[[alternative HTML version deleted]]

_______________________________________________
Bioc-devel at r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/bioc-devel

This email message may contain legally privileged and/or...{{dropped:2}}

Thank You Dr. Morgan,

When I cloned a repository with git clone , it automatically creates a
remote connection called *origin* pointing back to the cloned repository.

I tried to update bioCancer using old scenario 1:

   -  git clone https://github.com/Bioconductor-mirror/bioCancer
   - cd bioCancer/
   - ../update_remotes.sh
   - get changes to code
   - commit -m "just vignette" -a
   - git svn rebase
   - git svn dcommit --add-author-f

I removed the 'origin' remote but still can not push updates.

git remote remove origin
 git remote -v
upstream    git at git.bioconductor.org:packages/bioCancer.git (fetch)
upstream    git at git.bioconductor.org:packages/bioCancer.git (push)

 git push upstream master
Permission denied (publickey).
fatal: Could not read from remote repository.

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

Thanks,
Karim

Thank You Dr. Morgan,

When I cloned a repository with |git clone| , it automatically creates a 
remote connection called *|origin|* pointing back to the cloned repository.

I tried to update bioCancer using old scenario 1:

  *   git clone https://github.com/Bioconductor-mirror/bioCancer
    <https://github.com/Bioconductor-mirror/bioCancer>

this wasn't the right place to clone from; see the instructions at

   http://bioconductor.org/developers/how-to/git/

you'll probably want to either maintain your package independent of github

   'Maintain a Bioconductor-only repository'

or 'Sync an existing GitHub repository' if you already have bioCancer in 
a github repository.

In either case, you'll need to submit your 'ssh' public key using the form

https://docs.google.com/forms/d/e/1FAIpQLSdlTbNjsQJDp0BA480vo4tNufs0ziNyNmexegNZgNieIovbAA/viewform

using your current svn id 'k.mezhoud'.  The form is still processed 'by 
hand', so you'll have to wait for approximately 24 hours after submission...

Martin

  * cd bioCancer/
  * ../update_remotes.sh
  * get changes to code
  * commit -m "just vignette" -a
  * git svn rebase
  * git svn dcommit --add-author-f

I removed the 'origin' remote but still can not push updates.

git remote remove origin
  git remote -v
upstream    git at git.bioconductor.org:packages/bioCancer.git (fetch)
upstream    git at git.bioconductor.org:packages/bioCancer.git (push)

  git push upstream master
Permission denied (publickey).
fatal: Could not read from remote repository.

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

Thanks,
Karim

This email message may contain legally privileged and/or...{{dropped:2}}