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#37925 - [libftdi] [i2c-tools] conflicts i2c-tools in file system but not in dependency relationship

Attached to Project: Community Packages
Opened by Felix Yan (felixonmars) - Wednesday, 27 November 2013, 07:42 GMT
Last edited by Eric Belanger (Snowman) - Tuesday, 03 December 2013, 16:45 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Eric Belanger (Snowman)
Jelle van der Waa (jelly)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

Description:
/usr/bin/eeprom exists in both packages

Additional info:
* package version(s)
testing/libftdi 1.0-1
community/i2c-tools 3.1.0-5
This task depends upon

Closed by  Eric Belanger (Snowman)
Tuesday, 03 December 2013, 16:45 GMT
Reason for closing:  Fixed
Additional comments about closing:  libftdi-1.0-2
Comment by Eric Belanger (Snowman) - Wednesday, 27 November 2013, 08:48 GMT
Not sure what best fix would be. Just add a conflicts? If the binary does the same thing, remove it from a package? If so, from which one?
Comment by Timothée Ravier (Siosm) - Wednesday, 27 November 2013, 20:49 GMT
find examples -type f -perm -755 -exec install {} "$pkgdir/usr/bin" \;

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.
Comment by Jelle van der Waa (jelly) - Sunday, 01 December 2013, 20:02 GMT
I'm not sure either, but this is breaking [testing]. I'll try to take a look at the different binaries tomorrow night
Comment by Timothée Ravier (Siosm) - Sunday, 01 December 2013, 20:07 GMT
I think the examples should be dropped for now, as they're not explicitly installed by upstream, thus should not be required.
They can be added back in the right folder once a decision has been made.

Loading...