Re: python-SocksiPy (was: Re: non-responsive)

2012-07-25 Thread Fl
On Wed, 18 Jul 2012 18:29:03 +0100 "Richard W.M. Jones" wrote: > On Mon, Jul 16, 2012 at 09:12:42PM +0400, Fl@sh wrote: > > https://bugzilla.redhat.com/show_bug.cgi?id=831743 > > > > Maybe anyone knows how to contact the maintainer? (His mail > > is not answer.) > there is still no answer --

Re: python-SocksiPy

2012-07-19 Thread Jóhann B. Guðmundsson
On 07/18/2012 05:29 PM, Richard W.M. Jones wrote: On Mon, Jul 16, 2012 at 09:12:42PM +0400, Fl@sh wrote: https://bugzilla.redhat.com/show_bug.cgi?id=831743 Maybe anyone knows how to contact the maintainer? (His mail is not answer.) To save everyone the trouble of opening this bug, the summary

Re: python-SocksiPy (was: Re: non-responsive)

2012-07-19 Thread Fl
> That's still no excuse for not submitting a more comprehensible bug report > and a more readable unified diff (man diff --> diff -u …). > OK, I will correct it. -- Fl@sh -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel

Re: python-SocksiPy (was: Re: non-responsive)

2012-07-19 Thread Michael Schwendt
On Wed, 18 Jul 2012 22:09:27 +0400, Fl@sh wrote: > > The bug report is almost completely incomprehensible. I'm not > > surprised the maintainer is ignoring it. > > > > Rich. > > > Not too difficult for maintainer to see these lines and see > the difference in exactly four brackets ;) > This ma

Re: python-SocksiPy (was: Re: non-responsive)

2012-07-18 Thread Fl
> The bug report is almost completely incomprehensible. I'm not > surprised the maintainer is ignoring it. > > Rich. > Not too difficult for maintainer to see these lines and see the difference in exactly four brackets ;) This maintainer does not respond, and may be not active for about a year

Re: python-SocksiPy (was: Re: non-responsive)

2012-07-18 Thread Fl
On Wed, 18 Jul 2012 18:29:03 +0100 "Richard W.M. Jones" wrote: > On Mon, Jul 16, 2012 at 09:12:42PM +0400, Fl@sh wrote: > > https://bugzilla.redhat.com/show_bug.cgi?id=831743 > > > > Maybe anyone knows how to contact the maintainer? (His mail > > is not answer.) > > To save everyone the trouble