Bug 26734 - isodumper 1.17 fails to start
Summary: isodumper 1.17 fails to start
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: David GEIGER
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-06-05 19:13 CEST by Jani Välimaa
Modified: 2020-06-06 07:33 CEST (History)
1 user (show)

See Also:
Source RPM: isodumper-1.17-1.mga8
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Jani Välimaa 2020-06-05 19:13:38 CEST 
$ isodumper 
Traceback (most recent call last):
  File "/usr/bin/isodumper", line 2, in <module>
    from isodumper import isodumper
  File "/usr/lib/python3.8/site-packages/isodumper/isodumper.py", line 33, in <module>
    imporlib.reload(sys)
NameError: name 'imporlib' is not defined

There's a typo: imporlib vs. importlib.
Comment 1 Lewis Smith 2020-06-05 20:11:25 CEST 
Thanks for the alert.
Assigning to its maintainer DavidG.

Assignee: bugsquad => geiger.david68210

Comment 2 Lewis Smith 2020-06-05 20:13:37 CEST 
I was not quick enough; I have just noticed, typical rapidity:
"Modified Fri Jun 5 17:28:37 2020 UTC (41 minutes ago) by daviddavid
- fix a typo in isodumper.py file (mga#26734)"
so am daring to close this fixed.

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

Comment 3 Jani Välimaa 2020-06-05 20:34:31 CEST 
It needs to be fixed in source code in our git also. Now it was fixed by a patch in our package svn.
Comment 4 Lewis Smith 2020-06-05 20:44:30 CEST 
Alas, I know not about these things. I jumped the gun; thanks for the warning.
Perhaps it is safer to re-open it until what you say has been done. DavidG will close it in due course.

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

Comment 5 David GEIGER 2020-06-06 07:33:56 CEST 
Fixed also in our git.

Status: REOPENED => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.