In Buster and Stretch, and probably earlier, there is a meta-package 
“default-mysql-client” that installs the preferred version of the client, 
mariadb-client.  In Stretch the mysql-client package still existed but it was 
just dependent on default-mysql-client so still got the mariadb version.  I 
don’t have an older system handy to poke around on but I imagine this 
arrangement existed for several previous versions.  Apparently by Buster, 
debian expects people to have cleaned up explicit dependencies on the mysql 
packages.

What about the server side?  It looks like the same thing applies to the 
mysql-server packge.

  -Les



> On 3 Mar 2020, at 12:36, John Kline <[email protected]> wrote:
> 
> FWIW, WRT mysql-client, I’m not seeing any difference in buster between 
> Raspbian and standard Debian.  mysql-client does not exist in both cases.
> 
> It appears to me that Debian has moved on to mariadb as the drop in 
> replacement.
> 
> As for: “ but is referred to by another package.”; perhaps an “apt 
> dist-upgrade” will fix it.
> 
>> On Mar 3, 2020, at 11:53 AM, Vince Skahan <[email protected]> wrote:
>> 
>> 
>> On Tuesday, March 3, 2020 at 9:14:29 AM UTC-8, Lucas Heijst wrote:
>> I did a fresh install of raspbian buster on a rpi 3b+
>> 
>> Package mysql-client is not available, but is referred to by another package.
>> 
>> This may mean that the package is missing, has been obsoleted, or
>> 
>> is only available from another source
>> 
>> However the following packages replace it:
>> 
>> mariadb-client-10.0
>> 
>> 
>> 
>> E: Package 'mysql-client' has no installation candidate
>> 
>> 
>> 
>> I installed module mariadb-client-10.0 instead without any further errors.
>> 
>> 
>> 
>> 
>> 
>> 
>> This sounds like the renaming of mysql that happened a while back.   If they 
>> did the mariadb packages correctly they would be set up to 'provide' 
>> mariadb-whatever as a capability of their package (I'm speaking from a 
>> RedHat background and how RPM does it, I don't know if debian packages can 
>> do that or not)
>> 
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-development" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected] 
>> <mailto:[email protected]>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-development/95142a8e-430e-4c88-bc4b-010972640dc6%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-development/95142a8e-430e-4c88-bc4b-010972640dc6%40googlegroups.com?utm_medium=email&utm_source=footer>.
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "weewx-development" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected] 
> <mailto:[email protected]>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-development/A065D115-61F2-4DCC-9D83-0AF1A44E483C%40johnkline.com
>  
> <https://groups.google.com/d/msgid/weewx-development/A065D115-61F2-4DCC-9D83-0AF1A44E483C%40johnkline.com?utm_medium=email&utm_source=footer>.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/E65C7D54-E8F6-4074-B169-A39FD410A644%402pi.org.

Reply via email to