[Rt-commit] rt branch, 4.2-trunk, updated. rt-4.1.23-9-g0d32129

[Kevin Falcone]

The branch, 4.2-trunk has been updated
       via  0d32129bfc4357d96e81732a5c56bef06d4ecf82 (commit)
      from  1e55469b07891cff0cc5b703f2376b4aea4dad47 (commit)

Summary of changes:
 lib/RT/Config.pm | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

- Log -----------------------------------------------------------------
commit 0d32129bfc4357d96e81732a5c56bef06d4ecf82
Author: Kevin Falcone <falcone at bestpractical.com>
Date:   Thu Sep 5 11:30:40 2013 -0400

    Bump up GnuPG's warning about the homedir
    
    Previously, we would Enable GnuPG if you had gpg in your path and then
    spit out a debug warning on startup because you don't have
    /opt/rt4/var/data/gnupg.
    
    We now only Enable => 1 GnuPG if you --enable-gpg or if you do it
    manually.  As such, you're expecting GnuPG to stay enabled and any
    warnings about why RT is disabling it should come at a higher log level.
    
    S/MIME uses info for this message, so I went for parity.

diff --git a/lib/RT/Config.pm b/lib/RT/Config.pm
index a99ba24..7ea5433 100644
--- a/lib/RT/Config.pm
+++ b/lib/RT/Config.pm
@@ -722,7 +722,7 @@ our %META;
                 $gpgopts->{homedir} = File::Spec->catfile( $RT::BasePath, $gpgopts->{homedir} );
             }
             unless (-d $gpgopts->{homedir}  && -r _ ) { # no homedir, no gpg
-                $RT::Logger->debug(
+                $RT::Logger->info(
                     "RT's GnuPG libraries couldn't successfully read your".
                     " configured GnuPG home directory (".$gpgopts->{homedir}
                     ."). GnuPG support has been disabled");

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