DragonFlyBSD

pkg_radd pulls from binary packages built using the latest quarterly
release of pkgsrc. Our images (I assume you're running a 2.11
install) are built using pkgsrc-current, so the pkgsrc items that came
as part of your install are from a newer version that what pkg_radd
pulls down.

Here's some solutions:

- You can install pkgsrc in /usr/pkgsrc using make pkgsrc-update in
/usr, and use either the latest branch, in which case binary packages
added with pkg_radd will work, or use the bleeding edge, which should
match what you have installed.

- Except you said your download of pkgsrc keeps not working, in a
different email, I think. So that doesn't help.

- You could rip out pkgsrc completely and re-add it in a way where you
know everything is up to date. WARNING: I have not tested this
directly; I may have missed something really important!

rm -rf /usr/pkgsrc
rm -rf /usr/pkg
rm -rf /var/db/pkg
rm -rf /var/db/pkg.refcount

1. the next two items assume you are using tcsh
   setenv CVSROOT anoncvs@anoncvs.NetBSD.org:/cvsroot
   setenv CVS_RSH ssh
   cd /usr
   cvs -q checkout -rpkgsrc-2011Q1 -P pkgsrc
   cd pkgsrc/bootstrap
   ./bootstrap

When that's done, you should have pkgsrc-2011Q1 in /usr/pkgsrc, which
matches the binary packages available for download.

You will need to re-add all packages that you want to have installed,
at that point, either through pkg_radd or by building from source in
/usr/pkgsrc.

- The step that really needs to be done is making sure the install
ISOs are built with the matching release, instead of bleeding-edge
pkgsrc. That's our fault. I'm not sure how to change that, since I
haven't built ISOs.

On Sun, Aug 7, 2011 at 4:55 AM, ferz <nonsolosoft@diff.org> wrote:

Hi,

pkg_radd gdm (or emacs, or many other packages)

return warning about "Shared object libintl.so.3 not found, required by ..."

it installs gettext-lib-0.18.1.1 but it is too new for pre built packages.

Bye,              \ferz

I had this problem a few weeks ago, but I just created a symbolic link
libintl.so.3 to the latest libintl.so and everything went fine. After all the
libintl-dependent packages are built, this symlink can be deleted.

It was the quickest, most painless solution anyway.