I was configuring wip/grip and it failed with:

/usr/bin/ld: warning: libgnutls.so.11, needed by
/tmp/pkgsrc/wip/grip/work.montecristo/.buildlink/lib/libgnomevfs-2.so, not
found (try using -rpath or -rpath-link)
/tmp/pkgsrc/wip/grip/work.montecristo/.buildlink/lib/libgnomevfs-2.so:
undefined reference to `gnutls_compression_set_priority@GNUTLS_REL_1_0_9'

I have libgnomevfs-2.so which is libgnomevfs-2.so.0.1000.0 from package
gnome-vfs2-2.10.0.

That package depends on:

gnutls>=1.0.20nb2

I have gnutls-1.2.3 installed which provides libgnutls.so.12.3.0.

I found libgnutls.so.11 in my old vulnerable/gnutls-1.0.20nb2.tbz package.
So I guess that gnome-vfs2 I am using was built using older gnutls.

On April 15, gnome-vfs2/buildlink3.mk set
+BUILDLINK_RECOMMENDED.gnome-vfs2+=     gnome-vfs2>=2.10.0
(The update to 2.10.0 was done on March 22.)

And on May 2, gnutls/buildlink3.mk set
+BUILDLINK_RECOMMENDED.gnutls+= gnutls>=1.2.3
(Update was done on same day.)

My packages were built May 7 (gnutls) and April 22 (gnome-vfs2). (Notice
how it allowed me to install older gnome-vfs2 built with newer gnutls.)

Does anyone see the same of the soname change for gnutls?

Our pkgsrc guide (section 10.2.2) says "In some cases, the packages that
depend on this new version may need their PKGREVISIONs increased and, if
they have buildlink3.mk files, their BUILDLINK_DEPENDS. pkg adjusted,
too."

jmmv: may I do commit this for sysutils/gnome-vfs2/buildlink3.mk

-BUILDLINK_RECOMMENDED.gnome-vfs2+=     gnome-vfs2>=2.10.0
+BUILDLINK_RECOMMENDED.gnome-vfs2+=     gnome-vfs2>=2.10.1

This will force using a newer version of gnome-vfs2 which uses the new
gnutls.

Or should I just forget about it since this happened 15 days ago?

 Jeremy C. Reed

 	  	 	 BSD News, BSD tutorials, BSD links
	  	 	 http://www.bsdnewsletter.com/