Arch Linux

tony5429

Member

Registered: 2006-03-28

Posts: 1,025

Website

ImageMagick Pacnew Files

I just ran a system update and ImageMagick updated from version 6 to version 7, but the pacnew config files were created in the old version's directory (ImageMagick-6)... Is this normal?

[2017-12-15 02:49] [ALPM] upgraded imagemagick (6.9.9.25-1 -> 7.0.7.14-1)
[2017-12-15 02:49] [ALPM] warning: /etc/ImageMagick-6/type-ghostscript.xml installed as /etc/ImageMagick-6/type-ghostscript.xml.pacnew
[2017-12-15 02:49] [ALPM] warning: /etc/ImageMagick-6/type-dejavu.xml installed as /etc/ImageMagick-6/type-dejavu.xml.pacnew
[2017-12-15 02:49] [ALPM] warning: /etc/ImageMagick-6/type.xml installed as /etc/ImageMagick-6/type.xml.pacnew
[2017-12-15 02:49] [ALPM] warning: /etc/ImageMagick-6/delegates.xml installed as /etc/ImageMagick-6/delegates.xml.pacnew

What's more, after updating I ran "pacman -Rsn $(pacman -Qdtq)" to remove any dependencies that are no longer needed. When I did that just now it actually uninstalled ImageMagick, but the /etc/ImageMagick-6 directory and the new pacnew files remained. I'm guessing I can just delete the whole directory since I no longer have ImageMagick and it should have been deleted during the uninstall process...

---

Get AtlasZIM, the Offline World Atlas for Kiwix

arojas

Developer

From: Spain

Registered: 2011-10-09

Posts: 2,290

Re: ImageMagick Pacnew Files

No. Those files are in the libmagick6 package, do not delete them manually.

amish

Member

Registered: 2014-05-10

Posts: 513

Re: ImageMagick Pacnew Files

I dont recall manually changing these files.

So I wonder why pacnew files were created?

I moved pacnew file to actual files.

Hope it wouldn't cause any issue.

R00KIE

Forum Fellow

From: Between a computer and a chair

Registered: 2008-09-14

Posts: 4,734

Re: ImageMagick Pacnew Files

I dont recall manually changing these files.

So I wonder why pacnew files were created?

I moved pacnew file to actual files.

Hope it wouldn't cause any issue.

Consider this, if you were installing your system from scratch now you would get the new files, so if you haven't changed them manually then it's fine to just move the pacnew files over the old ones.

---

R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K

amish

Member

Registered: 2014-05-10

Posts: 513

Re: ImageMagick Pacnew Files

No I was just wondering what changed it?

I hardly use imagemagick (except command line convert) so doesnt make big difference to me.

jkhsjdhjs

Member

Registered: 2017-09-05

Posts: 39

Re: ImageMagick Pacnew Files

No I was just wondering what changed it?

I hardly use imagemagick (except command line convert) so doesnt make big difference to me.

I overwrote those files too a few days ago. But now that you're saying it I'm wondering too why pacman didn't overwrite them in the first place, cause I can't remember to have ever changed them, too.

Last edited by jkhsjdhjs (2017-12-16 02:01:36)

Lone_Wolf

Administrator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 15,065

Re: ImageMagick Pacnew Files

Some programs change their own configuration files, there used to be a kde package that did this.
It resulted in a pacnew being created at every update of that package.

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky