Install of pkg fuse-ntfs fails because of undefined symbol in pkg!?!

scratch65535 at scratch65535 at
Wed Feb 8 17:38:01 UTC 2017

On Wed, 8 Feb 2017 14:43:25 +0000, Matthew Seaman
<matthew at> wrote:

>On 02/08/17 11:56, scratch65535 at wrote:
>> So, what's the deal here?  To "encourage" people to upgrade, pkg
>> will break their existing install?  That is both hostile and
>> deeply arrogant!
>mat's response is more exasperation than anything else.  This is a well
>known problem for which there have been /numerous/ bug reports.  You're
>meant to check that there isn't already a relevant bug report when
>creating a PR in bugzilla.

I *did* check for bug reports.  I did a search on "utimenstat"
and found exactly one, which had been withdrawn as not being a

But it *is* a bug.  It's a bug on several levels, the most
significant of which is that the overly frantic schedule makes
versions have the lifespan of a mayfly.   And we're told "just
upgrade", as though there's some physical law mandating the

There are people for whom the system is a tool, not a hobby. They
don't want to have to rebuild their tools any more than
carpenters want to replace their hammers and levels every year or

For those people (I'm one) long version lifespans and bug-free
operation  is a much bigger desideratum than winning the secret
race (I presume there is some kind of secret race going on, since
otherwise the crazy scheduling makes No Sense At All).  I can't
work out what the strategy for winning is, if there is a
strategy, but I do know that it's not working.   Linux has all
but won already, and that's sickening.

I've been using the o/s since before v2 (I still have the cds)
and have watched FreeBSD go from being the leading Unix on Intel
boxes to all-but-dead.  I don't know how to express how saddened
I feel about that.

More information about the freebsd-ports mailing list