whenever i grab a snapshot and get library version mismatches after a `pkg_add -u`, i've found the easiest way to get those objects is grab a fresh source tree and compile them manually. for example, libc:
cd /usr/src/lib/libc edit 'shlib_version' to have the appropriate major/minor versions (pkg_add(1) will tell you which ones it wants. a good article on how these work here: http://www.tedunangst.com/flak/post/OpenBSD-version-numbers) make && make install the bsd.port.mk(5) build system is well thought out and allows for straightforward, helpful maneuvers like this pkg_check(8) is also an invaluable tool in helping deal with package issues. also, use the right $PKG_PATH! On Thu, Dec 11, 2014 at 3:13 PM, STeve Andre' <and...@msu.edu> wrote: > On 12/11/14 05:59, FRIGN wrote: > >> On Wed, 10 Dec 2014 21:27:46 -0500 >> "STeve Andre'" <and...@msu.edu> wrote: >> >> You might want to subscribe to the ports-changes changes list, >>> which will show you what's been changed. The source-changes >>> list will show you all the other cvs commits. Look at >>> >>> http://www.openbsd.org/mail.html >>> >> Btw, now that the topic has come up. Is there a way to view the >> diffs quickly on a source- or port-change? >> Just reading the titles is not very helpful and I also don't feel >> like pulling the entire OpenBSD CVS-tree just to view the recent >> code-changes. >> >> I'm subscribed to numerous mailing lists, and all of them provide >> diff-data in the mail itself. I'm sure more people would subscribe >> to such a list if it actually encouraged to read and check the >> source. >> >> Cheers >> >> FRIGN >> >> Have you looked at http://cvsweb.openbsd.org/cgi-bin/cvsweb/ ? > > You can get a diff of the change of any revision, which should > help out. > > --STeve Andre'
