David, the issue is marked as resolved since the problem has occurred in the past and it was resolved then. I assume that the problem has occurred again. So, you might want to re-open the issue. In case, you don't have rights to do that, I can do it for you.
David, same repo and computer do not matter in case of this bug. It is on the server side and possibly for the "user" that is trying to unpack the changeset on the server. So, please try this over https.