[Bioc-devel] Fwd: update bioconductor package

[minoo ashtiani]

Thanks for your reply.

The email associated with jafarilab was  jafarilab.pasteur using gmail.com and I
can't sign in with that. I am the only one who makes changes on the IMMAN
package and I would be really grateful help to get through this. I saw
below materials on BiocCredential:

Bioconductor Git Credentials
Logout
View User Profile
Which packages do I have access to?
User Profile
Email: ashtiani.minoo using gmail.com
GitHub Username: Minoo-Ashtiani
Last login: Jan. 27, 2019, 12:29 p.m.
SSH Key(s):
ssh-rsa
.......

So I think Minoo-Ashtiani username is associated with
ashtiani.minoo using gmail.com. And so how can I apply the first step?

Bests,
Minoo






[image: Mailtrack]
<https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5&>
Sender
notified by
Mailtrack
<https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5&>
02/09/19,
12:41:40 AM

On Sat, Feb 9, 2019 at 12:20 AM Turaga, Nitesh <
Nitesh.Turaga using roswellpark.org> wrote:

> You have the same email associated with “jafarilab” (
> ashtiani.mino using gmail.com). The main problem is, you need to have two
> completely separate entities as profiles.
>
> I suggest once again, that instead of us changing things on our end to
> accommodate a special case, you just push your changes to your GitHub
> repository, and just sync with the existing credentials.
>
> Otherwise, there is a different solution,
>
> 1. You have to change the email associated with the “jafarilab”
> BiocCredentials handle.
>
> 2. If no one from that “jafarilab” handle is going to be sending updates
> to git.bioconductor.org, we change it completely to another profile
> created on BiocCredentials which is associated with your email,
> ashtiani.minoo using gmail.com
>
> Once you have done step 1, please let me know I will create a new profile
> for you on BiocCredentials and get it up and running.
>
> Best,
>
> Nitesh
>
>
> > On Feb 8, 2019, at 2:22 PM, minoo ashtiani <ashtiani.minoo using gmail.com>
> wrote:
> >
> > Thank you very much Nitesh.
> >
> > I would be really grateful if you give me the access right.
> >
> > Bests,
> > Minoo
> >
> > On Fri, Feb 8, 2019 at 8:58 PM Turaga, Nitesh <
> Nitesh.Turaga using roswellpark.org> wrote:
> > Hi Minoo,
> >
> > There is access to just one username with the IMMAN package “jafarilab”.
> You cannot gain access through “Minoo-Ashtiani” as it checks for the SSH
> key and knows there is one user already registered with that key.
> >
> > I would suggest everyone in the lab, submit changes to
> https://github.com/jafarilab/IMMAN. And then, sync the GitHub repo with
> git.bioconductor.org:packages/IMMAN using the “jafarilab” account. This
> way, there credential management is handled entirely from your end.
> >
> > Otherwise, I’d have to give you access rights and you’d have to set up
> new SSH keys again.
> >
> > Best,
> >
> > Nitesh
> >
> >
> >
> > > On Feb 8, 2019, at 4:01 AM, minoo ashtiani <ashtiani.minoo using gmail.com>
> wrote:
> > >
> > >
> > > Dear Nitesh,
> > >
> > > Thanks for your help. I used
> http://bioconductor.org/developers/how-to/git/maintain-bioc-only/ to
> maintain my package. However, when I write this line
> > >
> > >  $ git clone git using git.bioconductor.org:packages/IMMAN
> > > Cloning into 'IMMAN'...
> > > git using git.bioconductor.org: Permission denied (publickey).
> > > fatal: Could not read from remote repository.
> > >
> > > Please make sure you have the correct access rights
> > > and the repository exists.
> > >
> > > I got this error and I don't know how to fix it.
> > >
> > > PS: I am using another GitHub profile for maintenance. The first one
> was "jafarilab" that I published the package with that and now I am using
> "Minoo-Ashtiani" for updating. However, I have added the package SSH key to
> the "Minoo-AShtiani" profile.
> > > Would please help get through this? I have no idea how to fix.
> > >
> > > All the best,
> > > Minoo
> > >
> > >
> > >
> > >       Sender notified by
> > > Mailtrack 02/08/19, 12:29:23 PM
> > >
> > > On Sun, Jan 27, 2019 at 7:07 PM Turaga, Nitesh <
> Nitesh.Turaga using roswellpark.org> wrote:
> > > You need to have access to your repository at git.bioconductor.org.
> > >
> > > http://bioconductor.org/developers/how-to/git/
> > >
> > > You should find all of your documentation in that link.
> > >
> > > Nitesh
> > >
> > >
> > >
> > > > On Jan 27, 2019, at 2:50 AM, minoo ashtiani <
> ashtiani.minoo using gmail.com> wrote:
> > > >
> > > > Hello everyone,
> > > >
> > > > I would like to update my Bioconductor package named "IMMAN". I made
> some
> > > > changes and I wanted to update the package on the Bioconductor
> repository
> > > > too, but I don't know how can I do it. Any idea?
> > > >
> > > >
> > > > Bests,
> > > > Minoo
> > > >
> > > >
> > > > [image: Mailtrack]
> > > > <
> https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5&
> >
> > > > Sender
> > > > notified by
> > > > Mailtrack
> > > > <
> https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5&
> >
> > > > 01/27/19,
> > > > 11:18:05 AM
> > > >
> > > >       [[alternative HTML version deleted]]
> > > >
> > > > _______________________________________________
> > > > Bioc-devel using 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.
>
>
>
> 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.


[image: Mailtrack]
<https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5&>
Sender
notified by
Mailtrack
<https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5&>
02/09/19,
12:52:20 AM

	[[alternative HTML version deleted]]