Red Hat Bugzilla – Bug 1180403
Readline backward search broken in mysql client
Last modified: 2017-06-09 05:19:17 EDT
Description of problem:
Fedora release 21 (Twenty One) :
mysql Ver 15.1 Distrib 10.0.15-MariaDB, for Linux (x86_64) using EditLine wrapper
Steps to Reproduce:
1. run mysql client
2. type any command
3. try to search with Ctr-r keys
search word requested
As the version info says: mariadb client is now using EditLine (since #1079637), which has slightly different default bindings. Just put this in your ~/.editrc (yes, /etc/editrc is not considered):
bind ^R em-inc-search-prev
I also have this:
bind "^W" ed-delete-prev-word
bind "^U" vi-kill-line-prev
So it's not a bug, just unexpected and surprising behaviour.
(In reply to Jakob Hirsch from comment #1)
> As the version info says: mariadb client is now using EditLine (since
> #1079637), which has slightly different default bindings. Just put this in
> your ~/.editrc (yes, /etc/editrc is not considered):
Also cleaned all my .mysql_history , shouldn't do a backup of previous .mysql_history ?
I will check bug #1079637
Thanks for reporting, I think it may be fixed directly in mariadb or in libedit, we just need to find the best way. Just reported: https://mariadb.atlassian.net/browse/MDEV-7777
Honza Horak you on bug #1079637 drop readline because :
"First thing ... would be compiling against the recent version of readline. However, since version 6.x it is GPLv3+, so we cannot use it because mariadb is GPLv2 only."
and I wrote:
I think this is a mistake, "GPLv2 only" is "linkable" with GPLv3+ but result will be GPLv2 and GPLv3+ , not "GPLv2 only" and that is not a problem for us .
Mariadb is GPLv2 only and use a copy of readline under GPLv2, that is fine. We can use mariadb with readline GPLv3+ but the final License will be GPLv2 and GPLv3+ .
Can I block bug #1079637 with FE-Legal tracker (bug #182235) and reopen this bug ? to FE-Legal clarify who is right .
Hi, Honza Horak
I'm pretty sure that you can use readline with mysql just need change License to
GPLv2 and GPLv3+ . or GPLv2 with exception of readline that use GPLv3+
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
(In reply to Sergio Monteiro Basto from comment #5)
I just found this :
3 - A package has multiple binaries, some of them are GPLv2, some are GPLv3, and some are MIT licensed. In this case, you do need to list all of the individual licenses of the compiled binaries in the License tag, so it should read: License: GPLv2 and GPLv3 and MIT
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 21 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.