Re: how to implement a renamed package
> Just out of curiosity: what happens if an unrelated package with the old,
> obsoleted name is introduced into the archive?
> In the case in hand, upstream renamed puzzle -> tree-puzzle precisely because
> there exists something with the name puzzle. If that other puzzle got put
> into debian, there could be great confusion.
> Has this ever happened?
One way to avoid this situation is to use Conflicts: oldpackage (<= version)
where version is the last version of oldpackage. Of course, this would need to
take into account possible updates to the old package (security updates,
critical bugfixes in stable), so maybe leaving some padding in the version
number might be appropriate (a few Debian revisions).