[Bioc-devel] git push confusion

[Turaga, Nitesh]

You can check which version is being used by going to this link

http://bioconductor.org/checkResults/devel/bioc-LATEST/rgsepd/malbec2-buildsrc.html

It seems that your package is using the commit from Oct 30th. We’ll take a look at this, it seems to be an issue with the build system. Your Bioconductor git server is up to date though, you can see if you commit posted by taking a look at our log http://bioconductor.org/developers/gitlog/ or subscribing to our feed.


Best,

Nitesh 



> On Apr 23, 2018, at 12:19 PM, Karl Stamm <karl.stamm at gmail.com> wrote:
> 
> I did all that. git push upstream master says "everything up to date" and step 7 says confirm the changes by browsing Github.
> Github.org has had the changes since Friday but the build servers did not have the changes when the build was attempted on Sunday.  Are they on a branch other than "master"? How can I tell what the build servers are using ? 
> 
> On Mon, Apr 23, 2018 at 11:14 AM, Turaga, Nitesh <Nitesh.Turaga at roswellpark.org> wrote:
> Please check out the documentation
> 
> http://bioconductor.org/developers/how-to/git/push-to-github-bioc/
> 
> > On Apr 23, 2018, at 12:13 PM, Karl Stamm <karl.stamm at gmail.com> wrote:
> > 
> > How do I "push to both"? I dont understand the numerous git terminology. On Friday I tried to push the bugfix but the build server still errors.
> > git log
> > commit 17c35588bcb6d87a9520cfad6d7d52fa209c517f (HEAD -> master, upstream/master, origin/master, origin/HEAD)
> > 
> > So I guess the build servers are not "upstream/master" ?? 
> > 
> > I have this setup as given in the bioconductor documentation
> > git remote -v
> > origin        git at github.com:kstammits/rgsepd.git (fetch)
> > origin        git at github.com:kstammits/rgsepd.git (push)
> > upstream      git at git.bioconductor.org:packages/rgsepd.git (fetch)
> > upstream      git at git.bioconductor.org:packages/rgsepd.git (push)
> > 
> > 
> > And when I do various push commands they say "everything up to date"  
> > But I want to make sure the bioc servers get the update before the 3.7 lockdown. Is there any way to see what the are holding ? 
> > 
> > 
> > 
> > 
> > 
> > On Mon, Apr 23, 2018 at 10:26 AM, Turaga, Nitesh <Nitesh.Turaga at roswellpark.org> wrote:
> > Hi Karl,
> > 
> > Bioconductor doesn’t automatically grab changes from your Github. A large body of the work is maintained only on our Bioconductor git server. The maintainer has to push to both Github and the Bioconductor server if the changes have to propagate. 
> > 
> > RELEASE_3_6 is now frozen forever. We announced this on April 11th. You cannot push to this anymore. You can still make your changes on your master branch. 
> > 
> > https://stat.ethz.ch/pipermail/bioc-devel/2018-April/013212.html
> > 
> > Best,
> > 
> > Nitesh 
> > 
> > 
> > 
> > 
> > > On Apr 23, 2018, at 11:21 AM, Karl Stamm <karl.stamm at gmail.com> wrote:
> > > 
> > > I got a message this morning that malbec2 has build errors on my package.
> > > It's a bug I fixed a few days ago, but it looks like I didn't push changes
> > > to the right branches or something.  How do I get the bioc systems to take
> > > from the github updates?
> > > The help documents on the bioconductor website say to push to RELEASE_3_6
> > > but that doesn't seem to work. And the build server is running the previous
> > > code version, but calling it 3.7.
> > > I'm not sure they've gotten my changes, how can i see which versions the
> > > build servers have? Seems they do not automatically grab from github since
> > > the bug was fixed a few days ago there.
> > > 
> > >       [[alternative HTML version deleted]]
> > > 
> > > _______________________________________________
> > > 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.
> > 
> 
> 
> 
> 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.