You are not logged in.
Hi all,
I did pacman -Syu this morning and when trying to upgrade scrollkeeper it gave me a conflict:
scrollkeeper-0.3.12-4.pk [####################################] 100% | 210K
loading package data... done.
checking for file conflicts...
error: the following file conflicts were found:
/var/log/scrollkeeper.log: exists in filesystem
As /var/log/scrollkeeper.log just contains one line concerning its installation time, I suppose it's quite safe to delete it, but there should still be a better way to avoid this conflict.
Jan
Offline
I've had many similar problems, maybe it would be a feature for new versions of pacman, to avoid this problems by some way...
And where were all the sportsmen who always pulled you though?
They're all resting down in Cornwall
writing up their memoirs for a paper-back edition
of the Boy Scout Manual.
Offline
The problem exists because the old package had the scrollkeeper log file in /usr/var/log/scrollkeeper.log and the new one is in /var/log/scrollkeeper.log. The problem is that /usr/var is a symlink to /var but pacman doesn't know that. It thinks that /var/log/scrollkeeper.log is some errant file that it doesn't know what to do with. Everyone who had scrollkeeper installed and is upgrading will have this problem.
I have discovered that all of mans unhappiness derives from only one source, not being able to sit quietly in a room
- Blaise Pascal
Offline
there is also the trusty (though not always desirable) force option:
pacman -Sf scrollkeeper
AKA uknowme
I am not your friend
Offline
I just renamed scrollkeeper.log to scrollkeeper.log.old
Offline