This bug has been copied from bug #498625 and has been proposed to be backported to 5.4 z-stream (EUS).
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2009-1494.html
After the 6.14-14.el5_4.2 update was installed on our Linux systems, the following behavior was observed by tcsh users ... -------- coates-adm: ls [0-9]*/*.coor 128/bpti_out.coor 320/bpti_out.coor 448/bpti_out.coor 192/bpti_out.coor 32/bpti_out.coor 64/bpti_out.coor 256/bpti_out.coor 384/bpti_out.coor 96/bpti_out.coor coates-adm: ls [0-9]*/*.{BAK,coor,log,pbsid,vel} ls: No match. -------- Basically, anyone with scripts using [] or {} operations in filename matching cannot expect behavior consistent with previous versions. In the above example, the files listed by the first ls would have been listed within the group found by the second ls, using the pre-update tcsh. The second ls fails any time one of the {} members is not present in any of the directories. This appears to be a new bug to me. It's causing problems for various users. Best regards, Phil
The fix for this regression is already on the way. See bug 547529 for more details about the issue. You can expect the new tcsh package very soon.