Hide Forgot
Description of problem: A recently released bug fix version of lftp no longer works when used for mirroring repositories as part of the mrepo program. Version-Release number of selected component (if applicable): 4.0.9-6.el6_8.2 exhibits has the problem. Downgrading to 4.0.9-6.el6 (previous version) fixes it. How reproducible: The following will show the problem, lftp -c 'mirror -c -P -v -v -v -e -I *.rpm -X "/headers/" -X "/repodata/" -X "*.src.rpm" -X "/SRPMS/" -X "*-debuginfo-*.rpm" -X "/debug/" http://spacewalk.redhat.com/yum/2.3-client/RHEL/5/i386/ /tmp/test' Some of the output from above:- $ lftp -c 'mirror -c -P -v -v -v -e -I *.rpm -X "/headers/" -X "/repodata/" -X "*.src.rpm" -X "/SRPMS/" -X "*-debuginfo-*.rpm" -X "/debug/" http://spacewalk.redhat.com/yum/2.3-client/RHEL/5/i386/ /tmp/test' ---- Resolving host address... ---- 1 address found: 209.132.183.81 ---- Connecting to spacewalk.redhat.com (209.132.183.81) port 80 <--- HTTP/1.1 200 OK <--- Date: Wed, 31 Aug 2016 15:31:36 GMT <--- Server: Apache <--- Connection: close <--- Content-Type: text/html;charset=ISO-8859-1 <--- does not ---- Connecting to spacewalk.redhat.com (209.132.183.81) port 80 <--- HTTP/1.1 200 OK <--- Date: Wed, 31 Aug 2016 15:31:36 GMT <--- Server: Apache <--- Content-Length: 6864 <--- Connection: close <--- Content-Type: text/html;charset=ISO-8859-1 .. .. .. ---- Connecting to spacewalk.redhat.com (209.132.183.81) port 80 <--- HTTP/1.1 200 OK <--- Date: Wed, 31 Aug 2016 15:37:06 GMT <--- Server: Apache <--- Content-Length: 2572 <--- Connection: close <--- Content-Type: text/html;charset=ISO-8859-1 <--- ---- Connecting to spacewalk.redhat.com (209.132.183.81) port 80 repodata: Getting files information (100%) [Waiting for response...] Hangs at this point. Actual results: lftp command does not complete. does not Expected results: lftp command should complete. Additional info: I have tested this on a virgin vagrant centos 6.8 VM and a number of VM's running Centos 6 with the same result. Downgrading makes the lftp command work again.
*** This bug has been marked as a duplicate of bug 1228484 ***