Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#50412 - remove atom installed from AUR first before install atom from community packages

Attached to Project: Community Packages
Opened by Arno Gaboury (gabx) - Tuesday, 16 August 2016, 10:10 GMT
Last edited by Doug Newgard (Scimmia) - Tuesday, 16 August 2016, 13:16 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Installing atom from community packages fails when atom has already been installed with AUR packages.

Additional info:
* package version(s)
atom-1.9.8-3
* config and/or log files etc.
Error output when running pacman:
error: failed to commit transaction (conflicting files)
apm: /usr/bin/apm exists in filesystem
atom: /usr/bin/atom exists in filesystem
atom: /usr/share/applications/atom.desktop exists in filesystem
Errors occurred, no packages were upgraded.


Steps to reproduce:

# pacman -Syu atom

Suggestion: introduce a invite to remove the already installed atom.

Workaround: remove manually atom before install.



This task depends upon

Closed by  Doug Newgard (Scimmia)
Tuesday, 16 August 2016, 13:16 GMT
Reason for closing:  Not a bug

Loading...