Re: dpkg: error processing package mysql-client

2023-07-20 Thread Andy Smith
Hello,

On Thu, Jul 20, 2023 at 08:17:34PM -0400, Greg Wooledge wrote:
> On Thu, Jul 20, 2023 at 05:55:12PM -0600, William Torrez Corea wrote:
> > Setting up mysql-common (8.0.34-1debian11) ...
> 
> This package did not come from Debian.

[…]

> If your third-party MySQL packages are not working, you might seek help
> from whoever built them.

I would add that the fact that OP is having problems on an upgrade
with third party packages probably means that OP did not read the
release notes regarding identifying third party repositories, so OP
should also definitely go and read those before any upgrade.

https://www.debian.org/releases/stable/releasenotes
https://www.debian.org/releases/bullseye/releasenotes

(not sure which release OP is upgrading to; 11 (bullseye)
maybe.)

Cheers,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting



Re: dpkg: error processing package mysql-client

2023-07-20 Thread Greg Wooledge
On Thu, Jul 20, 2023 at 05:55:12PM -0600, William Torrez Corea wrote:
> Setting up mysql-common (8.0.34-1debian11) ...

This package did not come from Debian.  That's not a Debian version
string (*none* of them have that pattern, with the literal word "debian"
in between numbers), and besides, looking at
 you can clearly see that no
version of Debian has a mysql-common package with a version number
that high.

If your third-party MySQL packages are not working, you might seek help
from whoever built them.  Failing that, you should *definitely* back
up your database(s) if possible, and then give serious thought to
purging these packages by whatever means, and then reinstalling them.
Or installing Debian's Mariadb packages instead.

Once you get a working database back on the system, then you can restore
your backed-up data.