Your message dated Mon, 07 Feb 2022 21:45:15 +0000
with message-id <[email protected]>
and subject line Bug#1004944: Removed package(s) from unstable
has caused the Debian Bug report #992560,
regarding mariadb-client-core-10.5: erases mysql client command history
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
992560: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992560
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mariadb-client-core-10.5
Version: 1:10.5.11-1
Severity: important

Dear Maintainer,

After upgrading from Debian buster to bullseye, and running the mysql command 
line client for the first time, the command line history is wiped, leaving a 
.mysql_history devoid of entries.

This is rather inconvenient, particularly in multi-user environments, where 
multiple .mysql_history files must be recovered from backups.

The bug seems to be related to the regression from GNU readline to BSD EditLine 
as the linked command line/history manager library. This regression is not 
apparent in upstream, at least as they package mariadb-client-core-10.5 for 
buster (versions up to and including: 1:10.5.12+maria~buster).

As far as I can tell, there are two apparent fixes, one apparently technically 
(if not policy-wise) easy, the other rather labor intensive.

Easy fix: revert the regression from readline to EditLine, so that the client 
library uses readline, as upstream does.

More labor intensive fix:

1) Prompt the user upon first use of the command for how to handle the 
situation.

2) Provide conversion for the command line history from readline format to the 
current EditLine format, whatever that may be.

3) Automatically back up the command line history when the user chooses to 
start with a fresh history file.

-- System Information:
Debian Release: 11.0
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-8-amd64 (SMP w/2 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages mariadb-client-core-10.5 depends on:
ii  libc6           2.31-13
ii  libedit2        3.1-20191231-2+b1
ii  libmariadb3     1:10.5.11-1
ii  libncurses6     6.2+20201114-2
ii  libssl1.1       1.1.1k-1
ii  libstdc++6      10.2.1-6
ii  libtinfo6       6.2+20201114-2
ii  mariadb-common  1:10.5.11-1
ii  zlib1g          1:1.2.11.dfsg-2

mariadb-client-core-10.5 recommends no packages.

mariadb-client-core-10.5 suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
Version: 1:10.5.12-1+rm

Dear submitter,

as the package mariadb-10.5 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1004944

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[email protected].

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

--- End Message ---

Reply via email to