-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"pkg: unknown command: bootstrap" if system has an update pkg #6
Comments
What pkg version are you using? I cannot reproduce this issue or see why it would happen. When I run |
Hi Isaac, this is in a different box:
|
Ok, I can reproduce the issue. |
Currently, this causes pkg to exit with the very unhelpful error message "pkg: unknown command: bootstrap" This used to have the same behavior as `pkg bootstrap`in older versions of pkg prior to commit fb9b331. This commit restores the old behavior of `pkg bootstrap -y` and does not affect the behavior if `-f` is passed. Sponsored by: The FreeBSD Foundation References: ifreund/pkgbasify#6
Currently, this causes pkg to exit with the very unhelpful error message "pkg: unknown command: bootstrap" This used to have the same behavior as `pkg bootstrap`in older versions of pkg prior to commit fb9b331. This commit restores the old behavior of `pkg bootstrap -y` and does not affect the behavior if `-f` is passed. Sponsored by: The FreeBSD Foundation References: ifreund/pkgbasify#6
Thanks for the bug report, this should be working now :) |
Currently, this causes pkg to exit with the very unhelpful error message "pkg: unknown command: bootstrap" This used to have the same behavior as `pkg bootstrap`in older versions of pkg prior to commit fb9b331. This commit restores the old behavior of `pkg bootstrap -y` and does not affect the behavior if `-f` is passed. Sponsored by: The FreeBSD Foundation References: ifreund/pkgbasify#6
Hi,
if system has a pkg updated, running pkgbasify I got:
pkg: unknown command: bootstrap
Solution:
pkg delete -f pkg
Maybe this should be in the README file.
The text was updated successfully, but these errors were encountered: