"pkg: pkg is not installed" even after installing it
perryh at pluto.rain.com
Mon Jan 11 10:41:03 UTC 2016
Matthew Seaman <matthew at freebsd.org> wrote:
> On 11/01/2016 03:10, Perry Hutchison wrote:
> > That doesn't produce any output, either. However, after mounting
> > tmpfs on /var/db/pkg and /var/cache, I got:
> Hmmm... that's certainly a bug. Could you open an issue at
> https://github.com/freebsd/pkg/issues please, explaining exactly
> what you did and what happened (or didn't as the case may be)?
> pkg(8) shouldn't die quietly in those or any circumstances.
I will try to get to it later this week.
> > # chroot -u 0 -g 0 -G 105,0,5,20,25 /mnt pkg-static add /usr/local/pkg/pkg.txz
> > Installing pkg-1.5.4...
> > Extracting pkg-1.5.4: 100%
> > ldconfig: mkstemp(/var/run/ld-elf.so.hints.6wHhnd): Read-only file system
> > pkg-static: POST-INSTALL script failed
> > Message for pkg-1.5.4:
> > If you are upgrading from the old package format, first run:
> > # pkg2ng
> > # chroot -u 0 -g 0 -G 105,0,5,20,25 /mnt pkg -N
> > pkg: 1 packages installed
> > This time it installed a bunch of stuff in /usr/local and a
> > "local.sqlite" in /var/db/pkg ...
> That looks to have worked.
Any concern about the POST-INSTALL failure due to /var/run being
read-only? (That one is not as simple to fix as /var/cache and
/var/db/pkg, since the memstick's /var/run is not empty.)
> Curious as to why you're using an older version of pkg there --
> we're up to 1.6.2 nowadays.
It is the version I downloaded from
on 12/21 (when I started on this exercise).
If I'm remembering correctly, .../release_2 appeared to be the area
which most nearly corresponded to what would have been current when
10.2 was released. I have gotten burned before by trying to install
package sets that are newer than the release on which they are being
installed -- sticking with what presumably worked at release time
seems safer, at least to get an initial, working configuration.
More information about the freebsd-questions