NetBSD Problem Report #47441

From diro@nixsyspaus.org  Sun Jan 13 23:33:58 2013
Return-Path: <diro@nixsyspaus.org>
Received: from mail.netbsd.org (mail.netbsd.org [149.20.53.66])
	by www.NetBSD.org (Postfix) with ESMTP id 0536863ECE1
	for <gnats-bugs@gnats.netbsd.org>; Sun, 13 Jan 2013 23:33:57 +0000 (UTC)
Message-Id: <20130113233355.0476320420A@asche.nixsyspaus.org>
Date: Sun, 13 Jan 2013 23:33:54 +0000 (UTC)
From: diro@nixsyspaus.org
Reply-To: diro@nixsyspaus.org
To: gnats-bugs@gnats.netbsd.org
Subject: Please, pull up sysutils/libnotify to latest version
X-Send-Pr-Version: 3.95

>Number:         47441
>Category:       pkg
>Synopsis:       Please, pull up sysutils/libnotify to latest version
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    pkg-manager
>State:          closed
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Sun Jan 13 23:35:00 +0000 2013
>Closed-Date:    Sun Apr 21 01:01:07 +0000 2013
>Last-Modified:  Sun Apr 21 01:01:07 +0000 2013
>Originator:     diro@nixsyspaus.org
>Release:        NetBSD 6.0.1
>Organization:
>Environment:
System: NetBSD 6.0.1 amd64
Architecture: amd64
Machine: amd64
>Description:
	wm/compix-fusion-plugins-extra-0.8.8 (patches coming soon) needs
libnotify>=0.6.1; however, the last version in 0.6 was 0.6.0. There's an
update request to 0.7.1, so this meets and exceeds that. I have tested this
with Transmission-gui, but as many other packages depend on this one
>How-To-Repeat:
	Have something that needs libnotify>=0.6.1. Notice we keep revbumping an
archive version of it.
>Fix:
	Patches here: http://pastebin.com/aWJWmzg3

>Release-Note:

>Audit-Trail:
From: Thomas Klausner <wiz@NetBSD.org>
To: NetBSD bugtracking <gnats-bugs@NetBSD.org>
Cc: 
Subject: Re: pkg/47441: Please, pull up sysutils/libnotify to latest version
Date: Mon, 14 Jan 2013 09:00:56 +0100

 On Sun, Jan 13, 2013 at 11:35:00PM +0000, diro@nixsyspaus.org wrote:
 > 	Patches here: http://pastebin.com/aWJWmzg3

 Why is xmlto a DEPENDS -- is it perhaps only a BUILD_DEPENDS?
 BUILDLINK_API_DEPENDS.libnotify shouldn't be bumped.
 (if a package needs that version, it should set the variable in its own Makefile)

 Due to the switch from gtk2 to gtk3, all packages using it need to PKGREVISION++.

 Have you tried if they still build? (Perhaps some are stuck in gtk2.)
  Thomas

From: David Holland <dholland-pbugs@netbsd.org>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: pkg/47441: Please, pull up sysutils/libnotify to latest version
Date: Mon, 14 Jan 2013 09:40:50 +0000

 On Mon, Jan 14, 2013 at 08:05:02AM +0000, Thomas Klausner wrote:
  >  Due to the switch from gtk2 to gtk3, all packages using it need to
  >  PKGREVISION++.
  >  
  >  Have you tried if they still build? (Perhaps some are stuck in gtk2.)

 It seems likely to me that we ought to keep a gtk2 version.

 -- 
 David A. Holland
 dholland@netbsd.org

From: diro@nixsyspaus.org
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: pkg/47441: Please, pull up sysutils/libnotify to latest version
Date: Mon, 14 Jan 2013 09:24:52 -0500

 On Mon, Jan 14, 2013 at 08:05:02AM +0000, Thomas Klausner wrote:
 > The following reply was made to PR pkg/47441; it has been noted by GNATS.
 > 
 > From: Thomas Klausner <wiz@NetBSD.org>
 > To: NetBSD bugtracking <gnats-bugs@NetBSD.org>
 > Cc: 
 > Subject: Re: pkg/47441: Please, pull up sysutils/libnotify to latest version
 > Date: Mon, 14 Jan 2013 09:00:56 +0100
 > 
 >  On Sun, Jan 13, 2013 at 11:35:00PM +0000, diro@nixsyspaus.org wrote:
 >  > 	Patches here: http://pastebin.com/aWJWmzg3
 >  
 >  Why is xmlto a DEPENDS -- is it perhaps only a BUILD_DEPENDS?

 Oh, right. Yes, it is only needed to build part of the documentation and thus
 just a BUILD_DEPEND.

 >  BUILDLINK_API_DEPENDS.libnotify shouldn't be bumped.

 The update for compiz-fusion-plugins-extra requires libnotify >=0.6.1. I
 suppose that means that the newer version had an backwards-incompatible API change.


 >  (if a package needs that version, it should set the variable in its own Makefile)

 (It needed that anyway to appease verifypc).

 >  Due to the switch from gtk2 to gtk3, all packages using it need to PKGREVISION++.

 Right, and a lot of them depend on it, so it's a big deal.

 >  Have you tried if they still build? (Perhaps some are stuck in gtk2.)
 >   Thomas

 Like i said, just with Transmission-gui. There's no other packages that i use
 (besides ekiga maybe and compiz-fusion-plugins-extra) and those had no issue
 with it. Saw no problems with either of those. I could probably get someone to
 test it with the xfce4 stuff.

 dh's suggestion is probably for the best, but could we import this as
 libnotify07, and slowly link packages to it as we test them (such as the above
 two which have been shown to work)?

From: Patrick Welche <prlw1@cam.ac.uk>
To: gnats-bugs@gnats.netbsd.org
Cc: 
Subject: Re: pkg/47441
Date: Thu, 17 Jan 2013 13:39:16 +0000

 I have been running

 libnotify-0.7.5     Desktop notification framework

 for a while now. As the gtk3 dependency is just there for building tests,
 I patched libnotify 0.7.5 to not require it - afterall:
 /usr/pkg/lib/libnotify.so:
         -lgdk_pixbuf-2.0.0 => /usr/pkg/lib/libgdk_pixbuf-2.0.so.0
         -lgio-2.0.0 => /usr/pkg/lib/libgio-2.0.so.0
         -lgobject-2.0.0 => /usr/pkg/lib/libgobject-2.0.so.0
         -lgthread-2.0.0 => /usr/pkg/lib/libgthread-2.0.so.0
         -lglib-2.0.0 => /usr/pkg/lib/libglib-2.0.so.0
         -lpcre.1 => /usr/pkg/lib/libpcre.so.1
         -lc.12 => /usr/lib/libc.so.12
         -lintl.1 => /usr/lib/libintl.so.1
         -lgcc_s.1 => /lib/libgcc_s.so.1
         -lpthread.1 => /usr/lib/libpthread.so.1
         -lffi.6 => /usr/pkg/lib/libffi.so.6
         -lgmodule-2.0.0 => /usr/pkg/lib/libgmodule-2.0.so.0
         -lz.1 => /usr/lib/libz.so.1
         -lpng15.15 => /usr/pkg/lib/libpng15.so.15
         -lm.0 => /usr/lib/libm.so.0

 The reason I didn't commit it, is that it broke my
 zenity build. zenity has gone to require gtk3 and then make libnotify
 optional.

 Options for zenity are:
 - update it to the gtk3 version - but then what of meta-pkgs/gnome (2)
 - disable libnotify in zenity

 But then what of all the other libnotify using packages? Suck it and see?

From: diro@nixsyspaus.org
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: pkg/47441
Date: Fri, 8 Mar 2013 20:43:00 -0500

 Well, looks like we're going to bake on this one for another couple of months.
 In the interim, there's wip/libnotify, which contains the applied patch
 originally attached. We can start testing packages with it, report back here,
 and perhaps make an eventual transition to this version.

From: diro@nixsyspaus.org
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: pkg/47441
Date: Sat, 9 Mar 2013 17:14:07 -0500

 wip/Eina works with wip/libnotify

From: Blue Rats <rodent@netbsd.org>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: pkg/47441
Date: Thu, 28 Mar 2013 02:20:14 +0000

 > The reason I didn't commit it, is that it broke my
 > zenity build. zenity has gone to require gtk3 and then make libnotify
 > optional.

 How did it break zenity?

 > Options for zenity are:
 >  - update it to the gtk3 version - but then what of meta-pkgs/gnome (2)

 Not a GNOME user, so don't really have an opinion on the future of the GNOME 2 packages. I'd say update zenity, but import it as zenity-gnome3 or something. We're likely going to have to maintain gnome3 versions of these packages in parallel to the ones we have in HEAD now. Some of the GNOME 3-based packages are already in -wip. 

 I don't see the point of not importing newer versions of these packages and instead waiting for the older series to bitrot to a point where no one uses them and demands the current, stable, supported branch by upstream. We're just wasting time not having these packages in HEAD, where they could be tested by our bulk builds across OSes, versions of those OSes, architectures, and pkgsrc versions. In the end, it slows the development of upstreams' packages too (assuming we stay good in pushing those changes/suggestions/feature requests to them and they integrate them in a timely manner).

 >  - disable libnotify in zenity

 Seems like that would violate the POLA. If it's a PKG_OPTION, can we make it one?

 > But then what of all the other libnotify using packages? Suck it and see?

 With both versions imported, we could test each package and its dependencies before throwing the switch for good. It seems better than just maintaining the version of libnotify that we have until it becomes a problem.

 Just wanted to note in this PR that an updated version of py-notify (pkg/47698) and wip/py-notify-dev builds fine with wip/libnotify.

From: Thomas Klausner <wiz@NetBSD.org>
To: NetBSD bugtracking <gnats-bugs@NetBSD.org>
Cc: 
Subject: Re: pkg/47441
Date: Thu, 28 Mar 2013 09:08:51 +0100

 On Thu, Mar 28, 2013 at 02:25:03AM +0000, Blue Rats wrote:
 >  With both versions imported, we could test each package and its dependencies before throwing the switch for good. It seems better than just maintaining the version of libnotify that we have until it becomes a problem.

 I don't think that the two libnotify packages can currently be
 installed in parallel; I think you can't even have them in the same
 pbulk build without problems. Perhaps fixing that would be a good
 first step?
  Thomas

From: rodent@NetBSD.org
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: pkg/47441
Date: Thu, 11 Apr 2013 20:42:23 -0400

 On Thu, Mar 28, 2013 at 08:10:05AM +0000, Thomas Klausner wrote:
 >  
 >  I don't think that the two libnotify packages can currently be
 >  installed in parallel; I think you can't even have them in the same
 >  pbulk build without problems. Perhaps fixing that would be a good
 >  first step?

 Well, how about we set them to CONFLICT with each other? We have tons of
 packages already which do this. Some even conflict with themselves (in the
 case of some python packages). wip/libnotify could be imported as
 libnotify-dev, so that it's even built after libnotify in the bulk builds and
 thus wouldn't interfere with building the packages that are depending on libnotify.

 The deal is that I don't want to sit on this for a while. The updates to the
 compiz packages depend on having this later version of libnotify installed. I
 don't want us to sacrifice versions of packages that are supported by upstream
 for any perceived stability we get by continuing to maintain older versions
 which upstream no longer supports, if that makes sense.

From: Thomas Klausner <wiz@NetBSD.org>
To: NetBSD bugtracking <gnats-bugs@NetBSD.org>
Cc: 
Subject: Re: pkg/47441
Date: Fri, 12 Apr 2013 12:25:19 +0200

 On Fri, Apr 12, 2013 at 12:45:04AM +0000, rodent@NetBSD.org wrote:
 > The following reply was made to PR pkg/47441; it has been noted by GNATS.
 > 
 > From: rodent@NetBSD.org
 > To: gnats-bugs@NetBSD.org
 > Cc: 
 > Subject: Re: pkg/47441
 > Date: Thu, 11 Apr 2013 20:42:23 -0400
 > 
 >  On Thu, Mar 28, 2013 at 08:10:05AM +0000, Thomas Klausner wrote:
 >  >  
 >  >  I don't think that the two libnotify packages can currently be
 >  >  installed in parallel; I think you can't even have them in the same
 >  >  pbulk build without problems. Perhaps fixing that would be a good
 >  >  first step?
 >  
 >  Well, how about we set them to CONFLICT with each other? We have tons of
 >  packages already which do this. Some even conflict with themselves (in the
 >  case of some python packages). wip/libnotify could be imported as
 >  libnotify-dev, so that it's even built after libnotify in the bulk builds and
 >  thus wouldn't interfere with building the packages that are depending on libnotify.

 If you want to go that way, the new libnotify must have a different PKGNAME.
  Thomas

From: rodent@NetBSD.org
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: pkg/47441
Date: Fri, 12 Apr 2013 11:54:20 -0400

 On Fri, Apr 12, 2013 at 11:05:03AM +0000, Thomas Klausner wrote:
 >  
 >  If you want to go that way, the new libnotify must have a different PKGNAME.

 That is fine. We're doing multimedia/vlc* this way now. Also, the package uses
 pkg-config, so other packages won't have an issue finding it.

 Summary of changes:

 1) Import wip/libnotify as sysutils/libnotify07;
 2) Set its PKGNAME as libnotify07;
 3) Set libnotify and libnotify07 to CONFLICT with each other;
 4) Begin the slow transition;

 Sound good? Anything else?

From: "Blue Rats" <rodent@netbsd.org>
To: gnats-bugs@gnats.NetBSD.org
Cc: 
Subject: PR/47441 CVS commit: pkgsrc/sysutils
Date: Sun, 21 Apr 2013 00:50:04 +0000

 Module Name:	pkgsrc
 Committed By:	rodent
 Date:		Sun Apr 21 00:50:04 UTC 2013

 Modified Files:
 	pkgsrc/sysutils: Makefile
 	pkgsrc/sysutils/libnotify: Makefile
 Added Files:
 	pkgsrc/sysutils/libnotify07: DESCR Makefile PLIST buildlink3.mk
 	    distinfo options.mk

 Log Message:
 Adding latest version of libnotify as libnotify07. Setting libnotify and
 libnotify07 to conflict with each other. Resolves PR pkg/47441


 To generate a diff of this commit:
 cvs rdiff -u -r1.567 -r1.568 pkgsrc/sysutils/Makefile
 cvs rdiff -u -r1.26 -r1.27 pkgsrc/sysutils/libnotify/Makefile
 cvs rdiff -u -r0 -r1.1 pkgsrc/sysutils/libnotify07/DESCR \
     pkgsrc/sysutils/libnotify07/Makefile pkgsrc/sysutils/libnotify07/PLIST \
     pkgsrc/sysutils/libnotify07/buildlink3.mk \
     pkgsrc/sysutils/libnotify07/distinfo \
     pkgsrc/sysutils/libnotify07/options.mk

 Please note that diffs are not public domain; they are subject to the
 copyright notices on the relevant files.

State-Changed-From-To: open->closed
State-Changed-By: rodent@NetBSD.org
State-Changed-When: Sun, 21 Apr 2013 01:01:07 +0000
State-Changed-Why:
Resolved by import of libnotify07 and transition of transmission-gtk to use it.


>Unformatted:

NetBSD Home
NetBSD PR Database Search

(Contact us) $NetBSD: query-full-pr,v 1.51 2026/08/10 02:28:17 riastradh Exp $
$NetBSD: gnats_config.sh,v 1.10 2026/05/13 22:00:09 riastradh Exp $
Copyright © 1994-2026 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.