4565f58a75
We are not forcing an update, in the sense that we make the update service run. Rather, we are ensuring that the next update wont return after doing nothing, with the message "repos already up to date". In this case, the repo metadata (and hence its etag) is the same, but we made changes in the client to handle the metadata correctly. Thus, we don't care that it hasn't changed, we want to update anyhow.