On 21.08.20 22:09, Morten Linderud via arch-general wrote:
There are more ".pacnew" in my /etc. All for files that I never touched myself.
That is concerning, but it is simply something touching those files you are unaware of. It's however you system and it's expected that you are aware of what does this.
I don't know what this could be. What exactly is compared? File timestamps? Checksums? How to debug this? For example I have a /etc/ppp/ip-up.d/00-dns.sh.pacnew I for sure never edited this. I don't care about ppp at all. This package came as dependency of something else (maybe NetworkManger). A diff between the actuall file and its ".pacnew": $ diff -U 8 -p 00-dns.sh 00-dns.sh.pacnew --- 00-dns.sh 2013-05-30 19:35:30.000000000 +0200 +++ 00-dns.sh.pacnew 2020-02-20 22:37:04.000000000 +0100 @@ -1,7 +1,11 @@ #!/bin/sh if [ "$USEPEERDNS" = "1" -a -f /etc/ppp/resolv.conf ]; then - [ -e /etc/resolv.conf ] && mv /etc/resolv.conf /etc/resolv.conf.backup.${IFNAME} - mv /etc/ppp/resolv.conf /etc/resolv.conf - chmod 644 /etc/resolv.conf + if [ -x /usr/bin/resolvconf ]; then + /usr/bin/resolvconf -a ${IFNAME} </etc/ppp/resolv.conf + else + [ -e /etc/resolv.conf ] && mv /etc/resolv.conf /etc/resolv.conf.backup.${IFNAME} + mv /etc/ppp/resolv.conf /etc/resolv.conf + chmod 644 /etc/resolv.conf + fi fi
I guess there is something wrong with the way how pacman decides when to move ".pacnew" into place directly.
There isn't. Peopel with `.pacnew` has modified their files, wittingly or not.
For sure not. I guess it somehow also depends on how they are compared. At some point in the past I replaced my HDD with an SSD and as far as I remember I copied over the system. Could this have caused the way how pacman decides when to move ".pacnew" into place somehow? I may also have deleted the whole /var/cache/pacman/pkg at some point in the past to save space. Is this where pacman checks for "old files"? Manuel