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#73256 - [opensearch] Conflicts with optional dependency opensearch-cli
Attached to Project:
Community Packages
Opened by Mark Wagie (yochananmarqos) - Tuesday, 04 January 2022, 16:20 GMT
Last edited by Justin Kromlinger (hashworks) - Wednesday, 05 January 2022, 12:09 GMT
Opened by Mark Wagie (yochananmarqos) - Tuesday, 04 January 2022, 16:20 GMT
Last edited by Justin Kromlinger (hashworks) - Wednesday, 05 January 2022, 12:09 GMT
|
DetailsDescription: opensearch and opensearch-cli both contain /usr/bin/opensearch-cli.
Additional info: * package version(s) opensearch 1.2.3-1 opensearch-cli 1.1.0-1 |
This task depends upon
Closed by Justin Kromlinger (hashworks)
Wednesday, 05 January 2022, 12:09 GMT
Reason for closing: Fixed
Additional comments about closing: opensearch 1.2.3-2
Wednesday, 05 January 2022, 12:09 GMT
Reason for closing: Fixed
Additional comments about closing: opensearch 1.2.3-2

Which is why opensearch-cli conflicts with opensearch. Everything seems normal here.

I forgot to mention opensearch-cli is an optional dependency of opensearch. How does that work if they conflict?

Right, an optional dep doesn't make sense.

Correct, I should drop the optional dep. It was created before I noted the conflict. I'll remove the opt dep, however I need to ask the opensearch guys if the new go binary fully replaces the old java binary.