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#77876 - perf 6.2-1 regresses perf script command (invalid script extension/invalid language specifier)
Attached to Project:
Community Packages
Opened by M Henning (drawoc) - Thursday, 16 March 2023, 19:01 GMT
Last edited by Toolybird (Toolybird) - Thursday, 16 March 2023, 20:51 GMT
Opened by M Henning (drawoc) - Thursday, 16 March 2023, 19:01 GMT
Last edited by Toolybird (Toolybird) - Thursday, 16 March 2023, 20:51 GMT
|
DetailsDescription:
perf 6.2-1 can no longer run `perf script` with python scripts. Downgrading the package to 6.1-1 resolves the issue. The easiest way to see the issue is to run `perf script -s lang`, which lists available languages on 6.1: $ perf script -s lang Scripting language extensions (used in perf script -s [spec:]script.[spec]): Perl [Perl] pl [Perl] Python [Python] py [Python] but doesn't list anything on 6.2: $ perf script -s lang Scripting language extensions (used in perf script -s [spec:]script.[spec]): Trying to actually run a script on 6.2-1 always gives me either 'invalid script extension' or `invalid language specifier` depending on how I invoke the script. I haven't figured out if this is an upstream change or a packaging change. |
This task depends upon
Closed by Toolybird (Toolybird)
Thursday, 16 March 2023, 20:51 GMT
Reason for closing: Duplicate
Additional comments about closing: FS#77873
Thursday, 16 March 2023, 20:51 GMT
Reason for closing: Duplicate
Additional comments about closing:
FS#77873- sorry