* Sandro Tosi <mo...@debian.org>, 2010-05-29, 09:51:
Shouldn't this be closed? http://packages.qa.debian.org/uncertaintiesWell, they seem 2 different projects, note the (missing 'i'): python-uncertainities python-uncertainties I've added in CC Jakub, so that he can give a look at the differencebetween the 2 projects
The differences are: - My package doesn't have a typo in its name. ;) - The orphaned package is dead upstream.- My package provides all the functionality of the orphaned one and way more.
- They have incompatible API.
and decide if #553076 can be reassigned to ftp.debian.org for RM
I don't feel entitled to make such a decision. Anyway, a more conservative approach might be:1. Make uncertainties build a compatibility binary package python-uncertainities, which would:
- warn that this package is deprecated; - use python-uncertainties under the hood. 2. Remove source package python-uncertainities. 3. Drop binary package python-uncertainities after release of squeeze. -- Jakub Wilk
signature.asc
Description: Digital signature