Thanks @xnox for the reply. The patches don't need to be perfect. Upstreaming is helpful because it will bring the issue attention, and the fact that you have identified the issue exactly and written a workaround that is proven to work is surely very helpful and that information should flow upstream in some way or another. If it is not the final solution, this level of debugging information with a working patch surely helps upstream devs a lot and is the path towards a more complete solution.
Riscv64 is also a platform most devs don't have any clue about even exists nowadays in Ubuntu. I already filed an issue for Galera upstream at https://github.com/codership/galera/issues/576 I hope you support the effort by filing an issue upstream at jira.mariadb.org about the issues you found (or for RocksDB even upstream upstream at https://github.com/facebook/rocksdb/issues), and if you open a MR on the Debian packaging at least the mariadb-10.3 can continue to sync while we wait for a better solution to be developed for the riscv64 issues. Thanks! ** Bug watch added: github.com/codership/galera/issues #576 https://github.com/codership/galera/issues/576 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876814 Title: Package mariadb-10.3 forked in Debian, patches not upstreamed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb-10.3/+bug/1876814/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
