-
Notifications
You must be signed in to change notification settings - Fork 883
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
freebsd > 14.0-RELEASE uses /home
not /usr/home
#5850
Comments
Yes, we can upstream it.
Hmm, not sure. One approach would be to avoid carrying the patch forever by could upstreaming this change and then inverting the patch version check so that it only sets Thoughts? |
FWIW the expected EOL for the final FreeBSD 13.x release is April 30, 2026.
Indeed, it seems that would clearly indicate intent. |
…LEASE the softlinked home -> /usr/home has been removed in FreeBSD 14.0-RELEASE and upwards, as the mountpoints are now /home. Sponsored by: SkunkWerks, GmbH Approved by: maintainer Differential Revision: https://reviews.freebsd.org/D47338 Upstream Issue: canonical/cloud-init#5850
…LEASE the softlinked home -> /usr/home has been removed in FreeBSD 14.0-RELEASE and upwards, as the mountpoints are now /home. Sponsored by: SkunkWerks, GmbH Approved by: maintainer Differential Revision: https://reviews.freebsd.org/D47338 Upstream Issue: canonical/cloud-init#5850 (cherry picked from commit 00a3688)
In upstream the move of
/usr/home
to/home
is documented, and there are several prior commitsthat update the machinery during the installer and elsewhere.
This needs to be adjusted in cloud-init also, but only > FreeBSD 14.0-RELEASE:
cloud-init/cloudinit/distros/freebsd.py
Line 38 in 96a07fb
Currently I'm proposing to address this as a FreeBSD ports patch, where we have
tooling to accommodate per-version patching in the ports tree:
https://reviews.freebsd.org/D47338
Should this be upstreamed to cloud-init?
If so, what sort of trick would you suggest to make this OS version-aware?
The text was updated successfully, but these errors were encountered: