Hi, On Mon, Oct 16, 2006 at 06:17:35AM -0400, Debian user wrote: > It works!
Glad to hear it. > This is what I did. > > After you suggested it may be a local set up problem I googled for the > problem as it was mentioned on the pan users list that others had the > same trouble. As far as I can tell from that thread, only "pan user and I like it" (which I am assuming is you) appears to be having this issue? Or am I missing something? > > What I found was this: > http://comments.gmane.org/gmane.comp.gnome.apps.pan.user/7580 > > Scroll down in the blog to this: > > > Rhialto | 8 Oct 18:39 > Picon > > Re: Re: Upgrade to 0.113 in debian etch causes proxy connection to fail > From: Rhialto <[EMAIL PROTECTED]> > Subject: Re: Re: Upgrade to 0.113 in debian etch causes proxy connection > to fail > Newsgroups: gmane.comp.gnome.apps.pan.user > Date: 2006-10-08 16:39:46 GMT > > On Sun 08 Oct 2006 at 16:18:34 +0000, Duncan wrote: > > (If you are on amd64, 0.115 requires a patch to build. See > > http://bugzilla.gnome.org/show_bug.cgi?id=358654 and use the rollup patch I > > posted.) > > I have always wondered why gcc isn't a bit stricter in its type checking > and simply would catch such problems regardless of target architecture. > It would save a lot of portability problems. > > -Olaf > > Last night there was an update in etch with regards to gcc and I thought this > morning maybe after the upgrade to gcc it may have made a change and what the > heck it was worth a try. > > So I switched from the stable sarge release of Pan to 0.116 and I can connect > to the tunnel server now! What exactly did you do? Did you upgrade? The version in testing is currently 0.113-1 ? -- Søren O. "Oh, bother" said the Borg, "we've assimilated Pooh".
