Actually, looks like this was just fixed in 1:0.167 (sudo apt-get update; sudo apt-get upgrade; to work around the issue until you can use update-manager again). Marking this as a dup of bug #1023474
Actually, looks like this was just fixed in 1:0.167 (sudo apt-get update; sudo apt-get upgrade; to work around the issue until you can use update-manager again). Marking this as a dup of bug #1023474