[pkgsrc/trunk]: pkgsrc/databases/p5-DBD-ODBC pkgsrc changes:

[sno <sno%pkgsrc.org@localhost>]

details:   https://anonhg.NetBSD.org/pkgsrc/rev/f16535c8fa6f
branches:  trunk
changeset: 560575:f16535c8fa6f
user:      sno <sno%pkgsrc.org@localhost>
date:      Sun Jun 14 21:23:57 2009 +0000

description:
pkgsrc changes:
  - Updating package of p5 module DBD::ODBC from 1.21 to 1.22
  - Adjusting LICENSE to ${PERL5_LICENSE} according to META.yaml

Upstream changes:
* Changes in DBD::ODBC 1.22 June 10, 2009

    Fixed bug which led to "Use of uninitialized value in subroutine
    entry" warnings when writing a NULL into a NVARCHAR with a
    unicode-enabled DBD::ODBC. Thanks to Jirka Novak and Pavel Richter who
    found, reported and patched a fix.

    Fixed serious bug in unicode_helper.c for utf16_len which I'm ashamed to
    say was using an unsigned short to return the length. This meant you
    could never have UTF16 strings of more than ~64K without risking serious
    problems. The DBD::ODBC test code actually got a

    *** glibc detected *** /usr/bin/perl: double free or corruption
    (out): 0x406dd008 ***

    If you use a UNICODE enabled DBD::ODBC (the default on Windows) and
    unicode strings larger than 64K you should definitely upgrade now.

* Changes in DBD::ODBC 1.21_1 June 2, 2009

    Fixed bug referred to in rt 46597 reported by taioba and identified by
    Tim Bunce. In Calls to bind_param for a given statement handle if you
    specify a SQL type to bind as, this should be "sticky" for that
    parameter.  That means if you do:

    $sth->bind_param(1, $param, DBI::SQL_LONGVARCHAR)

    and follow it up with execute calls that also specify the parameter:

    $sth->execute("a param");

    then the parameter should stick with the SQL_LONGVARCHAR type and not
    revert to the default parameter type. The DBI docs (from 1.609)
    make it clear the parameter type is sticky for the duration of the
    statement but some DBDs allow the parameter to be rebound with a
    different type - DBD::ODBC is one of those drivers.

diffstat:

 databases/p5-DBD-ODBC/Makefile |  6 +++---
 databases/p5-DBD-ODBC/distinfo |  8 ++++----
 2 files changed, 7 insertions(+), 7 deletions(-)

diffs (36 lines):

diff -r fd051fa74344 -r f16535c8fa6f databases/p5-DBD-ODBC/Makefile
--- a/databases/p5-DBD-ODBC/Makefile    Sun Jun 14 21:21:54 2009 +0000
+++ b/databases/p5-DBD-ODBC/Makefile    Sun Jun 14 21:23:57 2009 +0000
@@ -1,7 +1,7 @@
-# $NetBSD: Makefile,v 1.1.1.1 2009/05/17 13:29:15 sno Exp $
+# $NetBSD: Makefile,v 1.2 2009/06/14 21:23:57 sno Exp $
 #
 
-DISTNAME=      DBD-ODBC-1.21
+DISTNAME=      DBD-ODBC-1.22
 PKGNAME=       p5-${DISTNAME}
 CATEGORIES=    databases perl5
 MASTER_SITES=  ${MASTER_SITE_PERL_CPAN:=DBD/}
@@ -9,7 +9,7 @@
 MAINTAINER=    pkgsrc-users%NetBSD.org@localhost
 HOMEPAGE=      http://search.cpan.org/dist/DBD-ODBC/
 COMMENT=       Perl DBI/DBD driver for ODBC
-LICENSE=       gnu-gpl-v2 # OR artistic
+LICENSE=       ${PERL5_LICENSE}
 
 .include "options.mk"
 
diff -r fd051fa74344 -r f16535c8fa6f databases/p5-DBD-ODBC/distinfo
--- a/databases/p5-DBD-ODBC/distinfo    Sun Jun 14 21:21:54 2009 +0000
+++ b/databases/p5-DBD-ODBC/distinfo    Sun Jun 14 21:23:57 2009 +0000
@@ -1,6 +1,6 @@
-$NetBSD: distinfo,v 1.1.1.1 2009/05/17 13:29:15 sno Exp $
+$NetBSD: distinfo,v 1.2 2009/06/14 21:23:57 sno Exp $
 
-SHA1 (DBD-ODBC-1.21.tar.gz) = 7984e031ce3614b523920deebac03b80aa473a71
-RMD160 (DBD-ODBC-1.21.tar.gz) = 738d1d57676658a75ceb4676567547dc5292f25e
-Size (DBD-ODBC-1.21.tar.gz) = 174208 bytes
+SHA1 (DBD-ODBC-1.22.tar.gz) = 31094dae98d2dbe04be6d4b21bebea6ce9b34e14
+RMD160 (DBD-ODBC-1.22.tar.gz) = b7c96f9cfd189c0fb17ed57d19c35bfcf54b03d7
+Size (DBD-ODBC-1.22.tar.gz) = 179081 bytes
 SHA1 (patch-aa) = e731a710838e86f05c4f3b223f768968ba1d9489