Probably caused by the new GLIB and GTK+ packages. * QA Notice: Package has poor programming practices which may compile * fine but exhibit random runtime failures. * gdaemonvolumemonitor.c:155: warning: implicit declaration of function ‘g_volume_monitor_adopt_orphan_mount’ ^G * * QA Notice: Package has poor programming practices which may compile * but will almost certainly crash on 64bit architectures. * * Function `g_volume_monitor_adopt_orphan_mount' implicitly converted to pointer at gdaemonvolumemonitor.c:155 * * Please file a bug about this at http://bugs.gentoo.org/ * with the maintaining herd of the package. Debian bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=524905 Something like: sed -i -e 's:-DG_DISABLE_DEPRECATED::g' $(find . -name Makefile.in) || die Should fix this.
+ 08 May 2009; Peter Alfredsen <loki_val@gentoo.org> gvfs-1.0.3-r1.ebuild, + gvfs-1.0.3-r2.ebuild, gvfs-1.0.3-r12.ebuild, gvfs-1.0.3-r13.ebuild: + Fix bug 268788, Function 'g_volume_monitor_adopt_orphan_mount' implicitly + converted to pointer at gdaemonvolumemonitor.c:155, caused by newer + gtk/glib combos deprecating more functions. +
Please don't touch our packages without permission. You have successfully made it so that when we happen to need to patch something so that we need to eautoreconf, it will break again. And an obvious fix for that one would probably cause maintainer mode build system rebuilds...
