Am I really the only one having this problem?

no.


it wasn't fixed at _all_ when i said it was originally, due to a failed
"chdir" which then caused the `release' update to run in the `current'
tree.  rob windsor kicked off another update a few hours ago and this
completed shortly afterwards.


i have verified with a small sup that things are back to normal.


again, i'm extremely sorry for any inconvience caused :-(