Bug#1025915: skill: -p $pid seems broken

2023-01-05 Thread Craig Small
On Thu, 5 Jan 2023 at 18:26, Chris Hofstaedtler wrote: > Right. For the avoidance of doubt, if you think removing it is a > better option, from my PoV, please do so. It would be nice, but we're sort-of locked in for the "user API". I would rationalise the ps command line parsing first. If you're

Bug#1025915: skill: -p $pid seems broken

2023-01-04 Thread Chris Hofstaedtler
Hi Craig, * Craig Small : > Thanks for your bug report. skill is one of those programs that isn't > used or loved much, but still hangs around. That being said, it shouldn't > have bugs like this! Right. For the avoidance of doubt, if you think removing it is a better option, from my PoV,

Bug#1025915: skill: -p $pid seems broken

2022-12-11 Thread Craig Small
Hi Chris, Thanks for your bug report. skill is one of those programs that isn't used or loved much, but still hangs around. That being said, it shouldn't have bugs like this! When the program was converted to use the new API, the bit of code that actually checks there is a match against the

Bug#1025915: skill: -p $pid seems broken

2022-12-11 Thread Chris Hofstaedtler
Package: procps Version: 2:4.0.2-2 Dear Maintainer, skill's -p flag seems to have stopped working as a selector. In version 2:3.3.17-5, this did what I expected: % echo $$ 3004161 % skill -n -p $$ 3004161 In 2:4.0.2-2 in unstable: % echo $$ 50078 % skill -n -p $$ [list of ALL pids, including