At 9:41 AM -0400 4/26/07, Patrick Doyle wrote: ... >So, if anybody would care to enlighten me, I would love to learn: > >1) Why would yum complain about an incomplete header after downloading >a full 1.4Mbyte RPM? Well, I'd look in the yum source for the message and work my way back from there, possibly running with a higher debug level or adding print statements. >2) If I managed to download the RPM manually, what would I look at to >see if the header was or was not, in fact, complete? If this is a HTTP problem, it may well be outside the RPM itself, in the HTTP tranasction. I suppose tcpdump could be of service, but mostly I'd prefer to work inside yum, as above. >3) If I managed to download an RPM with a complete header manually, >could I manually place it whereever yum would have exepcted to find >it? Where would that be? (This would make sense for small updates >behind the company firewall, but not so for the 300 package update I >went through last night). yum localinstall /path/to/package -- ____________________________________________________________________ TonyN.:' <mailto:tonynelson@xxxxxxxxxxxxxxxxx> ' <http://www.georgeanelson.com/>
