Re: Build with DEB_BUILD_OPTIONS="nocheck" when testing for reproducibility?

> Maybe it would be worth adding DEB_BUILD_OPTIONS=nocheck on the second > build for https://tests.reproducible-builds.org/debian ? It might save > some build time and find some issues that would probably be worth > fixing... This sounds like a good idea! > > Is there some general technique to ru

Build with DEB_BUILD_OPTIONS="nocheck" when testing for reproducibility?

Hi! I noticed https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/mariadb.html is failing on a single test failing in the test suite that runs after the actual build. While the test should of course be made more robust, I am not sure running those tests are relevant for testing rep

Re: Help with Mroonga to finally get all of MariaDB Server reproducible

Hello! Thanks to everybody who helped with MariaDB reproducible builds! Finally mariadb-10.6 builds fully reproducibility in Debian unstable: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/mariadb-10.6.html While I didn't get the `export DEB_BUILD_MAINT_OPTIONS=reproducible=-

Re: Help with Mroonga to finally get all of MariaDB Server reproducible

Hello Vagrant! Picking up this old thread as MariaDB is still unreproducible in Debian unstable. In https://github.com/mroonga/mroonga/issues/298 you wrote: > You could also build with > DEB_BUILD_OPTIONS=reproducible=-fixfilepath,+fixdebugpath and then it might > actually show the embedded bui

Galera 4 reprodicibility on i386 - help needed

Hello! Thanks to Vagrant and Chris for looking into MariaDB/Mroonga reproducibility. I would also like to request help with Galera 4, which fails to build in a reproducible way on i386 only: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/i386/diffoscope-results/galera-4.html Upstre

Help with Mroonga to finally get all of MariaDB Server reproducible

Hello! We still have one issue in MariaDB to solve to have the whole package fully reproducible: https://tests.reproducible-builds.org/debian/rb-pkg/experimental/amd64/diffoscope-results/mariadb-10.5.html Chris Lamb looked into this in Feb 2020[1] and we added one patch[2] but it wasn't enough.

Re: Request for help to make mariadb-10.3 in Debian reproducible

> > Unfortunately none of the changes I made seemed to solve this.. > > 10.3.22 is still unreproducible in unstable due to RocksDB, TokuDB and > > Mroonga. > > Mmm, alas, I only managed to get this to "almost reproducible" stage > before my attention was required elsewhere. > > However, I quickly n

Re: Request for help to make mariadb-10.3 in Debian reproducible

Hello Chris and others, I reported your results at - https://github.com/mroonga/mroonga/issues/298 - https://github.com/groonga/groonga/issues/1079 I also updated the upstream issue at - https://github.com/facebook/rocksdb/issues/6276 Unfortunately none of the changes I made seemed to solve this

Re: Request for help to make mariadb-10.3 in Debian reproducible

Thanks for this! Incredible that any build would ever store the path of the original source code. I can think of anything more useless that having /home/otto/ran/dom permanently in the resulting binary, but apparently some do this. I hope you don't mind if I re-post your findings in upstreams' bu

Re: Request for help to make mariadb-10.3 in Debian reproducible

Hello! ti 21. tammik. 2020 klo 2.06 Chris Lamb kirjoitti: > > As a side note, the search engine groonga itself is also currently > > unreproducible in a similar way (build-id changes, root cause > > unclear): > > Heh, so sometimes I get the impression that some maintainers see the > build-id diff

Re: Request for help to make mariadb-10.3 in Debian reproducible

> > 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 >

Request for help to make mariadb-10.3 in Debian reproducible

Hello! The MariaDB server itself and most of it's additional components are already reproducible and we are very close to the whole source package build reproducibly. For the last remaining issues I now need to request help. Latest results from https://tests.reproducible-builds.org/debian/rb-pkg

Re: Empty build-id to make package reproducible

Thanks everyone for your input. So it was after all a bug in GCC which you fixed in the r-b infra and the hack me and a few others ended up doing at DebConf is now reverted. Git master for package galera-3 is in an optimal state after this discussion and passing CI and reprotest verify it. https

Re: Empty build-id to make package reproducible

Hello! la 1. syysk. 2018 klo 20.42 Mattia Rizzolo (mat...@debian.org) kirjoitti: .. > The thing I can say is that that commit is not fixing *anything*. The > pipeline failed before and after > https://salsa.debian.org/mariadb-team/galera-3/commit/1460cfa128fb457b5b5c60fcc5cac6faf5a216d5 > (as can

Re: Empty build-id to make package reproducible

Hello! pe 31. elok. 2018 klo 0.46 Daniel Kahn Gillmor (d...@fifthhorseman.net) kirjoitti: .. > does this mean that galera-3 debugging symbols won't be easily findable? Perhaps, but we decided that responsibility is important and the package should pass the new CI pipeline we set up at https://sal