Thanks for your note. I don't know that bioc-devel is a great venue to discuss this event for a particular package.
Nor am I completely clear on what platform-specific failures imply for package acceptance etc., but it seems to me the package is part of 3.21 and hence implicitly for 3.22. Finally, ** testing if installed package can be loaded from temporary location adding rname 'SignalR.db' Warning in value[[3L]](cond) : trying to add rname 'SignalR.db' produced error: all(rtype == "web" | file.exists(fpath)) is not TRUE Error: package or namespace load failed for ‘BulkSignalR’: .onLoad failed in loadNamespace() for 'BulkSignalR', details: call: BiocFileCache::bfcrpath(bfc, rnames = basename(url)) error: not all 'rnames' found or unique. Error: loading failed Execution halted ERROR: loading failed * removing ‘/home/biocbuild/tmp/RtmpdavE0V/Rinst13968a1cf9dbf8/BulkSignalR’ seems to me to be a problem of intermittent failure of web access. While it may resolve "by itself" in some future attempt, it would be wise to program defensively so that your package installation does not fail when something of this sort occurs in the future. This topic could be entertained further on support.bioconductor.org or on the developer forum slack channel. I would greatly appreciate having improvements to our documentation components that address this topic, and PRs would be welcome. Hope that is helpful; thanks for your participation in Bioconductor! On Sat, Apr 12, 2025 at 8:21 AM Jean-Philippe Villemin <jpville...@gmail.com> wrote: > Dear Bioconductor team, > > We were surprised to see that the build of our package BulkSignalR has > recently failed, although it was successful in previous snapshots. We > haven't made any changes to the package since the last successful builds, > so we're unsure what might be causing the issue. > > Interestingly, the build fails only on certain platforms — namely Windows > Server 2022 and Linux (openEuler 24.03 LTS) / aarch64 — while it completes > successfully(install/build & check) on Linux distributions and macOS. > > Would it be possible to access the list or history of build/check results > across the different time snapshots? Do you keep such logs somewhere that > we could consult to better understand what might have changed? > > As this issue appeared at the very last minute, just before the upcoming > April 16 release, we would also like to know if there is still a chance for > *BulkSignalR* to be included in the release if the issue is resolved > quickly. > > If not, what happens next? Will the package remain in the *devel* branch > automatically until the next Bioconductor release in October? > > Thank you very much for your help. > > -- > *Jean-Philippe Villemin *- Bioinformatics, PhD - > > Precision Imaging as a New Key in Cancer Care (PINKcc Lab) > > Institut de Recherche en Cancérologie de Montpellier > > Inserm U1194 > > > *jpville...@gmail.com <jpville...@gmail.com>* > > [[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
