[debian-mysql] Bug#787864: mysql-server-5.5: fails to start in piuparts test environment

[Andreas Beckmann]

Control: severity -1 important

Hi Robie,

On 2015-07-02 16:53, Robie Basak wrote:
> On Fri, Jun 05, 2015 at 09:54:04PM +0200, Andreas Beckmann wrote:
>> during a test with piuparts I noticed your package now fails to start
>> the server in a piuparts test environment, i.e. a a minimal sid or
>> stretch chroot (while jessie works fine). This is most likely a
>> regression introduced by another package since the versions in jessie
>> and sid are the same ...
> 
> I've pinned this down to a change in the behaviour of logger(1) as used
> by the postinst and filed bug 790875 against bsdutils.

Thanks for digging into this. I've now applied a crude hack in my
piuparts instance and use the logger binary from jessie for stretch and
sid. That works for stretch, but not for sid, so there seems to be
something different in 5.6 ... oh wait, there is a pending commit about
exit 0 in the initscript ... I'll wait for that to be uploaded before
digging further ...

> We can always stop using logger or wrap calls to it somehow as a
> workaround.
> 
> This bug does not affect anyone running a syslog daemon or systemd, so I
> think it only affects piuparts testing and the non-default case. On this
> basis would it be reasonable to drop the severity and stop blocking this
> package from entering stretch?

Yes, but not before I filed another RC bug regarding the my.cnf
migration that needs to handle the mess created by mariadb-common:
#792080 :-)


Andreas