Skip to content

[Bioc-devel] Trying to access the source repository of a bioconductor package (Developer Access)

8 messages · Enio Gjerga, Shepherd, Lori, Turaga, Nitesh

#
You should try and set up your system using SSH from your Github account as well.
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.
2 days later
#
Hi,

Thank you very much. After following your suggestion I went to set up the
SSH and I was also able to clone the packages I was maintaining locally.
Next I did my desired changes to the cloned package locally and I wanted to
push these changes to the Bioconductor repositories. For that I used the
following commands:

1. git checkout master from where I got a list of files in the package
labeled as M/D and the message: Already on 'master'. Your branch is up to
date with 'origin/master'.

2. git push upstream master from where I got the message: Everything
up-to-date.

Does this mean that my changes are pushed to Bioconductor repositories
correctly?

 Thank you again for all the help:))

Cheers,
Enio

On Fri, 27 Mar 2020 at 17:43, Turaga, Nitesh <Nitesh.Turaga at roswellpark.org>
wrote:

  
    
#
I do not see any changes in the git.bioconductor.org server on the master branch.

Did you remember to do the following to commit your changes before you tried pushing?

git commit -a


In general a good basic workflow for working on the devel (master) branch is

git fetch --all
git pull
git pull upstream origin
# make your changes  including a version bump
git commit -a       # commit your changes and give an informative message
git push
git push upstream master



Lori Shepherd

Bioconductor Core Team

Roswell Park Comprehensive Cancer Center

Department of Biostatistics & Bioinformatics

Elm & Carlton Streets

Buffalo, New York 14263
#
Hi,

Ok thank you. I do the commit as following: 'git commit -a #update
CNORfeeder' and then I get the following:

# Please enter the commit message for your changes. Lines starting

# with '#' will be ignored, and an empty message aborts the commit.

#

# On branch master

# Your branch is up to date with 'origin/master'.

#

# Changes to be committed:

#       modified:   DESCRIPTION

#       modified:   NAMESPACE

#       modified:   vignettes/CNORfeeder-vignette.Rnw

#

# Untracked files:

#       R/buildFeederObjectDynamic.R

#       R/computeMSE.R

#       R/getLBodeContObjFunctionWeighted.R

#       R/identifyMisfitIndices.R

#       R/integrateLinks.R

#       R/parEstimationLBodeSSmWeighted.R

#       R/parEstimationLBodeWeighted.R

#       R/preprocessingWeighted.R

#       R/runDynamicFeeder.R

#       data/CNOlistToy_Gene.RData

"~/CNORfeeder/.git/COMMIT_EDITMSG" 43L, 1176C

However from this point the terminal becomes un-responsive and cannot type
anything. Then I quit this dialog through :wq after which I get the
following error:

hint: Waiting for your editor to close the file... error: There was a
problem with the editor 'vi'.

Please supply the message using either -m or -F option.

Please, how can I fix this issue?

Cheers,

On Mon, 30 Mar 2020 at 13:56, Shepherd, Lori <Lori.Shepherd at roswellpark.org>
wrote:

  
    
#
That is asking you to make a commit message to summarize the changes.  It is traceable when you use git log.   You should type a commit message summarizing what you want to say


Lori Shepherd

Bioconductor Core Team

Roswell Park Comprehensive Cancer Center

Department of Biostatistics & Bioinformatics

Elm & Carlton Streets

Buffalo, New York 14263
#
Hi Enio,

Based on the conversation you, Lori and I had, it seems that you are having a hard time with git as a version control system in general and not the Bioconductor git repository in general. 

Please consider going through some good learning material so you can get started with git.

There are many resources where you can learn about git and GitHub.
	? git-and-github-learning-resources, https://help.github.com/articles/git-and-github-learning-resources/
	? git-scm, https://git-scm.com/
	? Guides, https://guides.github.com/


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.
#
Hello,

Yes thank you. I am very new on git and will definitively have a look.
However I think that I might have correctly pushed my changes to the
CNORfeeder and the CNORode packages. Can someone please confirm if that the
case? If not, I will carefully read the links before for the next time.

Best,

On Mon, 30 Mar 2020 at 14:46, Turaga, Nitesh <Nitesh.Turaga at roswellpark.org>
wrote:

  
    
#
Yes.  I see the changes pushed this morning.   They should be reflected on tomorrow's build report.


Lori Shepherd

Bioconductor Core Team

Roswell Park Comprehensive Cancer Center

Department of Biostatistics & Bioinformatics

Elm & Carlton Streets

Buffalo, New York 14263