On Saturday 25 February 2017 22:45:25 gregor herrmann wrote:
> On Sat, 25 Feb 2017 01:18:04 +0100, p...@cpan.org wrote:
> > But if you are fixing "regressions" from older versions, consider apply
> > also fix for zerofill.
>
> Since Debian is in deep freeze, I'm just trying to fix reported RC
> b
Hi,
On Sun, Feb 26, 2017 at 09:49:44PM +0100, gregor herrmann wrote:
> > So from my point of view, as it is two days until the 1st of March right
> > now (at least in my timezone) we need to get a fixed version of
> > libdbd-mysql-perl in unstable by tomorrow at the latest. Is this going
> > to be
On Mon, 27 Feb 2017 07:37:53 +1100, Brian May wrote:
> Brian May writes:
> > amavisd-new has already been removed from testing. I think the chances
> > of getting it back in are remote - however I have asked the release team
> > - see #856067.
>
> The release gods^h^h^h^h^h team has spoken. They
Brian May writes:
> amavisd-new has already been removed from testing. I think the chances
> of getting it back in are remote - however I have asked the release team
> - see #856067.
The release gods^h^h^h^h^h team has spoken. They say they will accept
amavisd-new back in the archive:
"Not in a
gregor herrmann writes:
> Brian, do you have a chance to test this version against amavisd-new?
I am not able to test this myself. If however you can make a version
available for testing (experimental maybe?) I can ask people to test it.
> Since Debian is in deep freeze, I'm just trying to fix
On Sat, 25 Feb 2017 01:18:04 +0100, p...@cpan.org wrote:
> > > Upstream patch:
> > > https://github.com/perl5-dbi/DBD-mysql/pull/102
> >
> > This patch doesn't apply against 4.041-1 in Debian (or 4.041
> > upstream), and neither against the master branch in the upstream repo
> > (so unless I'm mi
Hi!
On Saturday 25 February 2017 00:41:31 gregor herrmann wrote:
> On Sat, 25 Feb 2017 09:29:23 +1100, Brian May wrote:
> > Package: libdbd-mysql-perl
> > Version: 4.041-1
> > Severity: grave
> > Justification: causes non-serious data loss
> >
> > When reading floats from mysql, they are always r
On Sat, 25 Feb 2017 09:29:23 +1100, Brian May wrote:
> Package: libdbd-mysql-perl
> Version: 4.041-1
> Severity: grave
> Justification: causes non-serious data loss
>
> When reading floats from mysql, they are always read as 0.
Thanks for the bug report and all the information!
> Upstream patc
Brian May writes:
> Possibly only happens in Perl's tainted mode; I have asked for
> confirmation.
Actually is a fair bit more complicated then that. See:
https://github.com/perl5-dbi/DBD-mysql/issues/78#issuecomment-282425847
The fix is simple. Understanding what the bug breaks is a lot more
c
Package: libdbd-mysql-perl
Version: 4.041-1
Severity: grave
Justification: causes non-serious data loss
When reading floats from mysql, they are always read as 0.
As values are currupted and as it is the cause of a grave bug in another
package, I have set this to grave.
Possibly only happens in
10 matches
Mail list logo
