Bug#613493: Bug in libdbd-pg-perl fixed in revision 72505

2011-04-12 Thread Ansgar Burchardt
Dmitry E. Oboukhov un...@debian.org writes: The bug had severity grave. So It would be nice If You uploaded the package into Debian/stable, too. It's a pity that the bug is done by new upstream version (release team can disagree to upload) but I think You should try :) AB No. The bug

Bug#613493: Bug in libdbd-pg-perl fixed in revision 72505

2011-04-12 Thread Dmitry E. Oboukhov
The bug had severity grave. So It would be nice If You uploaded the package into Debian/stable, too. It's a pity that the bug is done by new upstream version (release team can disagree to upload) but I think You should try :) AB No. The bug severity was inflated: the memory leak does not

Bug#613493: Bug in libdbd-pg-perl fixed in revision 72505

2011-04-11 Thread pkg-perl-maintainers
tag 613493 + pending thanks Some bugs are closed in revision 72505 by Ansgar Burchardt (ansgar) Commit message: * New upstream release. + Fix memory leak when binding arrays. (Closes: #613493) * Bump Standards-Version to 3.9.2 (no changes). -- To UNSUBSCRIBE, email to

Bug#613493: Bug in libdbd-pg-perl fixed in revision 72505

2011-04-11 Thread Dmitry E. Oboukhov
Hi, Ansgar! The bug had severity grave. So It would be nice If You uploaded the package into Debian/stable, too. It's a pity that the bug is done by new upstream version (release team can disagree to upload) but I think You should try :) 2.17.2 had also a few (at least two) additional memory

Bug#613493: Bug in libdbd-pg-perl fixed in revision 72505

2011-04-11 Thread Ansgar Burchardt
Dmitry E. Oboukhov un...@debian.org writes: The bug had severity grave. So It would be nice If You uploaded the package into Debian/stable, too. It's a pity that the bug is done by new upstream version (release team can disagree to upload) but I think You should try :) No. The bug severity

Bug#613493: Bug in libdbd-pg-perl fixed in revision 72505

2011-04-11 Thread Dmitry E. Oboukhov
The bug had severity grave. So It would be nice If You uploaded the package into Debian/stable, too. It's a pity that the bug is done by new upstream version (release team can disagree to upload) but I think You should try :) AB No. The bug severity was inflated: the memory leak does not