duplicity on EPEL4

[Jerome Benoit]

Hello,

Is there any plan to really make it work ?

The version shipped in EPEL 4 require subprocess (which is not present
in python 2.3).

I've already filled a bug report in bugzilla.

How other python package in EPEL 4 handle subprocess requirement ? 
So I can jump on my bug and fix the .spec file.

Cheers.

[Toshio Kuratomi]

On Tue, Oct 18, 2011 at 10:46:03PM +0200, Jérôme Benoit wrote:
> Hello,
>
> Is there any plan to really make it work ?
>
> The version shipped in EPEL 4 require subprocess (which is not present
> in python 2.3).
>
> I've already filled a bug report in bugzilla.
>
> How other python package in EPEL 4 handle subprocess requirement ? 
> So I can jump on my bug and fix the .spec file.

You can either make do without duplicity on EPEL4, change the code to not
use subprocess, or change the code to use a replacement -- for instance
pyhton-kitchen provides a compat subprocess module.

Something like:
try:
    import subprocess
except ImportError:
    from kitchen.pycompat27 import subprocess

will likely work for you.

-Toshio

[Jerome Benoit]

On Tue, 18 Oct 2011 15:04:26 -0700
Toshio Kuratomi  wrote:
> > How other python package in EPEL 4 handle subprocess requirement ? 
> > So I can jump on my bug and fix the .spec file.
>
> You can either make do without duplicity on EPEL4

Well ... is EPEL policy include : We can ship borken package, user just
have to not use them.

I don't think so.
> change the code to
> not use subprocess,

Not a good idea.
> or change the code to use a replacement -- for
> instance pyhton-kitchen provides a compat subprocess module.
>
> Something like:
> try:
>     import subprocess
> except ImportError:
>     from kitchen.pycompat27 import subprocess
>
> will likely work for you.

Sound great, a conditional patch to apply in the .spec file. 
Will work on it ASAP.

Thks.

[Toshio Kuratomi]

On Wed, Oct 19, 2011 at 01:42:47AM +0200, Jérôme Benoit wrote:
> On Tue, 18 Oct 2011 15:04:26 -0700
> Toshio Kuratomi  wrote:
> > You can either make do without duplicity on EPEL4
>
> Well ... is EPEL policy include : We can ship borken package, user just
> have to not use them.
>
> I don't think so.

<nod>  I meant -- we'd wnat to remove duplicity from the EPEL4 repository.
> > try:
> >     import subprocess
> > except ImportError:
> >     from kitchen.pycompat27 import subprocess
> >
> > will likely work for you.
>
> Sound great, a conditional patch to apply in the .spec file. 
> Will work on it ASAP.

Excellent.  I'm also kitchen upstream if you have problems with it.

-Toshio

[Jerome Benoit]

On Tue, 18 Oct 2011 18:04:39 -0700
Toshio Kuratomi  wrote:
> Excellent.  I'm also kitchen upstream if you have problems with it.

Can someone please commit my patches on
https://bugzilla.redhat.com/show_bug.cgi?id=745535

and push the fixed build of duplicity RPM on EPEL 4 ASAP ?

Thks.

Sponsorship Wanted (was, Re: duplicity on EPEL4)

[Jerome Benoit]

On Tue, 25 Oct 2011 21:54:09 +0200
Jérôme Benoit  wrote:
> Can someone please commit my patches on
> https://bugzilla.redhat.com/show_bug.cgi?id=745535

Who would like to sponsor me to become a package maintainer ?

You probably do not me as much, I work on various different FOSS
projects (coregrenouille, OCaml patches, GODI patches, etc.). My
implication in Fedora will mostly be in EPEL because I ran a lots of
RHEL at work.

To begin with, I will like to co-maintain duplicity and curlftpfs (I've
asked to the curlftpfs maintainer already).

Who want to mentor me ?

Regards,