Well, as it turns out my botched KDE (and other updates) was due to that rpmdrake bug (Bugzilla 9411) ... packages were downloading but not installing, and remaining in /var/cache/urpmi/rpms.
The bad news is that it threw my system into a state of disarray for awhile (particularly if, like me, you use KDE 99% of the time :-) and required some "manual labor" to get things back to normal. The good news is two-fold: (1) that it gave me an opportunity to find, download and apply a patch from Bugzilla (which //did// fix the problem, and left me feeling warm, fuzzy and accomplished all over), and (2) that it required some work to get things going again this morning but I //could// get them going -- something I doubt would have been possible on the Windows side of things without major hassles and/or reinstall. So, here's my question ... I am, by default, now running cooker 10.1 because of the updates from last night (the communication surrounding the mirrors, directory structures and update procedures being the subject of a different thread, not this one <g>). Given that I know cooker is the "bleeding edge" and not for a production machine (this one isn't), would it now make sense for me to simply remain with cooker, at least for awhile? If I were to do so, would I be able to continue updating using the cooker mirrors as I've been doing these past weeks with the 10CE updates, or would it require a different procedure(s) as 10.1 continues to diverge from 10.0, and onward? (I've seen mention of mirroring the directory structure, etc., locally, I think, and don't quite understand that concept, nor am I sure I would be able to do so.) For those more-than-newbies who have experience with running previous cooker versions, //how// volatile is it, i.e., are problems which occur generally annoyances from which one may recover after another update cycle or two, or are they more-critical show-stoppers which would render one's system useless and force a reinstall? If I //weren't// to stay on the cooker path, should I now expect problems with my "slightly cooker" current install (with its 10.1 designation) with respect to trying to stay current with 10.0 updates (I suspect so?), or am I pretty much stuck with the system as is until 10.1 comes out and/or I do a reinstall, or ...? Hope you get the gist of what I'm asking, probably in a more or less bass ackwards way here ... I think I have a grasp of //some// of the concepts and structures involved here, but not all, certainly, so I need clarification up the proverbial wazoo before I'm comfortable with a particular course of action. TIA -- Chuck Mattsen / [EMAIL PROTECTED] / RLU #346519 Mandrakelinux release 10.1 (Cooker) for i586 kernel 2.6.3-4mdk 20:47:33 up 5:46, 0 users, load average: 0.54, 0.22, 0.16 No one should ever see how laws and sausages are made.
____________________________________________________ Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com ____________________________________________________
