Community Packages

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!
Tasklist

FS#48103 - transmission-remote-cli-1.7.1-1 PKGBUILD incorrectly sets the #! to "python22"

Attached to Project: Community Packages
Opened by George Angelopoulos (l4than-d3vers) - Tuesday, 09 February 2016, 00:01 GMT
Last edited by Doug Newgard (Scimmia) - Tuesday, 09 February 2016, 02:50 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To No-one
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

transmission-remote-cli-1.7.1-1 PKGBUILD incorrectly sets the #! to "python22"

or to more accurately address the direct issue as seen from the user:

$ transmission-remote-cli
/usr/bin/env: python22: No such file or directory


Additional info:
I'm guessing the upstream shebang changed from "python" to "python2".
In your PKGBUILD, in build() you are replacing "python" with "python2" so we end up with "python22".
You can probably get rid of the entire build() function now.
Cheers

Simple workaround:
Edit /usr/bin/transmission-remote-cli and change the first line from:

#!/usr/bin/env python22
to

#!/usr/bin/env python2

Since the program doesn't run at all without the workaround, I've marked this as high.
This task depends upon

Closed by  Doug Newgard (Scimmia)
Tuesday, 09 February 2016, 02:50 GMT
Reason for closing:  Fixed
Additional comments about closing:  transmission-remote-cli 1.7.1-2
Comment by George Angelopoulos (l4than-d3vers) - Tuesday, 09 February 2016, 01:51 GMT
Looks like it's fixed in transmission-remote-cli-1.7.1-2

Loading...