tag 683671 - patch fixed-upstream tag 779416 + patch fixed-upstream thanks Hi Vincent,
Er, it appears that I misunderstood the discussion in the bug history. I had been fixing a bug where an INT signal handler improperly did not reraise INT against itself, and had Martin Cracauer's article on INT, QUIT and shell signal handlers[1] fresh in my brain. When I addressed the bad signal handler issue I was startled that dash did not behave according to my expectations. I prepared to file a bug against dash, and when scanning the existing bug list I found this one and, perhaps hastily, concluded that it was the same issue. Re-reviewing the list of open bugs against dash, it looks like I should have stumbled across #779416 instead. I apologize for my error. Thanks for the clarification. Cheers! [1] https://www.cons.org/cracauer/sigint.html -- G. Branden Robinson Trustworthy Systems Group, CSIRO's Data61 "Every good idea will be discovered twice: once by a logician and once by a computer scientist." - Philip Wadler ________________________________________ From: Vincent Lefevre <vinc...@vinc17.net> Sent: Tuesday, February 11, 2020 13:59 To: Robinson, Branden (Data61, Kensington NSW); 683671-qu...@bugs.debian.org Cc: cont...@bugs.debian.org; 683...@bugs.debian.org; 683671-submit...@bugs.debian.org; jcris...@debian.org Subject: Re: Bug#683671: dash: 'set -e'+'trap' malfunction is fixed in upstream git On 2020-02-11 02:36:32 +0000, Robinson, Branden (Data61, Kensington NSW) wrote: > # hello, control, been a while... > tag 683671 + patch fixed-upstream > thanks > > Hi Andrej et al., > > After independently encountering and then debugging this problem to the point > where I had a fix, I learned that Antonio Ospite had come up with an > identical one (modulus whitespace) over a year ago[1]. I've attached a copy. > > It really sucks that dash has had this bug for 12 years, given that: > 1. It's Debian's default /bin/sh; > 2. We're required by Policy to 'set -e' in our maintainer scripts[2]; and > 3. Script authors generally don't write signal handlers for fun--they do it > because they need to clean up or roll back some activity, and this bug > utterly frustrates their efforts. [...] I don't see the relation with bug 683671. -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
