On Sat, 11 Jun 2011 15:57:42 +0100
Nigel Taylor <njtay...@asterisk.demon.co.uk> wrote:
> On 06/11/11 13:49, Remi Pointel wrote:
> > On Sat, 11 Jun 2011 14:15:22 +0200
> > viq <v...@viq.ath.cx> wrote:
> >> It appears there is exactly same issue with graphics/py-Imaging
> >
> > Yes, this is the diff for py-Imaging.
> >
> > I tested to update py-Imaging-1.1.7p3-python2.6 to
> > py-Imaging-1.1.7p4-python2.7 and it's ok.
> > (FYI, I also tested with py-mxDateTime).
> >
> > % sudo pkg_add -uiv
> > Update candidates: py-Imaging-1.1.7p3-python2.6 ->
> > py-Imaging-1.1.7p4-python2.7 (ok)
> > py-Imaging-1.1.7p3-python2.6->py-Imaging-1.1.7p4-python2.7: ok
> >
> > Thanks for the report.
> > Are you ok ?
> >
> > Thanks,
> >
> > Remi.
> Hi,
>
> I did a locate PFRAG.python2.6 and found databases/py-ldap and
> databases/py-psycopg have same problem. Attached patch, bumped version,
> not sure about ${MODPY_WANTLIB} so haven't included in the changes.
>
> Regards
>
> Nigel Taylor
Thanks a lot, I commited it (with few tweaks by me).
Cheers,
Remi.
