On Thu, 4 May 2006, seth vidal wrote: > On Thu, 2006-05-04 at 13:03 -0400, Tom Diehl wrote: > > Hi all, > > > > I am having a problem getting yum-2.6.1-0.fc5 working the way I want it to. > > > > With 2.4 and previous versions of yum I could so something like > > > > yum -c "http://yumconf.tntechs.com/yum.conf/yumconf.php?ver=5&fqdn=bullwinkle.tntechs.com&group=tntechs&dist=FC"; > > and yum would get a config file and do its thing. > > > > For some reason that same command line with 2.6 gives me > > > > Config Error: No such config file http://yumconf.tntechs.com/yumconf.php?ver=... > > > > If I do a wget http://yumconf.tntechs.com/yum... I get the proper config file. > > > > In addition the webserver logs show no attempts to get the config file. > > > > Has something changed wrt the -c option with yum-2.6 or am I making an obvious > > error?? > > > > So far I have not been able to find anything via google or the man pg. > > > > This is a freshly installed FC5 machine. Yum works normally when used with > > the config files in /etc > > pretty sure we broke that in 2.6. I'll look into it. Do you want me to file a bug? If so Red Hat or Duke's bugzilla?? > > on the plus side, however: > > > echo "include=http://your/path/to/yum.conf"; > /etc/yum.conf > > > same effect Thanks for the quick response and workaround but AFAICS it is not quite the same. In my case I have variables that get set at login to different values depending on the machine hostname and OS it is running. The idea is to be able to use the same config files in yum for all of the machines on my net. I currently build 4 versions of yum (FC4, FC5, el3, el4) but use the same support scripts across all 4 versions. I do things like the following at login time which sets up an alias with the correct options: export releasever=`perl -ne 'm/.* release (\S+)/; print $1;' \ < /etc/redhat-release` or export DIST=`perl -ane '$_ = $F[2]; s/release/FC/; s/Linux/RHL/; \ s/Enterprise/RHEL/; print;' </etc/redhat-release` Is there a better way?? Regards, Tom Diehl tdiehl@xxxxxxxxxxxx Spamtrap address mtd123@xxxxxxxxxxxx
