

Re: future of python-pipeline package

* Dmitry Nezhevenko <dion@dion.org.ua>, 2012-05-16, 11:57:
I'm trying to package a ReviewBoard package that depends on django-pipeline module. Unfortunately there is already another package named python-pipeline in debian that uses same python module name (pipeline). This another package is orphaned for a year:


I've asked it's upstream and author is going to rename it to something else:


(btw I've also asked upstream of django-pipeline but without any luck for now)

apt-cache rdepends shows nothing for current python-pipeline. Also popcon shows only 48 installation without information about usage:


So I'm asking how to deal with it? django-pipeline looks like more popular according to project github page and bugtracker.

Holger suggests to ask here and thinks that it's better to remove orphaned pipeline package.

How would the removal help?

With my upstream and ex-maintainer hats on, I'm fine with removing python-pipeline from unstable. However, I object to another package taking over the module name.

Jakub Wilk

Reply to: