Yes, I swear, I did it - yum 1.0.2 and 2.0.2 both in the same evening. This probably means they're broken in some incredibly dumb way :) 1.0.2 changes: - tolerant mode (-t) added - urlgrabber changes from mstenner - corrected zlib error traceback - corrected exactarch not being obeyed - handful of other fixes Tarball: http://linux.duke.edu/yum/download/1.0/yum-1.0.2.tar.gz srpm for rpm 4.0.4, python 2.2 machines: http://linux.duke.edu/yum/download/1.0/yum-1.0.2-1_80.src.rpm srpm for rpm 4.0.4, python 1.5.2 machines: http://linux.duke.edu/yum/download/1.0/yum-1.0.2-1_73.src.rpm rpm for rpm 4.0.4, python 1.5.2 machines: http://linux.duke.edu/yum/download/1.0/yum-1.0.2-1_73.noarch.rpm 2.0.2 changes: - security fix: unsigned packages in repositories with gpgcheck=1 will now cause an error to occur. - added kernelpkgnames and installonlypkgs setting to handle kernels for kernel updating and packages that should be installed not updated. - yum-arch -s for source-rpm handling now does the 'right thing' - fix numerous bugs since the 2.0.1 yum-arch brokenness - quiet down yum-arch -q more - exclude= in [main] now obeys $variables - clean up some error codes - doc clean ups tarball: http://linux.duke.edu/yum/download/2.0/yum-2.0.2.tar.gz srpm: http://linux.duke.edu/yum/download/2.0/yum-2.0.2-1.src.rpm rpm: http://linux.duke.edu/yum/download/2.0/yum-2.0.2-1.noarch.rpm Enjoy, let me know what breaks. -sv
