Hi, > Thorsten Grothe wrote: > > But now I have a lot of *.pacnew files. How can I get rid of them > > automatically? > > > You probably want to check the pacnew-files against the other files > you got, and do the changes yourself, until someone makes a > pacnew-diff utility. > Having used ArchLinux only for a week, I hope my understanding is correct :-)
Basically, a pacnew file means the three-way-diff in the upgrade logic found a possible problem. The "old" file (usually a config file coming with the package as an example) has been changed locally, and the "new" file is different from both the "old" *and* the "local" one. So you should check what has changed, and whether you need to update the local copy. Look at the manpage for pacman, it is well written :-) Another way to deal with it might be to include the file in the /etc/pacman.conf file with a "NoUpgrade" line. This avoids the pacnew in the beginning, but then again you might end up with invalid config files (because the format in the new package may have changed). So, you should do this only if you know what you do. Kind regards Volker _______________________________________________ arch mailing list [email protected] http://www.archlinux.org/mailman/listinfo/arch
