FS#68599 - [sx] [sz] [lrzsz] Conflict on /usr/bin/sx /usr/bin/sz files

Attached to Project: Community Packages
Opened by Aleksei (nesk_bugs) - Thursday, 12 November 2020, 16:24 GMT
Last edited by Sergej Pupykin (sergej) - Thursday, 10 August 2023, 01:09 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sergej Pupykin (sergej)
Bruno Pagani (ArchangeGabriel)
Ivy Foster (escondida)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Can't install sx when lrzsz is already installed.

Additional info:
* lrzsz 0.12.20-7, sx-2.1.6-1-any

Steps to reproduce:

* Have lrzsz installed
* pacman -S sx
resolving dependencies...
community/sx 2.1.6-1 0.00 MiB 0.01 MiB
# ...
error: failed to commit transaction (conflicting files)
sx: /usr/bin/sx exists in filesystem (owned by lrzsz)
Errors occurred, no packages were upgraded.
This task depends upon

Closed by  Sergej Pupykin (sergej)
Thursday, 10 August 2023, 01:09 GMT
Reason for closing:  Fixed
Comment by Michal Wojdyla (micwoj92) - Friday, 26 February 2021, 20:20 GMT
lrzsz also conflicts with sz usr/bin/sz, I don't know if that should be reported as new bug or not...
Comment by Sergej Pupykin (sergej) - Saturday, 27 February 2021, 08:58 GMT
I would suggest to fix it in sx package, because of rx/sx are default names which all terminals expect by default.

| A zmodem sz -vv -b Y U N Y Y |
| B ymodem sb -vv Y U N Y Y |
| C xmodem sx -vv Y U N Y N |
| D zmodem rz -vv -b -E N D N Y Y |
| E ymodem rb -vv N D N Y Y |
| F xmodem rx -vv Y D N Y N |
Comment by Eli Schwartz (eschwartz) - Sunday, 28 February 2021, 01:15 GMT
What is a "default names which all terminals expect by default"? Are you suggesting "terminals" (all of them???) inherently bake in an understanding of the command name and expect it to be a fairly niche file transfer protocol?

It's just a command name. :/ People can use it where- and how- ever they like.

And this is apparently not just about sx!

My $0.02 -- conflicts are fine.
Comment by Sergej Pupykin (sergej) - Sunday, 28 February 2021, 09:29 GMT
I mean default commands are hardcoded:

minicom/src/rwconf.c:
{ "sz -vv -b", 0, "pprog1" },
{ "sb -vv", 0, "pprog2" },
{ "sx -vv", 0, "pprog3" },
{ "rz -vv -b -E", 0, "pprog4" },
{ "rb -vv", 0, "pprog5" },
{ "rx -vv", 0, "pprog6" },

picocom/picocom.c:
.send_cmd = "sz -vv",
.receive_cmd = "rz -vv -E",

They can be overwritten with config or command line options.
Comment by Ivy Foster (escondida) - Sunday, 01 January 2023, 15:40 GMT
[Just got the notification that this was assigned to me]

So...not really sure what to do here: both in the case of my sx package and Archange's sz package, the name of the package is the name of the command and the one and only executable shipped.

Perhaps the lrzsz commands could go into /usr/bin/lrzsz/ or /opt/lrzsz/, since the hardcoding seems to imply their own unique ecosystem?

edit: end dir paths with slashes for clarity
Comment by Aleksei (nesk_bugs) - Monday, 02 January 2023, 05:15 GMT
sx is specific to Xorg - maybe rename it (and binary) to sx-xorg? Will break a lot of people's startup scripts though, better give plenty of warnings in pacman/website.
Comment by Ivy Foster (escondida) - Tuesday, 16 May 2023, 16:21 GMT
Sergei, any thoughts on my suggestion above? It seems as though these commands are specific to one particular ecosystem, and could easily be grouped together in a subdirectory.
Comment by Sergej Pupykin (sergej) - Tuesday, 16 May 2023, 17:51 GMT
I am not sure, maybe I can move it to /usr/lib/lrzsz/, xmodem used rarely, I think people who use it will find a way to use lrzsz with their terminals.
Comment by Buggy McBugFace (bugbot) - Tuesday, 08 August 2023, 19:11 GMT
This is an automated comment as this bug is open for more then 2 years. Please reply if you still experience this bug otherwise this issue will be closed after 1 month.
Comment by Layne (xente) - Wednesday, 09 August 2023, 16:16 GMT
this is still an issue

Loading...