Bug#996028: InnoDB: corrupted TRX_NO after upgrading to 10.3.31
> With 10.3.29 running, I've dumped all databases (mysqldump --all-databases -p > >mysql.dump), > then dropped all databases, stopped mariadb and deleted /var/lib/mysql/ib*. > Then restarted mariadb, restored databases (source mysql.dump) and finally > upgraded to 10.3.31. > > So my problem is solved. I've also found the patch that's causing the problem. > I'm not going to waste any more time on this. > > During many years of running mysql, upgrade just worked all the time. > Looks like there are some quality problems with the developement process now. First of all, I fully understand that maintaining is a voluntary work and that you are free to do as you please =) In the following, I am not meaning *you* (or anyone else) "must" do anything they don't want to. Merely raising some questions. Am I to understand that the expected path forward with what is supposed to be a minor update offered on oldstable is that everyone shall dump their databases, delete the data folder, restore, then upgrade??? Sure I can do that, not happy to, but I can. However, that's an awful upgrade path and user experience for what would have normally been a mere and uneventful "apt-get upgrade". I do hope not everyone still on buster will have to do that after learning about it from a bug report. Seems to me it would be better to not have pushed this update to oldstable in the first place. (I'm not familiar with process, but could it be possibly undone, such that users stay on 10.3.29 and are not proposed the broken upgrade?). Any chance for a mitigating change coming from Debian's side? (not thinking about my specific case, but rather the general case of the thousands or more of people using mariadb on buster currently) Marc
Bug#996028: InnoDB: corrupted TRX_NO after upgrading to 10.3.31
Package: mariadb-server Followup-For: Bug #996028 Hi, I've been brought to this bug by apt-listbugs while doing upgrades on my buster install, warning me of a grave bug. I have not attempted the upgrade yet, since, after reading this bug, I see a risk of data corruption and I would like to avoid going into recovery procedures (from backups) as a result of what should be a stable upgrade. It seems there was an attempt at fixing the problem for buster, but this hasn't been pushed as a new version yet, right? Am I correct to assume this issue is still relevant for buster and that for now, I should simply defer the upgrade (marking the packages to be held back) and simply wait for this bug to be resolved? Thanks -- System Information: Debian Release: 10.11 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-18-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages mariadb-server depends on: hi mariadb-server-10.3 1:10.3.29-0+deb10u1 mariadb-server recommends no packages. mariadb-server suggests no packages. -- no debconf information
Bug#715141: apt_all update cronjob creates error mails when testing and unstable are not in the apt sources
Package: munin-plugins-core
Version: 2.0.25-1+deb8u2
Followup-For: Bug #715141
Hi,
This issue just appeared on my Jessie stable in one of the recent update
of the package through unattended-upgrades.
For now I've worked around by manually editing the apt_all script to
change
> my @releases = ("stable", "testing","unstable");
to
> my @releases = ("stable")
and using dpkg-divert to avoid subsequent updates to nuke the change...
That's not really a good solution.
What fix can be expected for jessie concerning this issue?
Regards
Marc
-- System Information:
Debian Release: 8.7
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
Versions of packages munin-plugins-core depends on:
ii munin-common 2.0.25-1+deb8u2
ii perl 5.20.2-3+deb8u6
Versions of packages munin-plugins-core recommends:
ii libnet-snmp-perl 6.0.1-2
Versions of packages munin-plugins-core suggests:
ii conntrack 1:1.4.2-2+deb8u1
ii libcache-cache-perl 1.07-2
ii libdbd-mysql-perl 4.028-2+deb8u2
ii libnet-dns-perl 0.81-2+deb8u1
pn libnet-netmask-perl
pn libnet-telnet-perl
ii libxml-parser-perl 2.41-3
ii python 2.7.9-1
ii ruby1:2.1.5+deb8u2
ii ruby2.1 [ruby-interpreter] 2.1.5-2+deb8u3
-- no debconf information
Bug#826939: certbot requires python-psutil >= 2.2.1
Package: certbot Followup-For: Bug #826939 For information, the package python-psutil has been updated today in jessie-backports to version 4.1.0-1~bpo8+1, which should solve this issue.
Bug#823279: debtree: Warning "Useless use of \E at /usr/bin/debtree line 612."
Package: debtree
Version: 1.0.10
Severity: normal
Dear Maintainer,
While using debtree on Jessie, the following warning is outputted twice
at the beginning of the output:
Useless use of \E at /usr/bin/debtree line 612.
Example:
$ debtree reportbug
Useless use of \E at /usr/bin/debtree line 612.
Useless use of \E at /usr/bin/debtree line 612.
Reading package lists... Done
Building dependency tree
Reading state information... Done
digraph "reportbug" {
rankdir=LR;
node [shape=box];
"reportbug" -> "python" [color=blue];
[...]
---
-- System Information:
Debian Release: 8.4
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
Versions of packages debtree depends on:
ii dctrl-tools 2.23
ii libapt-pkg-perl 0.1.29+b2
ii perl 5.20.2-3+deb8u4
ii ucf 3.0030
Versions of packages debtree recommends:
ii graphviz 2.38.0-7
debtree suggests no packages.
-- no debconf information
