Bug 1338986
| Summary: | Output of tcsh builtin command "jobs" now goes to stderror. | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Paulo Andrade <pandrade> | |
| Component: | tcsh | Assignee: | David Kaspar // Dee'Kej <deekej> | |
| Status: | CLOSED ERRATA | QA Contact: | Iveta Wiedermann <isenfeld> | |
| Severity: | medium | Docs Contact: | Lenka Špačková <lkuprova> | |
| Priority: | urgent | |||
| Version: | 6.8 | CC: | bnater, fkrska, karlamrhein, mkolaja | |
| Target Milestone: | rc | Keywords: | Patch, Regression, Reproducer, ZStream | |
| Target Release: | --- | |||
| Hardware: | All | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | tcsh-6.17-36.el6 | Doc Type: | Release Note | |
| Doc Text: |
Output of "jobs" in *tcsh* is now correctly displayed to stdout
Previously, the output of the "jobs" built-in command was displayed to standard error instead of standard output. This bug has been fixed, and the output of "jobs" is now correctly displayed to stdout.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1338987 1357127 (view as bug list) | Environment: | ||
| Last Closed: | 2017-03-21 11:18:09 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: | 1357127 | |||
|
Description
Paulo Andrade
2016-05-23 20:22:48 UTC
Yes, this is definitely a regression. I will be contacting upstream about this during today. Upstream has been informed: http://mx.gw.com/pipermail/tcsh-bugs/2016-May/001048.html Here are the commits that should fix the regression (from upstream): https://github.com/tcsh-org/tcsh/commit/17d484bfacf46f https://github.com/tcsh-org/tcsh/commit/50029cb5d4fe43 I have closed this by mistake (thought this was fixed in RHEL 6.7.z), reopening... Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2017-0731.html |