Bug 28442 - ranger does not work. Fails with "Unknown option: - " message.
Summary: ranger does not work. Fails with "Unknown option: - " message.
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 8
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL:
Whiteboard: MGA7TOO MGA7-64-OK MGA8-64-OK
Keywords: advisory, validated_update
Depends on:
Blocks:
 
Reported: 2021-02-26 00:59 CET by PC LX
Modified: 2021-03-01 00:17 CET (History)
4 users (show)

See Also:
Source RPM: ranger-1.9.2-2.mga7.src.rpm
CVE:
Status comment:


Attachments

Description PC LX 2021-02-26 00:59:49 CET
Description of problem:

In a up-to-date Mageia 7, run ranger and the result is the following:

$ uname -a
Linux marte 5.10.14-desktop-1.mga7 #1 SMP Sun Feb 7 19:36:25 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
$ ranger
Unknown option: - 
usage: /usr/bin/python3 [option] ... [-c cmd | -m mod | file | -] [arg] ...
Try `python -h' for more information.
$ head -n 1 $(which ranger)
#!/usr/bin/python3 -s -O


Removing the one or both parameters (-s -O) from /usr/bin/ranger solves the issue but both parameters seem valid (at least, according to "python3 -h") so I don't actually understand what is the cause.


System: Mageia 7, x86_64, Intel CPU.



Version-Release number of selected component (if applicable):

$ rpm -q ranger
ranger-1.9.2-2.mga7



How reproducible:

Always.



Steps to Reproduce:
1. Installed ranger in a Mageia 7 up-to-date system.
2. Run ranger.
3. See "Unknown option: - " message.
Comment 1 Dave Hodgins 2021-02-26 02:13:27 CET
Confirmed.
$ ranger
Unknown option: - 
usage: /usr/bin/python3 [option] ... [-c cmd | -m mod | file | -] [arg] ...
Try `python -h' for more information.

$ head -n 1 /usr/bin/ranger
#!/usr/bin/python3 -s -O

Strange thing is that running "/usr/bin/python3 -s -O /usr/bin/ranger" from
the command line does work.

CC: (none) => davidwhodgins

Comment 2 Dave Hodgins 2021-02-26 02:19:26 CET
And it works in Mageia 8 which has 1.9.3-3
Assigning to all packagers as there is no dedicated maintainer.
Adding shlomif to cc list as the last person to change it in Mageia 8.

Assignee: bugsquad => pkg-bugs
CC: (none) => shlomif

Comment 3 David GEIGER 2021-02-26 13:01:17 CET
Should be fixed with ranger-1.9.2-2.1.mga7 and ranger-1.9.2-3.1.mga8 in Core/Updates_testing repo!

CC: (none) => geiger.david68210

Comment 4 PC LX 2021-02-26 23:01:22 CET
Installed and tested without issues.


System: Mageia 7, x86_64, Intel CPU.


$ uname -a
Linux marte 5.10.14-desktop-1.mga7 #1 SMP Sun Feb 7 19:36:25 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
$ rpm -q ranger
ranger-1.9.2-2.1.mga7
$ head -n 1 /usr/bin/ranger
#!/usr/bin/python3 -s

Whiteboard: (none) => MGA7-64-OK

Comment 5 David GEIGER 2021-02-27 08:48:15 CET
Assigning to QA now,


Advisory:
========================

Our current ranger package doesn't launch because of a wrong python shebang option, so this update fixes this issue.

========================

Packages in 8/core/updates_testing:
========================
ranger-1.9.3-3.1.mga8.noarch.rpm

Packages in 7/core/updates_testing:
========================
ranger-1.9.2-2.1.mga7.noarch.rpm

Source RPM: 
========================
ranger-1.9.3-3.1.mga8.src.rpm
ranger-1.9.2-2.1.mga7.src.rpm

Assignee: pkg-bugs => qa-bugs

David GEIGER 2021-02-27 08:49:55 CET

Whiteboard: MGA7-64-OK => MGA7TOO MGA7-64-OK
Version: 7 => 8

Comment 6 Dave Hodgins 2021-02-28 05:33:58 CET
Confirmed working in both Mageia 7 and 8. Validating the update.

Keywords: (none) => validated_update
Whiteboard: MGA7TOO MGA7-64-OK => MGA7TOO MGA7-64-OK MGA8-64-OK
CC: (none) => sysadmin-bugs

Comment 7 Dave Hodgins 2021-02-28 05:39:19 CET
Advisory committed to svn.

Keywords: (none) => advisory

Comment 8 Mageia Robot 2021-03-01 00:17:49 CET
An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2021-0028.html

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.