diff --git a/perl-Test-Spelling-0.11-hunspell.patch b/perl-Test-Spelling-0.11-hunspell.patch
new file mode 100644
index 0000000..bdfde05
--- /dev/null
+++ b/perl-Test-Spelling-0.11-hunspell.patch
@@ -0,0 +1,48 @@
+diff -up Test-Spelling-0.11/lib/Test/Spelling.pm.BAD Test-Spelling-0.11/lib/Test/Spelling.pm
+--- Test-Spelling-0.11/lib/Test/Spelling.pm.BAD	2010-01-20 19:35:34.771928737 -0500
++++ Test-Spelling-0.11/lib/Test/Spelling.pm	2010-01-20 19:37:45.806790957 -0500
+@@ -12,7 +12,7 @@ use Carp;
+ our $VERSION = '0.11';
+ 
+ my $Test        = Test::Builder->new;
+-my $Spell_cmd   = 'spell';
++my $Spell_cmd   = 'hunspell -l';
+ my $Spell_temp  = File::Temp->new->filename;
+ 
+ sub import {
+@@ -155,7 +155,7 @@ Test::Spelling - check for spelling erro
+ 
+ C<Test::Spelling> lets you check the spelling of a POD file, and report
+ its results in standard C<Test::Simple> fashion. This module requires the
+-F<spell> program.
++F<hunspell> program.
+ 
+     use Test::More;
+     use Test::Spelling;
+@@ -172,7 +172,7 @@ module distribution:
+ 
+ Note, however that it is not really recommended to include this test with a
+ CPAN distribution, or a package that will run in an uncontrolled environment,
+-because there's no way of predicting if F<spell> will be available or the
++because there's no way of predicting if F<hunspell> will be available or the
+ word list used will give the same results (what if it's in a different language,
+ for example?). You can have the test, but don't add it to F<MANIFEST> (or add
+ it to F<MANIFEST.SKIP> to make sure you don't add it by accident). Anyway,
+@@ -189,7 +189,7 @@ ways to add per-file stopwords to each .
+ 
+ =head1 DESCRIPTION
+ 
+-Check POD files for spelling mistakes, using L<Pod::Spell> and F<spell> to do
++Check POD files for spelling mistakes, using L<Pod::Spell> and F<hunspell> to do
+ the heavy lifting.
+ 
+ =head1 FUNCTIONS
+@@ -278,7 +278,7 @@ in verbatim blocks and code labeled with
+ 
+ =head2 set_spell_cmd($command)
+ 
+-If the F<spell> program has a different name or is not in your path, you can
++If the F<hunspell> program has a different name or is not in your path, you can
+ specify an alternative with C<set_spell_cmd>. Any command that takes text
+ from standard input and prints a list of misspelled words, one per line, to
+ standard output will do. For example, you can use C<aspell -l>.
diff --git a/perl-Test-Spelling.spec b/perl-Test-Spelling.spec
index 507f894..4b71df7 100644
--- a/perl-Test-Spelling.spec
+++ b/perl-Test-Spelling.spec
@@ -1,19 +1,20 @@
 Name:           perl-Test-Spelling
 Version:        0.11
-Release:        6%{?dist}
+Release:        7%{?dist}
 Summary:        Check for spelling errors in POD files
 
 Group:          Development/Libraries
 License:        GPL+ or Artistic
 URL:            http://search.cpan.org/dist/Test-Spelling/
 Source0:        http://www.cpan.org/authors/id/I/IT/ITUB/Test-Spelling-%{version}.tar.gz
+Patch0:		perl-Test-Spelling-0.11-hunspell.patch
 BuildRoot:      %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
 
 BuildArch:      noarch
 BuildRequires:  perl(Pod::Spell) >= 1.01
 BuildRequires:  perl(Test::Pod)
 Requires:       perl(:MODULE_COMPAT_%(eval "`%{__perl} -V:version`"; echo $version))
-Requires:       aspell
+Requires:       hunspell
 
 %description
 "Test::Spelling" lets you check the spelling of a POD file, and report
@@ -54,6 +55,9 @@ rm -rf $RPM_BUILD_ROOT
 
 
 %changelog
+* Wed Jan 20 2010 Tom "spot" Callaway <tcallawa@redhat.com> - 0.11-7
+- use hunspell instead of aspell (bz 508643)
+
 * Fri Dec  4 2009 Stepan Kasal <skasal@redhat.com> - 0.11-6
 - rebuild against perl 5.10.1