[debian-mysql] Bug#853008: Bug#853008: mysql-server-5.7: purge could delete mariadb-server files with inadequate warning

[Lars Tangvald]

On 01/29/2017 01:13 PM, Julian Gilbey wrote:
> On Sat, Jan 28, 2017 at 09:21:13PM +0000, Julian Gilbey wrote:
>> Package: mysql-server-5.7
>> Version: 5.7.16-2
>> Severity: serious
>>
>> Hello!
>>
>> I'm really confused by the change in the postrm introduced in response
>> to LP: #1602945, and I simply do not understand the rationale of the
>> original bug report, and the comment there (and in the git commit log)
>> that "Remove the check on the server binary, since it shouldn't be
>> possible for another package to own that file anyway" is clearly
>> incorrect: during a postrm remove|purge run, if that file exists -
>> which it may well do, it will certainly belong to a different package,
>> such as mysql-server-5.8 or mariadb-server-10.1.
> And looking at the existing postrms, I see that this is effectively
> just Debian bug #307473 reopened.  That was regarded as critical!
>
The problem with the old code was that at the point it was run, 
usr/sbin/mysqld  _always_ existed, so it was just a big chunk of dead 
code. The code was just copied from the old packages that had a 
different structure. I think the code would need to be in the maintainer 
script for the package that has the server binary, so that it would run 
correctly after the package's own binary is removed, but that's 
-server-core, which doesn't run any postrm (we could add it, but part of 
the point of the core packages is that they don't run anything).

Anyone else have any good ideas on how to handle this?

--
Lars
> Best wishes,
>
>     Julian
>
> _______________________________________________
> pkg-mysql-maint mailing list
> pkg-mysql-maint at lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-mysql-maint