After seeing the recent commit for libbluray about hosting the source, I was curious to see if this was a wget bug. I got a hit when doing a web search (1). I'm not certian if it's a bug or not, but the info from the link bore out: curl has no problems with this source address; and, if the source address is changed from ftp://ftp... to http://ftp... , then wget fetches the tarball just fine. 1) http://comments.gmane.org/gmane.linux.slackware.slackbuilds.user/13108 Cheers, John
Hey, On 31/03/16 14:36, John Vogel wrote:
After seeing the recent commit for libbluray about hosting the source, I was curious to see if this was a wget bug. I got a hit when doing a web search (1). I'm not certian if it's a bug or not, but the info from the link bore out: curl has no problems with this source address; and, if the source address is changed from ftp://ftp... to http://ftp... , then wget fetches the tarball just fine.
1) http://comments.gmane.org/gmane.linux.slackware.slackbuilds.user/13108
it worked without passive ftp mode: wget --no-passive-ftp ftp://ftp.videolan.org/pub/videolan/libbluray/0.9.2/libbluray-0.9.2.tar.bz2 You could setup PKGMK_WGET_OPTS="--no-passive-ftp" in /etc/pkgmk.conf Regards, -- Jose V Beneyto | sepen@crux.nu
On 2016-03-31 22:11, Jose Vicente Beneyto wrote:
Hey,
On 31/03/16 14:36, John Vogel wrote:
After seeing the recent commit for libbluray about hosting the source, I was curious to see if this was a wget bug. I got a hit when doing a web search (1). I'm not certian if it's a bug or not, but the info from the link bore out: curl has no problems with this source address; and, if the source address is changed from ftp://ftp... to http://ftp... , then wget fetches the tarball just fine.
1) http://comments.gmane.org/gmane.linux.slackware.slackbuilds.user/13108
it worked without passive ftp mode:
wget --no-passive-ftp ftp://ftp.videolan.org/pub/videolan/libbluray/0.9.2/libbluray-0.9.2.tar.bz2
You could setup PKGMK_WGET_OPTS="--no-passive-ftp" in /etc/pkgmk.conf
Regards,
It looks like this FTP server responds to PASV with 127.0.0.1 instead of real IP address, its probably a configuration error. Disabling passive mode might work if you are directly connected to the Internet or your firewall is good enough. It looks like curl uses EPSV instead of PASV, so it works. Instead of disabling passive mode, I would advise using curl in pkgmk.conf: PKGMK_DOWNLOAD_PROG="curl" Regards, Alan
On Thu, 31 Mar 2016 22:30:14 +0900 Alan Mizrahi <alan+crux@mizrahi.com.ve> wrote:
On 2016-03-31 22:11, Jose Vicente Beneyto wrote:
Hey,
On 31/03/16 14:36, John Vogel wrote:
After seeing the recent commit for libbluray about hosting the source, I was curious to see if this was a wget bug. I got a hit when doing a web search (1). I'm not certian if it's a bug or not, but the info from the link bore out: curl has no problems with this source address; and, if the source address is changed from ftp://ftp... to http://ftp... , then wget fetches the tarball just fine.
1) http://comments.gmane.org/gmane.linux.slackware.slackbuilds.user/13108
it worked without passive ftp mode:
wget --no-passive-ftp ftp://ftp.videolan.org/pub/videolan/libbluray/0.9.2/libbluray-0.9.2.tar.bz2
You could setup PKGMK_WGET_OPTS="--no-passive-ftp" in /etc/pkgmk.conf
Regards,
It looks like this FTP server responds to PASV with 127.0.0.1 instead of real IP address, its probably a configuration error.
Disabling passive mode might work if you are directly connected to the Internet or your firewall is good enough.
It looks like curl uses EPSV instead of PASV, so it works.
Instead of disabling passive mode, I would advise using curl in pkgmk.conf: PKGMK_DOWNLOAD_PROG="curl"
Regards,
Alan
I wish I had caught this before my most recent post. Using curl is what I intend to do as it seems least likely to cause issues later on. Cheers, John
On Thu, 31 Mar 2016 15:11:44 +0200 Jose Vicente Beneyto <sepen@crux-arm.nu> wrote:
Hey,
On 31/03/16 14:36, John Vogel wrote:
After seeing the recent commit for libbluray about hosting the source, I was curious to see if this was a wget bug. I got a hit when doing a web search (1). I'm not certian if it's a bug or not, but the info from the link bore out: curl has no problems with this source address; and, if the source address is changed from ftp://ftp... to http://ftp... , then wget fetches the tarball just fine.
1) http://comments.gmane.org/gmane.linux.slackware.slackbuilds.user/13108
it worked without passive ftp mode:
wget --no-passive-ftp ftp://ftp.videolan.org/pub/videolan/libbluray/0.9.2/libbluray-0.9.2.tar.bz2
You could setup PKGMK_WGET_OPTS="--no-passive-ftp" in /etc/pkgmk.conf
Regards,
-- Jose V Beneyto | sepen@crux.nu
This looks good at first glance. But I wonder if this opens up a new issue with firewalls (either client or server or both) blocking the ftp data port. If that is the case, might setting PKGMK_WGET_OPTS globally like that be a recipe for headaches later? Cheers, John
participants (3)
-
Alan Mizrahi -
John Vogel -
Jose Vicente Beneyto