-
Notifications
You must be signed in to change notification settings - Fork 349
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
Update freebsd pkg version #15289
base: main
Are you sure you want to change the base?
Update freebsd pkg version #15289
Conversation
cc @Thefrank |
As long as the packages end up the correct place, it should be OK. As a heads up: 13.3 is EOL. You might want to bump it to 13.4. |
Found a better fix with |
Thanks for the info @Thefrank, dropped EOL'd 13 (ref: https://www.freebsd.org/releases/). |
13.x can be dropped if desired but for now I think it should stay. I really wish FreeBSD did a better job of explaining some of their terms. "Legacy" here does not mean EOL it is more of "no new features. Good for those that want to remain conservative with updates". The in-support with estimated EOL dates are here: https://www.freebsd.org/security/#sup |
+1 I did argue, fairly strongly, against use of the word legacy.
Some production-quality legacy supported releases probably do gain features, however at https://www.freebsd.org/ neither of the legacy releases are classified as production. |
We had to revert it in #14408.
Although freebsd/pkg#2232 is still unresolved, I've figured that-r
(rootdir) option is unnecessary. The packages are resolved at the correct place.Found a better fix with -r and just adjusting the fingerprint path. :)
cc @wfurt, it fixes a build issue on arm64 host (e.g. running it inside ubuntu arm64 container on M1 mac).