Hold fire, it just happened on an unrelated site. I had updated Debian Testing this morning and it turns out a couple other things are hinky, so it's likely not to be your fault.