Bug 889491
| Summary: | introduce parseoctal variable for tcsh-6.17* in RHEL6 | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | BillXu <padkiller> | ||||||
| Component: | tcsh | Assignee: | David Kaspar // Dee'Kej <deekej> | ||||||
| Status: | CLOSED WONTFIX | QA Contact: | BaseOS QE - Apps <qe-baseos-apps> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | 6.3 | CC: | g.tavkelishvili, ovasik, pchavan | ||||||
| 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: | 2015-10-19 14:25:32 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: | |||||||||
| Bug Depends On: | |||||||||
| Bug Blocks: | 1075802, 1172231 | ||||||||
| Attachments: |
|
||||||||
|
Description
BillXu
2012-12-21 12:32:17 UTC
030920 -> leading zero means octal -> there is no 9 in octal - and this leads to an error - so this behaviour may be intentional. However, it is worth to investigate why other systems behave differently and to find the reasons for the change. What exact versions of tcsh are you using on those other systems? Also, I think we should update the manpage in rhel, as changing this or backporting tcsh-6.18.00 behavior(parseoctal variable) would cause problems to users. (In reply to comment #3) > What exact versions of tcsh are you using on those other systems? Also, I > think we should update the manpage in rhel, as changing this or backporting > tcsh-6.18.00 behavior(parseoctal variable) would cause problems to users. I just know Fedora7, the tcsh version is tcsh-6.14-15.i386.rpm, but for other system, I need to check next time, the workstation in my customer's office. Could you please tell me the behavior in next version? whan't the solution? I compiled tcsh-6.18-01 from http://www.tcsh.org/, it OK. Well, in upstream: In version up to tcsh-6.14.00(I checked tcsh-6.12.00 and up) the man page says that octal parsing(every string with a leading zero is considered octal number) should work, but it does not. From tcsh-6.15.00 it's removed from the man page. From tcsh-6.16.00 octal parsing works again, but it is not mentioned in the man page. From tcsh-6.17.04 parsing octal numbers is opt-in with the parseoctal variable and this is also in the man page. In rhel-5.8/tcsh-6.14.00 the octal parsing is fixed and works as expected(see bug 438109). This is probably why the reproducer works in Fedora, but not in rhel. In rhel-6.3/tcsh-6.17.00 the octal parsing works but it's not documented(same as upstream). Created attachment 672500 [details]
Proposed man page change
Created attachment 733247 [details]
Added parseoctal variable
Upstream way how to fix this issue. Problem is fixed in f17+.
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate, in the next release of Red Hat Enterprise Linux. Changed the few parameters in the bugzilla to correctly show the requirements.
The if statements are not working because tcsh is considering the numbers mentioned leading with 0 as octal number. This can be considered using variable parseoctal.
~~~
parseoctal
To retain compatibily with older versions numeric variables starting with 0 are not interpreted as octal. Setting this variable enables proper octal parsing.
~~~
Can we get the test packages with the patch?
- Pushpendra
I am really sorry, but our customers expect the default behaviour to remain unchanged. Changing it could break some vital scripts they are using. This new functionality is already present in 'tcsh' of RHEL-7. If you really need this behvaiour, I would politely suggest to consider switching to the current RHEL-7 release. *** Bug 1045961 has been marked as a duplicate of this bug. *** |