This sounds like a transient error in the archive (this sometimes happens when some updates are already available, but other are still being build and not yet published).
Does it work now? If so, I would like to mark it a wishlist bug to improve the error message.
Thanks for your bugreport.
This sounds like a transient error in the archive (this sometimes happens when some updates are already available, but other are still being build and not yet published).
Does it work now? If so, I would like to mark it a wishlist bug to improve the error message.