[SCM] Debian packaging of liborlite-migrate-perl branch, master, updated. da05df664a3c22e6f008d56e8c666d4b66089213

[gregor herrmann]

The following commit has been merged in the master branch:
commit 16cfe323fb50a150fe10257653d9e541589d9c2e
Author: gregor herrmann <gregoa at debian.org>
Date:   Sat Oct 15 23:24:12 2011 +0200

    Add a patch to fix a spelling mistake.

diff --git a/debian/patches/series b/debian/patches/series
new file mode 100644
index 0000000..5299247
--- /dev/null
+++ b/debian/patches/series
@@ -0,0 +1 @@
+spelling.patch
diff --git a/debian/patches/spelling.patch b/debian/patches/spelling.patch
new file mode 100644
index 0000000..c4e66ef
--- /dev/null
+++ b/debian/patches/spelling.patch
@@ -0,0 +1,20 @@
+Description: fix a spelling mistake
+Origin: vendor
+Bug: https://rt.cpan.org/Ticket/Display.html?id=71709
+Forwarded: https://rt.cpan.org/Ticket/Display.html?id=71709
+Author: gregor herrmann <gregoa at debian.org>
+Reviewed-by: gregor herrmann <gregoa at debian.org>
+Last-Update: 2011-10-15
+Applied-Upstream: *** FIXME ***
+
+--- a/lib/ORLite/Migrate/Timeline.pm
++++ b/lib/ORLite/Migrate/Timeline.pm
+@@ -34,7 +34,7 @@
+ The default L<ORLite::Migrate> timeline implementation makes use of separate
+ Perl "patch" scripts to move the database schema timeline forwards.
+ 
+-This solution is prefered because the separate scripts provide process
++This solution is preferred because the separate scripts provide process
+ isolation between your migration and run-time code. That is, the code that
+ migrates the schema a single step forwards is guarenteed to never use the same
+ variables or load the same modules or interact strangely with any other patch

-- 
Debian packaging of liborlite-migrate-perl