Luca Olivetti <[EMAIL PROTECTED]> writes: >... > Let's go for a summary of the problems: > > * The "urpmi urpmi" step worked well. After that I had to stop the "urpmi > --auto-select" because it was scrolling a bazillion of error messages regarding > /var/lib/rpm/PubKeys. Had to remove the file and manually "rpm --import" the > keys
Problably a problem of specific extension of rpm 4.2 versus 4.0.4 used in 9.1, a missing rpm --rebuilddb could be the cause ? Anyway, a urpmi.update -a could be much nicer after, except if urpmi database is already up-to-date ? > * There was some conflict with files with some updated packages. Removed the > offending packages and urpmi --auto-select worked well. A commend line --skip pkg1,pkg2,...,pkgN can be used in such case, it is depending on the humor of the moment. > * It couldn't update libavifile0.7 libaviplayavcodec (and dependent packages) > due to dependencies. I think this is a problem caused by urpmi batching, since > when I manually issued an "urpmi libavifile0.7 libaviplayavcodec" it could > upgrade both flawlessly. Maybe this problem will be more noticeable on the other > machine since it has many more packages installed. If you could have saved bug report of urpmi for that... in order to see what is the cause. >... > gettext-0.11.5-2mdk, kdeutils-3.1-9mdk, screem-0.6.0-1mdk > > in 9.2: > > gettext-0.11.5-7mdk, kdeutils-3.1.3-20mdk, screem-0.6.2-4mdk > > Add to the list automake, but that's because of the naming (I had automake1.6 > while 9.2 has automake1.7). Again, it is domage you didn't issue an --bug of urpmi, it is always nice when something seems to be bad. > * The last issue is that by rebooting (I didn't upgrade the kernel) I had a dead > machine: it couldn't find the initrd so it couldn't mount the root directory > (since it's xfs). Hopefully one of the older kernels I had could boot, ran lilo > from it and the machine went back to life. I don't understand what happened > here, really. The other machine has a much more convoluted lilo setup, so I fear > it won't be as easy to recover. lilo was problably updated, and lilo upgrade should call lilo by itself. > Well, I'm impressed by how well the procedure worked. Sure, there were some > hurdles and the modification in libraries versions wasn't earth shattering (I > wonder if everything would work as well with a major glibc update) but still > it's much better that what was available before. Oh, btw, I was using the > machine (logged in in X) during the whole process. That's incredible. Kudos to > mandrake developers and contributors. Yes, but there was still some problems. Thanks, Fran�ois.
