RPMDRAKE will behave as you described if it is unable to connect or log into the remote URPMI repositories.
It will usually sit there and it may time out.
When it does, it MAY seem to skip the file, which will now be incomplete.
Subsequent attempts at installation will fail until you both, exit from urpmi/rpmdrake and fix the source problem.
The repositories can be overloaded, rejecting logins, offline, etc.
Often if they fail, merely try again later and things will work.
However at worst case, "update" your URPMI sources and see which one is failing, then delete it and add it back from another location.