[Bioc-devel] unable to push to new package

[Gross Fridolin]

Dear Nitesh,

Thanks so much! After we did as you suggested, pushing upstream worked fine.

There is still a warning in the build report<http://bioconductor.org/spb_reports/scanMiR_buildreport_20210426195015.html>, but it seems that this is not under our control:
* checking whether package 'scanMiR' can be installed ... WARNING
Found the following significant warnings:
  Warning: no function found corresponding to methods exports from 'S4Vectors' for: 'combineRows'
See 'C:/Users/pkgbuild/packagebuilder/workers/jobs/2067/scanMiR_20210426194208/scanMiR.Rcheck/00install.out' for details.

Do you have any suggestions on how to proceed?

Thanks again.

Best,
Fridolin

On 23 Apr 2021, at 14:49, Nitesh Turaga <nturaga.bioc using gmail.com<mailto:nturaga.bioc using gmail.com>> wrote:

Another problem is you SSH key available on your github accout is compromised. It’s available on another account already. (This usually happens when you share the same key around and it gets added to user accounts who that want to maintain the same package).

Please create a new SSH key and add it to your account after you activate ithttps://git.bioconductor.org/BiocCredentials/account_activation .

I would also recommend deleting your Github SSH key, because it matches Pierre’s. This is the wrong way to do it. Both of you should delete that key.

Best,

Nitesh

From: Nitesh Turaga <nturaga.bioc using gmail.com<mailto:nturaga.bioc using gmail.com>>
Date: Friday, April 23, 2021 at 8:41 AM
To: Gross Fridolin <fridolin.gross using hest.ethz.ch<mailto:fridolin.gross using hest.ethz.ch>>, bioc-devel using r-project.org<mailto:bioc-devel using r-project.org> <bioc-devel using r-project.org<mailto:bioc-devel using r-project.org>>
Subject: Re: unable to push to new package
Hi,

You do not have write privileges to the package because only the maintainer (cre) is given write access.

The submission is a little messy here, because


  1.  It’s submitted from a lab account (this is ok in general)
  2.  You are not listed as maintainer, but want to maintain the package.
  3.  You are the one corresponding with us, when ideally,  ("Pierre-Luc", "Germain", email=pierre-luc.germain using hest.ethz.ch<mailto:pierre-luc.germain using hest.ethz.ch>) should be the one.


I will manually make an account for you. Please add your SSH keys to your BiocCredentials account (https://git.bioconductor.org/BiocCredentials/) after activating it. Then change the Maintainer field in the description file.

Best,

Nitesh

From: Bioc-devel <bioc-devel-bounces using r-project.org<mailto:bioc-devel-bounces using r-project.org>> on behalf of Gross Fridolin <fridolin.gross using hest.ethz.ch<mailto:fridolin.gross using hest.ethz.ch>>
Date: Friday, April 23, 2021 at 4:14 AM
To: bioc-devel using r-project.org<mailto:bioc-devel using r-project.org> <bioc-devel using r-project.org<mailto:bioc-devel using r-project.org>>
Subject: [Bioc-devel] unable to push to new package
Hi all,

I have submitted our package ‘scanMiR’ yesterday, which is now in the 'review in progress’ phase (https://github.com/Bioconductor/Contributions/issues/2067).

When trying to push changes upstream, I get the error:

> $ git push upstream master
> Enter passphrase for key '/home/fgross/.ssh/id_ed25519':
> FATAL: W any packages/scanMiR plger 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.


The remotes seem to be set up correctly:

> $ git remote -v
> origin        https://github.com/ETHZ-INS/scanMiR/ (fetch)
> origin        https://github.com/ETHZ-INS/scanMiR/ (push)
> upstream      git using git.bioconductor.org<mailto:git using git.bioconductor.org>:packages/scanMiR (fetch)
> upstream      git using git.bioconductor.org<mailto:git using git.bioconductor.org>:packages/scanMiR (push)


However, I do not have write permission to the package (as shown by  ssh -T git using git.bioconductor.org<mailto:git using git.bioconductor.org>).

Could this be related to the fact that the original repo was located not on my account but at an organization? Or that I am listed as “author” in the package description, and not as “creator”?

I’d be grateful for any kind of help to understand and resolve this problem.

Best,
Fridolin




_______________________________________________
Bioc-devel using r-project.org<mailto:Bioc-devel using r-project.org> mailing list
https://stat.ethz.ch/mailman/listinfo/bioc-devel


	[[alternative HTML version deleted]]