[Bug 1832257] Re: regression: sudo returns exit code 0 if child is killed with SIGTERM
Marc Deslauriers
marc.deslauriers at canonical.com
Mon Jun 10 19:38:58 UTC 2019
Oh wow, I'm not sure how that happened. I'll release an update for this.
** Changed in: sudo (Ubuntu)
Status: New => Confirmed
** Changed in: sudo (Ubuntu)
Assignee: (unassigned) => Marc Deslauriers (mdeslaur)
** Also affects: sudo (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: sudo (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: sudo (Ubuntu Xenial)
Status: New => Confirmed
** Changed in: sudo (Ubuntu Xenial)
Assignee: (unassigned) => Marc Deslauriers (mdeslaur)
** Changed in: sudo (Ubuntu Xenial)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to sudo in Ubuntu.
https://bugs.launchpad.net/bugs/1832257
Title:
regression: sudo returns exit code 0 if child is killed with SIGTERM
Status in sudo package in Ubuntu:
Fix Released
Status in sudo source package in Xenial:
Confirmed
Bug description:
hey there- it looks like we accidentally removed the patch that fixed
this problem when releasing sudo 1.8.16-0ubuntu1.6 -
https://git.launchpad.net/ubuntu/+source/sudo/commit/?h=ubuntu/xenial-
updates&id=15345b19b82f587498573b38554e24ec0ab816cb
note that `terminate-with-commands-signal.patch` is removed from
debian/patches/series in that commit
and the behavior described in the original bug (LP 1686803) has
returned in xenial.
can we get this back into the current sudo package? the fix still
exists upstream so it feels like this was an accidental reversion.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1832257/+subscriptions
More information about the foundations-bugs
mailing list