On 2/22/21 3:30 PM, Antony Stone wrote:
> On Monday 22 February 2021 at 22:26:17, Hector Gonzalez Jaime via Dng wrote:
>
>> I've seen your original problem frequently, mysql and mariadb both are
>> turned off during upgrades, and then apt-get goes on to install other
>> packages, which might require a database to be running and have no
>> control over this. A workaround is, whenever you have mysql (or
>> mariadb) present, update it first and alone, like this:
>>

>> apt-get update
>> apt-get install default-mysql-server      # this command depends on your
>> version, just reinstall mysql's server first.
>> apt-get upgrade
>> apt-get dist-upgrade

>>
>> This way mysql gets updated first, and will be running for the rest of
>> your system.
> I like that - it sounds like an excellent tip (hard to see how it might be
> included in an automated update process, but that would of course be even
> better).
>
> Have you ever mentioned this to the Debian project, to see whether they
> consider this either to be a bug in the upgrade process, or at least a
> workaround worth documenting for people doing the upgrade?
I had only seen this with external packages, so, no, I've never
mentioned it.  I think if packages depend on a database of any kind to
be updated, they should wait for it to be done before they run their
scripts, but then again, the database might not even be configured to
run in the same system.
>
> Antony.
>
--
Hector Gonzalez
cacho@???