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 <a.badger@gmail.com> 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
_______________________________________________
epel-devel-list mailing list
epel-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/epel-devel-list

On Tue, 18 Oct 2011 18:04:39 -0700
Toshio Kuratomi <a.badger@gmail.com> 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.

--
Jérôme Benoit aka fraggle
La Météo du Net - http://grenouille.com
OpenPGP Key ID : 9FE9161D
Key fingerprint : 9CA4 0249 AF57 A35B 34B3 AC15 FAA0 CB50 9FE9 161D
_______________________________________________
epel-devel-list mailing list
epel-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/epel-devel-list