Bug#620067: future of python-pipeline package
Hi Jakub, On Dienstag, 22. Mai 2012, Jakub Wilk wrote: * Dmitry Nezhevenko d...@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: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620067 I've asked it's upstream and author is going to rename it to something else: http://code.google.com/p/python-pipeline/issues/detail?id=1 but it seems this issue is stalled. apt-cache rdepends shows nothing for current python-pipeline. Also popcon shows only 48 installation without information about usage: http://qa.debian.org/popcon.php?package=python-pipeline 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? well, with the following request from yours, not much: 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. So the current situation is, that a package which is orphaned, has a low popcon score, no reverse depends and which the upstream maintainer is fine being removed from Debian, blocks another package, which is a depends for reviewboard (see reviewboard.org), which is a rather useful package, which now probably will not make it into wheezy because of this. I think this is a pretty sad situation. Frankly I wonder if it's reasonable to listen to your objections or not. You clearly stated you don't care about python-pipeline in Debian (sid), so I'm not sure you have any grounds blocking django-pipeline to enter. Comments, suggestions, ideas? cheers, Holger -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#620067: future of python-pipeline package
* Dmitry Nezhevenko d...@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: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620067 I've asked it's upstream and author is going to rename it to something else: http://code.google.com/p/python-pipeline/issues/detail?id=1 (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: http://qa.debian.org/popcon.php?package=python-pipeline 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 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#620067: future of python-pipeline package
Hi, 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: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620067 I've asked it's upstream and author is going to rename it to something else: http://code.google.com/p/python-pipeline/issues/detail?id=1 (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: http://qa.debian.org/popcon.php?package=python-pipeline 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. Any ideas or suggestions? -- WBR, Dmitry signature.asc Description: Digital signature
