Error bootstrapping on a NanoBSD build
Karl Denninger
karl at denninger.net
Thu Jun 15 14:14:38 UTC 2017
On 6/14/2017 22:55, Karl Denninger wrote:
> I'm attempting to bring up pkg packages on a NanoBSD build for one of
> the PCEngines devices, and running into something I've not seen before.
>
> The image builds perfectly well (FreeBSD-11) and runs, but if I try to
> use the cust_pkgng customize command it fails with a complaint thus:
>
> + touch /pics/Crochet-work-AMD/obj/_.w/usr/local/etc/pkg.conf
> + grep -Eiq '^PKG_DBDIR:.*'
> /pics/Crochet-work-AMD/obj/_.w/usr/local/etc/pkg.conf
> + echo 'PKG_DBDIR: "/var/db/pkg"'
> + [ ! -d /usr/src/tools/tools/nanobsd/Pkg ]
> + find -s /usr/src/tools/tools/nanobsd/Pkg -iname 'pkg-*'
> + basename /usr/src/tools/tools/nanobsd/Pkg/pkg-1.10.1.txz
> + _NANO_PKG_PACKAGE=pkg-1.10.1.txz
> + [ -z pkg-1.10.1.txz -o ! -f
> /usr/src/tools/tools/nanobsd/Pkg/pkg-1.10.1.txz ]
> + NANO_PACKAGE_LIST='pkg-1.10.1.txz *'
> + mkdir -p /pics/Crochet-work-AMD/obj/_.w/_.p
> + mount -t nullfs -o noatime -o ro /usr/src/tools/tools/nanobsd/Pkg
> /pics/Crochet-work-AMD/obj/_.w/_.p
> + trap 'umount /pics/Crochet-work-AMD/obj/_.w/_.p ; rm -rf
> /pics/Crochet-work-AMD/obj/_.w/_.p' 1 2 15 EXIT
> + echo 'pkg-1.10.1.txz *'
> + awk '{ print NF }'
> + todo=2
> + echo '=== TODO: 2'
> === TODO: 2
> + echo 'pkg-1.10.1.txz *'
> pkg-1.10.1.txz *
> + echo '==='
> ===
> + CR 'env ASSUME_ALWAYS_YES=YES PKG_DBDIR=/var/db/pkg
> SIGNATURE_TYPE=none /usr/sbin/pkg add /_.p/pkg-1.10.1.txz'
> + chroot /pics/Crochet-work-AMD/obj/_.w /bin/sh -exc 'env
> ASSUME_ALWAYS_YES=YES PKG_DBDIR=/var/db/pkg SIGNATURE_TYPE=none
> /usr/sbin/pkg add /_.p/pkg-1.10.1.txz'
> + env 'ASSUME_ALWAYS_YES=YES' 'PKG_DBDIR=/var/db/pkg'
> 'SIGNATURE_TYPE=none' /usr/sbin/pkg add /_.p/pkg-1.10.1.txz
> Installing pkg-1.10.1...
> Extracting pkg-1.10.1: .......... done
> + CR 'env ASSUME_ALWAYS_YES=YES PKG_DBDIR=/var/db/pkg
> SIGNATURE_TYPE=none /usr/sbin/pkg add /_.p/Files'
> + chroot /pics/Crochet-work-AMD/obj/_.w /bin/sh -exc 'env
> ASSUME_ALWAYS_YES=YES PKG_DBDIR=/var/db/pkg SIGNATURE_TYPE=none
> /usr/sbin/pkg add /_.p/Files'
> + env 'ASSUME_ALWAYS_YES=YES' 'PKG_DBDIR=/var/db/pkg'
> 'SIGNATURE_TYPE=none' /usr/sbin/pkg add /_.p/Files
> pkg: /_.p/Files: No such file or directory
> pkg: Was 'pkg install /_.p/Files' meant?
>
> Failed to install the following 1 package(s): /_.p/Files
> + umount /pics/Crochet-work-AMD/obj/_.w/_.p
> + rm -rf /pics/Crochet-work-AMD/obj/_.w/_.p
> + echo 'NANO RM -rf /pics/Crochet-work-AMD/obj/_.w/_.p'
> NANO RM -rf /pics/Crochet-work-AMD/obj/_.w/_.p
> + uname -r
> + command rm -x -rf /pics/Crochet-work-AMD/obj/_.w/_.p
>
> OK, so I gave up on having the packages I wanted loaded as part of the
> image I built, mounted the root directory writeable, and tried to
> bootstrap it normally:
>
> root@:~ # pkg bootstrap
> The package management tool is not yet installed on your system.
> Do you want to fetch and install it now? [y/N]: y
> Bootstrapping pkg from
> pkg+http://pkg.FreeBSD.org/FreeBSD:11:amd64/latest, please wait...
> pkg: Error loading revoked certificates
> root@:~ #
>
> I can't find a reason for this to fail, but it certainly does.... and
> there's nothing in the docs telling me WHY it's failing.
>
> Where is whatever it is looking for and not finding supported to be, and
> why would it be missing if I'm bootstrapping from zero?
>
This is related to what appears to be a bug in the Nanobsd script and
there's a PR and patch out for it. Applying same fixed the "included"
problem.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219405
--
Karl Denninger
karl at denninger.net <mailto:karl at denninger.net>
/The Market Ticker/
/[S/MIME encrypted email preferred]/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2993 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.freebsd.org/pipermail/freebsd-pkg/attachments/20170615/2cc4872e/attachment.bin>
More information about the freebsd-pkg
mailing list