Re: [Bioc-devel] Interpreting BiocCheck output

2022-10-10 Thread Sergio Oller
Hi Giulia, hi all I often run BiocCheck::BiocCheck() on my packages and end up with errors, warnings and notes that have not printed specific enough messages, just as you did. When that happens, on the same R terminal, I use: BiocCheck::.BiocCheck$error BiocCheck::.BiocCheck$warning BiocCheck::.

[Bioc-devel] Version number trouble

2022-10-10 Thread Brüggemann , Mirko
Hello, I’m having some troubles updating my package(BindingSiteFinder) on the devel branch. I’ve made some changes to the code and as always incremented the z part of the version number. Then I realized that the y part of the version number was already changed by the Bioconductor team (to 1.3.

Re: [Bioc-devel] Version number trouble

2022-10-10 Thread Vincent Carey
Hi Mirko -- the devel branch has an odd y in x.y.z stvjc@stvjc-XPS-13-9300:~/BIOC_SOURCES$ cd BindingSiteFinder stvjc@stvjc-XPS-13-9300:~/BIOC_SOURCES/BindingSiteFinder$ grep Version DE* Version: 1.3.0 stvjc@stvjc-XPS-13-9300:~/BIOC_SOURCES/BindingSiteFinder$ git fetch --all Fetching origin The c

Re: [Bioc-devel] Issue with a package dependent on rJava

2022-10-10 Thread Hervé Pagès
Thanks Anestis for your analysis and detailed feedback. @J. Aravind: I hope this is helpful. You should be able to reproduce the problem with a recent version of Java. Generally speaking you want to make sure that your package is compatible with reasonably recent versions of Java. FWIW here ar

Re: [Bioc-devel] Version number trouble

2022-10-10 Thread Brüggemann , Mirko
Hi Vincent, thanks for the clarification. I can now see where I went wrong. I’ve dumped the version number from 1.3.0 to 1.3.1 now. Thanks a lot Mirko Von: Vincent Carey Datum: Montag, 10. Oktober 2022 um 18:26 An: "Brüggemann, Mirko" Cc: "bioc-devel@r-project.org" Betreff: Re: [Bioc-devel