On Aug 11, 2025, at 09:12, Cy Schubert <cy.schub...@cschubert.com> wrote:
> In message <ajovayrytlhtr...@freefall.freebsd.org>, Lexi Winter writes: >> >> >> --wIXzWfAGt3+JA0ql >> Content-Type: text/plain; charset=us-ascii >> Content-Disposition: inline >> >> Mark Millard: >>> # ls /usr/local/poudriere/jails/main-amd64/usr/libexec/krb5kdc >>> ls: /usr/local/poudriere/jails/main-amd64/usr/libexec/krb5kdc: No such file >> or directory >> >> this is probably caused by not having the FreeBSD-kerberos-kdc package >> installed in the jail. either install it (or recreate the jail), or >> update to ports d30d5dfae517 or later which no longer uses >> /usr/libexec/krb5kdc to determine the base Kerberos version. >> >> you also need to be running src 0c13e9c3c464 or later; see [0], but in >> short if you don't have /usr/libdata/pkgconfig/mit-krb5.pc in your jail >> then the jail is too old. >> >> [0] https://lists.freebsd.org/archives/freebsd-ports/2025-August/008256.html. >> > > > How was the jail built? I assumed you built yours from source like I do. If > installed using pkgbase check the above. The jail has been around for a while and so was not only created but has had updates too. Creation (some time ago) was via: # cat ~/poud-jail-create-main-amd64.sh #! /bin/sh poudriere jail -c -jmain-amd64 -aamd64 -U https://pkg.freebsd.org -mpkgbase=base_latest -v 15 -X That does not do a source based build of its own. It just implicitly uses the standard pre-built pkgbase materials from: https://pkg.freebsd.org/FreeBSD:15:amd64/ The updates to the jail's world have been via: # poudriere jail -j main-amd64 -u That also does not do a source based build of its own. It just implicitly uses the standard pre-built pkgbase materials from the same place. Looking at the scripts, it looks to me like the update is done via package's update and upgrade commands. In other words, any insufficient content was from upstream of my context. https://pkg.freebsd.org/FreeBSD:15:amd64/base_latest/?C=M&O=D indicates 2025-Aug-11 11:29 UTC currently. I'll need to be sure a build has been released that has all the recent/required changes before I try another round of updates: so timed after the commits sufficiently. I really wish that there was a way to look up what commit the available release is based on before trying to upgrade (base_latest in this context). === Mark Millard marklmi at yahoo.com
