Bug in amavisd-new, or p5-DBD-mysql?

[Tom Sommer]

On 2018-09-17 19:00, David Newman wrote:
> On 9/17/18 2:58 AM, Tom Sommer wrote:
> 
>>> I'm frankly not qualified to answer: Is this an amavisd problem, or a
>>> p5-DBD-mysql problem? As it is, amavisd-new is getting bad data.
>> 
>> FYI: I just hit this issue when updating DBD::mysql to 4.048, 
>> reverting
>> to 4.037 solved it for me (no other version worked).
> 
> I filed bug 231250 against amavisd-new for this. Previously I'd
> contacted the package/port maintainer. I haven't heard back on either
> that contact or the bug report.
> 
> At this point I'm pretty sure this is a bug in amavisd-new, as the
> change in p5-DBD-mysql from 4.038 onward corrected a data-typing issue.
> Any newer version "now returns mysql doubles as perl doubles and mysql
> floats as perl floats (and not as a string anymore)" and that seems 
> like
> correct behavior to me.
> 
> Problem is, while amavisd-new can coexist with 4.037, there are other
> issues in that older version, never mind the additional need to exclude
> that pkg/port when updating a system.

Yes, I agree with that - but amavisd-new seems a bit stale at the 
moment, sadly :)

Do you have a link to this bug report?

--
Tom