Re: [Bioc-devel] package size issue

It's not appropriate to 'split' your package between the bioconductor git repository and other locations on the internet; you should carefully revise your vignette to convey high quality information within the constraints of Bioconductor's guidelines. Martin On 4/30/19, 1:55 PM, "Bioc-devel o

Re: [Bioc-devel] check error in SeqVarTools

If a user gave that exact set of random numbers as input, then a missing value would be the correct result; it's just the unit test that makes an assumption that all values are not missing. So the problem is in the test, not the code itself. set.seed() is probably the right thing to do here, but a

Re: [Bioc-devel] check error in SeqVarTools

Hi Stephanie, In addition to Lori's advice to make sure that your code works whatever random numbers get generated (otherwise the current issue could also affect your users, not just your unit tests), it's recommended to call set.seed() before you start generating the random numbers in your tes

Re: [Bioc-devel] pushing changes to an existing package

Hi Simina, http://bioconductor.org/developers/how-to/git/faq/ #14 to help us out a little more please. Best, Nitesh On Apr 30, 2019, at 10:45 AM, Simina Boca mailto:smb...@georgetown.edu>> wrote: Hello, I am trying to update my package MultiMed https://www.bioconductor.org/packages/release/

[Bioc-devel] pushing changes to an existing package

Hello, I am trying to update my package MultiMed https://www.bioconductor.org/packages/release/bioc/html/MultiMed.html. It's on Github at https://github.com/SiminaB/MultiMed. I got and updated the SSH key (since I am using a new computer) but when I try to "git fetch --all" I still get a permissio

Re: [Bioc-devel] check error in SeqVarTools

How are you generating random numbers? How is the generation ending up with a missing number? This seems like it might be an edge case that should be caught in your code? Lori Shepherd Bioconductor Core Team Roswell Park Cancer Institute Department of Biostatistics & Bioinformatics Elm &

Re: [Bioc-devel] Access to Bioconductor Git Credentials

Hi Frank, We have reset your email to the new one. Please take a look and activate the account now, and add your SSH keys. I will your credentials to activate in a private email. Thanks, Nitesh > On Apr 30, 2019, at 7:22 AM, Dondelinger, Frank > wrote: > > Hi, > > I am trying to update

Re: [Bioc-devel] Error: remote: error: hook declined to update refs/heads/RELEASE_3_8

The RELEASE_3_8 branch was frozen as of Monday April 15 as announced in preparation for the release 3.9 http://bioconductor.org/developers/release-schedule/ Pushing to the master branch is sufficient for now. Lori Shepherd Bioconductor Core Team Roswell Park Cancer Institute Department

[Bioc-devel] Error: remote: error: hook declined to update refs/heads/RELEASE_3_8

Hello I tried to fix a bug in my Bioconductor package. I managed to push the changes to upstream/master, but I am unable to do so for upstream/RELEASE_3_8. Here is the error message: Counting objects: 12, done. Delta compression using up to 4 threads. Compressing objects: 100% (12/12), done. Writ

[Bioc-devel] Access to Bioconductor Git Credentials

Hi, I am trying to update a package I maintain prior to the upcoming release, but I can't seem to get the Git Credentials. The package is nethet: http://bioconductor.org/packages/3.9/bioc/html/nethet.html and the email address that should be associated with me is fdondelinger.w...@gmail.com. B

Re: [Bioc-devel] Mc OSX fail [MSData::Spectrum::getMZIntensityPairs()] Sizes do not match

Thanks Rainer! Seems to be building and passing now :) http://bioconductor.org/checkResults/devel/bioc-LATEST/msPurity/ Very strange that the error occurs so randomly - I will keep an eye out for it. Thanks, Tom On Mon, Apr 29, 2019 at 5:03 AM Rainer Johannes wrote: > Hi Tom! > > > On 28 Ap