Bug#604934: Update on libproxy

2012-04-16 Thread Iain Lane
Hi there, I heard that the situation might have changed a bit and that we may be able to move forward on this package now? In the interim (since my initial mail offering to update in Debian), the package has been put into Ubuntu without major issues. I believe the situation is now stable enough t

Bug#604934:

2011-09-30 Thread Brian J. Murrell
On 11-09-30 06:29 AM, Josselin Mouette wrote: > > This “ideal of perfection” only requires someone to stick his fingers > out of his ass and actually do the work. Message #12 offered to do that and in Message 19 you told him not to do that. I sure got the impression from your tone that there was

Bug#604934:

2011-09-30 Thread Josselin Mouette
Le mercredi 28 septembre 2011 à 16:37 -0400, Brian J. Murrell a écrit : > And so, while we wait for perfection, instead of having functional we > accept completely broken? And we prefer completely broken to functional > simply because functional is not "perfect"? Seems to me that completely > br

Bug#604934:

2011-09-30 Thread Josselin Mouette
Le vendredi 30 septembre 2011 à 07:04 -0400, Brian J. Murrell a écrit : > On 11-09-30 06:29 AM, Josselin Mouette wrote: > > > > This “ideal of perfection” only requires someone to stick his fingers > > out of his ass and actually do the work. > > Message #12 offered to do that and in Message 19

Bug#604934:

2011-09-30 Thread Brian J. Murrell
On 11-09-30 07:06 AM, Josselin Mouette wrote: > > Message #12 offered to update libproxy to 0.4, which would make things > worse. Maybe you'd care to explain how. I am running 0.4.7 here on my Ubuntu system and it works a heck of a lot better than 0.3.1 did. Have you brought up your issues with

Bug#604934:

2011-09-28 Thread Brian J. Murrell
On 37-01--10 02:59 PM, wrote: > Le jeudi 22 septembre 2011 à 17:59 +0100, Iain Lane a écrit : >> I've been working recently on upgrading libproxy to 0.47, the latest >> upstream. > > Seriously, don’t do that. > > The 0.3 series was already broken, and the 0.4 one is even worse. They > reimplem

Bug#604934: libproxy: Please upgrade to 0.46

2011-09-22 Thread Josselin Mouette
Le jeudi 22 septembre 2011 à 17:59 +0100, Iain Lane a écrit : > I've been working recently on upgrading libproxy to 0.47, the latest > upstream. Seriously, don’t do that. The 0.3 series was already broken, and the 0.4 one is even worse. They reimplemented again a non-standards-compliant HTTP pa

Bug#604934: libproxy: Please upgrade to 0.46

2011-09-22 Thread Iain Lane
retitle 604394 Upgrade to 0.4 series thanks On Thu, Nov 25, 2010 at 04:39:32PM +0100, Artur Rona wrote: > Package: libproxy > Version: 0.3.1-2 > > Please upgrade libproxy to latest upstream version (ATM is 0.46). > Current version is out-of-dated. I've been working recently on upgrading libproxy

Bug#604934: libproxy: Please upgrade to 0.46

2010-11-25 Thread Artur Rona
Package: libproxy Version: 0.3.1-2 Please upgrade libproxy to latest upstream version (ATM is 0.46). Current version is out-of-dated. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org