Hello! su 6. tammik. 2019 klo 12.54 Helmut Grohne (hel...@subdivi.de) kirjoitti: > > Hi Otto, > > On Sun, Jan 06, 2019 at 12:19:50PM +0200, Otto Kekäläinen wrote: > > Currenlty in Debian unstable we have mariadb-10.3. Would you be kind > > and rebase, test and submit your patch on mariadb-10.3? > > If "apt-get source libmariadbclient-dev-compat" yields a non-default > version in unstable, then you have cruft in unstable. Would you be kind > and clean up that cruft to make standard workflows work?
I think I have been doing Debian packaging almost every day, even on weekends, for the past 5 weeks. Currently we are in the middle of having mariadb-10.1 in testing and mariadb-10.3 in unstable (along with an updated mysql-defaults in unstable). There are a multitude of issues and due to the complexity of having to adopt to upstream changes that sometimes conflict with Debian needs there is a lot of work. Also, as some areas are regression prone, I have been forced to spend time to develop on CI tooling to ensure we don't get old regressions back again. So all help and encouragement is welcome. Thanks for your patch! In mariadb-10.3 the package libmariadbclient-dev-compat has been replaced by libmariadb-dev-compat (which was previously alreadi in Debian as well as part of https://tracker.debian.org/pkg/mariadb-connector-c but upstream merged the connector into the server source so we need to adapt now. > In particular, please don't let important bugs linger for extended > periods of time without any response. Much less ones that are as trivial > to fix as this one is. Sorry, I wasn't active with the packaging in the fall 2017 due to other priorities and the person active at the time overlooked this, and I seem to have overlooked it as well when i in DebConf 2018 triaged and updated all bugs (but apparently not this one, sorry).
