Bruce Nagel wrote:
> I think there is still an issue in that pkgin refused to install it,
> and I wonder why I had to manually install libraries that it should
> have been pulling in automagically (as I understand it) but at least
> I have a working office suite again.
A simple `make update`
On Sun, 12 Aug 2018, C??g wrote:
Date: Sun, 12 Aug 2018 14:00:21 -0500
From: "[utf-8] C??g"
To: netbsd-users@netbsd.org
Subject: Re: Libreoffice after upgrade to NetBSD 8.0
Bruce Nagel wrote:
File attached for the output of that, thanks for the tip on using tee.
It appear
Bruce Nagel wrote:
> File attached for the output of that, thanks for the tip on using tee.
> It appears to still be failing in much the same way.
[...]
Okay, I'm at loss now. Upgrade to pkgsrc-2018Q2 maybe? On CURRENT
boost-jam builds and installs without errors, the same 1.67.0 as in
2018Q2.
Bruce Nagel wrote:
> I'm at a loss, but willing to try other ideas, thanks to all who are
> trying to help.
Hi,
What version of pkgsrc are you using?
Run `make show-depends` to see the dependencies. -current reports these,
apart from others:
boost-libs-1.67.*:../../devel/boost-libs
On Tue, Aug 07, 2018 at 01:05:30PM -0500, C?g wrote:
Robert Nestor wrote:
I?ve run into this a few times using pkgin. Not sure if it?s a problem
with pkgin or with the packages and their dependencies. What seems to
work for me is to remove the newer version of the package that it?s
complaining
Robert Nestor writes:
> I wasn’t sure if it was a pkgin issue or something else, but I have
> run into this problem just installing packages using pkgin without
> having pkgsrc installed. But if the solution is to run “make
> deinstall clean” in devel/boost-headers, doesn’t that require that
I wasn’t sure if it was a pkgin issue or something else, but I have run into
this problem just installing packages using pkgin without having pkgsrc
installed. But if the solution is to run “make deinstall clean” in
devel/boost-headers, doesn’t that require that pkgsrc be installed on the
Robert Nestor wrote:
> I’ve run into this a few times using pkgin. Not sure if it’s a problem
> with pkgin or with the packages and their dependencies. What seems to
> work for me is to remove the newer version of the package that it’s
> complaining about, then retrying the installation. In you
I’ve run into this a few times using pkgin. Not sure if it’s a problem with
pkgin or with the packages and their dependencies. What seems to work for me
is to remove the newer version of the package that it’s complaining about, then
retrying the installation. In you case, remove
