Dennis Klein

I can confirm this. Had similar behaviour on current master (a59506f) when running `aliDoctor --defaults o2 FairRoot`. It was missing ROOT and DDS in my case: ``` $ aliDoctor --defaults...

Superseded by #1529 and #1527

https://cdash.gsi.de/testDetails.php?test=19728299&build=448681 This shows also a segfault which is unrelated to your geoloader patches (`v18.6_patches`).

nvm, i confused the PR numbers...

Can you try with the `v18.8_patches` branch of FairRoot? It contains https://github.com/FairRootGroup/FairRoot/commit/db27083b7b54e6cd3dacd77b95590d6bd652f9a6 which appears to address this issue. I'll put on our agenda to prepare a `18.8.2` point release as...

FYI: https://github.com/FairRootGroup/FairRoot/compare/v18.8.1...v18.8_patches

I have also updated the [release notes of FairSoft `jan24`](https://github.com/FairRootGroup/FairSoft/releases/tag/jan24) to reflect this issue. It was actually mistakenly claiming that FairRoot v18.8.1 was tested which clearly it was not. Sry...

> Please consider some of this: > > * Turn `vList` into a value member: currently at thread exit the FairVolumeList is not destructed > * Turn `vList` into a...

FYI: Check https://www.conventionalcommits.org/en/v1.0.0/#summary (That is where the `fix:` comes from when @ChristianTackeGSI or I use them) e.g. * fix(generators): Remove `sprintf` * fix(geobase): Remove `sprintf` * fix(parbase): Remove `sprintf`

What is the decision making process here? Is it possible to re-open it to give zenodo inclusion another shot?