Refresh fix-spelling.patch.

1 files changed, 83 insertions, 29 deletions

diff --git a/debian/patches/fix-spelling.patch b/debian/patches/fix-spelling.patch
index d86c837..5309324 100644
--- a/debian/patches/fix-spelling.patch
+++ b/debian/patches/fix-spelling.patch
@@ -1,13 +1,22 @@
 Description: Fix some spelling errors
-Author: Jonas Genannt <jonas.genannt@capi2name.de>
-Forwarded: yes
 Bug: https://rt.cpan.org/Public/Bug/Display.html?id=87898
+Forwarded: yes
+Author: Jonas Genannt <jonas.genannt@capi2name.de>
+Reviewed-by: gregor herrmann <gregoa@debian.org>
+Last-Update: 2021-01-31
 
-diff --git a/lib/Test/Inline.pm b/lib/Test/Inline.pm
-index f101f00..99ea86f 100644
 --- a/lib/Test/Inline.pm
 +++ b/lib/Test/Inline.pm
-@@ -36,7 +36,7 @@ following.
+@@ -764,7 +764,7 @@
+ 			return $self->InputHandler->read(shift);
+ 		} elsif ( $self->InputHandler->exists_dir($_[0]) ) {
+ 			# Directory path
+-			return shift; # Handled seperately
++			return shift; # Handled separately
+ 		}
+ 		return undef;
+ 	}
+@@ -847,7 +847,7 @@
  
  You can add as many, or as few, of these chunks of tests as you wish.
  The key condition when writing them is that they should be logically
@@ -16,7 +25,7 @@ index f101f00..99ea86f 100644
  or crash if it is run before or after another chunk.
  
  Using L<inline2test> or another test compiler, you can then transform
-@@ -63,7 +63,7 @@ based on the test failures, you can correct your assumption.
+@@ -874,7 +874,7 @@
  
  It's also extremely useful for systematically testing self-contained code.
  
@@ -25,7 +34,7 @@ index f101f00..99ea86f 100644
  external systems such as databases, and that has no side-effects on external
  systems.
  
-@@ -176,7 +176,7 @@ debugging information to STDOUT as it runs.
+@@ -951,7 +951,7 @@
  
  B<manifest> - The C<manifest> option, if provided, will cause a manifest
  file to be created and written to disk. The manifest file contains a list
@@ -34,29 +43,18 @@ index f101f00..99ea86f 100644
  should be processed to best satisfy the class-level dependency of the
  tests.
  
-@@ -771,7 +771,7 @@ sub _source {
- 			return $self->InputHandler->read(shift);
- 		} elsif ( $self->InputHandler->exists_dir($_[0]) ) {
- 			# Directory path
--			return shift; # Handled seperately
-+			return shift; # Handled separately
- 		}
- 		return undef;
- 	}
-diff --git a/lib/Test/Inline/Section.pm b/lib/Test/Inline/Section.pm
-index 784dd34..603c244 100644
 --- a/lib/Test/Inline/Section.pm
 +++ b/lib/Test/Inline/Section.pm
-@@ -54,7 +54,7 @@ are considered low priority, and we be run, in order of appearance, AFTER all
- named tests have been run.
- 
- Any and all arguments used after "testing" must be in the form of simple
--space seperated words. The first word is considered the "name" of the test.
-+space separated words. The first word is considered the "name" of the test.
- The intended use for these is generally to create one named test section for 
- each function or method, but you can name them as you please. Test names 
- B<must> be unique, and B<are> case sensitive.
-@@ -142,7 +142,7 @@ sub new {
+@@ -51,7 +51,7 @@
+ #pod named tests have been run.
+ #pod
+ #pod Any and all arguments used after "testing" must be in the form of simple
+-#pod space seperated words. The first word is considered the "name" of the test.
++#pod space separated words. The first word is considered the "name" of the test.
+ #pod The intended use for these is generally to create one named test section for 
+ #pod each function or method, but you can name them as you please. Test names 
+ #pod B<must> be unique, and B<are> case sensitive.
+@@ -136,7 +136,7 @@
  	# Split into lines
  	my @lines = split /(?:\015{1,2}\012|\015|\012)/, $pod;
  
@@ -65,7 +63,25 @@ index 784dd34..603c244 100644
  	if ( $pod =~ /^$RE_example\b/ ) {
  		return $class->_example( \@lines, $context );
  	}
-@@ -349,7 +349,7 @@ sub _trim_empty_lines {
+@@ -343,7 +343,7 @@
+ #pod
+ #pod Since version 1.50 L<Test::Inline> has been extracting package statements
+ #pod so that as the sections are extracted, we can determine which sections
+-#pod belong to which packages, and seperate them accordingly.
++#pod belong to which packages, and separate them accordingly.
+ #pod
+ #pod The C<parse> method takes B<all> of the elements from a file, and returns
+ #pod all of the Sections. By doing it here, we can track the package context
+@@ -600,7 +600,7 @@
+ named tests have been run.
+ 
+ Any and all arguments used after "testing" must be in the form of simple
+-space seperated words. The first word is considered the "name" of the test.
++space separated words. The first word is considered the "name" of the test.
+ The intended use for these is generally to create one named test section for 
+ each function or method, but you can name them as you please. Test names 
+ B<must> be unique, and B<are> case sensitive.
+@@ -656,7 +656,7 @@
  
  Since version 1.50 L<Test::Inline> has been extracting package statements
  so that as the sections are extracted, we can determine which sections
@@ -74,3 +90,41 @@ index 784dd34..603c244 100644
  
  The C<parse> method takes B<all> of the elements from a file, and returns
  all of the Sections. By doing it here, we can track the package context
+--- a/lib/Test/Inline/Script.pm
++++ b/lib/Test/Inline/Script.pm
+@@ -7,7 +7,7 @@
+ #pod
+ #pod This class is where the heavy lifting happens to actually generating a
+ #pod test file takes place. Given a source filename, this modules will load
+-#pod it, parse out the relavent bits, put them into order based on the tags,
++#pod it, parse out the relevant bits, put them into order based on the tags,
+ #pod and then merge them into a test file.
+ #pod
+ #pod =head1 METHODS
+@@ -262,7 +262,7 @@
+ #pod sections. For the full file contents, see the C<file_content> method.
+ #pod
+ #pod Returns a string containing the merged section content on success, false
+-#pod if there is no content, despite the existance of sections ( which would
++#pod if there is no content, despite the existence of sections ( which would
+ #pod have been empty ), or C<undef> on error.
+ #pod
+ #pod =cut
+@@ -420,7 +420,7 @@
+ 
+ This class is where the heavy lifting happens to actually generating a
+ test file takes place. Given a source filename, this modules will load
+-it, parse out the relavent bits, put them into order based on the tags,
++it, parse out the relevant bits, put them into order based on the tags,
+ and then merge them into a test file.
+ 
+ =head1 METHODS
+@@ -505,7 +505,7 @@
+ sections. For the full file contents, see the C<file_content> method.
+ 
+ Returns a string containing the merged section content on success, false
+-if there is no content, despite the existance of sections ( which would
++if there is no content, despite the existence of sections ( which would
+ have been empty ), or C<undef> on error.
+ 
+ =head1 SUPPORT