Hi,

I just spend about an hour wrestling with rt-crontool after an upgrade from 
4.0.6 to 4.0.10.

I couldn't find the place where to report this bug to be fixed, so I hope 
someone from Bestpractical
will see this.

After the upgrade the "new" rt-crontool from 4.0.10 wouldn't work anymore:

# /opt/rt4/bin/rt-crontool
[Thu Feb 14 18:54:44 2013] [critical]: Undefined subroutine &main::loc called at
/opt/rt4/bin/rt-crontool line 312. (/opt/rt4/bin/../lib/RT.pm:356)
Undefined subroutine &main::loc called at /opt/rt4/bin/rt-crontool line 312.


I finally found out, that loc was missing in the RT::Interface::CLI call.

This fixed everything:

--------------------------------------
--- /usr/src/rt-4.0.10/bin/rt-crontool  2013-02-14 18:26:41.000000000 +0100
+++ /opt/rt/bin/rt-crontool     2013-02-14 20:04:07.000000000 +0100
@@ -79,7 +79,7 @@

 use Getopt::Long;

-use RT::Interface::CLI qw(CleanEnv GetCurrentUser GetMessageContent);
+use RT::Interface::CLI qw(loc CleanEnv GetCurrentUser GetMessageContent);

 #Clean out all the nasties from the environment
 CleanEnv();
--------------------------------------

Hope this can be fixed in the source, so this will work in future releases.

Best regards,

Lars




-- 
RT training in Amsterdam, March 20-21: 
http://bestpractical.com/services/training.html

Help improve RT by taking our user survey: 
https://www.surveymonkey.com/s/N23JW9T

Reply via email to