On Fri, 6 Sep 2002, Connie Sieh wrote: > As long as we are talking about the first pass to get the headers. I have > seen it just stop alot. I installed yum on my system at home. It has a > cable modem. Yum would download a few headers and then stop. I would > restart it and it would get a few more. I resorted to getting them via > ncftp. > > I was thinking that we might have to package up the headers as a rpm and > install it when we install yum. This will thus seed the cache and yum > will then only have to get new headers. Absolutely fabulous idea -- I was thinking something similar but didn't think of it being a "pre" rpm, just a tarball. I also run installs from home over DSL and the system I borked was a DSL install. It is a heck of a lot easier (and faster) to install just one big file than a lot of little files and just do the updates. The rpm (or tarball) could probably be generated at the same time as the headers themselves, by the same script. rgb > > > -Connie Sieh > Fermi National Accelerator Laboratory > > On Fri, 6 Sep 2002, Troy Dawson wrote: > > > Robert G. Brown wrote: > > > On 6 Sep 2002, seth vidal wrote: > > > > > > > > >>of course it does. exception handling is easy - but you have to grab the > > >>exception first - I hadn't encountered it much/at all - I'd still like > > >>to more gracefully handle a broken header. > > > > > > > > > What you need is to put salt on the tail of a broken header or two; then > > > you could play with it until you could handle at least them. > > > > > > Alas I through my broken headers away (and I'd guess Troy did too). I > > > therefore have no idea why they were broken in the first place or where > > > they were broken. Next time I get an error like this, though, I'll try > > > to send you the contents of the header directory to debug with. > > > > > > I'd debug it myself, except that (as previously noted) I will learn > > > python only if somebody ties me to a table and threatens me with hot > > > irons. Too many programming languages... > > > > > > Historically this (hot irons) happens every year or two (seems like) so > > > I'll probably be programming in it regularly by mid-2003...;-) > > > > > > rgb > > > > > > Robert G. Brown http://www.phy.duke.edu/~rgb/ > > > Duke University Dept. of Physics, Box 90305 > > > Durham, N.C. 27708-0305 > > > Phone: 1-919-660-2567 Fax: 919-660-2525 email:rgb@xxxxxxxxxxxx > > > > > > > > > > > Now that I know what the problem is, I'm pretty sure I know how it happened. > > The user was running off a wireless card, and I was doing a yum update for the > > first time. It was busy pulling down the header files when it just stopped, I > > believe because of a bad network connection or something. I then killed yum, > > started it again, and away it went. But evidently that header that it got > > stuck on much have been mangled. > > So maybe if you pull the network halfway through a header update, we can get a > > nice mangled header. > > > > Troy > > > > -- > > __________________________________________________ > > Troy Dawson dawson@xxxxxxxx (630)840-6468 > > Fermilab ComputingDivision/OSS CSI Group > > __________________________________________________ > > > > _______________________________________________ > > Yum mailing list > > Yum@xxxxxxxxxxxxxxxxxxxx > > https://lists.dulug.duke.edu/mailman/listinfo/yum > > > > _______________________________________________ > Yum mailing list > Yum@xxxxxxxxxxxxxxxxxxxx > https://lists.dulug.duke.edu/mailman/listinfo/yum > -- Robert G. Brown http://www.phy.duke.edu/~rgb/ Duke University Dept. of Physics, Box 90305 Durham, N.C. 27708-0305 Phone: 1-919-660-2567 Fax: 919-660-2525 email:rgb@xxxxxxxxxxxx
