Script 'mail_helper' called by obssrc Hello community, here is the log from the commit of package perl-DBM-Deep for openSUSE:Factory checked in at 2023-09-29 21:13:57 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/perl-DBM-Deep (Old) and /work/SRC/openSUSE:Factory/.perl-DBM-Deep.new.28202 (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Package is "perl-DBM-Deep" Fri Sep 29 21:13:57 2023 rev:21 rq:1114062 version:2.0017 Changes: -------- --- /work/SRC/openSUSE:Factory/perl-DBM-Deep/perl-DBM-Deep.changes 2023-08-09 17:26:47.057952188 +0200 +++ /work/SRC/openSUSE:Factory/.perl-DBM-Deep.new.28202/perl-DBM-Deep.changes 2023-09-29 21:15:17.401463806 +0200 @@ -1,0 +2,16 @@ +Tue Sep 26 19:20:20 UTC 2023 - Tina Müller <tina.mueller@suse.com> + +- Remove package-separator-perl5.38.patch, fixed upstream + +------------------------------------------------------------------- +Tue Sep 5 16:45:07 UTC 2023 - Tina Müller <timueller+perl@suse.de> + +- updated to 2.0017 + see /usr/share/doc/packages/perl-DBM-Deep/Changes + + 2.0017 2023-09-01 + + - get rid of old perl4-style ' package separator and use :: instead + for compatibility with perl 5.38 + +------------------------------------------------------------------- Old: ---- DBM-Deep-2.0016.tar.gz package-separator-perl5.38.patch New: ---- DBM-Deep-2.0017.tar.gz ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ perl-DBM-Deep.spec ++++++ --- /var/tmp/diff_new_pack.MFbTRD/_old 2023-09-29 21:15:18.641508547 +0200 +++ /var/tmp/diff_new_pack.MFbTRD/_new 2023-09-29 21:15:18.641508547 +0200 @@ -18,15 +18,13 @@ %define cpan_name DBM-Deep Name: perl-DBM-Deep -Version: 2.0016 +Version: 2.0017 Release: 0 License: Artistic-1.0 OR GPL-1.0-or-later Summary: Pure perl multi-level hash/array DBM that supports transactions URL: https://metacpan.org/release/%{cpan_name} -Source0: https://cpan.metacpan.org/authors/id/S/SP/SPROUT/%{cpan_name}-%{version}.tar.gz +Source0: https://cpan.metacpan.org/authors/id/D/DC/DCANTRELL/%{cpan_name}-%{version}.tar.gz Source1: cpanspec.yml -# PATCH-FIX-UPSTREAM deprecated package separator https://rt.cpan.org/Public/Bug/Display.html?id=148417 -Patch0: package-separator-perl5.38.patch BuildArch: noarch BuildRequires: perl BuildRequires: perl-macros @@ -47,7 +45,7 @@ Windows. %prep -%autosetup -n %{cpan_name}-%{version} -p1 +%autosetup -n %{cpan_name}-%{version} %build perl Build.PL --installdirs=vendor ++++++ DBM-Deep-2.0016.tar.gz -> DBM-Deep-2.0017.tar.gz ++++++ diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/DBM-Deep-2.0016/Build.PL new/DBM-Deep-2.0017/Build.PL --- old/DBM-Deep-2.0016/Build.PL 2018-05-21 00:53:02.000000000 +0200 +++ new/DBM-Deep-2.0017/Build.PL 2023-09-01 20:40:47.000000000 +0200 @@ -74,7 +74,8 @@ meta_add => { no_index => { directory => [ 'utils' ] } }, meta_merge => { resources => { - repository => 'https://github.com/robkinyon/dbm-deep', + repository => 'https://github.com/DrHyde/perl-modules-DBM-Deep', + bugtracker => 'https://github.com/DrHyde/perl-modules-DBM-Deep/issues', } }, ); diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/DBM-Deep-2.0016/Changes new/DBM-Deep-2.0017/Changes --- old/DBM-Deep-2.0016/Changes 2018-05-21 00:53:02.000000000 +0200 +++ new/DBM-Deep-2.0017/Changes 2023-09-01 20:40:47.000000000 +0200 @@ -1,5 +1,10 @@ Revision history for DBM::Deep (ordered by revision number). +2.0017 2023-09-01 + +- get rid of old perl4-style ' package separator and use :: instead + for compatibility with perl 5.38 + 2.0016 May 20 15:50:00 2018 PDT - Fix mistake in the previous release that prevented indexing. diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/DBM-Deep-2.0016/META.json new/DBM-Deep-2.0017/META.json --- old/DBM-Deep-2.0016/META.json 2018-05-21 00:53:02.000000000 +0200 +++ new/DBM-Deep-2.0017/META.json 2023-09-01 20:40:47.000000000 +0200 @@ -4,13 +4,13 @@ "unknown" ], "dynamic_config" : 1, - "generated_by" : "Module::Build version 0.4218", + "generated_by" : "Module::Build version 0.4234", "license" : [ "perl_5" ], "meta-spec" : { "url" : "http://search.cpan.org/perldoc?CPAN::Meta::Spec", - "version" : "2" + "version" : 2 }, "name" : "DBM-Deep", "no_index" : { @@ -47,7 +47,7 @@ "provides" : { "DBM::Deep" : { "file" : "lib/DBM/Deep.pm", - "version" : "2.0016" + "version" : "2.0017" }, "DBM::Deep::Array" : { "file" : "lib/DBM/Deep/Array.pm" @@ -127,13 +127,16 @@ }, "release_status" : "stable", "resources" : { + "bugtracker" : { + "web" : "https://github.com/DrHyde/perl-modules-DBM-Deep/issues" + }, "license" : [ "http://dev.perl.org/licenses/" ], "repository" : { - "url" : "https://github.com/robkinyon/dbm-deep" + "url" : "https://github.com/DrHyde/perl-modules-DBM-Deep" } }, - "version" : "2.0016", - "x_serialization_backend" : "JSON::PP version 2.27300" + "version" : "2.0017", + "x_serialization_backend" : "JSON::PP version 4.16" } diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/DBM-Deep-2.0016/META.yml new/DBM-Deep-2.0017/META.yml --- old/DBM-Deep-2.0016/META.yml 2018-05-21 00:53:02.000000000 +0200 +++ new/DBM-Deep-2.0017/META.yml 2023-09-01 20:40:47.000000000 +0200 @@ -13,7 +13,7 @@ configure_requires: Module::Build: '0.42' dynamic_config: 1 -generated_by: 'Module::Build version 0.4218, CPAN::Meta::Converter version 2.150005' +generated_by: 'Module::Build version 0.4234, CPAN::Meta::Converter version 2.150010' license: perl meta-spec: url: http://module-build.sourceforge.net/META-spec-v1.4.html @@ -25,7 +25,7 @@ provides: DBM::Deep: file: lib/DBM/Deep.pm - version: '2.0016' + version: '2.0017' DBM::Deep::Array: file: lib/DBM/Deep/Array.pm DBM::Deep::Engine: @@ -82,7 +82,8 @@ Scalar::Util: '1.14' perl: 5.008_004 resources: + bugtracker: https://github.com/DrHyde/perl-modules-DBM-Deep/issues license: http://dev.perl.org/licenses/ - repository: https://github.com/robkinyon/dbm-deep -version: '2.0016' + repository: https://github.com/DrHyde/perl-modules-DBM-Deep +version: '2.0017' x_serialization_backend: 'CPAN::Meta::YAML version 0.018' diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/DBM-Deep-2.0016/Makefile.PL new/DBM-Deep-2.0017/Makefile.PL --- old/DBM-Deep-2.0016/Makefile.PL 2018-05-21 00:53:02.000000000 +0200 +++ new/DBM-Deep-2.0017/Makefile.PL 2023-09-01 20:40:47.000000000 +0200 @@ -1,24 +1,24 @@ -# Note: this file was auto-generated by Module::Build::Compat version 0.4218 +# Note: this file was auto-generated by Module::Build::Compat version 0.4234 require 5.008004; use ExtUtils::MakeMaker; WriteMakefile ( - 'VERSION_FROM' => 'lib/DBM/Deep.pm', - 'EXE_FILES' => [], - 'INSTALLDIRS' => 'site', - 'PL_FILES' => {}, 'PREREQ_PM' => { - 'Digest::MD5' => '1.00', - 'Test::Exception' => '0.21', - 'File::Path' => '0.01', - 'Fcntl' => '0.01', 'Test::Warn' => '0.08', + 'File::Temp' => '0.01', + 'Scalar::Util' => '1.14', + 'Test::More' => '0.88', + 'File::Path' => '0.01', 'Pod::Usage' => '1.3', 'Test::Deep' => '0.095', - 'Scalar::Util' => '1.14', - 'File::Temp' => '0.01', - 'Test::More' => '0.88' + 'Digest::MD5' => '1.00', + 'Test::Exception' => '0.21', + 'Fcntl' => '0.01' }, - 'NAME' => 'DBM::Deep' + 'NAME' => 'DBM::Deep', + 'PL_FILES' => {}, + 'INSTALLDIRS' => 'site', + 'EXE_FILES' => [], + 'VERSION_FROM' => 'lib/DBM/Deep.pm' ) ; diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/DBM-Deep-2.0016/README new/DBM-Deep-2.0017/README --- old/DBM-Deep-2.0016/README 2018-05-21 00:53:02.000000000 +0200 +++ new/DBM-Deep-2.0017/README 2023-09-01 20:40:47.000000000 +0200 @@ -2,9 +2,6 @@ DBM::Deep - A pure perl multi-level hash/array DBM that supports transactions -VERSION - 2.0016 - SYNOPSIS use DBM::Deep; my $db = DBM::Deep->new( "foo.db" ); @@ -356,8 +353,8 @@ and direct them to the right place -- the DB file. This has nothing to do with the "Tie Construction" section above. This simply tells you how to use DBM::Deep using regular hashes and arrays, rather than calling - functions like "get()" and "put()" (although those work too). It is - entirely up to you how to want to access your databases. + functions like get() and put() (although those work too). It is entirely + up to you how to want to access your databases. Hashes You can treat any DBM::Deep object like a normal Perl hash reference. @@ -371,25 +368,25 @@ print $db->{myhash}->{subkey} . "\n"; - You can even step through hash keys using the normal Perl "keys()" + You can even step through hash keys using the normal Perl keys() function: foreach my $key (keys %$db) { print "$key: " . $db->{$key} . "\n"; } - Remember that Perl's "keys()" function extracts *every* key from the - hash and pushes them onto an array, all before the loop even begins. If - you have an extremely large hash, this may exhaust Perl's memory. - Instead, consider using Perl's "each()" function, which pulls - keys/values one at a time, using very little memory: + Remember that Perl's keys() function extracts *every* key from the hash + and pushes them onto an array, all before the loop even begins. If you + have an extremely large hash, this may exhaust Perl's memory. Instead, + consider using Perl's each() function, which pulls keys/values one at a + time, using very little memory: while (my ($key, $value) = each %$db) { print "$key: $value\n"; } - Please note that when using "each()", you should always pass a direct - hash reference, not a lookup. Meaning, you should never do this: + Please note that when using each(), you should always pass a direct hash + reference, not a lookup. Meaning, you should never do this: # NEVER DO THIS while (my ($key, $value) = each %{$db->{foo}}) { # BAD @@ -403,8 +400,8 @@ Arrays As with hashes, you can treat any DBM::Deep object like a normal Perl array reference. This includes inserting, removing and manipulating - elements, and the "push()", "pop()", "shift()", "unshift()" and - "splice()" functions. The object must have first been created using type + elements, and the push(), pop(), shift(), unshift() and splice() + functions. The object must have first been created using type "DBM::Deep->TYPE_ARRAY", or simply be a nested array reference inside a hash. Example: @@ -427,9 +424,8 @@ In addition to the *tie()* interface, you can also use a standard OO interface to manipulate all aspects of DBM::Deep databases. Each type of object (hash or array) has its own methods, but both types share the - following common methods: "put()", "get()", "exists()", "delete()" and - "clear()". "fetch()" and "store()" are aliases to "put()" and "get()", - respectively. + following common methods: put(), get(), exists(), delete() and clear(). + fetch() and store() are aliases to put() and get(), respectively. * new() / clone() @@ -491,7 +487,7 @@ This will compress the datafile so that it takes up as little space as possible. There is a freespace manager so that when space is freed up, it is used before extending the size of the datafile. But, - that freespace just sits in the datafile unless "optimize()" is + that freespace just sits in the datafile unless optimize() is called. "optimize" basically copies everything into a new database, so, if @@ -499,11 +495,10 @@ * import() - Unlike simple assignment, "import()" does not tie the right-hand - side. Instead, a copy of your data is put into the DB. "import()" - takes either an arrayref (if your DB is an array) or a hashref (if - your DB is a hash). "import()" will die if anything else is passed - in. + Unlike simple assignment, import() does not tie the right-hand side. + Instead, a copy of your data is put into the DB. import() takes + either an arrayref (if your DB is an array) or a hashref (if your DB + is a hash). import() will die if anything else is passed in. * export() @@ -536,7 +531,7 @@ Hashes For hashes, DBM::Deep supports all the common methods described above, - and the following additional methods: "first_key()" and "next_key()". + and the following additional methods: first_key() and next_key(). * first_key() @@ -575,8 +570,8 @@ Arrays For arrays, DBM::Deep supports all the common methods described above, - and the following additional methods: "length()", "push()", "pop()", - "shift()", "unshift()" and "splice()". + and the following additional methods: length(), push(), pop(), shift(), + unshift() and splice(). * length() @@ -659,16 +654,16 @@ locking => 1 ); - This causes DBM::Deep to "flock()" the underlying filehandle with + This causes DBM::Deep to flock() the underlying filehandle with exclusive mode for writes, and shared mode for reads. This is required if you have multiple processes accessing the same database file, to - avoid file corruption. Please note that "flock()" does NOT work for - files over NFS. See "DB over NFS" below for more. + avoid file corruption. Please note that flock() does NOT work for files + over NFS. See "DB over NFS" below for more. Explicit Locking You can explicitly lock a database, so it remains locked for multiple - actions. This is done by calling the "lock_exclusive()" method (for when - you want to write) or the "lock_shared()" method (for when you want to + actions. This is done by calling the lock_exclusive() method (for when + you want to write) or the lock_shared() method (for when you want to read). This is particularly useful for things like counters, where the current value needs to be fetched, then incremented, then stored again. @@ -691,16 +686,16 @@ future release. IMPORTING/EXPORTING - You can import existing complex structures by calling the "import()" + You can import existing complex structures by calling the import() method, and export an entire database into an in-memory structure using - the "export()" method. Both are examined here. + the export() method. Both are examined here. Importing Say you have an existing hash with nested hashes/arrays inside it. Instead of walking the structure and adding keys/elements to the - database as you go, simply pass a reference to the "import()" method. - This recursively adds everything to an existing DBM::Deep object for - you. Here is an example: + database as you go, simply pass a reference to the import() method. This + recursively adds everything to an existing DBM::Deep object for you. + Here is an example: my $struct = { key1 => "value1", @@ -720,18 +715,18 @@ This recursively imports the entire $struct object into $db, including all nested hashes and arrays. If the DBM::Deep object contains existing data, keys are merged with the existing ones, replacing if they already - exist. The "import()" method can be called on any database level (not - just the base level), and works with both hash and array DB types. + exist. The import() method can be called on any database level (not just + the base level), and works with both hash and array DB types. Note: Make sure your existing structure has no circular references in it. These will cause an infinite loop when importing. There are plans to fix this in a later release. Exporting - Calling the "export()" method on an existing DBM::Deep object will - return a reference to a new in-memory copy of the database. The export - is done recursively, so all nested hashes/arrays are all exported to - standard Perl objects. Here is an example: + Calling the export() method on an existing DBM::Deep object will return + a reference to a new in-memory copy of the database. The export is done + recursively, so all nested hashes/arrays are all exported to standard + Perl objects. Here is an example: my $db = DBM::Deep->new( "foo.db" ); @@ -746,10 +741,10 @@ print $struct->{key1} . "\n"; # prints "value1" This makes a complete copy of the database in memory, and returns a - reference to it. The "export()" method can be called on any database - level (not just the base level), and works with both hash and array DB - types. Be careful of large databases -- you can store a lot more data in - a DBM::Deep object than an in-memory Perl structure. + reference to it. The export() method can be called on any database level + (not just the base level), and works with both hash and array DB types. + Be careful of large databases -- you can store a lot more data in a + DBM::Deep object than an in-memory Perl structure. Note: Make sure your database has no circular references in it. These will cause an infinite loop when exporting. There are plans to fix this @@ -761,7 +756,7 @@ perfect way to extend the engine, and implement things like real-time compression or encryption. Filtering applies to the base DB level, and all child hashes / arrays. Filter hooks can be specified when your - DBM::Deep object is first constructed, or by calling the "set_filter()" + DBM::Deep object is first constructed, or by calling the set_filter() method at any time. There are four available filter hooks. set_filter() @@ -782,8 +777,8 @@ * filter_fetch_key This filter is called whenever a hash key is fetched (i.e. via - "first_key()" or "next_key()"). It is passed the transformed key, - and expected to return the plain key. + first_key() or next_key()). It is passed the transformed key, and + expected to return the plain key. * filter_fetch_value @@ -855,8 +850,7 @@ LOW-LEVEL ACCESS If you require low-level access to the underlying filehandle that - DBM::Deep uses, you can call the "_fh()" method, which returns the - handle: + DBM::Deep uses, you can call the _fh() method, which returns the handle: my $fh = $db->_fh(); @@ -864,7 +858,7 @@ child hashes or arrays. All levels share a *root* structure, which contains things like the filehandle, a reference counter, and all the options specified when you created the object. You can get access to - this file object by calling the "_storage()" method. + this file object by calling the _storage() method. my $file_obj = $db->_storage(); @@ -906,9 +900,9 @@ $db2->{foo} = $db1->{foo}; # dies Note: Passing the object to a function that recursively walks the object - tree (such as *Data::Dumper* or even the built-in "optimize()" or - "export()" methods) will result in an infinite loop. This will be fixed - in a future release by adding singleton support. + tree (such as *Data::Dumper* or even the built-in optimize() or export() + methods) will result in an infinite loop. This will be fixed in a future + release by adding singleton support. TRANSACTIONS As of 1.0000, DBM::Deep has ACID transactions. Every DBM::Deep object is @@ -1036,10 +1030,10 @@ Data::Dump::Streamer provides a mechanism for serializing coderefs, including saving off all closure state. This would allow for DBM::Deep to store the code for a subroutine. Then, whenever the - subroutine is read, the code could be "eval()"'ed into being. - However, just as for SCALAR and REF, that closure state may change - without notifying the DBM::Deep object storing the reference. Again, - this would generally be considered a feature. + subroutine is read, the code could be eval()'ed into being. However, + just as for SCALAR and REF, that closure state may change without + notifying the DBM::Deep object storing the reference. Again, this + would generally be considered a feature. External references and transactions If you do "my $x = $db->{foo};", then start a transaction, $x will be @@ -1052,7 +1046,7 @@ The current level of error handling in DBM::Deep is minimal. Files *are* checked for a 32-bit signature when opened, but any other form of corruption in the datafile can cause segmentation faults. DBM::Deep may - try to "seek()" past the end of a file, or get stuck in an infinite loop + try to seek() past the end of a file, or get stuck in an infinite loop depending on the level and type of corruption. File write operations are not checked for failure (for speed), so if you happen to run out of disk space, DBM::Deep will probably fail in a bad way. These things will be @@ -1062,15 +1056,15 @@ Beware of using DBM::Deep files over NFS. DBM::Deep uses flock(), which works well on local filesystems, but will NOT protect you from file corruption over NFS. I've heard about setting up your NFS server with a - locking daemon, then using "lockf()" to lock your files, but your - mileage may vary there as well. From what I understand, there is no real - way to do it. However, if you need access to the underlying filehandle - in DBM::Deep for using some other kind of locking scheme like "lockf()", - see the "LOW-LEVEL ACCESS" section above. + locking daemon, then using lockf() to lock your files, but your mileage + may vary there as well. From what I understand, there is no real way to + do it. However, if you need access to the underlying filehandle in + DBM::Deep for using some other kind of locking scheme like lockf(), see + the "LOW-LEVEL ACCESS" section above. Copying Objects Beware of copying tied objects in Perl. Very strange things can happen. - Instead, use DBM::Deep's "clone()" method which safely copies the object + Instead, use DBM::Deep's clone() method which safely copies the object and returns a new, blessed and tied hash or array to the same level in the DB. @@ -1106,10 +1100,10 @@ stale reference as an array or hash reference will cause an error. Large Arrays - Beware of using "shift()", "unshift()" or "splice()" with large arrays. - These functions cause every element in the array to move, which can be - murder on DBM::Deep, as every element has to be fetched from disk, then - stored again in a different location. This will be addressed in a future + Beware of using shift(), unshift() or splice() with large arrays. These + functions cause every element in the array to move, which can be murder + on DBM::Deep, as every element has to be fetched from disk, then stored + again in a different location. This will be addressed in a future version. This has been somewhat addressed so that the cost is constant, @@ -1140,7 +1134,7 @@ future changes to $x can be tracked within the DBM::Deep file and is considered to be a feature. By the time the rollback occurs, there is no knowledge that there had been an $x or what memory location to assign an - "export()" to. + export() to. NOTE: This does not affect importing because imports do a walk over the reference to be imported in order to explicitly leave it untied. @@ -1182,18 +1176,16 @@ ---------------------------- ------ ------ ------ ------ ------ ------ ------ MORE INFORMATION - Check out the DBM::Deep Google Group at - <http://groups.google.com/group/DBM-Deep> or send email to - DBM-Deep@googlegroups.com <mailto:DBM-Deep@googlegroups.com>. You can - also visit #dbm-deep on irc.perl.org - - The source code repository is at <http://github.com/robkinyon/dbm-deep> + The source code repository is at + <http://github.com/DrHyde/perl-modules-DBM-Deep> MAINTAINERS - Rob Kinyon, rkinyon@cpan.org <mailto:rkinyon@cpan.org> + Currently maintained by David Cantrell dcantrell@cpan.org + <mailto:dcantrell@cpan.org>. Originally written by Joseph Huckaby, jhuckaby@cpan.org - <mailto:jhuckaby@cpan.org> + <mailto:jhuckaby@cpan.org> with significant additions by Rob Kinyon, + rkinyon@cpan.org <mailto:rkinyon@cpan.org> SPONSORS Stonehenge Consulting (<http://www.stonehenge.com/>) sponsored the @@ -1225,7 +1217,7 @@ perltie(1), Tie::Hash(3), Fcntl(3), flock(2), lockf(3), nfs(5) LICENSE - Copyright (c) 2007-14 Rob Kinyon. All Rights Reserved. This is free - software, you may use it and distribute it under the same terms as Perl - itself. + Copyright (c) 2007-23 Rob Kinyon and others. All Rights Reserved. This + is free software, you may use it and distribute it under the same terms + as Perl itself. diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/DBM-Deep-2.0016/lib/DBM/Deep.pm new/DBM-Deep-2.0017/lib/DBM/Deep.pm --- old/DBM-Deep-2.0016/lib/DBM/Deep.pm 2018-05-21 00:53:02.000000000 +0200 +++ new/DBM-Deep-2.0017/lib/DBM/Deep.pm 2023-09-01 20:40:47.000000000 +0200 @@ -6,7 +6,7 @@ use warnings FATAL => 'all'; no warnings 'recursion'; -our $VERSION = q(2.0016); +our $VERSION = q(2.0017); use Scalar::Util (); @@ -647,13 +647,13 @@ # to avoid this hack. warnings.pm did not allow us to specify # exactly the call frame we want, so we have to look at the bitmask # ourselves. - if( vec $bitmask, $warnings'Offsets{$_[0]}, 1, - || vec $bitmask, $warnings'Offsets{all}, 1, + if( vec $bitmask, $warnings::Offsets{$_[0]}, 1, + || vec $bitmask, $warnings::Offsets{all}, 1, ) { my $msg = $_[1] =~ /\n\z/ ? $_[1] : "$_[1] at $file line $line.\n"; die $msg - if vec $bitmask, $warnings'Offsets{$_[0]}+1, 1, - || vec $bitmask, $warnings'Offsets{all}+1, 1; + if vec $bitmask, $warnings::Offsets{$_[0]}+1, 1, + || vec $bitmask, $warnings::Offsets{all}+1, 1; warn $msg; } } diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/DBM-Deep-2.0016/lib/DBM/Deep.pod new/DBM-Deep-2.0017/lib/DBM/Deep.pod --- old/DBM-Deep-2.0016/lib/DBM/Deep.pod 2018-05-21 00:53:02.000000000 +0200 +++ new/DBM-Deep-2.0017/lib/DBM/Deep.pod 2023-09-01 20:40:47.000000000 +0200 @@ -2,10 +2,6 @@ DBM::Deep - A pure perl multi-level hash/array DBM that supports transactions -=head1 VERSION - -2.0016 - =head1 SYNOPSIS use DBM::Deep; @@ -1275,17 +1271,15 @@ =head1 MORE INFORMATION -Check out the DBM::Deep Google Group at L<http://groups.google.com/group/DBM-Deep> -or send email to L<DBM-Deep@googlegroups.com|mailto:DBM-Deep@googlegroups.com>. -You can also visit #dbm-deep on irc.perl.org - -The source code repository is at L<http://github.com/robkinyon/dbm-deep> +The source code repository is at L<http://github.com/DrHyde/perl-modules-DBM-Deep> =head1 MAINTAINERS -Rob Kinyon, L<rkinyon@cpan.org|mailto:rkinyon@cpan.org> +Currently maintained by David Cantrell L<dcantrell@cpan.org|mailto:dcantrell@cpan.org>. Originally written by Joseph Huckaby, L<jhuckaby@cpan.org|mailto:jhuckaby@cpan.org> +with significant additions by Rob Kinyon, L<rkinyon@cpan.org|mailto:rkinyon@cpan.org> + =head1 SPONSORS @@ -1323,7 +1317,7 @@ =head1 LICENSE -Copyright (c) 2007-14 Rob Kinyon. All Rights Reserved. +Copyright (c) 2007-23 Rob Kinyon and others. All Rights Reserved. This is free software, you may use it and distribute it under the same terms as Perl itself. ++++++ cpanspec.yml ++++++ --- /var/tmp/diff_new_pack.MFbTRD/_old 2023-09-29 21:15:18.813514753 +0200 +++ /var/tmp/diff_new_pack.MFbTRD/_new 2023-09-29 21:15:18.821515042 +0200 @@ -7,10 +7,10 @@ #sources: # - source1 # - source2 -patches: +#patches: # foo.patch: -p1 # bar.patch: - package-separator-perl5.38.patch: -p1 PATCH-FIX-UPSTREAM deprecated package separator https://rt.cpan.org/Public/Bug/Display.html?id=148417 +# package-separator-perl5.38.patch: -p1 PATCH-FIX-UPSTREAM deprecated package separator https://rt.cpan.org/Public/Bug/Display.html?id=148417 #preamble: |- # BuildRequires: gcc-c++ #post_prep: |-