On 14 January 2024 at 06:49, Dirk Eddelbuettel wrote: | | FYI two days before you filed #1060101 I actually happened to have updated | r-cran-bh to 1.84.0 (upstream, which is me, went to the 1.84.0 version | released in December as Boost releases every four months) using 1.83: | | r-cran-bh (1.84.0-1) unstable; urgency=medium | | * debian/control: Update Depends back to libboost-dev which will ensure | use of Boost 1.83 matching the just-updated BH package at CRAN which | is now at Boost 1.84 (released in December) which should be close | enough for our needs; a versioned name is no longer needed as the | default is now 1.83.0-2+b2 | | * debian/control: Set Build-Depends: to current R version | * debian/control: Switch to virtual debhelper-compat (= 13) | | -- Dirk Eddelbuettel <e...@debian.org> Wed, 10 Jan 2024 07:20:09 -0600 | | So this should sort itself out by itself in a matter of days. r-cran-bh is | healthy: | | https://tracker.debian.org/pkg/r-cran-bh
And it did, as expected. So no issues from r-cran-bh. Dirk -- dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
