Bug 50955

Summary:	up2date --configure doesn't work well with old style config files
Product:	[Retired] Red Hat Linux	Reporter:	Peter Bowen <pzbowen+rhbeta>
Component:	up2date	Assignee:	Adrian Likins <alikins>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Jay Turner <jturner>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.3	CC:	srevivo
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2001-08-11 00:18:52 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:

Description Peter Bowen 2001-08-05 17:07:47 UTC

In up2date v1.x config files, pkgProxy was set to be the package server if
no proxy was used.  It defaulted to priority.redhat.com.  If this style
config file is used with a current up2date it won't work as the XML-RPC
methods for modern up2date clients are not on priority.redhat.com.

The natural solution is to run up2date --configure and have it write a new
config file.  This works fine, execpt for that it puts priority.redhat.com
in the proxy section of the new config file, preventing it from working
properly.

I think that the proper solution is to leave proxy server blank in the new
configfile if pkgProxy == pgkServer in the original config file

Comment 1 Cristian Gafton 2001-08-10 20:57:05 UTC

Assigned to the owner of component

Comment 2 Adrian Likins 2001-08-10 22:21:12 UTC

Hmmm. pkgProxy is set to priority?  That seems odd to me.

Need to dig into it a bit more. I'll take a look.

Comment 3 Peter Bowen 2001-08-11 00:18:48 UTC

Switching to Beta Program

Comment 4 Adrian Likins 2002-03-26 23:07:32 UTC

should be fixed in current version, the name of the proxy
config option changed along time ago