I replied to this once but an SMTP server somewhere along the way denied it so you get the abridged version (lucky you :))
On Mon, 2002-08-19 at 10:45, Russell Davie wrote: > >The latest > >urpmi depends on a perl module which depends on perl 5.8mdk. perl 5.8mdk > >may or may not depend on gcc 3.1 stuff - I upgraded to gcc 3.1 before > >upgrading urpmi. > > I read this too late... > and have now downloaded urpmi-3.9-8mdk.noarch.rpm and will do gcc 3.1 > later, could only find gcc-3.2-1mdk.i586.rpm > > maybe this is all due to out of date urpmi:.... > when running urpmi-3.3-22mdk.noarch.rpm after doing urpmi.addmedia and > urpmi.update for planetmirror, urpmi wanted files that were not on this > server. ie urpmi wanted to upgrade within version mdk 8.2 and refused to > upgrade between version 7.2 to 8.2. I want just the vanilla 8.2 and urpmi > was not helping with this. So I used rpm -Uvh and downloaded the files one > by one to fulfill dependencies. ouch. I don't remember 7.2 well enough to say whether or not it had something to do with the urpmi install on it. I know I've had some problems with recent development versions of urpmi, but they've been fixed as of about a fortnight ago. > > after doing this the X server is not starting, though I can log in Ok, let's try to fix that. What's it doing? Is this in runlevel 5 or 3? > > I investigated apt-get which seemed useful for mdk 7.2, though not yet for > mdk 8.x. umm, I didn't actually know that mandrake had bothered with apt-get in 7.x. I've learnt something new. There definitely is a version of apt-get for mandrake 8.2. It works ok. There are fundamental differences between .deb and .rpm, but as long as you don't have a system as messy as mine it works ok. > > comment: > this is too grindly tedious, to spend two sundays at a console, to not be > able to upgrade over the net the mdk distro to 7.2 to 8.2. > and still having to the another OS for this message coz its more reliable > for this newbie... > which will lead me into the next post: is there an easier way? maybe > migrating from mdk to deb? Well, just as a sidenote, don't compare old mandrake versions to new debian versions. But if you're going to the trouble of migrating from mandrake to debian (and you can't just click "upgrade" somewhere and have it work, but I don't know if that's what you were asking), you might as well grab mandrake 8.2 (or better yet, 9.0) CDs and install from that. But back to your original problem - I really do recommend just getting the latest urpmi to work and then letting it fix all the rest of your problems. You can with relative safety just --force it to upgrade perl, perl-URPM, urpmi and rpm* and urpmi will just work. It's not very elegant but it will work. From there you can tell urpmi to fix your perl install (broken from doing --force). Then use your system normally. If you find something not working, get urpmi to install the latest version for you. I generally don't like advocating the above method, because there's some not-so-deeply buried computer scientist in me that twitches when instructing people to misuse software. But it will get the system working again. James. -- SLUG - Sydney Linux User's Group - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
