The problem suddenly went away, can not reproduce, too. Some transitional state of the repository on the package update?