install_tidyverse.sh will fail due to fstcore 0.9.10

[eitsupi]

Today's build of rocker/tidyverse:devel was failing.
https://github.com/rocker-org/rocker-versioned2/runs/5637125401?check_suite_focus=true#step:5:13618

The new version of fstcore released today seems to be the cause. (fstpackage/fstcore#7)

#6 1783.9 * installing *source* package ‘fstcore’ ...
#6 1783.9 ** package ‘fstcore’ successfully unpacked and MD5 sums checked
#6 1783.9 ** using staged installation
#6 1783.9 0.29.1
#6 1783.9 Package liblz4 was not found in the pkg-config search path.
#6 1783.9 Perhaps you should add the directory containing `liblz4.pc'
#6 1783.9 to the PKG_CONFIG_PATH environment variable
#6 1783.9 No package 'liblz4' found
#6 1783.9 Package liblz4 was not found in the pkg-config search path.
#6 1783.9 Perhaps you should add the directory containing `liblz4.pc'
#6 1783.9 to the PKG_CONFIG_PATH environment variable
#6 1783.9 No package 'liblz4' found
#6 1783.9 Using PKG_CFLAGS= and PKG_LIBS=-llz4
#6 1783.9 ------------------------- ANTICONF ERROR ---------------------------
#6 1783.9 Configuration failed because liblz4 was not found. Try installing:
#6 1783.9  * deb: liblz4-dev (Debian, Ubuntu, etc)
#6 1783.9  * rpm: liblz4-devel (Fedora, CentOS, RHEL)
#6 1783.9  * csw: liblz4_dev (Solaris)
#6 1783.9  * OSX: lz4 (macOS)
#6 1783.9 If liblz4 is already installed, check that 'pkg-config' is in your
#6 1783.9 PATH and PKG_CONFIG_PATH contains a liblz4.pc file. If pkg-config
#6 1783.9 is unavailable you can set INCLUDE_LZ4_DIR and LIB_LZ4_DIR manually via:
#6 1783.9 R CMD INSTALL --configure-vars='INCLUDE_LZ4_DIR=... LIB_LZ4_DIR=...'
#6 1783.9 Alternatively, you can build the required libraries directly from bundled code by
#6 1783.9 setting BUILD_INTERNAL_LIBS to true
#6 1783.9 --------------------------------------------------------------------
#6 1783.9 ERROR: configuration failed for package ‘fstcore’

[benz0li]

libzstd-dev is required for source installation, too.

[eitsupi]

I found that even URLs that are supposed to do a binary install fail because they do a source install fstcore.
fstcore 0.9.12 is not yet available in RSPM, so I guess I will have to wait until tomorrow.

https://github.com/rocker-org/rocker-versioned2/actions/runs/2027975192

#8 83.03 * installing *binary* package ‘duckdb’ ...
#8 83.03 * DONE (duckdb)
#8 83.03 make: Target 'all' not remade because of errors.
#8 83.03 * installing *source* package ‘fstcore’ ...
#8 83.03 ** package ‘fstcore’ successfully unpacked and MD5 sums checked
#8 83.03 ** using staged installation
#8 83.03 0.29.1
#8 83.03 Package liblz4 was not found in the pkg-config search path.
#8 83.03 Perhaps you should add the directory containing `liblz4.pc'
#8 83.03 to the PKG_CONFIG_PATH environment variable
#8 83.03 No package 'liblz4' found
#8 83.03 Package liblz4 was not found in the pkg-config search path.
#8 83.03 Perhaps you should add the directory containing `liblz4.pc'
#8 83.03 to the PKG_CONFIG_PATH environment variable
#8 83.03 No package 'liblz4' found
#8 83.03 Using PKG_CFLAGS= and PKG_LIBS=-llz4
#8 83.03 ------------------------- ANTICONF ERROR ---------------------------
#8 83.03 Configuration failed because liblz4 was not found. Try installing:
#8 83.03  * deb: liblz4-dev (Debian, Ubuntu, etc)
#8 83.03  * rpm: liblz4-devel (Fedora, CentOS, RHEL)
#8 83.03  * csw: liblz4_dev (Solaris)
#8 83.03  * OSX: lz4 (macOS)
#8 83.03 If liblz4 is already installed, check that 'pkg-config' is in your
#8 83.03 PATH and PKG_CONFIG_PATH contains a liblz4.pc file. If pkg-config
#8 83.03 is unavailable you can set INCLUDE_LZ4_DIR and LIB_LZ4_DIR manually via:
#8 83.03 R CMD INSTALL --configure-vars='INCLUDE_LZ4_DIR=... LIB_LZ4_DIR=...'
#8 83.03 Alternatively, you can build the required libraries directly from bundled code by
#8 83.03 setting BUILD_INTERNAL_LIBS to true
#8 83.03 --------------------------------------------------------------------
#8 83.03 ERROR: configuration failed for package ‘fstcore’
#8 83.03 * removing ‘/usr/local/lib/R/site-library/fstcore’
#8 83.04 cat: fst.out: No such file or directory

[eitsupi]

Seems to have been resolved in a new release.