On Tue, May 20, 2025 at 4:40 AM Rodrigo Arcoverde Cerveira < rodrigo.arcove...@gmail.com> wrote:
> Hi, > > I got this email and went to check what was the error. It seems it comes > from basilisk r package. From what I checked, the other packages that > depend on basilisk and have used the functions isWindows() or isMacOSX() > are now failing. Were those functions removed from newer basilisk versions > or something else is happening with basilisk? Maybe the basilisk developers > can give us some input. > > Your package declares isMacOSX etc. as being importable from basilisk.utils. The function has moved to basilisk in 3.21. > Best, > Rodrigo > > From: bbs-nore...@bioconductor.org <bbs-nore...@bioconductor.org> > Date: Monday, 19 May 2025 at 18:16 > To: rodrigo.arcove...@gmail.com <rodrigo.arcove...@gmail.com> > Subject: scifer problems reported in the Multiple platform build/check > report for BioC 3.22 > [This is an automatically generated email. Please don't reply.] > > Hi scifer maintainer, > > According to the Multiple platform build/check report for BioC 3.22, > the scifer package has the following problem(s): > > o ERROR for 'R CMD INSTALL' on nebbiolo2. See the details here: > > https://bioconductor.org/checkResults/3.22/bioc-LATEST/scifer/nebbiolo2-install.html > > o ERROR for 'R CMD build' on nebbiolo2. See the details here: > > https://bioconductor.org/checkResults/3.22/bioc-LATEST/scifer/nebbiolo2-buildsrc.html > > Please take the time to address this by committing and pushing > changes to your package at git.bioconductor.org > > Notes: > > * This was the status of your package at the time this email was sent to > you. > Given that the online report is updated daily (in normal conditions) > you > could see something different when you visit the URL(s) above, > especially if > you do so several days after you received this email. > > * It is possible that the problems reported in this report are false > positives, > either because another package (from CRAN or Bioconductor) breaks your > package (if yours depends on it) or because of a Build System problem. > If this is the case, then you can ignore this email. > > * Please check the report again 24h after you've committed your changes > to the > package and make sure that all the problems have gone. > > * If you have questions about this report or need help with the > maintenance of your package, please use the Bioc-devel mailing list: > > https://bioconductor.org/help/mailing-list/ > > (all package maintainers are requested to subscribe to this list) > > For immediate notification of package build status, please > subscribe to your package's RSS feed. Information is at: > > https://bioconductor.org/developers/rss-feeds/ > > Thanks for contributing to the Bioconductor project! > > [[alternative HTML version deleted]] > > _______________________________________________ > Bioc-devel@r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/bioc-devel > -- The information in this email is intended only for the p...{{dropped:15}} _______________________________________________ Bioc-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/bioc-devel