PKG wrong ABI in jail

Hi - I have a poudriere build machine that was recently upgraded to 10.0-RELEASE. The build machine also has a couple of jails which I manage with ezjail. I updated the base jail to 10.0-RELEASE and also rebuilt my packages for 10.0-RELEASE. I use pkg inside the jails to install packages built on the host (the package directory is mounted inside the jail so pkg can find a file-based repository). I updated my /usr/local/etc/pkg/repo/myrepo-.conf file to point to the 10.0 packages.

Anyway, now when I try to do "pkg upgrade" within one of the jails I get this:

pkg: wrong architecture: freebsd:10:x86:64 instead of freebsd:9:x86:64

Here the output of pkg -vv:

root@web:/root # pkg -vv
Version : 1.2.5
PACKAGESITE :
PKG_DBDIR : /var/db/pkg
PKG_CACHEDIR : /var/cache/pkg
PORTSDIR : /usr/ports
PUBKEY :
HANDLE_RC_SCRIPTS : no
ASSUME_ALWAYS_YES : no
REPOS_DIR : [
/etc/pkg/,
/usr/local/etc/pkg/repos/,
]
PLIST_KEYWORDS_DIR :
SYSLOG : yes
AUTODEPS : yes
ABI : freebsd:9:x86:64
DEVELOPER_MODE : no
PORTAUDIT_SITE : http://portaudit.FreeBSD.org/auditfile.tbz
VULNXML_SITE : http://www.vuxml.org/freebsd/vuln.xml.bz2
MIRROR_TYPE : SRV
FETCH_RETRY : 3
PKG_PLUGINS_DIR : /usr/local/lib/pkg/
PKG_ENABLE_PLUGINS : yes
PLUGINS : [
]
DEBUG_SCRIPTS : no
PLUGINS_CONF_DIR : /usr/local/etc/pkg/
PERMISSIVE : no
REPO_AUTOUPDATE : yes
NAMESERVER :
EVENT_PIPE :
FETCH_TIMEOUT : 30
UNSET_TIMESTAMP : no
SSH_RESTRICT_DIR :
PKG_SSH_ARGS :
PKG_ENV : {
}
DISABLE_MTREE : no
DEBUG_LEVEL : 0
ALIAS : {
}

Repositories:
Server: {
url : "pkg+file:///var/www/poudriere/packages/REL10amd64-default-server",
enabled : yes,
mirror_type : "SRV"
}

You can see that the ABI is still set to FreeBSD 9 but I can't figure out how to change that. Any suggestions would be greatly appreciated. Thanks!
 
According to pkg.conf(5) the ABI is determined by checking /bin/sh (unless, of course, it was explicitly set in pkg.conf).

Are you sure those jails are up-to-date? What does file /bin/sh return?
 
Indeed, I tried updating the jails again just after posting here and it seemed to update (which I thought it had completed before but apparently it didn't or I didn't do it right or something). Regardless, once I ran the ezjail update again, restarted the jails, and everything worked. Those PEBKAC issues are the worst! :-) Thanks for the reply.
 
Back
Top