1011484 – Typo in environment module of openmpi-devel 1.10.3

Bug 1011484 - Typo in environment module of openmpi-devel 1.10.3

Summary: Typo in environment module of openmpi-devel 1.10.3

Status:	RESOLVED FIXED

Alias:	None

Product:	openSUSE Distribution
Classification:	openSUSE
Component:	Development (show other bugs)
Version:	Leap 42.2
Hardware:	x86-64 Other

Priority:	P3 - Medium Severity: Normal with 5 votes (vote)
Target Milestone:	---
Assignee:	Philipp Thomas
QA Contact:	E-mail List

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:	1012380
	Show dependency tree / graph

Clone This Bug

Reported:	2016-11-21 20:05 UTC by Forgotten User 94j2Zm_jz-
Modified:	2017-11-09 15:40 UTC (History)
CC List:	5 users (show)

See Also:
Found By:	---
Services Priority:
Business Priority:
Blocker:	---
Marketing QA Status:	---
IT Deployment:	---

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

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

Description Forgotten User 94j2Zm_jz- 2016-11-21 20:05:03 UTC

There is a typo in 

/usr/share/modules/gnu-openmpi/1.10.3 

second line should be 

proc ModulesHelp { } {

but actually it is 

[5~proc ModulesHelp { } {

Comment 1 Philipp Thomas 2016-11-22 06:53:56 UTC

Yep, the typo is also in mvapich2.

Comment 2 Philipp Thomas 2016-12-27 12:47:11 UTC

Fixed package was submitted for SLE-12-SP2 so it should make its way into Leap.

Comment 3 Forgotten User -z4SIGzSs7 2017-02-02 08:51:10 UTC

The fix is over a month old and still not in Leap.
For a typo that completely breaks the default usage mode of the package this seems long. Any ETA?

Comment 4 Philipp Thomas 2017-02-02 10:14:23 UTC

Should be rather soon.

Comment 5 Forgotten User -z4SIGzSs7 2017-03-01 10:12:55 UTC

Sorry to bother you again, but it appears there is still no fix published and in my view the bug is quite severe, since it makes the package unusable via modules, which is the recommended way to use it afaik.

Would it be possible to get a timeline for this patch?

Comment 6 Philipp Thomas 2017-03-01 14:21:52 UTC

I have no idea how Leap is handling this. Ludwig?

Comment 7 Ludwig Nussel 2017-03-01 17:16:03 UTC

updates get pushed to Leap once released for SLE. Low severity issues may take a while to pass the process for SLE though. So if there is need to get the fix into Leap earlier please talk to maintenance (maintenance.opensuse.org) to reprioritize or take a shortcut.