|Summary:||ports-mgmt/pkg: @shell keyword is broken: attempt to index a nil value (global 'shell') pkg: lua script failed|
|Product:||Ports & Packages||Reporter:||Christian Ullrich <chris>|
|Component:||Individual Port(s)||Assignee:||freebsd-pkg (Nobody) <pkg>|
|Severity:||Affects Some People||CC:||bapt, daniel.tihanyi, ehaupt, franco, freebsd.org, kevans, pauamma, ross|
Description Christian Ullrich 2020-11-07 15:19:41 UTC
The @shell keyword is broken: # pkg install -f bash Updating packagesite repository catalogue... packagesite repository is up to date. All repositories are up to date. Checking integrity... done (0 conflicting) The following 1 package(s) will be affected (of 0 checked): Installed packages to be REINSTALLED: bash-5.0.18_3 Number of packages to be reinstalled: 1 Proceed with this action? [y/N]: y [1/1] Reinstalling bash-5.0.18_3... [1/1] Extracting bash-5.0.18_3: 100% pkg: Failed to execute lua script: [string "shell_path = pkg.prefixed_path("bin/bash")..."]:7: attempt to index a nil value (global 'shell') pkg: lua script failed Same for other ports with the @shell keyword (devel/git), same within poudriere testport. The last change to Keywords/shell.ucl replaced the working sh implementation with Lua. I noticed the problem with the second git upgrade since then, so this was the first time pkg tried to run a post-deinstall script that has the Lua implementation. FreeBSD 12.2-RELEASE (releng/12.2), pkg 1.15.10, ports head, amd64.
Comment 1 Kyle Evans 2020-11-07 15:21:13 UTC
I have a PR against PKG that fixes it here: https://github.com/freebsd/pkg/pull/1900
Comment 2 Emanuel Haupt 2020-12-21 07:36:30 UTC
@bapt: do you think you could merge the upstream committed patch? I am getting a lot of reports due to the recent bash updates.
Comment 3 Emanuel Haupt 2020-12-21 17:49:23 UTC
Comment 4 Emanuel Haupt 2020-12-21 17:53:08 UTC
Comment 5 Kubilay Kocak 2020-12-23 02:49:26 UTC
^Triage: Regression in ports/latest only or MFH required?
Comment 6 Emanuel Haupt 2020-12-23 07:32:09 UTC
(In reply to Kubilay Kocak from comment #5) No, the regression is in ports/latest only. 2020Q4 is not affected.