[SCM] Debian packaging of libio-async-perl branch, master, updated. debian/0.44-1-6-g5007232

Sat Nov 26 14:10:26 UTC 2011

The following commit has been merged in the master branch:
commit 24061ee6fdc5065b2d3ff592129c02bbd043d461
Author: Salvatore Bonaccorso <carnil at debian.org>
Date:   Sat Nov 26 14:54:47 2011 +0100

    Add fix-spelling-error-in-manpage.patch
    
    Fix some spelling errors reported by lintian.

diff --git a/debian/patches/fix-spelling-error-in-manpage.patch b/debian/patches/fix-spelling-error-in-manpage.patch
new file mode 100644
index 0000000..daab43f
--- /dev/null
+++ b/debian/patches/fix-spelling-error-in-manpage.patch
@@ -0,0 +1,141 @@
+Description: Fix some spelling errors
+Origin: vendor
+Bug: https://rt.cpan.org/Public/Bug/Display.html?id=72736
+Forwarded: yes
+Author: Salvatore Bonaccorso <carnil at debian.org>
+Last-Update: 2011-11-26
+
+--- a/README
++++ b/README
+@@ -44,7 +44,7 @@
+     would consist of a single subclass of IO::Async::Loop to act as a
+     container of other objects, which perform the actual IO work required by
+     the program. As well as IO handles, the loop also supports timers and
+-    signal handlers, and includes more higher-level functionallity built on
++    signal handlers, and includes more higher-level functionality built on
+     top of these basic parts.
+ 
+     Because there are a lot of classes in this collection, the following
+@@ -53,7 +53,7 @@
+   Notifiers
+     The base class of all the event handling subclasses is
+     IO::Async::Notifier. It does not perform any IO operations itself, but
+-    instead acts as a base class to build the specific IO functionallity
++    instead acts as a base class to build the specific IO functionality
+     upon. It can also coordinate a collection of other Notifiers contained
+     within it, forming a tree structure.
+ 
+@@ -118,7 +118,7 @@
+   Loops
+     The IO::Async::Loop object class represents an abstract collection of
+     IO::Async::Notifier objects, and manages the actual filehandle IO
+-    watchers, timers, signal handlers, and other functionallity. It performs
++    watchers, timers, signal handlers, and other functionality. It performs
+     all of the abstract collection management tasks, and leaves the actual
+     OS interactions to a particular subclass for the purpose.
+ 
+--- a/lib/IO/Async.pm
++++ b/lib/IO/Async.pm
+@@ -63,7 +63,7 @@
+ consist of a single subclass of L<IO::Async::Loop> to act as a container of
+ other objects, which perform the actual IO work required by the program. As
+ well as IO handles, the loop also supports timers and signal handlers, and
+-includes more higher-level functionallity built on top of these basic parts.
++includes more higher-level functionality built on top of these basic parts.
+ 
+ Because there are a lot of classes in this collection, the following overview
+ gives a brief description of each.
+@@ -72,7 +72,7 @@
+ 
+ The base class of all the event handling subclasses is L<IO::Async::Notifier>.
+ It does not perform any IO operations itself, but instead acts as a base class
+-to build the specific IO functionallity upon. It can also coordinate a
++to build the specific IO functionality upon. It can also coordinate a
+ collection of other Notifiers contained within it, forming a tree structure.
+ 
+ The following sections describe particular types of Notifier.
+@@ -139,7 +139,7 @@
+ 
+ The L<IO::Async::Loop> object class represents an abstract collection of
+ L<IO::Async::Notifier> objects, and manages the actual filehandle IO
+-watchers, timers, signal handlers, and other functionallity. It performs all
++watchers, timers, signal handlers, and other functionality. It performs all
+ of the abstract collection management tasks, and leaves the actual OS
+ interactions to a particular subclass for the purpose.
+ 
+--- a/lib/IO/Async/Loop.pm
++++ b/lib/IO/Async/Loop.pm
+@@ -90,7 +90,7 @@
+ L<IO::Async::Notifier> objects or subclasses of them. It handles all of the
+ lower-level set manipulation actions, and leaves the actual IO readiness 
+ testing/notification to the concrete class that implements it. It also
+-provides other functionallity such as signal handling, child process managing,
++provides other functionality such as signal handling, child process managing,
+ and timers.
+ 
+ See also the two bundled Loop subclasses:
+@@ -444,7 +444,7 @@
+ =head1 FEATURES
+ 
+ Most of the following methods are higher-level wrappers around base
+-functionallity provided by the low-level API documented below. They may be
++functionality provided by the low-level API documented below. They may be
+ used by C<IO::Async::Notifier> subclasses or called directly by the program.
+ 
+ =cut
+@@ -1521,7 +1521,7 @@
+ 
+ As C<IO::Async::Loop> is an abstract base class, specific subclasses of it are
+ required to implement certain methods that form the base level of
+-functionallity. They are not recommended for applications to use; see instead
++functionality. They are not recommended for applications to use; see instead
+ the various event objects or higher level methods listed above.
+ 
+ These methods should be considered as part of the interface contract required
+@@ -1792,7 +1792,7 @@
+ 
+ Either one of C<time> or C<delay> is required.
+ 
+-For more powerful timer functionallity as a C<IO::Async::Notifier> (so it can
++For more powerful timer functionality as a C<IO::Async::Notifier> (so it can
+ be used as a child within another Notifier), see instead the
+ L<IO::Async::Timer> object and its subclasses.
+ 
+@@ -2045,7 +2045,7 @@
+ =head1 METHODS FOR SUBCLASSES
+ 
+ The following methods are provided to access internal features which are
+-required by specific subclasses to implement the loop functionallity. The use
++required by specific subclasses to implement the loop functionality. The use
+ cases of each will be documented in the above section.
+ 
+ =cut
+@@ -2119,7 +2119,7 @@
+ 
+ An Extension is a Perl module that provides extra methods in the
+ C<IO::Async::Loop> or other packages. They are intended to provide extra
+-functionallity that easily integrates with the rest of the code.
++functionality that easily integrates with the rest of the code.
+ 
+ Certain base methods take an C<extensions> parameter; an ARRAY reference
+ containing a list of extension names. If such a list is passed to a method, it
+@@ -2145,7 +2145,7 @@
+ This is provided so that extension modules, such as L<IO::Async::SSL> can
+ easily be invoked indirectly, by passing extra arguments to C<connect> methods
+ or similar, without needing every module to be aware of the C<SSL> extension.
+-This functionallity is generic and not limited to C<SSL>; other extensions may
++This functionality is generic and not limited to C<SSL>; other extensions may
+ also use it.
+ 
+ The following methods take an C<extensions> parameter:
+--- a/lib/IO/Async/ChildManager.pm
++++ b/lib/IO/Async/ChildManager.pm
+@@ -104,7 +104,7 @@
+ 
+ =head1 DESCRIPTION
+ 
+-This module extends the functionallity of the containing C<IO::Async::Loop> to
++This module extends the functionality of the containing C<IO::Async::Loop> to
+ manage the execution of child processes. It acts as a central point to store
+ PID values of currently-running children, and to call the appropriate
+ continuation handler code when the process terminates. It provides useful
diff --git a/debian/patches/series b/debian/patches/series
new file mode 100644
index 0000000..8810115
--- /dev/null
+++ b/debian/patches/series
@@ -0,0 +1 @@
+fix-spelling-error-in-manpage.patch

-- 
Debian packaging of libio-async-perl

