[SCM] Debian packaging of libmail-box-perl branch, master, updated. debian/2.107-1-13-ga9d109d

Tue Jun 25 21:05:42 UTC 2013

The following commit has been merged in the master branch:
commit 83545d461ee42904ca74a18d375f5e210d854ef1
Author: Salvatore Bonaccorso <carnil at debian.org>
Date:   Tue Jun 25 22:51:06 2013 +0200

    Add 03_spelling-error-in-manpage.patch patch

diff --git a/debian/patches/03_spelling-error-in-manpage.patch b/debian/patches/03_spelling-error-in-manpage.patch
new file mode 100644
index 0000000..ab721c8
--- /dev/null
+++ b/debian/patches/03_spelling-error-in-manpage.patch
@@ -0,0 +1,204 @@
+Description: Fix spelling errors in manpage
+Origin: vendor
+Author: Salvatore Bonaccorso <carnil at debian.org>
+Last-Update: 2013-06-25
+
+--- a/lib/Mail/Box/Dbx/Message.pod
++++ b/lib/Mail/Box/Dbx/Message.pod
+@@ -62,7 +62,7 @@
+ 
+ =item account_name => STRING
+ 
+-The string representation of the account which was used to retreive the
++The string representation of the account which was used to retrieve the
+ message.
+ 
+ =item account_nr => INTEGER
+@@ -584,13 +584,13 @@
+ 
+ =item $obj-E<gt>B<accountName>()
+ 
+-Returns the Outlook Express account name which was used to retreive
++Returns the Outlook Express account name which was used to retrieve
+ this message, represented as a string.  The L<accountNr()|Mail::Box::Dbx::Message/"The flags"> returns
+ a numerical representation of the same fact.
+ 
+ =item $obj-E<gt>B<accountNr>()
+ 
+-Returns the Outlook Express account name which was used to retreive
++Returns the Outlook Express account name which was used to retrieve
+ this message, represented as a number.  The L<accountName()|Mail::Box::Dbx::Message/"The flags"> returns
+ a string representation of the same fact.
+ 
+--- a/lib/Mail/Box/File.pod
++++ b/lib/Mail/Box/File.pod
+@@ -142,7 +142,7 @@
+  my_own_lockfile.test   # full filename, same dir
+  /etc/passwd            # somewhere else
+ 
+-When the program runs with less priviledges (as normal user), often the
++When the program runs with less privileges (as normal user), often the
+ default inbox folder can not be locked with the lockfile name which is
+ produced by default.
+ 
+@@ -723,7 +723,7 @@
+ Mail::Box is lazy: it tries to leave messages in the folders until they
+ are used, which saves time and memory usage.  When this message appears,
+ something is terribly wrong: some lazy message are needed for updating the
+-folder, but they cannot be retreived from the original file anymore.  In
++folder, but they cannot be retrieved from the original file anymore.  In
+ this case, messages can be lost.
+ 
+ This message does appear regularly on Windows systems when using the
+--- a/lib/Mail/Box/IMAP4.pod
++++ b/lib/Mail/Box/IMAP4.pod
+@@ -122,7 +122,7 @@
+ case, the body of a message is requested via L<Mail::Message::body()|Mail::Message/"The body">
+ or L<Mail::Message::decoded()|Mail::Message/"The body">.  This returns a handle to a body object.
+ You may decide wether that body object can be reused or not.  C<NO>
+-means: retreive the data each time again, C<YES> will cache the body data,
++means: retrieve the data each time again, C<YES> will cache the body data,
+ C<DELAY> will send the whole message when the folder is closed.
+ 
+         [local cache]  [write]
+@@ -690,7 +690,7 @@
+ 
+ =item Warning: Cannot read body for $uidl in $folder.
+ 
+-The header of the message was retreived from the IMAP4 server, but the
++The header of the message was retrieved from the IMAP4 server, but the
+ body is not read, for an unknown reason.
+ 
+ =item Error: Copying failed for one message.
+--- a/lib/Mail/Box/IMAP4/Head.pod
++++ b/lib/Mail/Box/IMAP4/Head.pod
+@@ -15,7 +15,7 @@
+ =head1 DESCRIPTION
+ 
+ This class implements a pure IMAP4 protocol interface, where as little
+-data is retreived from the header as possible.  This may look nice
++data is retrieved from the header as possible.  This may look nice
+ to you, but is not sufficient for many tasks.  For instance, you cannot
+ removed or modify fields this way.
+ 
+--- a/lib/Mail/Box/IMAP4/Message.pod
++++ b/lib/Mail/Box/IMAP4/Message.pod
+@@ -462,7 +462,7 @@
+ 
+ Use the IMAP's C<UID FETCH IMAP> command to get some data about this
+ message.  The INFO request is passed to L<Mail::Box::IMAP4::fetch()|Mail::Box::IMAP4/"Internals">.
+-Without INFO, C<ALL> information is retreived and returned as a HASH.
++Without INFO, C<ALL> information is retrieved and returned as a HASH.
+ 
+ =item $obj-E<gt>B<isDelayed>()
+ 
+--- a/lib/Mail/Box/Dbx.pod
++++ b/lib/Mail/Box/Dbx.pod
+@@ -653,7 +653,7 @@
+ Mail::Box is lazy: it tries to leave messages in the folders until they
+ are used, which saves time and memory usage.  When this message appears,
+ something is terribly wrong: some lazy message are needed for updating the
+-folder, but they cannot be retreived from the original file anymore.  In
++folder, but they cannot be retrieved from the original file anymore.  In
+ this case, messages can be lost.
+ 
+ This message does appear regularly on Windows systems when using the
+--- a/lib/Mail/Box/Mbox.pod
++++ b/lib/Mail/Box/Mbox.pod
+@@ -662,7 +662,7 @@
+ Mail::Box is lazy: it tries to leave messages in the folders until they
+ are used, which saves time and memory usage.  When this message appears,
+ something is terribly wrong: some lazy message are needed for updating the
+-folder, but they cannot be retreived from the original file anymore.  In
++folder, but they cannot be retrieved from the original file anymore.  In
+ this case, messages can be lost.
+ 
+ This message does appear regularly on Windows systems when using the
+--- a/lib/Mail/Box/POP3.pod
++++ b/lib/Mail/Box/POP3.pod
+@@ -644,7 +644,7 @@
+ 
+ =item Error: Cannot read body for $uidl on POP3 server $name.
+ 
+-The message's headers are retreived from the server, but the body seems
++The message's headers are retrieved from the server, but the body seems
+ to be lost.  Did the message get destroyed between reading the header
+ and reading the body?
+ 
+--- a/lib/Mail/Box/POP3s.pod
++++ b/lib/Mail/Box/POP3s.pod
+@@ -507,7 +507,7 @@
+ 
+ =item Error: Cannot read body for $uidl on POP3 server $name.
+ 
+-The message's headers are retreived from the server, but the body seems
++The message's headers are retrieved from the server, but the body seems
+ to be lost.  Did the message get destroyed between reading the header
+ and reading the body?
+ 
+--- a/lib/Mail/Box/Search/SpamAssassin.pod
++++ b/lib/Mail/Box/Search/SpamAssassin.pod
+@@ -127,7 +127,7 @@
+ 
+ Provide a Mail::SpamAssassin object to be used for searching spam.  If
+ none is specified, one is created internally.  The object can be
+-retreived with assassinator().
++retrieved with assassinator().
+ 
+ =item trace => LEVEL
+ 
+--- a/lib/Mail/Message.pod
++++ b/lib/Mail/Message.pod
+@@ -1038,7 +1038,7 @@
+ 
+ =head3 The body
+ 
+-The body contains the "payload": the data to be transfered.
++The body contains the "payload": the data to be transferred.
+ The data can be encoded, only accessible with a specific application,
+ and may use some weird character-set, like Vietnamese; the MailBox
+ distribution tries to assist you with handling these e-mails without
+--- a/lib/Mail/Box.pod
++++ b/lib/Mail/Box.pod
+@@ -1428,7 +1428,7 @@
+ 
+ =item * L<Mail::Box::POP3|Mail::Box::POP3> (read/delete only)
+ 
+-POP3 is a protocol which can be used to retreive messages from a
++POP3 is a protocol which can be used to retrieve messages from a
+ remote system.  After the connection to a POP server is made, the
+ messages can be looked at and removed as if they are on the local
+ system.
+--- a/lib/Mail/Message/Head/FieldGroup.pod
++++ b/lib/Mail/Message/Head/FieldGroup.pod
+@@ -181,7 +181,7 @@
+ Returns an abstract name for the field group; which software is
+ controling it.  C<undef> is returned in case the type is not known.
+ Valid names are group type dependent: see the applicable manual
+-pages.  A list of all types can be retreived with L<implementedTypes()|Mail::Message::Head::FieldGroup/"Constructors">.
++pages.  A list of all types can be retrieved with L<implementedTypes()|Mail::Message::Head::FieldGroup/"Constructors">.
+ 
+ =item $obj-E<gt>B<version>()
+ 
+--- a/lib/Mail/Transport/IMAP4.pod
++++ b/lib/Mail/Transport/IMAP4.pod
+@@ -108,7 +108,7 @@
+ shall be a L<Mail::IMAPClient|Mail::IMAPClient>.
+ 
+ When a CLASS is given, an object of that type is created for you.  The created
+-object can be retreived via L<imapClient()|Mail::Transport::IMAP4/"Protocol [internals]">, and than configured as
++object can be retrieved via L<imapClient()|Mail::Transport::IMAP4/"Protocol [internals]">, and than configured as
+ defined by L<Mail::IMAPClient|Mail::IMAPClient>.
+ 
+ =item interval => SECONDS
+--- a/lib/Mail/Transport/POP3.pod
++++ b/lib/Mail/Transport/POP3.pod
+@@ -355,7 +355,7 @@
+ 
+ =item Error: Cannot get the messages of pop3 via messages()
+ 
+-It is not possible to retreive all messages on a remote POP3 folder
++It is not possible to retrieve all messages on a remote POP3 folder
+ at once: each shall be taken separately.  The POP3 folder will hide this
+ for you.
+ 
diff --git a/debian/patches/series b/debian/patches/series
index bcdda5f..222edb7 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,2 +1,3 @@
 01_access_check_use_filetest::access.patch
 02_man_page_width_errors.patch
+03_spelling-error-in-manpage.patch

-- 
Debian packaging of libmail-box-perl

