You are not logged in.

#1 2015-02-11 00:19:14

pdizzle
Member
Registered: 2013-02-07
Posts: 16

Pacmatic .pacnew file error

My pacmatic is somehow stuck thinking there is a pacnew file somewhere when in fact there are none. I am very certain that there aren't, and additionally

$ locate pacnew

returns nothing.

Anytime I run pacmatic -Syu it returns

1 pacnew files found (0 added). Update files now ? (Y/n)

if I select yes, nothing happens.. I believe because there isn't any pacnew files. Is there a way to reset this? I had thought of pacman -Rs pacmatic && pacman -S pacmatic but would this somehow effect pacmatics cache/function?

Thanks

Offline

#2 2015-02-11 00:47:32

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 20,580

Re: Pacmatic .pacnew file error

Try sudo updatedb
Then do a locate pacnew


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way

Offline

#3 2015-02-11 00:50:08

pdizzle
Member
Registered: 2013-02-07
Posts: 16

Re: Pacmatic .pacnew file error

ewaller wrote:

Try sudo updatedb
Then do a locate pacnew

yes, I did that before executing locate. This state of pacmatic has existed on my system for several weeks now.

Offline

#4 2015-02-11 00:56:24

karol
Archivist
Registered: 2009-05-06
Posts: 25,440

Re: Pacmatic .pacnew file error

Run https://github.com/keenerd/pacmatic/blo … matic#L152

find /etc/ \( -name \*.pacnew -o -name \*.pacorig -o -name \*.pacsave \) 2> /dev/null | wc -l

Offline

#5 2015-02-11 01:00:51

pdizzle
Member
Registered: 2013-02-07
Posts: 16

Re: Pacmatic .pacnew file error

karol wrote:

Run https://github.com/keenerd/pacmatic/blo … matic#L152

find /etc/ \( -name \*.pacnew -o -name \*.pacorig -o -name \*.pacsave \) 2> /dev/null | wc -l

good find!

$ find /etc/ \( -name \*.pacnew -o -name \*.pacorig -o -name \*.pacsave \) 2> /dev/null | wc -l
1

and

$ find /etc/ \( -name \*.pacnew -o -name \*.pacorig -o -name \*.pacsave \)
/etc/unbound/unbound.conf.pacsave

so it was a pacsave file hiding. I don't intend to reinstall unbound, so I will just remove the file.. but why should pacmatic look for these? Isn't it likely that there would be a number of these on a system from removed packages that would be worth keeping around and not getting pestered about consistently?

Offline

#6 2015-02-11 01:39:25

karol
Archivist
Registered: 2009-05-06
Posts: 25,440

Re: Pacmatic .pacnew file error

pdizzle wrote:

why should pacmatic look for these? Isn't it likely that there would be a number of these on a system from removed packages that would be worth keeping around and not getting pestered about consistently?

https://github.com/keenerd/pacmatic/issues/1 ?

Offline

#7 2015-02-11 04:15:00

pdizzle
Member
Registered: 2013-02-07
Posts: 16

Re: Pacmatic .pacnew file error

karol wrote:
pdizzle wrote:

why should pacmatic look for these? Isn't it likely that there would be a number of these on a system from removed packages that would be worth keeping around and not getting pestered about consistently?

https://github.com/keenerd/pacmatic/issues/1 ?


I'm sorry, I this doesn't seem to answer my question.. wouldn't I want to just leave this config file in place until I possibly reinstall the associated package, and then at that point have pacmatic/pacman prompt me to reuse the old saved config? Why is it useful to have pacmatic notify me of it (which in my case doesn't really seem to work properly) every time I run it?

I am not interested in searching for and merging pacnew files as a standalone function, which as I understand it is what that question was about.

Offline

Board footer

Powered by FluxBB