You are not logged in.
- Topics: Active | Unanswered
#1 2011-03-03 12:26:37
- kynikos
- Wiki Admin
- Registered: 2010-12-28
- Posts: 170
[solved] package update: "original=X, current=Y, new=X" not applied
I was using custom icons for Firefox, so I had replaced the following png images with others:
/usr/lib/firefox-3.6/icons/mozicon128.png
/usr/lib/firefox-3.6/icons/document.png
/usr/lib/firefox-3.6/chrome/icons/default/default16.png
/usr/lib/firefox-3.6/chrome/icons/default/default32.png
/usr/lib/firefox-3.6/chrome/icons/default/default48.png
Recently there has been a firefox-3.6 upgrade which I normally handled with pacman, but it replaced those files with the original ones, which I md5sum-checked are exactly the same as the previous version. I thought it should have instead applied the documented rule "original = X, current = Y, new = X", thus keeping my version of the files.
Could this behaviour be expected for some reason? I'd like to understand more, thanks!
Last edited by kynikos (2011-03-03 13:42:57)
Offline
#2 2011-03-03 12:29:01
- Allan
- Pacman
- From: Brisbane, AU
- Registered: 2007-06-09
- Posts: 11,672
- Website
Re: [solved] package update: "original=X, current=Y, new=X" not applied
That only applies to backup files.
Offline
#4 2011-03-03 12:51:42
- Allan
- Pacman
- From: Brisbane, AU
- Registered: 2007-06-09
- Posts: 11,672
- Website
Re: [solved] package update: "original=X, current=Y, new=X" not applied
man pacman.conf - look at NoExtract
Offline
#5 2011-03-03 13:01:02
- kynikos
- Wiki Admin
- Registered: 2010-12-28
- Posts: 170
Re: [solved] package update: "original=X, current=Y, new=X" not applied
Thanks Allan, that quite solves the problem, but (last question, I promise) isn't it possible to tell pacman to consider every file a backup file? I know that would slow down a lot package updates, for it should create md5sums for every file...
Offline