Your message dated Wed, 5 Dec 2018 18:43:56 +1100
with message-id <[email protected]>
and subject line Bug#914172: "not a bug"
has caused the Debian Bug report #914172,
regarding mariadb-server-10.1: mariadb-server sec-update (10.1.37-0+deb9u1) 
uninstalls default-mysql-server, mysql-server, mariadb-server-10.1 & 
mariadb-client-10.1
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.)


-- 
914172: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914172
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mariadb-server-10.1
Version: unsure exactly - prior to today's security update
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Please excuse me setting the severity as grave. Under the circumstance it seems 
appropriate, but I'm
not 100% sure.

FYI TurnKey Linux is a Debian derivative which builds "software appliances" 
using mostly Debian packages,
many with upstream software pre-installed on top.

It has Debian (and TurnKey) security updates automatically installed daily via 
cron-apt.

As of the (automated) installation of today's MariaDB server security update 
(10.1.37-0+deb9u1)
all of our user's LAMP based appliances uninstalled mariadb-server (i.e. 
default-mysql-server,
mysql-server, mariadb-server-10.1 & mariadb-client-10.1) and thus most of web 
based software
stopped functioning.

The expected outcome was that the packages were simply updated to the latest 
security update and continued
functioning.

We're still not sure exactly what caused this, but would like to note the 
issue. Assitance in ensuring
that this sort of issue doesn't reoccur would also be welcomed.

It only appears to be an issue if security only updates are installed. A full 
upgrade does not cause the
same issue.

The resolution is to simply reinstall default-mysql-server (which depends on 
mariadb-server-10.1 &
mariadb-client-10.1 - mysql-server is an un-needed transitional package).

Please note that this report was created on a freshly launched WordPress 
appliance (based on LAMP)
with security updates installed on firstboot (and without the above menitoned 
fix applied).

Please ask if you need any further info.

Regards,
Jeremy

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

Kernel: Linux 4.9.0-8-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL 
set to C), LANGUAGE=en_US.UTF-8 (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set 
to C)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages mariadb-server-10.1 depends on:
ii  adduser                   3.115
ii  debconf [debconf-2.0]     1.5.61
ii  galera-3                  25.3.19-2
ii  gawk                      1:4.1.4+dfsg-1
ii  init-system-helpers       1.48
ii  iproute2                  4.9.0-1+deb9u1
ii  libaio1                   0.3.110-3
ii  libc6                     2.24-11+deb9u3
ii  libdbi-perl               1.636-1+b1
ii  libpam0g                  1.1.8-3.6
ii  libstdc++6                6.3.0-18+deb9u1
ii  libsystemd0               232-25+deb9u4
ii  lsb-base                  9.20161125
ii  lsof                      4.89+dfsg-0.1
pn  mariadb-client-10.1       <none>
ii  mariadb-common            10.1.37-0+deb9u1
ii  mariadb-server-core-10.1  10.1.37-0+deb9u1
ii  passwd                    1:4.4-4.1
ii  perl                      5.24.1-3+deb9u4
ii  psmisc                    22.21-2.1+b2
ii  rsync                     3.1.2-1+deb9u1
ii  socat                     1.7.3.1-2+deb9u1
ii  zlib1g                    1:1.2.8.dfsg-5

Versions of packages mariadb-server-10.1 recommends:
pn  libhtml-template-perl  <none>

Versions of packages mariadb-server-10.1 suggests:
ii  bsd-mailx [mailx]  8.1.2-0.20160123cvs-4
pn  mariadb-test       <none>
pn  netcat-openbsd     <none>
pn  tinyca             <none>

--- End Message ---
--- Begin Message ---
I'm closing this bug now as Salvatore's input clarifies that the bug is
NOT in the MariDB security update, it's in our config!

When I get a chance, I'll open a bug against unattended-updates due to
the fact that it didn't/won't install this particular security update
with the default "security updates only" config. IMO that IS a bug... :)

Thank you to everyone who contributed.

Regards,
Jeremy

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---

Reply via email to