usually it's as simple as running updatedb, then locate .rpmnew and fixing up any
config file changes that didn't get applied automatically. then run preupgrade, and
once the system is up repeat the same procedure to find new .rpmnew files.
when a package being updated discovers that some file from the already installed version
has been changed, the new file is named with a .rpmnew suffix instead of overwriting your
edits. this means that file doesn't get updated until you merge it with your changes
manually. when upgrading to a new release it is important to do this merge both before and
after since some config files could have changed enough that some service stops working.
birger
Martín Marqués <martin.marques(a)gmail.com>:
That's all I want (what's in the subject).
I've had some headaches with preupgrade, basically, I guess, because I
have /var on another partition.
--
Martín Marqués
select 'martin.marques' || '@' || 'gmail.com'
DBA, Programador, Administrador
--
users mailing list
users(a)lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines:
http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away:
http://ask.fedoraproject.org