It usually succeeds when I run it again. Is there a way to avoid this?
This sounds very similar to an issue people ran into on travis, which I believe was tracked down to travis putting a cache in between themselves and apt.postgresql.org, which broke the order of downloads. Any chance you also have a cache sitting there somewhere?
//Magnus
Thanks.
I should have added I was seeing this in travis. I tought it was a general issue.