Am Montag, den 01.11.2010, 21:12 -0400 schrieb Matthias Clasen:
I am planning to push libnotify 0.7.0 into rawhide by the end of this
week;
Next time you are making an update that affects a large number of
packages, please use devel-announce.
TIA,
Christoph
--
devel mailing list
On Mon, 2010-11-01 at 21:12 -0400, Matthias Clasen wrote:
I am planning to push libnotify 0.7.0 into rawhide by the end of this
week; this is going to be a little painful, since there are some api
changes that will require minor adjustment of all users. And there's
quite a few of them (see
On Tue, 2010-11-02 at 11:33 -0400, Tom spot Callaway wrote:
On 11/01/2010 09:12 PM, Matthias Clasen wrote:
I am planning to push libnotify 0.7.0 into rawhide by the end of this
week; this is going to be a little painful, since there are some api
changes that will require minor adjustment of
On Tue, 2010-11-02 at 11:33 -0400, Tom spot Callaway wrote:
Matthias, this seems like it will break the python bindings... will you
be fixing them at the same time?
I can certainly not do it all by myself. At least not in one day...
Looking at notify-python, it seems that running update-defs
On 11/02/2010 12:13 PM, Matthias Clasen wrote:
On Tue, 2010-11-02 at 11:33 -0400, Tom spot Callaway wrote:
Matthias, this seems like it will break the python bindings... will you
be fixing them at the same time?
I can certainly not do it all by myself. At least not in one day...
Looking
On Tue, 2010-11-02 at 12:11 -0400, Adam Jackson wrote:
As far as I can tell, none of the callers to pynotify.init() pass any
named arguments, so nothing should notice the lack of attach=. I only
searched for explicit calls to pynotify.init, if someone's doing like
foo = pynotify
I am planning to push libnotify 0.7.0 into rawhide by the end of this
week; this is going to be a little painful, since there are some api
changes that will require minor adjustment of all users. And there's
quite a few of them (see below). I will hopefully be able to handle most
of the GNOME
