Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 2 Sep 2017 12:11:04 +0100
From:      tech-lists <tech-lists@zyxst.net>
To:        freebsd-ports@freebsd.org
Subject:   Re: www/bluefish builds but fails to install
Message-ID:  <0f6dd5f9-cb14-cea5-3432-96f4099de43c@zyxst.net>
In-Reply-To: <CAN6yY1tAO9RAVZtvM=6R-uUh=9D7mKEL9M5OgBMFaRXtb=X43A@mail.gmail.com>
References:  <c8d2ffee-5767-1cca-4533-22e14fd95f1e@zyxst.net> <CAN6yY1s6L2bjLkwDAmh8yM434Fu%2BzNcQv8w753nDwzJT4i1VfQ@mail.gmail.com> <c4da78eb-b5ed-90c3-bec7-7d0595ffcda2@zyxst.net> <CAN6yY1tO0qxbd7BstB_0CnAZyL6yVJsUjdPYLWXR4GN0X8gBBA@mail.gmail.com> <d7fd0e01-13bf-e38b-3ebf-9aff8606b79e@zyxst.net> <CAN6yY1tAO9RAVZtvM=6R-uUh=9D7mKEL9M5OgBMFaRXtb=X43A@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Hi,

On 01/09/2017 23:33, Kevin Oberman wrote:
> No, not really "aha". If you have most anything using freedesktop specs
> (which includes all "modern" desktops), you will have these files. You
> should also  have a similar set of system wide mime files. These are
> normally found in /usr/local/share/mime, but that can be altered and it
> looks like yours is in "/storage". If the prefix for local is changed,
> ports must be rebuilt as many ports assume that related ports use the same
> location for shared resources.

The OS was initially installed onto a SSD, then 3xsata disks were added
for a zfs array. This array is /storage and /usr is symlinked to
/storage/usr

> FWIW, I just installed bluefish on my system using default options with no
> errors. As a result, I suspect thee is an issue with your environment and
> that is why you are having issues.

I'm running portupgrade -af in the hope this fixes things, or if it
fails hopefully the errors will show where the problem is. It'll take a
while as nearly 1400 ports are installed, then again this desktop is
quick. At the same time, I spun up a newly created, small, bhyve
11.1-stable instance, installed ports and it's now building bluefish
with all its dependencies.

I expect that you're right, that there's something broken in the
environment. In which case I'll probably have to return the machine to a
more-or-less pristine state, delete .local and install what I currently
require. Maybe some cruft has built up over the years that's causing
problems now. It's been a freebsd desktop since v9.

thanks,
-- 
J.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0f6dd5f9-cb14-cea5-3432-96f4099de43c>