Comment 6 for bug 1840485

Hi Rafael,

Thank you for working on this!

I see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933019 for the glusterfs issue, making this FTBFS in sid. There's also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922344 for an autopkgtest regression. I'm not sure if that's the same issue as the one you're fixing here, but I think Debian also currently has your failure.

I suppose the dropping of glusterfs support is a feature change, but bareos isn't currently in the Eoan release pocket at all right now.

Is this worth doing all this disabling in Ubuntu right now, or would it be better to leave it for Debian to fix for possible inclusion in Ubuntu next cycle? Is it worth the delta, the risk of introducing broken not-Postgres support (due to it now being untested), without Debian's support (since they have this version of the package stuck in unstable), and with the ongoing maintenance burden for Ubuntu?

Some minor notes on your debdiff in case we decide to continue:

+ * Disable glusterfs support due to API changes
+ * Disable MySQL/SQLite DEP8 due to bad tests (LP: #1840485)

This makes it look like LP: #1840485 doesn't relate to "Disable glusterfs support" but it does. You could adjust the changelog entry to make this clear, but it's also difficult to link this bug to the Debian glusterfs bug so perhaps this bug needs splitting into two?

It's a useful technique when experimenting, but please avoid "commenting out" in final uploads. I see this as unnecessary cruft that others are forced to read through later, though I'm interested to hear if others disagree. The changelog will record that you removed those lines, and we can use a VCS, or simply debdiffs, if we want to restore them again later.