Re: [Bioc-devel] verification on configuration

2019-06-10 Thread Nicolas Descostes
if you have any difficulties. > > > Cheers, > > > > Lori Shepherd > > Bioconductor Core Team > > Roswell Park Cancer Institute > > Department of Biostatistics & Bioinformatics > > Elm & Carlton Streets > > Buffalo, New York 14263 >

[Bioc-devel] verification on configuration

2019-06-07 Thread Nicolas Descostes
Hi, I am coming back to my package ChIPSeqSpike after a long break. I have followed the instructions here: https://bioconductor.org/developers/how-to/git/maintain-github-bioc/ I have imported my project in eclipse and did a push after modifying the NEWS file. Will this be visible on the dev page

Re: [Bioc-devel] BiocInstaller: next generation

2018-05-16 Thread Nicolas Descostes
perfect! thanks a lot 2018-05-16 10:32 GMT-04:00 Martin Morgan : > > > On 05/16/2018 10:23 AM, Nicolas Descostes wrote: > >> Dear Martin, >> >> I am starting using BiocInstaller. Regarding the BiocManager::valid(), >> would it be possible to retrieve a lis

[Bioc-devel] BiocInstaller: next generation

2018-05-16 Thread Nicolas Descostes
Dear Martin, I am starting using BiocInstaller. Regarding the BiocManager::valid(), would it be possible to retrieve a list with one element being a vector of the packages to update? or to run BiocManager() as we do with biocLite()? I would find it easier then copying/pasting the suggested comman

Re: [Bioc-devel] htSeqTools and giniCoverage error

2018-05-15 Thread Nicolas Descostes
s, > > > Lori Shepherd > > Bioconductor Core Team > > Roswell Park Cancer Institute > > Department of Biostatistics & Bioinformatics > > Elm & Carlton Streets > > Buffalo, New York 14263 > -- > *From:* Bioc-d

[Bioc-devel] htSeqTools and giniCoverage error

2018-05-13 Thread Nicolas Descostes
Dear all, I am using htseqtools on the devel version and I get the following error when using giniCoverage: test <- lapply(endoExoBamlist, function(bam_files){ return(lapply(bam_files, function(bamfile){ ga <- if(paired)

Re: [Bioc-devel] biocValid() and package version

2018-05-11 Thread Nicolas Descostes
gt; ------ > *From:* Bioc-devel on behalf of > Nicolas Descostes > *Sent:* Thursday, May 10, 2018 5:44:43 PM > *To:* bioc-devel@r-project.org > *Subject:* [Bioc-devel] biocValid() and package version > > Hi, > > I am using R-devel with R 3.5 as my pac

[Bioc-devel] biocValid() and package version

2018-05-10 Thread Nicolas Descostes
Hi, I am using R-devel with R 3.5 as my package will be released with this version. I want to make sure that I am using the latest version of all packages: library("BiocInstaller") biocValid() Installed Built ReposVer airway "0.112.0" "3.4.3" "

[Bioc-devel] commit not appearing in report

2018-04-13 Thread Nicolas Descostes
Dear Community, I have done a commit the 11th of April that does not appear anywhere. My package is ChIPSeqSpike and the last push should be 0.99.22. The build report indicates: *ChIPSeqSpike <http://bioconductor.org/packages/3.7/bioc/html/ChIPSeqSpike.html> 0.99.21* Nicolas Descoste

[Bioc-devel] Daily build

2018-03-07 Thread Nicolas Descostes
Dear community, When my package ChIPSeqSpike was accepted, I have been noticed that no further action was required regarding my github ( https://github.com/descostesn/ChIPSeqSpike). I did two commits with version bump yesterday and I did not receive any notification. I checked the version at http

[Bioc-devel] Best practice on commit

2018-02-23 Thread Nicolas Descostes
Dear Bioconductor community, When developing further a package, is the best practice to create a branch and bump the version when a full new feature is merged or to stay on the master without bumping when committing temporarily? More generally, When do you usually bump a version? Thank you. Nic