Bug 57041 - RPM fails on servers which do not recognize the SIZE command
RPM fails on servers which do not recognize the SIZE command
Status: CLOSED WONTFIX
Product: Red Hat Linux
Classification: Retired
Component: rpm (Show other bugs)
7.2
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Paul Nasrat
Mike McLean
:
: 50887 (view as bug list)
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-12-03 13:31 EST by Frank Hirtz
Modified: 2007-04-18 12:38 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-06-07 16:09:55 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Frank Hirtz 2001-12-03 13:31:56 EST
Description of Problem:
RPM fails on servers which do not recognize the SIZE command.

The SIZE command is not in the RFC for FTP and is not included in the
solaris ftp server. RPM fails when it tries to install over the ftp link.
Nortel would like this corrected as they are using solaris extensively.

See bug#'s 50887 and 17346 for more detailed information.


Version-Release number of selected component (if applicable):


How Reproducible:


Steps to Reproduce:
1. 
2. 
3. 

Actual Results:


Expected Results:


Additional Information:
Comment 1 Jeff Johnson 2001-12-09 12:58:44 EST
I need some help prioritizing this bug, basically whether rpm-4.0.4 or rpm-4.1
is gonna be the location of the fix. Frank has been very patient so far :-)

The issue is the use of a linux only ftpd SIZE command that
rpm uses to synthesize a Content-Length: field so that
the FTP command channel does not have to be repeatedly
torn down and reopened. If/when I attempt a fix, I will mark
the FTP command channel that has a failing SIZE command
as necessary to be reopened repeatedly.
Comment 2 Bill Nottingham 2001-12-09 23:40:50 EST
If a customer wants it, it will probably need to be backported to
whatever-they're -running, so it probably is best to do it against 4.0.3/4.0.4
first...
Comment 3 Jeff Johnson 2001-12-10 09:59:19 EST
*** Bug 50887 has been marked as a duplicate of this bug. ***
Comment 4 Paul Nasrat 2005-06-07 16:09:55 EDT
Use of a depsolver such as up2date or yum encouraged for network repos.

Note You need to log in before you can comment on or make changes to this bug.