Skip to main content ↑ ↓
Topic: world/minicom conflicts with system/openrc (Read 1395 times) previous topic - next topic
0 Members and 4 Guests are viewing this topic.

world/minicom conflicts with system/openrc

Hello,
After the last minicom update you(i don't remember the exact user) have fixed a similar issue.
But today the issue is back.
`/usr/bin/runscript` from minicom is in conflict with OpenRC.
The last time the fix was moving the script from minicom to `/usr/bin/runscript-minicom` and editing the default config to match the change

Re: Conflict between minicom and OpenRC

Reply #1 –
I’ll refix as soon as I can.

I have submited the fix, so will be available again. Next time I will try to not break it :D

Re: [SOLVED] Conflict between minicom and OpenRC

Reply #2 –
It's back again, with minicom 2.9-1

Re: [SOLVED] Conflict between minicom and OpenRC

Reply #3 –
I have the same:

pacman -Syu:
Code: [Select]
[...]
error: failed to commit transaction (conflicting files)
minicom: /usr/bin/runscript exists in filesystem (owned by openrc)
[...]
Regards!

Re: [SOLVED] Conflict between minicom and OpenRC

Reply #4 –
I could mark this issue as unresolved, or create a new one, I don't know what's best

Re: [SOLVED] Conflict between minicom and OpenRC

Reply #5 –
It's in the right category for me, you can mark back unsolved.
Also these simple file conflicts of pacman get resolved simply by deleting the file in question. Not ideal, of course, but it does the trick.

Re: [SOLVED] Conflict between minicom and OpenRC

Reply #6 –
Quote from: Hitman – on
Also these simple file conflicts of pacman get resolved simply by deleting the file in question. Not ideal, of course, but it does the trick.
Is it a simple conflict though ? I.E. one where two packages contain essentially the same file.
If so reasonable advice.

However if the minicom and openrc runscript's are totally different files which happen to have the same name (which seems to be the case) then deleting the openrc version to allow minicom to install could have very bad results. I'm guessing as even though I use openrc I don't know exactly how important runscript is ? I can guess what it does. Clue's in the name  :)
I'm not confident my system would boot correctly if I replaced it with mincom's version though ?
 

Re: [SOLVED] Conflict between minicom and OpenRC

Reply #7 –
Your concern is right but i'm pretty sure openrc doesn't need *bin/runscript, as it's services execute with *bin/openrc-run, and they both seem to be duplicates and not symlinks.
LE: oh okay, runscript has actually been deprecated for a good while https://bugs.gentoo.org/573846

https://bugs.gentoo.org/494220 also of interest

Re: [SOLVED] Conflict between minicom and OpenRC

Reply #8 –
Quote from: Hitman – on
Your concern is right but i'm pretty sure openrc doesn't need *bin/runscript, as it's services execute with *bin/openrc-run, and they both seem to be duplicates and not symlinks.
LE: oh okay, runscript has actually been deprecated for a good while https://bugs.gentoo.org/573846

https://bugs.gentoo.org/494220 also of interest
Interesting.
You are right runscript and openrc-run are identical. And it seems runscript is just cruft at this point ?
For science I renamed runscript and my system booted up fine.

Re: [SOLVED] Conflict between minicom and OpenRC

Reply #9 –
Quote from: Hitman – on
you can mark back unsolved.
This topic still has "[SOLVED]" in it's title but the issue is still present.

Can you un-mark it as "resolved"?

Regards!

Re: Conflict between minicom and OpenRC

Reply #10 –
Quote from: gripped – on
For science I renamed runscript and my system booted up fine.

Thank you.

Code: [Select]
cd /usr/bin
mv runscript runscript.bak
pacman -S minicom
du -sh runscript runscript.bak
--
28K	runscript
44K	runscript.bak
--

"Tonight at 11; DOOM!"
./follow-the-white-rabbit

world/minicom conflicts with system/openrc

Reply #11 –
A recent update of world/minicom to version 2.9-1 introduced a conflict with system/openrc:
Code: [Select]
error: failed to commit transaction (conflicting files)
minicom: /usr/bin/runscript exists in filesystem (owned by openrc)

Regards!

P.S.: This issue already appeared in 2020 and was resolved back then, see this thread. In that thread, it is also reported that the issue came back, but since the comeback was reported already on 2023-10-02 but not fixed until now I suspect that the maintainer does not read this old thread, so I make this new one. 
If this old thread is in fact read by the maintainer, then you can ignore this new report of mine here.

@Moderators, feel free to combine both threads if the new thread does not help to get maintainer's attention.

Re: Conflict between minicom and OpenRC

Reply #12 –
Quote from: Eragon – on
It's back again, with minicom 2.9-1

Since this issue is not resolved until today I suspect that the maintainer does not read this old thread, so I have reported in a new one: Here.

@Moderators, feel free to combine both threads if the new thread does not help to get maintainer's attention.

Regards!

Re: world/minicom conflicts with system/openrc

Reply #14 –
I now uses picocom, which have more options and does not have this recurrent conflict.