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#78186 - [clash-ghc] unnecessarily conflicts with `community/clash`
Attached to Project:
Community Packages
Opened by Shupei Fan (fansp) - Thursday, 13 April 2023, 07:17 GMT
Last edited by Toolybird (Toolybird) - Thursday, 13 April 2023, 20:43 GMT
Opened by Shupei Fan (fansp) - Thursday, 13 April 2023, 07:17 GMT
Last edited by Toolybird (Toolybird) - Thursday, 13 April 2023, 20:43 GMT
|
DetailsDescription: `community/clash-ghc` list `clash` as conflicts, leading to conflict with `community/clash`.
`community/clash-ghc` is a CAES Language for Synchronous Hardware; and `community/clash` is a rule based proxy in Go. I believe two tools are totally unrelated, despite of the coincidence in naming. We may remove `clash` from clash-ghc's conflict list. Additional info: * package version(s): clash-ghc 1.6.4-65 |
This task depends upon
Closed by Toolybird (Toolybird)
Thursday, 13 April 2023, 20:43 GMT
Reason for closing: Not a bug
Additional comments about closing: See comments
Thursday, 13 April 2023, 20:43 GMT
Reason for closing: Not a bug
Additional comments about closing: See comments
Comment by Shupei Fan (fansp) -
Thursday, 13 April 2023, 08:56 GMT
I just realized that both packages provide `/usr/bin/clash`, so they are indeed in conflict. There's nothing wrong with Arch's packaging, it's just a sad story.