L’algorithme de Cesium v1.7.x exclus les API BMA des nœuds Duniter v1.9.x.
Je veux bien faire des images de la 1.9.1 mais je ne vois aucun tag de ce nom sur le dépôt. C’est normal ?
J’ai tenté un build à partir de la branche release/1.9.1 et ça échoue :
Step 11/28 : RUN PATH=${HOME}/.cargo/bin:${PATH} RUSTFLAGS="-C target-feature=-crt-static -L/usr/lib" make -C release ADD_DEBUG=N INSTALL_DEX=${INSTALL_DEX} server-gui clean && rm -rf work/extra
---> Running in 05372e5b65a5
make: Entering directory '/duniter/release'
make[1]: Entering directory '/duniter/work'
> leveldown@5.6.0 install /duniter/work/node_modules/leveldown
> node-gyp-build
> sqlite3@4.1.1 install /duniter/work/node_modules/sqlite3
> node-pre-gyp install --fallback-to-build
node-pre-gyp WARN Using request for node-pre-gyp https download
[sqlite3] Success: "/duniter/work/node_modules/sqlite3/lib/binding/node-v64-linux-x64/node_sqlite3.node" is installed via remote
added 878 packages from 1069 contributors and audited 881 packages in 10.863s
19 packages are looking for funding
run `npm fund` for details
found 161 vulnerabilities (25 low, 34 moderate, 80 high, 22 critical)
run `npm audit fix` to fix them, or `npm audit` for details
> duniter@1.9.1 install /duniter/work
> ./neon/build.sh
neon info forcing rebuild for new build settings
neon info running cargo
error: failed to parse lock file at: /duniter/work/Cargo.lock
Caused by:
package `constant_time_eq` is specified twice in the lockfile
neon ERR! cargo build failed
Cela semble étrange que personne d’autre n’ai eu ce soucis de double définition dans le fichier Cargo.lock …