pkg broken in VirtualBox-4.3.12 jail in 9.3-STABLE-201511040813

[ses1984]

Summary

I was able to fix this by upgrading pkg through portsnap, as suggested here. I don't really like the portsnap solution because it takes a long while to fetch/extract, and it extracts almost 2GB of data.

My remaining questions are:

• Is this expected?
  
• What's the root cause?
• Is there a better solution?
• How do I clean up completely after using portsnap?

Problem description

The following was executed in a brand new jail using the VirtualBox 4.3.12 template.

Code:

root@vbox_test:/ # pkg update
Updating repository catalogue
digests.txz                                                              100% 2091KB   2.0MB/s   1.4MB/s   00:01
packagesite.txz                                                          100% 5410KB   2.6MB/s   2.1MB/s   00:02
pkg: package field incomplete: comment
Incremental update completed, 24621 packages processed:
21348 packages updated, 2174 removed and 3273 added.
pkg: Unable to find catalogs
root@vbox_test:/ # pkg update -f
Updating repository catalogue
digests.txz                                                              100% 2091KB   2.0MB/s   2.0MB/s   00:01
packagesite.txz                                                          100% 5410KB   5.3MB/s   3.3MB/s   00:01
pkg: package field incomplete: comment
Incremental update completed, 24621 packages processed:
21348 packages updated, 2174 removed and 3273 added.
pkg: Unable to find catalogs

Here's the output of `pkg -vv`

Code:

root@vbox_test:/ # pkg -vv

Version                 : 1.2.7_2
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:
  FreeBSD: {
    url             : "pkg+http://pkg.FreeBSD.org/freebsd:9:x86:64/latest",
    enabled         : yes,
    mirror_type     : "SRV"
  }

Fix

Code:

portsnap fetch
portsnap extract
cd /usr/ports/ports-mgmt/pkg/ && make reinstall clean

 

[danb35]

Short answer is you shouldn't mess with the VirtualBox jail. Don't try to update packages, etc.

 

[ses1984]

What's the long answer?

Ultimately I wanted to install vagrant in the jail. I really don't care about having the latest updates.

 

[danb35]

The long answer, as best I understand it, is that a fair bit of customization was needed to get VirtualBox to run, since it isn't written for FreeBSD (which is also why it's still on 4.3.12, rather than 5.whatever). Updates can break the customization done. I'm not sure if installing Vagrant would cause a problem.