Date: Mon, 8 Dec 2014 16:19:01 +0700 From: Olivier Nicole <olivier.nicole@cs.ait.ac.th> To: "O. Hartmann" <ohartman@zedat.fu-berlin.de> Cc: "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org>, freebsd-ports@freebsd.org Subject: Re: Difference between fetch(1) and firefox http-access Message-ID: <CA%2Bg%2BBvitiYVzhT1gKcXW8JQnMxZw1HhtXwubUYGh4x0V0b8YFQ@mail.gmail.com> In-Reply-To: <20141208081345.6960d593@prometheus> References: <20141208081345.6960d593@prometheus>
next in thread | previous in thread | raw e-mail | index | archive | help
Olivier, > Running CURRENT (FreeBSD 11.0-CURRENT #2 r275512: Fri Dec 5 16:00:34 > CET 2014 amd64), I ran into some kind of obscurity I can not fathom. > > Updating ports fails since a couple of days by now (I do updates on > a daily basis). fetch isn't capable of reaching any(!) server it tries > to download sourcecode tarballs from (neither via ports ftp, http, > https). > > When manually copied the sources of the tarball to Firefox' URL > requester, I can luckily download the sources to whatever destination I > like and I have to copy them to the /usr/ports/distfiles[/blabla] > destination manually. Did you try to fetch the source manually: fetch URL... Just to confirm/infirm the problem with fetch. Do you have some HTTP_PROXY env variable set? Olivier > > As I understood "fetch" it establishes a simple ftp, http or https > connection, as Firefox does. But it seems that something is going > terribly wrong. > > It would be nice if someone could push me towards a hint or something > to solve the problem. I hope it's not a serious bug but a simple error > in the configuration. > > Thanks in advance, > Oliver > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2Bg%2BBvitiYVzhT1gKcXW8JQnMxZw1HhtXwubUYGh4x0V0b8YFQ>