Request for help to make mariadb-10.3 in Debian reproducible

[Otto Kekäläinen]

> > For Mroonga I nor the upstream developers have no clue yet of the
> > root cause
>
> Do you happen to have instructions to just build this part of MariaDB?
> Would love to be able help you out but building the entire server on
> my laptop again and again might not be the most efficient use of
> resources. :)

No, sorry. I've never tried building it in parts. I guess in theory
one could modify the CMakeLists.txt in the project root to pick only
parts, but it might be that Mroonga depends on some previous step to
build. The project does support ccache, and thus later re-builds are
10x faster than the first (slow) build.

An alternative approach could be to build the stand-alone Mroonga from
https://github.com/mroonga/mroonga.

As a side note, the search engine groonga itself is also currently
unreproducible in a similar way (build-id changes, root cause
unclear): https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/diffoscope-results/groonga.html
BUT it is reproducible in testing – and also for mariadb-10.3 the
mroonga plugin does not fail for testing:
https://tests.reproducible-builds.org/debian/rb-pkg/bullseye/amd64/mariadb-10.3.html

If you do some test builds, could you also incorporate
https://salsa.debian.org/mariadb-team/mariadb-10.3/commit/935e2a0b26e11a485c15bd0b54e88d6a1e6afcaa
and validate for me if it fixed the RocksDB plugin?

- Otto