Bug 518187
Summary: | Package installs broken symlinks | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Steve Snyder <swsnyder> |
Component: | lam | Assignee: | Doug Ledford <dledford> |
Status: | CLOSED WONTFIX | QA Contact: | Red Hat Kernel QE team <kernel-qe> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 5.3 | ||
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2011-10-04 21:43:47 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Steve Snyder
2009-08-19 11:53:26 UTC
This bug is exceedingly stale. As it turns out, the problem is that lam is split up into lam, lam-devel, and lam-libs. The symlinks should have been part of lam-devel (which contains the mpi programs the symlinks point to), but that was missed. The easy workaround of course is to just install lam-devel and there are no dangling symlinks. Given that I doubt lam will ever see another update in rhel5, and given that this has such an easy workaround and no real ill side-effects, I'm closing this bug out as WONTFIX. |