Bug#240697: acknowledged by developer
I perfectly understand your reasoning, but frakly not quite the conlusion.
> We do not want a vast quantity of users with
> "sarge" in their sources.list, who will then be left without security
> updates and a trivial upgrade path when sarge+1 is released.
Yes, that's me ;-) I'd like my machine to stick with sarge when it is released
as stable and not following testing anymore after that. (which will be
So I thought by specifying sarge now users will have the correct pointer now
and then, without requirering manual change.