On 2021-05-22 Olaf van der Spek wrote: > Op za 22 mei 2021 om 04:27 schreef Trevor Cordes > <deb...@tecnopolis.ca>: > > > > On Thu, 26 Nov 2020 12:50:26 -0500 The Wanderer > > <wande...@fastmail.fm> wrote: > > Which means at one time this was fixed. That's why this used to > > work for us. But something must have regressed in the source, and > > the fix > > MariaDB 10.3 uses libreadline-gplv2 > MariaDB 10.5 uses libedit > I think this explains the changes in behavior.
Sort of. I think earlier MariaDB/Mysql gave the option for either libreadline or libedit? In any event, I experienced these symptoms a few years ago with MariaDB, and at that time (going from memory) it was because Fedora changed from compiling with readline to libedit. And at that time the solution was to make an .editrc with the bindings you wanted. Since I made an .editrc, and that fixed the symptoms, that proves it was using libedit before this current fiasco. That's my theory, anyhow. It's not two states we're dealing with, it's three: 1. MariaDB uses libreadline 2. MariaDB uses a working libedit that reads .editrc 3. MariaDB uses a broken libedit that doesn't read .editrc We're in state 3 right now, not state 2. That explains why the "fix" of using the included-with-MaraiDB libedit solves the symptoms: because that's a non-broken libedit that reads editrc. But it's always better (IMHO) to use the system libraries, so it seems prudent to get libedit fixed upstream. For instance, if libedit fixes a CVE, does MariaDB remember to patch or update their in-tree version?? Upstream Jess Thrysoee has already gotten back to me with a better patch and we're testing now. So it seems like this won't be an issue soon enough, once distros take on the upstream changes.
