Re: [Bioc-devel] Best practice on commit

2018-03-16 Thread Tyler Smith
On Thu, Mar 15, 2018, at 11:26 AM, Hervé Pagès wrote: > > Just to clarify, all software packages are built and checked every > night, independently of whether their version got bumped or not. > The version bump only allows the modified package to propagate > to the public repo and become available

Re: [Bioc-devel] failing Biocondcutor package STAN

2018-03-16 Thread Turaga, Nitesh
Hi, Your key on file is ssh-rsa B3NzaC1yc2EDAQABAAACAQDaTSWfVSqbms8zcOO4DTaf+/11VKnweBjns3Md9tn4TTw2+x4L5vRLj39AMiXVE81wXpzsISI9ybmZK9geVG2yhJyMWeYAbw9U/2tVWDYtfO1jQ2jZKk7ReatPCuVmGL0POZyFRk00CE3zHKBTgN6g29SVLpVffAQeVXR93gSY/X2usO1DNjARoR19kHrRerkn1fJdeKLvVbpeo3y7jUvBVkC4I/T4bkFB1h0o5D2

[Bioc-devel] Fwd: Re: failing Biocondcutor package STAN

2018-03-16 Thread campos
Dear Bioconductor team, I am having some problems with pushing the changes of the package STAN to the master brunch. I recently have changed my PC and I am trying to connect to the bioconductor package but I get the following error: Permission denied (publickey). fatal: Could not read from rem

[Bioc-devel] amplican tokay2 i386 error

2018-03-16 Thread Kornel Labun
Hi, Could you help me diagnose what is wrong with my package, amplican, that fails to pass check on tokay2 i386? I fail to understand what might be wrong from the report http://bioconductor.org/checkResults/devel/bioc-LATEST/amplican/tokay2-checksrc.html . It is long standing problem, since the f

Re: [Bioc-devel] updating experiment data package MethylAidData

2018-03-16 Thread Shepherd, Lori
Yes it can be treated the same as a software package. You would have to push to git.bioconductor.org with a version bump for it to propagate to our system. Your ssh key will have to be submitted and the appropriate maintainer user id will have to be associated with the package just as the softw

[Bioc-devel] Question about Wercker continuous integration

2018-03-16 Thread Kevin RUE
Dear all, I'm usually a big Travis CI fan, but I'm having a go at Wercker, using the bioconductor/devel_core2 docker (I have also tried the rocker 'parent' ones without further success). I am running into the following issue: [...] * creating vignettes ... ERROR Error: processing vignette 'NewPac

Re: [Bioc-devel] Applying changes to existing package

2018-03-16 Thread Shepherd, Lori
you can also check the build and check status on out systems off the daily build reports. It normally can take up to 24 hours for changes to appear but you should see the version number bump. http://bioconductor.org/checkResults/ Lori Shepherd Bioconductor Core Team Roswell Park Cancer Ins

Re: [Bioc-devel] Applying changes to existing package

2018-03-16 Thread Sean Davis
Hi, Christian. There is not yet a browsable version of the Bioconductor git repository. The way to check git.bioconductor.org status is, as you noted, to work with a checkout of the repository locally. If you'd like a more visual view of your local checkout, you might take a look at one of several

[Bioc-devel] Applying changes to existing package

2018-03-16 Thread Christian Oertlin
Hello everyone, I am the maintainer of the anota2seq package. The package was accepted for release 3.6 and is on the bioconductor webpage. I had minor updates for the package which I pushed to the github repositories by following the steps here: https://bioconductor.org/developers/how-to/git/