hi manoj
you can use pry to debug such issues[1]. Issues you are facing are
trivial, and more to do with ruby than to do with chef. In the current
example, if i was you I would install pry in the chef gemset, require it in
the recipe and then invoke binding.pry right before the notifies call. Once
im dropped inside the pry shell, print the value of base_name (or whatever
variable/method call thats causing trouble). This will help you much
faster, and beyond chef.
also, next time you seek help, send the trace/ debug log etc. Dont use the
mailing list as an REPL