Hi Tim, I've standardized your user name across your packages.
Firstly, please check https://git.bioconductor.org/BiocCredentials/permissions_by_user/, And tell me what you see? Nitesh On 11/18/19, 5:27 AM, "Bioc-devel on behalf of Turaga, Nitesh" <bioc-devel-boun...@r-project.org on behalf of nitesh.tur...@roswellpark.org> wrote: Hi Tim, It seems like you may have had more than two usernames. I might have ended my search too early. I'll fix this. Just give me a little time. Best Nitesh -- Nitesh Turaga Senior Programmer Analyst Bioconductor core team Roswell Park ________________________________ From: Tim Triche, Jr. <tim.tri...@gmail.com> Sent: Sunday, November 17, 2019 4:25:26 PM To: Turaga, Nitesh <nitesh.tur...@roswellpark.org> Cc: Hervé Pagès <Bioc-devel@r-project.org> Subject: Re: [Bioc-devel] Git pushing problems for data package Followup: I changed my github username associated with my email address to my actual GitHub username (I am thinking that we will need to update the maintainer email for `biscuiteer` and `biscuiteerData` as a result). However, the Bioconductor credentials checker indicates that I still don't have access to maintain the repositories that I am maintaining. So if you could counsel me on how to fix that, it would be awesome, because I've run out of ideas on my end :-/ Thanks so much! --t On Sun, Nov 17, 2019 at 4:19 PM Tim Triche, Jr. <tim.tri...@gmail.com<mailto:tim.tri...@gmail.com>> wrote: This is suboptimal: Email: tim.tri...@gmail.com<mailto:tim.tri...@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.tri...@gmail.com<mailto:tim.tri...@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.tri...@gmail.com<mailto:tim.tri...@gmail.com>) to: 'tim.tri...@gmail.com<mailto:tim.tri...@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.tri...@gmail.com<mailto:tim.tri...@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.tri...@gmail.com<mailto:tim.tri...@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 g...@github.com:trichelab/MTseekerData.git $ cd MTseekerData $ git remote add upstream g...@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 g...@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.tri...@gmail.com<mailto:tim.tri...@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.tur...@roswellpark.org<mailto:nitesh.tur...@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.tri...@gmail.com<mailto:tim.tri...@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@tim-ThinkPad-T470:~/Dropbox/MTseekerData$ git remote -v >> origin g...@github.com:trichelab/MTseekerData.git (fetch) >> origin g...@github.com:trichelab/MTseekerData.git (push) >> upstream g...@git.bioconductor.org:packages/MTseekerData (fetch) >> upstream g...@git.bioconductor.org:packages/MTseekerData (push) >> tim@tim-ThinkPad-T470:~/Dropbox/MTseekerData$ git pull upstream master >> From git.bioconductor.org:packages/MTseekerData >> * branch master -> FETCH_HEAD >> Already up to date. >> tim@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]] >> >> _______________________________________________ >> Bioc-devel@r-project.org<mailto:Bioc-devel@r-project.org> mailing list >> https://stat.ethz.ch/mailman/listinfo/bioc-devel > > > > 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. 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. [[alternative HTML version deleted]] _______________________________________________ Bioc-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/bioc-devel 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. _______________________________________________ Bioc-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/bioc-devel
