You are not logged in.
This is similar to pinentry.pacnew, and I have no problem normally with .pacnew files. I usually run vimdiff and either incorporate the changes or not. However, I went to do just that but on the system, in question, and instead of an original script in n pinenrty, there was a symkink to pinentry-gtk-2.
[root@ssc10 bin]# ls -l pinentry
lrwxrwxrwx 1 root root 14 Dec 9 2017 pinentry -> pinentry-gtk-2*
Any ideas how the symlink got there? Should I just leave it and delete the .pacnew file or delete the symlink and mv pinentry.pacnew pinentry?
Last edited by rossboulet (2018-08-01 17:20:07)
I really hate this damn machine,
I wish that they would sell it.
It never does just what I want,
But only what I tell it. -Anonymous
Offline
Sounds like a really old/out of date system. It used to be a symlink.
Offline
Please post your entire pacman.log
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Online
lol. It looks like I missed it by one day. As best I can tell, the release with the change from a symlink to a script was moved to the core repository on 2018-04-24. The last full pacman upgrade I ran on the system in question was on 2018-04-23. I will delete the symlink in favor of the script.
I really hate this damn machine,
I wish that they would sell it.
It never does just what I want,
But only what I tell it. -Anonymous
Offline