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

Bug#1031124: marked as done (unblock: mariadb/1:10.11.2-1)

Your message dated Mon, 27 Feb 2023 22:06:36 +0100
with message-id <a0fb7572-08e5-86fc-7687-b808726e4724@debian.org>
and subject line Re: Bug#1031124: unblock: mariadb/1:10.11.1-4
has caused the Debian Bug report #1031124,
regarding unblock: mariadb/1:10.11.2-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 owner@bugs.debian.org
immediately.)


-- 
1031124: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031124
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: unblock
Control: affects -1 + src:mariadb

Please unblock package mariadb (=10.11), so it can be included in
Debian Bookworm instead of previous mariadb-10.6 (=10.6).


[ Reason ]

MariaDB 10.11 is the latest stable and long-term supported (until
2028) version of a popular database software. Having it included in
Debian Bookworm would serve users best, both immediately and in the
long run when Bookworm becomes a LTS version.

The package src:mariadb has been in Debian unstable already for a
month but it didn't migrate to testing due to minor test suite
failures on various architectures, and due to autopkgtest interactions
with itself (mariadb-10.6) that were pure test issues and not real
regressions for users.

Current main reason for the block is regression in MariaDB running on
the new Linux kernel on s390x, which affects both MariaDB 10.11 and
10.6. The intent of unstable to testing migration rules treated the
package unfavorably in Jan/Feb - there is no indication that the
quality of 10.6 would be any better than 10.11.


[ Impact ]

Users would be stuck with MariaDB 10.6 and likely resort to using
other, less reliable ways to install and update it. The newer MariaDB
10.11 has more features and more bugs fixed, and it also works on more
architectures and has security updates for a longer time.


[ Quality assurance ]

During the past month in unstable, there were zero user bug reports
about MariaDB 10.11 quality issues - all new bugs were translations,
filed by maintainer or Debian QA related and already addressed. The
package has very extensive pre-upload CI testing in place
(https://salsa.debian.org/mariadb-team/mariadb-server/-/pipelines/497876)
and the package has a good track record of being well maintained (by
the same maintainer for past 10 years).


[ Risks ]

New bugs might surface when the package gets more use. However, both
the Debian maintainer and also upstream project are very responsive in
fixing issues affecting Debian.


[ Deep dive into current migration excuses ]

* Bug#1030604 (autopkgtest s390x failures) are most likely a kernel
regression reported in Bug#1020831. It visibly now affects MariaDB
10.11 (https://ci.debian.net/packages/m/mariadb/testing/s390x/) but
manually rerunning old MariaDB 10.6 tests
(https://ci.debian.net/packages/m/mariadb-10.6/testing/s390x/) shows
they also fail - thus this issue is not introduced by the new package,
and blocking it on this is "unfair".

* Bug#1031116 (autopkgtest cacti failures) is due to apt misordering
of dbconfig-common vs mariadb installation, and can easily be fixed in
next upload but have not done it now as it would reset the
unstable->testing migration timer.

--- End Message ---
--- Begin Message --- 
Hi,

On 12-02-2023 08:14, Otto Kekäläinen wrote:

Please unblock package mariadb (=10.11), so it can be included in
Debian Bookworm instead of previous mariadb-10.6 (=10.6).


MariaDB is in testing now.

Paul

Attachment: OpenPGP_signature
Description: OpenPGP digital signature


--- End Message ---
Reply to: