[Bug 233621] textproc/enchant - shared lib symlink fails to install

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Mon Dec 10 02:07:38 UTC 2018


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233621

--- Comment #4 from dave at jetcafe.org ---
(In reply to John Hein from comment #3)

Ordinarily, I would just reinstall this package. The machine in question has
easily had N major "pkg upgrade" done (N > 1 and probably somewhere around 8)
to it. The entire system is complex enough that I'm pretty sure edge cases
abound that ports maintainers might not have thought about and I can always
reset things.

However, there is at least one other person with the same problem. :) So I
don't mind sleuthing about some just to make sure this is only my issue and not
an actual bug. 

There's definitely something weird going on because as part of 'pkg upgrade':

# grep enchant /var/log/messages
Nov 28 14:50:12 myhost pkg: enchant-1.6.0_8 installed
Nov 28 14:50:33 myhost pkg: enchant-1.6.0_7 deinstalled
Nov 28 15:08:53 myhost pkg: enchant2-2.2.3_1 installed

Note the order of operations there. Further, I see this in pkg info -R:

files {
...
    /usr/local/lib/libenchant.so.1.6.0 =
"1$9977c2fc2550207d3c88f7eb7d0403acb4a235b0cc5a7a7d640b8c3b4d5e297e";
...
}

I presume the 1$ means "MD5 checksum". Proceeding on this presumption, none of
those entries I checked match the actual MD5 checksums of the files:

md5 /usr/local/lib/libenchant.so.1.6.0
MD5 (/usr/local/lib/libenchant.so.1.6.0) = a44295a753873da58a52418355d57493

So I'm fairly clueless as to what actually happened here. I did check the
enchant2 package to see if libenchant.so.1.6.0 was inside, but it's not.

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-gnome mailing list