[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#858996: marked as done (jessie-pu: package mariadb-10.0/10.0.30-0+deb8u2)

Your message dated Sat, 06 May 2017 14:44:18 +0100
with message-id <1494078258.26551.13.camel@adam-barratt.org.uk>
and subject line Closing bugs for updates included in 8.8
has caused the Debian Bug report #858996,
regarding jessie-pu: package mariadb-10.0/10.0.30-0+deb8u2
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 owner@bugs.debian.org
immediately.)


-- 
858996: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858996
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
Tags: jessie
User: release.debian.org@packages.debian.org
Usertags: pu

Dear release team,

in order to fix #858941 for mariadb-10.0 (and #852495 for mariadb-10.1)
I did couple of changes to both mariadb-10.0 and mariadb-10.1 (I will
fill unblock later).

1. there seemed to be excessive stopping of mysqld server (old-prerm,
   new-preinst, new-postinst), I have removed these and I have just
   added a safe-guard in the old-prerm to stop if mysqld is still
   running to mimick the old behaviour, as there probably have been
   problems with stopping mysqld in the past.

2. the #DEBHELPER# in the postrm got moved inside the block that has
   a safe-guard that checks whether the purged version is the currently
   installed version by checking for /var/lib/mysql/debian-<var>.flag
   that's created in all variants postinst scripts.

This is the bare minimum that needs to be done to not criple
mariadb-server-10.1 init scripts when mariadb-server-10.0 is purged.

I have tested all possible combinations of install/remove/purge
on jessie, jessie2stretch and stretch systems and it seems to
work as expected.

Cheers,
Ondrej

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.4.0-67-generic (SMP w/24 CPU cores)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

--- End Message ---
--- Begin Message --- 
Version: 8.8

Hi,

Each of these bugs refers to an update that was included in today's
jessie point release. Thanks!

Regards,

Adam

--- End Message ---
Reply to: