Bugzilla Bug 144590

I'm using the experimental gnome-overlay from overlays.gentoo.org and have been
having trouble building zenity. The build aborted with "unresolved symbol
notify_new_with_status_icon()".

After a bit of digging around I found out that libnotify does not have this
function if it is compiled against a gtk+ version prior to 2.9.2 (as it was
before I updated to the overlay).

Therefore I suggest to change the zenity ebuild to depend on a revision of the
libnotify ebuild which in turn depends on gtk+-2.10.x to ensure that libnotify
will be compiled against a suitable gtk+ version.

By doing that, we'd be forcing everyone to unmask gtk+-2.10 which is against
Gentoo policy. I think the best we can do is add an elog/ewarn message
somewhere to tell people to rebuild libnotify.

This issue will definitely be pointed out in the upgrade guide if we can't work
around it.

as a matter of fact it already is :
http://www.gentoo.org/proj/en/desktop/gnome/howtos/gnome-2.16-upgrade.xml

remember that by using overlays, you should try to communicate with the
maintener of the overlay before reporting bugs (on #gentoo-desktop for example)

For now, I've put a link to the upgrade guide on the overlay Wiki page.

How about adding something like the following to the affected ebuilds
(appearently zenity and rhythmbox)

if grep notification_new_with_status_icon /usr/lib/libnotify.so 
then true
else die "*** It seems your version of libnotify was originally compiled
against gtk+-version 2.8.x, please type: \"emerge -Ou libnotify\" to
re-compile."

That reduces the possibility of having duplicate bugs reported :-)

I think the easiest 90% solution is to gratuitously revbump libnotify when we
unmask gtk 2.10.  Then, people will get them both updated.  As long as they go
stable together, it should cover most people.

Anyone, of course, who unmasks a masked package gets what they deserve, right?
:)

(or at least should follow the upgrade docs...)

*** Bug 147905 has been marked as a duplicate of this bug. ***

I would like to add that this is the case with the version 2.16.0 from the main
portage tree, re-emerging libnotify after gtk+-2.10 fixed this right up.

*** Bug 151341 has been marked as a duplicate of this bug. ***

Hi,
Confirmed, re-emerging "libnotify" fixed the problem.
Thanks.Rumen

when gnome goes to stable we can force libnotify to go to stable too so we can
avoid this problem or add gtk-2.10 as a dependency for libnotify (bad way).
This shouldn't cause many troubles when 2.16 goes to stable.

*** Bug 154663 has been marked as a duplicate of this bug. ***

The problem persists with 2.16.2, but it is fixed after reemerging libnotify.

Thanks

*** Bug 173199 has been marked as a duplicate of this bug. ***

compnerd, do you think you can stabilize libnotify-0.4.4, that has been in the
tree since very end of February, to give a final touch here?
Though I'm sure anyone who had problems with this have things fixed by now
already..

Everything has been stabled and unmasked :) Closing