---
- branch: MAIN
  date: Sat Jun 12 16:00:44 UTC 2010
  files:
  - new: '1.7'
    old: '1.6'
    path: pkgsrc/databases/p5-DBM-Deep/Makefile
    pathrev: pkgsrc/databases/p5-DBM-Deep/Makefile@1.7
    type: modified
  - new: '1.6'
    old: '1.5'
    path: pkgsrc/databases/p5-DBM-Deep/distinfo
    pathrev: pkgsrc/databases/p5-DBM-Deep/distinfo@1.6
    type: modified
  - new: '1.2'
    old: '1.1'
    path: pkgsrc/databases/p5-DBM-Deep/patches/patch-aa
    pathrev: pkgsrc/databases/p5-DBM-Deep/patches/patch-aa@1.2
    type: modified
  id: 20100612T160044Z.c66964848e642babc94866e983f78bd958928e95
  log: |
    Update p5-DBM-Deep from version 1.0023 to version 1.0025.

    Upstream changes:
    1.0025 Jun 6 12:46:00 2010 PDT
        (This version is compatible with 1.0024)
        - Fixed t/39_singletons.t to work on Windows.

    1.0024 May 30 14:25:00 2010 PDT
        (This version is compatible with 1.0023)
        - Stale references (objects blessed into DBM::Deep::Null), which
          have always supposed to act like undef, now compare equal to
          undef, "" and 0. $stale_ref eq "" used to return false, even
          though "$stale_ref" was the empty string.
        - If you assign a stale reference to a database location,
          DBM::Deep now warns and assigns undef, instead of dying with
          obscure error messages.
        - Using a stale reference as a hash or array ref now causes an
          error with a more helpful message.
  module: pkgsrc
  subject: 'CVS commit: pkgsrc/databases/p5-DBM-Deep'
  unixtime: '1276358444'
  user: seb