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
I just spend about an hour wrestling with rt-crontool after an upgrade
from 4.0.6 to 4.0.10.
Sorry that this bug ate your time, and our apologies that it went
unfound until now.
I couldn’t find the place where to report this bug to be fixed, so I
hope someone from Bestpractical will see this.
The “BUGS” section in the README file addresses the usual reporting
path.
Hope this can be fixed in the source, so this will work in future releases.
Thanks for the patch. Do you have any objection to being marked as the
“author” of the commit in git, as “Lars Bräuer lb@mpexnet.de” ?
I couldn’t find the place where to report this bug to be fixed, so I
hope someone from Bestpractical will see this.
The “BUGS” section in the README file addresses the usual reporting
path.
There’s also a “Bug Reports” link in the navigation of
https://bestpractical.com/rt/, which points to
http://bestpractical.com/rt/issues.html.
Where did you look for bug reporting info? Maybe we can add it to the
places you didn’t find it.
I couldn’t find the place where to report this bug to be fixed, so I
hope someone from Bestpractical will see this.
The “BUGS” section in the README file addresses the usual reporting
path.
There’s also a “Bug Reports” link in the navigation of
https://bestpractical.com/rt/, which points to
http://bestpractical.com/rt/issues.html.
Where did you look for bug reporting info? Maybe we can add it to the
places you didn’t find it.
That’s really weird, it’s clearly there, I must have missed that somehow. I mainly looked in the
main navigation bar on top of the page.