Hello! Thanks for submitting this!
Would you like to volunteer to write a Salsa-CI test case for this use case? That way we can easily repeat the issue and once fixed, ensure it never happens again. Here is an example how we in the CI test that building an app against libmariadb works: https://salsa.debian.org/mariadb-team/mariadb-10.4/-/blob/master/debian/salsa-ci.yml#L300-321 Basically you just need to have the exact bash commands listed in order for the steps: script: - cd ${WORKING_DIR} # Don't repeat this step, it's just cd ./debian/output - mkdir -p debug # Ensure dir exists before using it - apt-get update - apt-get install -y pkg-config ./libmariadb-dev*.deb ./libmariadb3_*.deb ./mariadb-common*.deb - pkg-config --cflags --libs mysqlclient # See what MySQLdb builds with - apt-get install -y python3-pip - pip3 install mysqlclient # Compiles module against libmysqlclient - apt-get purge -y libmariadb-dev # Not needed for run-time - python3 -c "import MySQLdb; print(MySQLdb.get_client_info())"
