Bug#848137: problem with the upgrade of tango-db

[Paul Gevers]

Hi Andreas,

On 05-01-17 13:49, Andreas Beckmann wrote:
> On 2017-01-04 21:55, Paul Gevers wrote:
>> Hi Frederic-Emmanuel, Andreas,
>>
>> @Andreas, am I correct in the assumption that jessie to stretch with
>> tango-db was fine until MariaDB became the default? Or was this
>> migration with tango-db just never tested before? Have you seen other
>> dbconfig-common dependent packages fail since MariaDB became default (or
>> maybe since dbconfig-common 2.0.5 (26-08-2016)?
> 
> I can't remember the details right now, but it is possible that this
> started to fail after the mariadb switch (which is a non-trivial thing
> to test with piuparts). I could try to find some older logs ...
> And I don't remember any other package having a similar issue.
> 
> I needed, I could do further checks (or log lookup) next week.

It would still be nice to confirm that this issue exists (in
experimental) since 30 Mar 2015 (or dbconfig-common release 1.8.50).

Paul

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/debian-science-maintainers/attachments/20170108/65a79e66/attachment.sig>