Least hacky way to upgrade sage-scripts if they were modified locally?

[philt]

Hello,

As I explained in another thread I had to modify the sage-update
script to bypass a caching proxy and get the latest list&deps.
The problem is that now I see the sage_scripts-2.10.1 package was half-
installed:
If I compare with another sage server upgraded to 2.10.1, I've still
the old
sage.bin sage-banner sage-cachegrind sage-callgrind sage-doctest
sage-env sage-massif sage-omega sage-spkg sage-update sage-
valgrind

During the upgrade I was prompted with sth like a vi to fill a
changelog, where I simply quit vi.
Now if I try again, modifying sage-update and running "sage -f
sage_scripts-2.10.1"
it fails with:

ex/vi: Vi's standard input and output must be a terminal
transaction abort!
rollback completed
abort: edit failed: vi exited with status 1
pulling from /opt/sage-2.10/spkg/build/sage_scripts-2.10.1
searching for changes
no changes found
abort: there is nothing to merge, just use 'hg update' or look at 'hg
heads'

And if I try again "sage -f sage_scripts-2.10.1":
nothing changed
pulling from /opt/sage-2.10/spkg/build/sage_scripts-2.10.1
searching for changes
no changes found
abort: there is nothing to merge, just use 'hg update' or look at 'hg
heads'
nothing changed

Why now vi doesn't even want to prompt me I don't know but I don't
care.
I'd like to understand how I can force the install of the new
sage_scripts without
being annoyed with the versioning system.
BTW is it really the intention that the versioning system is used in a
production install?

Thanks for your help.
Phil