Debugging revealed that this only happens when you answer "yes" to "Add another
apt source?", which is not the default. I think it's a bug but not a showstopper
for breezy (particularly as it looks very hairy to fix); it will go away in
dapper anyway since by that point we'll be using a totally rewritten apt-setup.