Bug 79497
Summary: | proxy settings change after applying | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Need Real Name <darkwing> |
Component: | gftp | Assignee: | Havoc Pennington <hp> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Mike McLean <mikem> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.3 | Keywords: | MoveUpstream |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2002-12-16 18:45:19 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 79600 |
Description
Need Real Name
2002-12-12 13:07:54 UTC
Still present in newer releases? No, the problem isn't present in newer releases. I have a standard redhat 7.3 box fully updated which I would like to keep standard redhat. I compiled gFTP 2.0.14 from the SRPM (from gftp.seul.org) on a redhat 7.3 test machine and the problem was solved. Changing to MoveUpstream keyword instead of GnomeUpstream tracking bug. sorry about the spam. Does this mean gftp 2.0.14 will be included in the updates (rhn) for redhat 7.3 or am I forced to upgrade to redhat 8.0 ? There will not be a gftp errata for 7.3 for this issue, no. You could just rebuild the 8.0 package on a 7.3 system probably. If you want to stick to Red Hat packages only, you typically need to track new releases fairly closely. (Note that the Advanced product line has an 18-24 month release cycle instead of the shorter retail box product cycle, and correspondingly has more backported fixes, for customers that need more stability. The retail box product is a latest-and-greatest product.) |