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!
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!
FS#18530 - [minicom] syswide config tries to be overwrite
Attached to Project:
Arch Linux
Opened by Alexander Drozdov (adrozdov) - Tuesday, 02 March 2010, 16:18 GMT
Last edited by Giovanni Scafora (giovanni) - Tuesday, 02 March 2010, 22:38 GMT
Opened by Alexander Drozdov (adrozdov) - Tuesday, 02 March 2010, 16:18 GMT
Last edited by Giovanni Scafora (giovanni) - Tuesday, 02 March 2010, 22:38 GMT
|
DetailsDescription:
Durings pacman -Syu I was observe next issue: checking package integrity... (70/70) checking for file conflicts error: failed to commit transaction (conflicting files) minicom: /etc/minirc.dfl exists in filesystem Errors occurred, no packages were upgraded. Additional info: * package version(s): upgrade minicom from 2.4-1 to 2.4-2 * I looked into PKGBUILD for minicom (after abs run) and I observe, that directive backup=() there is not present in PKGBUILD Steps to reproduce: 1. install old minicom package 2. do minicom -s and configure it by root 2.1 select Save as dfl, exit from minicom 3. try to install latest minicom package |
This task depends upon
Closed by Giovanni Scafora (giovanni)
Tuesday, 02 March 2010, 22:38 GMT
Reason for closing: Not a bug
Tuesday, 02 March 2010, 22:38 GMT
Reason for closing: Not a bug
Comment by Gerardo Exequiel Pozzi (djgera) -
Tuesday, 02 March 2010, 22:30 GMT
No problem, there is a backup=('etc/minirc.dfl'). So do a manually backup, remove .dfl, upgrade minicom, restore. On next minicom upgrade, will be backed up automatically.