[Rt-commit] rt branch, 3.999-trunk, updated. 6e05b1a89eeea20468a2f5a054aeca8cd5975882

[sartak at bestpractical.com]

The branch, 3.999-trunk has been updated
       via  6e05b1a89eeea20468a2f5a054aeca8cd5975882 (commit)
      from  202d051d14c304ea1510353412522079c2ea5453 (commit)

Summary of changes:
 lib/RT/Action/ConfigSystem.pm |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

- Log -----------------------------------------------------------------
commit 6e05b1a89eeea20468a2f5a054aeca8cd5975882
Author: Shawn M Moore <sartak at bestpractical.com>
Date:   Mon Nov 23 22:31:00 2009 -0500

    Clearer error messages
    
        This was kind of special, I was getting the error:
            your configured GnuPG home directory does not exist:
            ''/home/sartak/.gnupg''
        but those double single-quotes looked like single double-quotes, so
        I didn't notice the problem - that it was checking the existence of
        the path '/home/sartak/.gnupg' quotes included. There's an error in
        config parsing too, apparently!

diff --git a/lib/RT/Action/ConfigSystem.pm b/lib/RT/Action/ConfigSystem.pm
index 932e702..bcf84f3 100644
--- a/lib/RT/Action/ConfigSystem.pm
+++ b/lib/RT/Action/ConfigSystem.pm
@@ -153,7 +153,7 @@ sub validate_gnupg {
             unless ( -d $homedir ) {
                 return $self->validation_error(
                     gnupg => _(
-"your configured GnuPG home directory does not exist: '%1'",
+'your configured GnuPG home directory does not exist: "%1"',
                         $homedir
                       )
                 );
@@ -161,7 +161,7 @@ sub validate_gnupg {
             unless ( -r $homedir ) {
                 return $self->validation_error(
                     gnupg => _(
-"couldn't read your configured GnuPG home directory: '%1'",
+'could not read your configured GnuPG home directory: "%1"',
                         $homedir
                       )
                 );

-----------------------------------------------------------------------