[Bioc-devel] Git pushing problems for data package

This is suboptimal:

Email: tim.triche at gmail.com
GitHub Username: jamorrison

As you might imagine, I am not Jacob and Jacob is not me.  I'm wondering
how this happened?


--t


On Sun, Nov 17, 2019 at 4:17 PM Tim Triche, Jr. <tim.triche at gmail.com>
wrote:

I went to the git login checker, and activated my (usual) maintainer
address:
https://git.bioconductor.org/BiocCredentials/permissions_by_user/

This informed me that I have access (as tim.triche at gmail.com) to:
'tim.triche at gmail.com' has access to the following packages:
methylumi
methyAnalysis

So that doesn't seem like a good thing either.  I'm getting progressively
more confused the deeper I look :-/


--t


On Sun, Nov 17, 2019 at 3:46 PM Tim Triche, Jr. <tim.triche at gmail.com>
wrote:

Actually, it seems to have somehow got worse?!

$ cd MTseeker
$ git push upstream
FATAL: W any packages/MTseeker t.triche 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.

Now it seems as if all repositories are using t.triche for access
somehow?  Perhaps I have misconfigured something somewhere.  I will look
into this... but my github SSH keys are all for `ttriche` not `t.triche`.



--t


On Sun, Nov 17, 2019 at 3:21 PM Tim Triche, Jr. <tim.triche at gmail.com>
wrote:

Hi Nitesh,

I'm afraid that I am still getting the same problems today where it
asks for authentication as "t.triche" instead of "ttriche".  Could you
check into this?

$ git clone git at github.com:trichelab/MTseekerData.git
$ cd MTseekerData
$ git remote add upstream git at git.bioconductor.org:
packages/MTseekerData
$ git push upstream master
FATAL: W any packages/MTseekerData t.triche 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.

# OK, let's check:

$ git clone git at git.bioconductor.org:packages/MTseekerData
MTseekerData.bioc
remote: Compressing objects: 100% (84/84), done.
remote: Total 165 (delta 82), reused 146 (delta 70)
Receiving objects: 100% (165/165), 9.93 MiB | 7.90 MiB/s, done.
Resolving deltas: 100% (82/82), done.

$ grep Version MTseekerData/DESCRIPTION
Version: 1.5.2

$ grep Version MTseekerData.bioc/DESCRIPTION
Version: 1.5.0

$ grep name ~/.gitconfig
name = ttriche

I'm out of ideas ...


--t


On Fri, Nov 15, 2019 at 11:09 AM Tim Triche, Jr. <tim.triche at gmail.com>
wrote:

Thanks Nitesh! Not sure how that happened but thanks for fixing it.

--t

On Nov 15, 2019, at 7:56 AM, Turaga, Nitesh <

Nitesh.Turaga at roswellpark.org> wrote:

?Hi Tim,

That's because you have for some reason two different usernames with

Bioconductor.

I've corrected the issue. You are now universally "ttriche" only.

You should have access now.

Best

Nitesh

On Nov 15, 2019, at 9:52 AM, Tim Triche, Jr. <tim.triche at gmail.com>

wrote:

Hi all,

How do I push changes to my  MTseekerData package in git?

I get the following error when I try to commit changes:

tim at tim-ThinkPad-T470:~/Dropbox/MTseekerData$ git remote -v
origin git at github.com:trichelab/MTseekerData.git (fetch)
origin git at github.com:trichelab/MTseekerData.git (push)
upstream git at git.bioconductor.org:packages/MTseekerData (fetch)
upstream git at git.bioconductor.org:packages/MTseekerData (push)
tim at tim-ThinkPad-T470:~/Dropbox/MTseekerData$ git pull upstream

master

From git.bioconductor.org:packages/MTseekerData
* branch            master     -> FETCH_HEAD
Already up to date.
tim at tim-ThinkPad-T470:~/Dropbox/MTseekerData$ git push upstream
FATAL: W any packages/MTseekerData t.triche 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 do not get this problem when pushing to the MTseeker git

repository.

Thanks for any insights,


--t
   [[alternative HTML version deleted]]

This email message may contain legally privileged and/or

confidential information.  If you are not the intended recipient(s), or the
employee or agent responsible for the delivery of this message to the
intended recipient(s), you are hereby notified that any disclosure,
copying, distribution, or use of this email message is prohibited.  If you
have received this message in error, please notify the sender immediately
by e-mail and delete this email message from your computer. Thank you.