Bug 144590 – zenity-2.15.9x should depend on a version of libnotify compiled against >=gtk+2.10.x

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Felix Braun 2006-08-20 23:28:24 UTC]

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.

[Comment 1 Rémi Cardona (RETIRED) 2006-08-20 23:45:04 UTC]

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.

[Comment 2 Gilles Dartiguelongue (RETIRED) 2006-08-21 00:27:54 UTC]

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)

[Comment 3 Daniel Gryniewicz (RETIRED) 2006-08-21 13:54:30 UTC]

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

[Comment 4 Felix Braun 2006-08-23 23:42:52 UTC]

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 :-)

[Comment 5 Daniel Gryniewicz (RETIRED) 2006-08-26 13:03:29 UTC]

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...)

[Comment 6 Alexander Skwar 2006-09-17 03:53:48 UTC]

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

[Comment 7 Andrew Frink 2006-09-17 21:05:08 UTC]

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.

[Comment 8 Jakub Moc (RETIRED) 2006-10-14 08:13:27 UTC]

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

[Comment 9 Rumen Yotov 2006-10-14 22:17:59 UTC]

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

[Comment 10 Luis Medinas (RETIRED) 2006-11-06 20:07:10 UTC]

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.

[Comment 11 John N. Laliberte (RETIRED) 2006-11-14 20:32:57 UTC]

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

[Comment 12 Pacho Ramos 2006-12-14 11:13:55 UTC]

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

Thanks

[Comment 13 Helmut Eberharter 2007-04-03 15:37:48 UTC]

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

[Comment 14 Mart Raudsepp 2007-06-19 02:53:17 UTC]

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..

[Comment 15 Rémi Cardona (RETIRED) 2007-09-02 13:15:46 UTC]

Everything has been stabled and unmasked :) Closing