Re: [Bioc-devel] Bioconductor 3.11 is Released!

Congratulations to the entire Bioconductor team for another successful release! I have one question. I cannot find the package artMS in the News . Is there anything wrong with the art

[Bioc-devel] Bioconductor 3.11 is Released!

Thanks to all developers and community members for contributing to the project! Please see the full release announcement: https://bioconductor.org/news/bioc_3_11_release/ The Bioconductor Core Team This email message may contain legally privileged and/or confidential information. If you a

Re: [Bioc-devel] Windows Development Build Error Message for COHCAP

It is not clear what the purpose of these "if" statement is. Apparently to set the $os_name variable but then where is this variable used and for what? So you might want to revisit the need for these tests. Maybe you don't need them after all. Another problem is that the temporary files gene

Re: [Bioc-devel] Windows Development Build Error Message for COHCAP

Hi H, Thank you for pointing that out. I am currently not seeing errors on my Windows computer, but I see that I need to add "msys" for Windows on your system (and add quotes as well as make the error message more clear). I have a 64-bit Windows computer and I didn't get an error message, but

Re: [Bioc-devel] Windows Development Build Error Message for COHCAP

Hi Charles, The error you get on Windows is because your Perl script integrate_island.pl fails on this platform. It contains the following code: if (($os eq "MacOS")||($os eq "darwin")||($os eq "linux")) { #Mac $os_name = "MAC"; }#end if ($os eq

Re: [Bioc-devel] Checking that last commit made the cut

That is the correct location to check. Notice the date at the top of the page is still yesterday. Today's report has not posted yet. When today's report is posted check to see if it is updated. Lori Shepherd Bioconductor Core Team Roswell Park Comprehensive Cancer Center Department of Bi

[Bioc-devel] Checking that last commit made the cut

Hi, I'm the developer for the package MOMA that was just accepted this past cycle. I was re-reading through the vignette on Sunday and realized I needed to add an additional link to a resource and committed the changes around 10 that evening (commit code: c305b841659c3de07ddaef83634cbd7338427462)

Re: [Bioc-devel] Fwd: About rcellminer package

Hi Fathi, You should update the version to 2.11.1, if you want a new build for your package. Developers should only change the version number in the "z" coordinate of the "x.y.z" versioning system. Best, Nitesh Hi Nitesh, My name is Fathi Elloumi one of the maintainer of package rcellm

Re: [Bioc-devel] regutools: request to add more git push access

I've resolved this with Carmina, but I haven't received Emiliano's email. Best, Nitesh On 4/27/2020 11:17 AM, Carmina Barjon wrote: Hi Nitesh! Yes, this it's the email address I will be using (car.bar...@gmail.com ). Thank you Carmina El lun., 27 abr. 2020 a las

Re: [Bioc-devel] Windows Development Build Error Message for COHCAP

Hi Lori, Thank you very much. I was thinking about reverting the change to test not specifying the full file path at one point (in v1.33.6), but I was planning on keeping the change to using a temporary directory in v1.33.4. Essentially, I tested making that change in v1.33.6 because there wa

Re: [Bioc-devel] Images from vignettes

I am not a lawyer, but if you wrote the vignette, then you likely could claim any "rights" to it. In other words, I don't see a problem. Perhaps others have something deeper to add. Sean On Tue, Apr 28, 2020 at 10:14 AM Diego Morais wrote: > Hi everyone, > > a collaborator intends to use an im

[Bioc-devel] Images from vignettes

Hi everyone, a collaborator intends to use an image from the vignette of my package in a book chapter. Do I have to ask permission to publish such image? I don't know if there are copyright issues related to the vignette I wrote. -- Best regards, Diego Morais [[alternative HTML version

Re: [Bioc-devel] Windows Development Build Error Message for COHCAP

I can investigate more on the windows machine after we are done with the release (later this week -- possibly early next) I would highly recommend not reverting the change to using a temporary directory. We don't normally allow anyone to write to anywhere but a temporary directory except in e