Bug 58119 - rpm ftp glob broken
rpm ftp glob broken
Status: CLOSED CURRENTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: rpm (Show other bugs)
7.2
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Jeff Johnson
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-01-09 00:07 EST by K Accardi
Modified: 2008-05-01 11:38 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-01-09 00:08:51 EST
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 K Accardi 2002-01-09 00:07:02 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.2.1) Gecko/20010901

Description of problem:
rpm-4.0.3-1.03 (supplied with 7.2)
doesn't find matching files using built-in ftp client.
Used to work with rpm-4.0.2-7x (Updated 7.0)



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


How reproducible:
Always

Steps to Reproduce:
1. rpm -Fvvh ftp://192.168.0.101:/pub/RedHat/Updates/7.2/wu*
D: logging into 192.168.0.101 as ftp, pw (username)
D: found 0 source and 0 binary packages 

2. Specifing wu-ftpd-2.6.1-20.i386.rpm works fine (the file exists on the ftp
server).

3. Globbing works if file is in current dir (local)
ie. rpm -Fvh ./wu*
	

Actual Results:  wu-ftpd-2.6.1-20 was not found on ftp server

Expected Results:  wu-ftpd package should have been updated

Additional info:

I can't believe this is the first report of this.  (Searches turned up empty). 
This will break thousands of scripts if it is real.
Comment 1 Jeff Johnson 2002-01-09 09:51:01 EST
Fixed in rpm-4.0.3 final, packages at ftp://ftp.rpm.org/pub/rpm/dist/rpm-4.0.x
Comment 2 K Accardi 2002-01-09 12:14:52 EST
Thanks, that works.  Um, shouldn't this be easier to find, like in Errata?  Or
are we sweeping it under the rug?

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