-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
John Allen wrote: |>It should create just .rpmnew file in this case, not rename the old to |>.rpmsave too. Or rename to .rpmsave but replace the file with a new |>version. |> | | | OK, boot from the CD/DVD, press F1, type rescue<enter> | mount the partitions, go to console, and rename files | reboot | |
Yeah, I know how to rescue my machine in such case. But the point is :
1) if you didn't notice, that pam config was changed, you can look for hours what is wrong (especialy if you have no idea about what PAM is)
2) it must not be necessary to rescue your machine after a botched upgrade. I could take this as a risk of running cooker (broken glibc update, do you remember?), but this will go to the official 9.2 updates, no ? Could you imagine the mess ?
3) the behavior of RPM in this case is strange (it is an RPM not urpmi issue). Maybe I do not get completely the rationale about why it works as it does, but it should either leave the older file in place and create .rpmnew file (if you changed the config by hand) or replace the file with a new version and save a .rpmsave file with your old config (if the changes are incompatible, e.g. a changed file format). Why does it remove the config file and create both .rpmnew and .rpmsave files instead breaking the machine in the process ?
Regards,
Jan
- --
Jan Ciger VRlab EPFL Switzerland GPG public key : http://www.keyserver.net/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQE/hsrxn11XseNj94gRAuLsAJ44o7Pz6AwcYe0nbVbyy+6Q2SBt7QCfT3Po gQwpJ7/vYCC0qdPdWXeeWSs= =42P7 -----END PGP SIGNATURE-----
