Hi Russel,
thanks for your report and your help making Ubuntu better.
Without more information, I can not try to reproduce this.
At least I need to understand the context:
- which version of ubuntu are you upgrading?
- which version of mariadb are you upgrading?
Regards.
** Changed in: mariadb-
Hi Carsten!
Thanks for your report!
mariadb-common can not be responsible of cleaning/uninstalling previous
mysql installations.
MySQL and MariaDB are different projects.
Regards,
Faustin
** Changed in: mariadb-10.3 (Ubuntu)
Status: New => Invalid
--
You received this bug notificat
upstream: https://github.com/MariaDB/server/commit/4ad148b148cf
downstream:
https://salsa.debian.org/mariadb-team/mariadb-10.3/-/commit/b57b9f5ba2
** Changed in: mariadb-10.3 (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubu
Hi Markus!
The problem is not which image to use (you can use one of mine, see
https://github.com/fauust/docker-systemd/ and #6). Or as explained in #5
by Julian, you can also try to build gardenlinux.
But if your are able to reproduce the bug on your setup that's good, can
you please describe yo
Hi Julian!
Strange, the GH CI was failing for me without this argument, see
https://github.com/fauust/docker-
systemd/blob/main/.github/workflows/build.yml#L129-L140 and
https://github.com/fauust/docker-
systemd/actions/runs/8139697623/job/22386833452.
--
You received this bug notification becau
Hi Markus!
Indeed not all images are impacted, here is a non exhaustive list (alpine is
particular since it use OpenRC):
https://github.com/fauust/docker-systemd/actions/runs/8139697623
My problem was that I was not able to reproduce it, see #6.
Anyway, I am a bit lost here but apparently some o
Ok, in #6 I tested with debian 11 which is not impacted, re-testing...
Ok all good, I can reproduce it too:
buildbot@bb-monty-bbw1-x64-ubuntu-2204-amd64:~$ uname -r
6.5.0-1015-azure
buildbot@bb-monty-bbw1-x64-ubuntu-2204-amd64:~$ podman run --rm -d
ghcr.io/fauust/docker-systemd:debian-12
Error:
1 09:10:37.835665302 +
Birth: 2024-03-11 09:10:35.335710674 +
Regards,
Faustin
** Changed in: mariadb-10.6 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
Hi uqbar!
SHOW USERS; is not a valid SQL command (you probably want "select user
from mysql.user;").
Anyway, I am wondering if this issue is not related to
https://bugs.launchpad.net/ubuntu/+source/mariadb-10.6/+bug/2055319?
Please explain the steps to reproduce this.
Regards
** Changed in:
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?
This will help us to find and resolve the problem.
** Changed in: mariadb-10.6 (Ubuntu)
I am not sure that this is something easy to find (at least I don't know
how to proceed). And above all, my understanding is that the problem
seems to be related to the "old" crun version and quite new kernels
(6.5).
Also, 22.04 (and Bullseye) comes with crun 0.17 and there is a huge gab
with the
Hi Clémentine!
Thanks for your report and and for your help making Ubuntu better.
You seem to have a previous installation of MySQL installed and MariaDB
and MySQL should not been installed together since they may use the same
PATH (from DpkgTerminalLog.txt). So, before installing MariaDB, please
Hi!
Same here:
# uname -a
Linux oph8 6.8.0-31-generic #31-Ubuntu SMP Sat Apr 20 00:05:55 UTC 2024 ppc64le
ppc64le ppc64le GNU/Linux
# modprobe -v wireguard
insmod
/lib/modules/6.8.0-31-generic/kernel/arch/powerpc/crypto/chacha-p10-crypto.ko.zst
modprobe: ERROR: could not insert 'wireguard': No
201 - 213 of 213 matches
Mail list logo
