On Sun, 12 Feb 2017, Brian May wrote: > Henrique de Moraes Holschuh <h...@debian.org> writes: > > > I don't know. I never use mysql (or any DB, really) with amavisd-new, > > and I have no idea why it would fetch 0 instead of the proper float > > value from mysql, or how to fix it :-( > > Same here. Not even convinced this should be RC, considering it only > affects users who use mysql. Adrian Bunk changed it but didn't justify > why - he may have incorrectly assumed the bug affects everyone. It may > not even be a bug in amavisd-new - there could be a problem with the > database on the system. > > I guess the strategy for dealing with this would be: > > 1. Try to reproduce the problem with upstream git. > 2. Try to do a git bisect. > > I am stuck on step 1. > > Unfortunately the original bug report is lacking in details required to > reproduce this. e.g. the tables (structure and data) that in mysql. The bug was caused by a change in dbd-mysql. Git bisecting amavisd won't help.
See also: https://github.com/perl5-dbi/DBD-mysql/issues/78 Alex
