I just experienced this issue on 10.10... Sadly, this very serious bug is still very much alive. I hope to see the priority raised. I have retained the corrupt package cache files if any further information is required.
I just experienced this issue on 10.10... Sadly, this very serious bug is still very much alive. I hope to see the priority raised. I have retained the corrupt package cache files if any further information is required.