[debian-mysql] Bug#996028: marked as done (InnoDB: corrupted TRX_NO after upgrading to 10.3.31)

[Debian Bug Tracking System]

Your message dated Sun, 20 Nov 2022 16:58:50 -0800
with message-id <CAOU6tAAMKcFXPVG-VcnTZ0CwLMgKVQ4J0Nt1VjhKN53Ww=d9Eg at mail.gmail.com>
and subject line Re: [debian-mysql] Bug#996028: Bug#996028: Bug#996028: InnoDB: corrupted TRX_NO after upgrading to 10.3.31
has caused the Debian Bug report #996028,
regarding InnoDB: corrupted TRX_NO after upgrading to 10.3.31
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 at bugs.debian.org
immediately.)


-- 
996028: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996028
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Ondrej Zary <zary at gsystem.sk>
Subject: InnoDB: corrupted TRX_NO after upgrading to 10.3.31
Date: Sun, 10 Oct 2021 16:13:29 +0200
Size: 2835
URL: <http://alioth-lists.debian.net/pipermail/pkg-mysql-maint/attachments/20221121/e7f0bc3e/attachment.eml>
-------------- next part --------------
An embedded message was scrubbed...
From: =?UTF-8?B?T3R0byBLZWvDpGzDpGluZW4=?= <otto at debian.org>
Subject: Re: [debian-mysql] Bug#996028: Bug#996028: Bug#996028: InnoDB: corrupted TRX_NO after upgrading to 10.3.31
Date: Sun, 20 Nov 2022 16:58:50 -0800
Size: 4746
URL: <http://alioth-lists.debian.net/pipermail/pkg-mysql-maint/attachments/20221121/e7f0bc3e/attachment-0001.eml>