Bug 916386 - Command substitution return code NOT same as from command executed.
Summary: Command substitution return code NOT same as from command executed.
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: tcsh
Version: 17
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Ondrej Vasik
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-28 00:00 UTC by Bertil Askelid
Modified: 2013-07-09 07:31 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-09 07:31:33 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Bertil Askelid 2013-02-28 00:00:32 UTC
Description of problem:

   Return code from command executed inside a command substitution
   is not set as the return code of the command substitution:

		~> set r = (`false`); echo $?
		0

   This is in the latest version as of date (tcsh-6.17-18). It works
   fine in a slightly older version tcsh-6.17-15:

		~> set r = (`false`); echo $?
		1

   This change in behavior break a lot of existing tcsh script code.

Version-Release number of selected component (if applicable):

   tcsh-6.17-18

How reproducible:

   Always.

Steps to Reproduce:

   1. set r = (`false`); echo $?
  
Actual results:

   0

Expected results:

   1

Additional info:

Comment 1 Fedora Admin XMLRPC Client 2013-03-26 16:51:05 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 2 Fedora Admin XMLRPC Client 2013-03-27 08:20:10 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 3 Fedora Update System 2013-04-05 08:47:25 UTC
tcsh-6.17-19.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/tcsh-6.17-19.fc17

Comment 4 Fedora Update System 2013-04-07 00:31:15 UTC
Package tcsh-6.17-19.fc17:
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing tcsh-6.17-19.fc17'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-5067/tcsh-6.17-19.fc17
then log in and leave karma (feedback).

Comment 5 Bertil Askelid 2013-04-07 01:00:19 UTC
Unable to verify fix as I can't find fixed rpm, please advice:

~> sudo yum update --enablerepo=updates-testing tcsh-6.17-19.fc17
Loaded plugins: langpacks, presto, refresh-packagekit
adobe-linux-i386                                         |  951 B     00:00     
adobe-linux-x86_64                                       |  951 B     00:00     
google-chrome                                            |  951 B     00:00     
updates/17/x86_64/metalink                               |  15 kB     00:00     
updates                                                  | 4.6 kB     00:00     
updates-testing/17/x86_64/metalink                       |  14 kB     00:00     
updates-testing                                          | 4.6 kB     00:00     
updates-testing/primary_db                               | 860 kB     00:01     
updates-testing/group_gz                                 | 439 kB     00:00     
No Match for argument: tcsh-6.17-19.fc17
No package tcsh-6.17-19.fc17 available.
No Packages marked for Update

Comment 6 Pavel Raiskup 2013-04-08 15:15:58 UTC
Hi Bertil, 

have you tried run the `yum clean [dbcache|...|all]`?

There is possible that the mirror you are using is not synced yet..  You may
then download the file here (mirror chosen very randomly):

   $ wget http://spo.linux.edu.lv/fedora/updates/testing/17/x86_64/tcsh-6.17-19.fc17.x86_64.rpm
   $ sudo yum install ./tcsh-6.17-19.fc17.x86_64.rpm

Pavel

Comment 7 Bertil Askelid 2013-04-08 15:53:29 UTC
Yes, I did do "yum clean all" -- no difference. However, the "wget"
worked. I tested your fixed version tcsh-6.17-19.fc17.x86_64.rpm. Works
just fine -- problem solved! Thanks a lot!

Comment 8 Fedora End Of Life 2013-07-04 07:43:22 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 10 Ondrej Vasik 2013-07-09 07:31:33 UTC
Unfortunately, only maintainer can push update to stable and Frido can't do that anymore. Closing NEXTRELEASE as it doesn't seem likely to get this updated via karma mechanism.


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