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#37934 - [libftdi] file conflict with i2c-tools for /usr/bin/eeprom
Attached to Project:
Arch Linux
Opened by Timothée Ravier (Siosm) - Wednesday, 27 November 2013, 18:47 GMT
Last edited by Eric Belanger (Snowman) - Wednesday, 27 November 2013, 20:46 GMT
Opened by Timothée Ravier (Siosm) - Wednesday, 27 November 2013, 18:47 GMT
Last edited by Eric Belanger (Snowman) - Wednesday, 27 November 2013, 20:46 GMT
|
Detailslibftdi 1.0-1 in testing includes /usr/bin/eeprom which is already provided by i2c-tools in community, thus creating a conflict upon update:
error: failed to commit transaction (conflicting files) libftdi: /usr/bin/eeprom exists in filesystem I don't know which one is the "good" version. I'll try to investigate the subject asap. Steps to reproduce: 0. Downgrade to libftdi 0.20-2 1. Install i2c-tools 2. Update |
This task depends upon
Closed by Eric Belanger (Snowman)
Wednesday, 27 November 2013, 20:46 GMT
Reason for closing: Duplicate
Additional comments about closing: FS#37925
Wednesday, 27 November 2013, 20:46 GMT
Reason for closing: Duplicate
Additional comments about closing:
This is the culprit. Is there any particular reason compiled examples are installed ? Maybe they should be placed in their own directory, in source code form.