Il giorno ven, 02/05/2014 alle 15.53 +1000, Brian May ha scritto:
> [...]
>
> Alternatively, django-pipeline could be modified to conflict with
> python-pipeline. This would allow closing the grave bug report, but
> seems wrong.
>
Sorry if this is trivial to all of you... (but it's not mentione
On 16 May 2012 18:57, Dmitry Nezhevenko wrote:
> Holger suggests to ask here and thinks that it's better to remove orphaned
> pipeline package. Any ideas or suggestions?
>
I just noticed this thread from 2012 in debian-devel / #620067, because I
am in exactly the same situation.
There has been
Hi Jakub,
On Dienstag, 22. Mai 2012, Jakub Wilk wrote:
> * Dmitry Nezhevenko , 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
* Dmitry Nezhevenko , 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:
On Wed, May 16, 2012 at 06:04:27PM +0200, Bastian Blank wrote:
> On Wed, May 16, 2012 at 11:57:07AM +0300, Dmitry Nezhevenko wrote:
> > I'm trying to package a ReviewBoard package that depends on
> > django-pipeline module. Unfortunately there is already another package
> > named python-pipeline in
On Wed, May 16, 2012 at 11:57:07AM +0300, Dmitry Nezhevenko wrote:
> 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 pa
6 matches
Mail list logo
