Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#61899 - [parallel] Process name of parallel should be parallel instead of perl
Attached to Project:
Community Packages
Opened by Yichao Zhou (zhou13) - Saturday, 02 March 2019, 09:18 GMT
Last edited by Balló György (City-busz) - Monday, 18 March 2019, 08:01 GMT
Opened by Yichao Zhou (zhou13) - Saturday, 02 March 2019, 09:18 GMT
Last edited by Balló György (City-busz) - Monday, 18 March 2019, 08:01 GMT
|
DetailsDescription:
Process name of parallel should be parallel instead of perl. This can be done by changing #!/usr/bin/env perl to #!/usr/bin/perl in /usr/bin/parallel Additional info: * package version(s) community/parallel 20181222-1 Steps to reproduce: 1. $ parallel sleep 10 ::: 1 2. $ killall parallel parallel: no process found |
This task depends upon
have you contacted upstream about the issue?
But I'm sure there are many thousands of scripts installed by Arch Linux, AUR packages, or manually, which contain shebang lines that are, arguably, completely correct, but show up as the wrong process or whatever. Should we modify all those too, because upstream has made the wrong decision?
I would advise instead using pkill -f which is a lot more flexible than killall. It is more scalable, works everywhere without requiring modifications to packages, etc.