Skip to content

[Bioc-devel] Need update access agaisnt package 'banocc'

11 messages · Obenchain, Valerie, Turaga, Nitesh, George Weingart +2 more

#
Hello,

The package banocc has a build error - I was given the task to fix it and
update the "Maintainer" information to include me and the head of our Lab,
Prof. Curtis Huttenhower.

The package was developed originally by Emma Schwager who has left our Lab.

I cloned the package, made the necessary changes, ran a successful BUILD ,
CHECK, BiocCheck and committed the changes and am ready to push the
changes,  but I am getting a "permission denied" message - and indeed, I
see in my profile I can update only ccrepe.

I need update access against 'banocc"

Thanks!

George Weingart PhD

Huttenhower Lab

Harvard School of Public Health
#
Hi George,

Thanks for letting us know - you should now have access.

Valerie
On 10/17/18 10:50 AM, George Weingart wrote:
Hello,

The package banocc has a build error - I was given the task to fix it and
update the "Maintainer" information to include me and the head of our Lab,
Prof. Curtis Huttenhower.

The package was developed originally by Emma Schwager who has left our Lab.

I cloned the package, made the necessary changes, ran a successful BUILD ,
CHECK, BiocCheck and committed the changes and am ready to push the
changes,  but I am getting a "permission denied" message - and indeed, I
see in my profile I can update only ccrepe.

I need update access against 'banocc"

Thanks!

George Weingart PhD

Huttenhower Lab

Harvard School of Public Health


_______________________________________________
Bioc-devel at r-project.org<mailto: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 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.
#
Hi,

This is a follow up to Valerie?s response in regards to the permission to
update ?banocc?

I am still getting an error message when I am trying to push:


Tanias-MacBook-Air:banocc georgeweingart$ git push origin master

fatal: remote error: FATAL: W any packages/banocc nobody DENIED by fallthru

(or you mis-spelled the reponame)


Am I doing something wrong or am I still not permitted to update the
repository ?

Thanks!

George Weingart PhD

Huttenhower Lab

Harvard School of Public Health


DETAILS

List of remotes

Tanias-MacBook-Air:banocc georgeweingart$ git remote -v

origin https://git.bioconductor.org/packages/banocc (fetch)

origin https://git.bioconductor.org/packages/banocc (push)

Log of the commits

Tanias-MacBook-Air:banocc georgeweingart$ git log --oneline

9c411f9 (HEAD -> master) Modified DESCRIPTION to update contacts and added
parms to enable correct compile using C++11

756f013 (origin/master, origin/HEAD) replace BiocInstaller biocLite
mentions with BiocManager

ef9422a bump x.y.z versions to odd y after creation of RELEASE_3_7 branch

d937c6d (origin/RELEASE_3_7) bump x.y.z versions to even y prior to
creation of RELEASE_3_7 branch

5cdd6e0 revert commit 63d51b83b60d6656930e0436a42cd606e5ef23b9

63d51b8 mark as unsupported on 32-bit windows; the builders only have
64-bit pandoc

7b7f415 bump x.y.z versions to odd y after creation of RELEASE_3_6 branch

40bc005 (origin/RELEASE_3_6) bump x.y.z versions to even y prior to
creation of RELEASE_3_6 branch

b471035 bump x.y.z versions to odd y after creation of 3_5 branch

e296cfc bump x.y.z versions to even y prior to creation of 3_5 branch

927028f Adding AnnotationFilter, NADfinder, GenomicDataCommons, RIVER,
BioMedR, banocc




Beginning of the extended log of the commits

Tanias-MacBook-Air:banocc georgeweingart$ git log

commit 9c411f9d62abf39cfc1a32cd888a412577463b5c (HEAD -> master)

Author: George Weingart <george.weingart at gmail.com>

Date:   Wed Oct 17 18:42:24 2018 -0700

   Modified DESCRIPTION to update contacts and added parms to enable
correct compile using C++11

commit 756f0130599144e9ec90e61e84f90a9cec307a94 (origin/master, origin/HEAD)

Author: LiNk-NY <mramos09 at gmail.com>

Date:   Tue Aug 28 18:51:28 2018 -0400

   replace BiocInstaller biocLite mentions with BiocManager

commit ef9422abd0d4e323268c9d807e0a094c9dd07dd6

Author: vobencha <valerie.obenchain at roswellpark.org>

Date:   Mon Apr 30 10:41:43 2018 -0400

   bump x.y.z versions to odd y after creation of RELEASE_3_7 branch

commit d937c6d2f55d92fd3fbcfa1226c65c260cd47387 (origin/RELEASE_3_7)

Author: vobencha <valerie.obenchain at roswellpark.org>

Date:   Mon Apr 30 10:35:46 2018 -0400

   bump x.y.z versions to even y prior to creation of RELEASE_3_7 branch


On Wed, Oct 17, 2018 at 12:21 PM Obenchain, Valerie <
Valerie.Obenchain at roswellpark.org> wrote:

            

  
  
#
Your remotes should look like this,

origin  git at git.bioconductor.org/packages/myPackage.git (fetch)
origin  git at git.bioconductor.org/packages/myPackage.git (push)

Access is through SSH protocol, not HTTPS.

	? SSH (developer) read / write access: git at git.bioconductor.org
	? HTTPS (public) read only access: https://git.bioconductor.org


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

Also, http://bioconductor.org/developers/how-to/git/faq/ (#13).

Best,

Nitesh
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.
#
Typo in there, its ?..org:packages/.."
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.
#
Hello,

Seems I have been able to push successfully but I do not see the build
report - Did I do something wrong or am I alooking at the wrong place?
See enclosed screen print

Thanks for your help !

Tanias-MacBook-Air:banocc georgeweingart$ git push origin master

Counting objects: 8, done.

Delta compression using up to 4 threads.

Compressing objects: 100% (8/8), done.

Writing objects: 100% (8/8), 1.02 KiB | 1.02 MiB/s, done.

Total 8 (delta 6), reused 0 (delta 0)

To git.bioconductor.org:packages/banocc

  756f013..9aee576  master -> master


On Thu, Oct 18, 2018 at 5:16 AM Turaga, Nitesh <
Nitesh.Turaga at roswellpark.org> wrote:

            
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen Shot 2018-10-18 at 7.02.44 AM.png
Type: image/png
Size: 227479 bytes
Desc: not available
URL: <https://stat.ethz.ch/pipermail/bioc-devel/attachments/20181018/ba11beeb/attachment.png>
#
After a push is made it can take up to 48 hours for it to appear on the build report and landing pages - i.e. we do one pull, build, check, propagate in 24 hours - so if your commit was after the pull for the day it wont be until the following day
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.
1 day later
#
Could I trouble you to look at banocc 1.5.2 that I pushed: it has a
warning-
Is that ok or can we leave it like that to be released?

On Thu, Oct 18, 2018 at 7:21 AM Turaga, Nitesh <
Nitesh.Turaga at roswellpark.org> wrote:

            

  
  
#
Good day,

The warning message is caused by a documentation linking inconsistency in R running on different operating systems. It may be avoided, but it's not essential. Perhaps documentation linking will be soon be consistent between operating systems.

--------------------------------------
Dario Strbenac
University of Sydney
Camperdown NSW 2050
Australia
9 days later
#
Could I trouble you to look at banocc 1.5.2 that I pushed: it has a
warning-
Is that ok or can we leave it like that to be released?

On Fri, Oct 19, 2018 at 4:07 PM George Weingart <george.weingart at gmail.com>
wrote:

  
  
#
The last push we had on the git server location was Oct 17th.

commit 9aee5761aaa97a063882a85295747640ec405dfb
Author: George Weingart <george.weingart at gmail.com>
Date:   Wed Oct 17 21:00:43 2018 -0700

    Updated the version number



We have not received any valid push after this date and this is Version: 1.5.2 as per the DESCRIPTION.  The package does not have a WARNING it has an ERROR but only in windows

 http://bioconductor.org/checkResults/devel/bioc-LATEST/banocc/



Your package will still be included in the release and we encourage you to look into this ERROR when you get a chance as having the package ERROR on windows will make in unavailable on this platform and lose a lot of potential users.  Let us know if you are having any troubles with the ERROR by starting a post at bioc-devel at r-project.org


Lori Shepherd

Bioconductor Core Team

Roswell Park Cancer Institute

Department of Biostatistics & Bioinformatics

Elm & Carlton Streets

Buffalo, New York 14263