Dear Paul, thanks for noticing. You are right the migration was not possible due to the Python transition.
The problem was a chicken and egg one. And the update of the package was done to make the python migration possible (by removing remnants of the old python version from all opm packages). In retrospect that might not have been the best idea? Seems like this has actually worked as after the python transition finished all the autopkgtests are green on [1]. Or am I missing something? But maybe the correct fix would be to have a versioned dependency on the python lib for all binary packages that have references to it in the CMake configuration files? That would then be for all libopm-*-dev packages which ship these. At least this might prevent problems in future transitions. On a side note: We seem to have similar (or more serious) problems with opm-material, see [2]. There I do not understand why opm-models (which requires opm-material) can actually block the migration. But that might my limited knowledge. Would be cool if someone would enlighten me in this regard. Cheers, Markus [1] https://qa.debian.org/excuses.php?package=opm-grid [2] https://qa.debian.org/excuses.php?package=opm-material
signature.asc
Description: PGP signature
