You are not logged in.
Pages: 1
I get this:
Proceed with installation? [Y/n]
checking package integrity...
(41/41) checking for file conflicts [#################################################] 100%
error: could not prepare transaction
error: failed to commit transaction (conflicting files)
shared-mime-info: /usr/share/mime/application/x-cdrdao-toc.xml exists in filesystem
Errors occurred, no packages were upgraded.any ideas would be appreciated
thanks
Offline
# rm /usr/share/mime/application/x-cdrao-toc.xml would work. ![]()
Offline
or just -Syf <package name>, but i dont know if it's advisable. i'm not sure what the whole mimetypes stuff is.
Last edited by rson451 (2008-06-27 04:03:19)
archlinux - please read this and this — twice — then ask questions.
--
http://rsontech.net | http://github.com/rson
Offline
or just -Syuf, but i dont know if it's advisable.
You are generally better to just for the package that is causing the conflict rather than the whole upgrade (provided you know why you are forcing...)
That mime-type file that is causing the conflict is safe to overwrite/delete.
Offline
rson451 wrote:or just -Syuf, but i dont know if it's advisable.
You are generally better to just for the package that is causing the conflict rather than the whole upgrade (provided you know why you are forcing...)
That mime-type file that is causing the conflict is safe to overwrite/delete.
yes yes, thanks for pointing that out. i'm actually going to edit that post cause that command could be dangerous in some situations.
archlinux - please read this and this — twice — then ask questions.
--
http://rsontech.net | http://github.com/rson
Offline
When I get a file conflict I check which package it belongs to
pacman -Qo /path/to/file
Then just reinstall the package or if it does not belong to any package then just rm it. Although, it may be from non-pacman related install, so be careful.
Last edited by Purch (2008-06-27 06:30:46)
Offline
rson451 wrote:or just -Syuf, but i dont know if it's advisable.
You are generally better to just for the package that is causing the conflict rather than the whole upgrade (provided you know why you are forcing...)
That mime-type file that is causing the conflict is safe to overwrite/delete.
+1
normally I would say mv the file, then if something is broken, just move it back. I had already done that with this package though, and knew it was safe to delete.
Offline
thanks
Offline
Pages: 1