Bug 1021704
Summary: | decimal/octal problems with mksh | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | jbmorris |
Component: | mksh | Assignee: | Michal Hlavinka <mhlavink> |
Status: | CLOSED DUPLICATE | QA Contact: | BaseOS QE - Apps <qe-baseos-apps> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.4 | ||
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-10-22 08:17:26 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
jbmorris
2013-10-21 20:54:34 UTC
Please beware, that bugzilla is bug tracking tool, nothing more. For support (including questions when/if we update some package) you should open support case at https://access.redhat.com/home There already is bug for decimal/octal numbers, bug #975748. Closing this one as duplicate. > Why is the version of mksh 4 years old? RHEL targets enterprise environments. In such environments unnecessary disruptions should be avoided. This includes different API, behaviour or configuration of any package. What would make one happy, could make tens or hundreds unhappy. That's why we rarely update packages to newer versions, unless there is strong reason (and customer demand). Instead of rebasing packages to newer versions, we backport fixes. *** This bug has been marked as a duplicate of bug 975748 *** I apologize for duplicating a bug, but I did search for mksh first and this didn't come up. I just tried to view bug 975748 and it said I wasn't authorized to view it, so I assume that's why it didn't show up in my search. Just curious why I cannot view that bug. I'd like to know how long it has been open and when you're planning to backport the fix. Some bugs are private because they can contain sensitive information. If you are Red Hat customer, you should use proper support channel (https://access.redhat.com/home) they'd do the search instead of you and inform you about fix availability. Almost certainly (99.9 %), fix for this bug will be in rhel-6.5 update |