[ISSUE] File conflict between cmark and python3-commonmark

[ISSUE] File conflict between cmark and python3-commonmark

[travankor]

[-- Attachment #1: Type: text/plain, Size: 785 bytes --]

New issue by travankor on void-packages repository

https://github.com/void-linux/void-packages/issues/34007

Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System

* xuname:
  Void 5.10.73_1 x86_64 GenuineIntel uptodate hold rrrmDDFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
* package:
  `cmark-0.30.2_1` and `python3-commonmark-0.9.1_2`

### Expected behavior
No file conflicts

### Actual behavior
File conflicts

```
xbps-query -Rf cmark
/usr/bin/cmark
...
xbps-quer -Rf python3-commonmark
/usr/bin/cmark
...
```

### Steps to reproduce the behavior
```
xbps-query -Rf cmark
xbps-quer -Rf python3-commonmark
```

Re: File conflict between cmark and python3-commonmark

[ericonr]

[-- Attachment #1: Type: text/plain, Size: 292 bytes --]

New comment by ericonr on void-packages repository

https://github.com/void-linux/void-packages/issues/34007#issuecomment-965918845

Comment:
Thoughts on preference? Are the command line flags similar?

I can see a case for alternatives or just renaming the script from the python package.

Re: File conflict between cmark and python3-commonmark

[ericonr]

[-- Attachment #1: Type: text/plain, Size: 249 bytes --]

New comment by ericonr on void-packages repository

https://github.com/void-linux/void-packages/issues/34007#issuecomment-965919264

Comment:
(assuming python3-commonmark is depended on by other packages, having it conflict would be far from ideal)

Re: File conflict between cmark and python3-commonmark

[bobertlo]

[-- Attachment #1: Type: text/plain, Size: 482 bytes --]

New comment by bobertlo on void-packages repository

https://github.com/void-linux/void-packages/issues/34007#issuecomment-994218317

Comment:
arch just renamed the python3-commonmark binary to `/usr/bin/py3-cmark` fwiw. I really think between the two noone is installing python3-commonmark to use that `cmark` cli.

If the commands were separate from the libraries I doubt this conflict would come up often, but with both packages providing libraries it's not a great situation.

Re: File conflict between cmark and python3-commonmark

[ericonr]

[-- Attachment #1: Type: text/plain, Size: 297 bytes --]

New comment by ericonr on void-packages repository

https://github.com/void-linux/void-packages/issues/34007#issuecomment-994244383

Comment:
I think we usually spell out "python3-" in these executable names, but if other distros uses py3 it might help to go with the flow. I will check them out.

Re: File conflict between cmark and python3-commonmark

[ericonr]

[-- Attachment #1: Type: text/plain, Size: 296 bytes --]

New comment by ericonr on void-packages repository

https://github.com/void-linux/void-packages/issues/34007#issuecomment-994244383

Comment:
I think we usually spell out "python3-" in these executable names, but if other distros use py3 it might help to go with the flow. I will check them out.

Re: File conflict between cmark and python3-commonmark

[bobertlo]

[-- Attachment #1: Type: text/plain, Size: 421 bytes --]

New comment by bobertlo on void-packages repository

https://github.com/void-linux/void-packages/issues/34007#issuecomment-994246680

Comment:
Yeah, that was just an example I was also thinking python3 might be more appropriate.

I noticed alpine and fedora both appear to have this conflict. I really don't think anyone will have an issue about the filename, but I could see someone installing both of these packages.

Re: File conflict between cmark and python3-commonmark

[github-actions]

[-- Attachment #1: Type: text/plain, Size: 293 bytes --]

New comment by github-actions[bot] on void-packages repository

https://github.com/void-linux/void-packages/issues/34007#issuecomment-1175700467

Comment:
Issues become stale 90 days after last activity and are closed 14 days after that.  If this issue is still relevant bump it or assign it.

Re: [ISSUE] [CLOSED] File conflict between cmark and python3-commonmark

[github-actions]

[-- Attachment #1: Type: text/plain, Size: 790 bytes --]

Closed issue by travankor on void-packages repository

https://github.com/void-linux/void-packages/issues/34007

Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System

* xuname:
  Void 5.10.73_1 x86_64 GenuineIntel uptodate hold rrrmDDFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
* package:
  `cmark-0.30.2_1` and `python3-commonmark-0.9.1_2`

### Expected behavior
No file conflicts

### Actual behavior
File conflicts

```
xbps-query -Rf cmark
/usr/bin/cmark
...
xbps-query -Rf python3-commonmark
/usr/bin/cmark
...
```

### Steps to reproduce the behavior
```
xbps-query -Rf cmark
xbps-query -Rf python3-commonmark
```