Re: GNOME 3.2 / pyatspi / at-spi2-core

2011-12-20 Thread Michael Biebl
On 17.12.2011 20:31, Jean-Philippe MENGUAL wrote:
 Hi guys,
 
 It seems that Mario is very busy and cannot answer. I would like to
 help, however everybody knows that my technical skills are limited, so I
 can't take a decision and test beyond the user point of view.
 
 So I propose something:
 - Could someone tell me what packages shuld be updated?

It's about updating pyatspi and at-spi2-core to 2.2.x

 - I would update the packages on experimental. Thus, even sid users will
 be able to work using experimental packages, without needing push to
 sid.

Sounds ok to me, if those packages are first uploaded to exp.

 
 What do you think of all that? If my help is needed, I can give it. If
 no... wait and see
 

I did notice that the debian git repository already has 2.2 versions for
both at-spi2-core and pyatspi which have been prepared for Ubuntu by
Luke Yelavich (in CC).
Maybe it would make sense to build on top of his work and working more
closely together would benefit both Debian and Ubuntu.

Cheers,
Michael



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature


Re: GNOME 3.2 / pyatspi / at-spi2-core

2011-12-19 Thread Jean-Philippe MENGUAL
Hi again,

 
 The existing at-spi 2.0 packages need to be updated to version 2.2.3.
 The following is the link to the announcement.
 http://mail.gnome.org/archives/gnome-announce-list/2011-November/msg00019.html

Please explain to me to enable me to understand fine: at-spi 2.0, on Debian, is 
only in experimental isn't it? If yes, I can try to update (probably before end 
2011).

  All I know now is that if Mario didn't push to sid, it's because it
  didn't consider that the atspi2 packages work enough. Is there some
  update which fix the problems? No idea.
  
 Yes, the 2.0 release wasn't much use.  The 2.2 release should do better.

Ok.

  What do you think of all that? If my help is needed, I can give it. If
  no... wait and see
  
 I think Debian needs packages for at-spi 2.2 and orca 3.2.2.
 Those are the latest upstream releases for gnome 3.2.

Yes, but given my power in Debian and my technical capability, I propose to do 
any tests on a sid environment with such packages (orca, at-spi, etc.) from 
experimental repo. Would it be enough? I ask not to work uselessly.

 The sooner packages exist in Debian, the sooner the issues can be documented 
 for Wheezy.

I agree, but the situation is now complex, so we have to try something waiting 
for the maintainer, which is the only people who has the technical skill and 
responsibility to push to sid. I'm not sure my initiative is good, so I stay 
careful. Sorry Mario if I did so much.

Regards,

   Kenny
 
 
Jean-Philippe MENGUAL





signature.asc
Description: Ceci est une partie de message	numériquement signée


Re: GNOME 3.2 / pyatspi / at-spi2-core

2011-12-18 Thread Kenny Hitt
Hi.
On Sat, Dec 17, 2011 at 08:31:45PM +0100, Jean-Philippe MENGUAL wrote:
 Hi guys,
 
 It seems that Mario is very busy and cannot answer. I would like to
 help, however everybody knows that my technical skills are limited, so I
 can't take a decision and test beyond the user point of view.
 
 So I propose something:
 - Could someone tell me what packages shuld be updated?
 - I would update the packages on experimental. Thus, even sid users will
 be able to work using experimental packages, without needing push to
 sid.
 - Then, let Mario decide about pushing to sid;
 - if he doesn't come back (I can't believe it), we'll have to find a
 solution to do technical tests.
 
The existing at-spi 2.0 packages need to be updated to version 2.2.3.
The following is the link to the announcement.
http://mail.gnome.org/archives/gnome-announce-list/2011-November/msg00019.html

 All I know now is that if Mario didn't push to sid, it's because it
 didn't consider that the atspi2 packages work enough. Is there some
 update which fix the problems? No idea.
 
Yes, the 2.0 release wasn't much use.  The 2.2 release should do better.

 What do you think of all that? If my help is needed, I can give it. If
 no... wait and see
 
I think Debian needs packages for at-spi 2.2 and orca 3.2.2.
Those are the latest upstream releases for gnome 3.2.
The sooner packages exist in Debian, the sooner the issues can be documented 
for Wheezy.

  Kenny


-- 
To UNSUBSCRIBE, email to debian-accessibility-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20111219055732.ga11...@hittsjunk.net



Re: GNOME 3.2 / pyatspi / at-spi2-core

2011-12-17 Thread Jean-Philippe MENGUAL
Hi guys,

It seems that Mario is very busy and cannot answer. I would like to
help, however everybody knows that my technical skills are limited, so I
can't take a decision and test beyond the user point of view.

So I propose something:
- Could someone tell me what packages shuld be updated?
- I would update the packages on experimental. Thus, even sid users will
be able to work using experimental packages, without needing push to
sid.
- Then, let Mario decide about pushing to sid;
- if he doesn't come back (I can't believe it), we'll have to find a
solution to do technical tests.

All I know now is that if Mario didn't push to sid, it's because it
didn't consider that the atspi2 packages work enough. Is there some
update which fix the problems? No idea.

What do you think of all that? If my help is needed, I can give it. If
no... wait and see

Best regards,

Jean-Philippe MENGUAL


Le vendredi 16 décembre 2011 à 16:07 +0100, Michael Biebl a écrit :
 On 15.12.2011 23:01, Michael Biebl wrote:
  Hi Mario, hi Samuel,
  
  to unblock the situation regarding GNOME 3.2, I wanted to let you know
  that I'm planning to NMU pyatspi tomorrow and upload the current version
  2.0.2 to unstable via DELAYED/5. 
 
 I've done the NMU a few moments ago. Attached is the debdiff.
 
 As using static and dynamic pygobject at the same time does not really
 work that well, I've pulled a fix from upstream Git for that.
 I've changed the dependency on python-gobject to python-gi accordingly.
 
 The complete changelog reads:
 
  pyatspi (2.0.2+dfsg-1.1) unstable; urgency=low
  .
* Non-maintainer upload.
* Upload to unstable.
* Use introspection for the GLib main loop.
  Patch cherry-picked from upstream Git.
* Depend on python-gi instead of python-gobject.
* Use dh_python2 so ${python:Depends} is correctly set.
 
 


signature.asc
Description: Ceci est une partie de message	numériquement signée


Re: GNOME 3.2 / pyatspi / at-spi2-core

2011-12-17 Thread Jason White
Jean-Philippe MENGUAL mengualjean...@free.fr wrote:
 
 - I would update the packages on experimental. Thus, even sid users will
 be able to work using experimental packages, without needing push to
 sid.

Perhaps it would be better just to ask the Debian Gnome maintainers if they
can do an NMU of the packages directly to Sid. That way, the updating and
uploading of the packages will be done by people who do have the right
background.

The only way to make Gnome 3.2 accessible, as I understand it, is to update
atspi2-core and Orca, and since 3.2 is on its way already, there really isn't
a decision to be made anymore.


-- 
To UNSUBSCRIBE, email to debian-accessibility-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20111217232608.ga5...@jdc.jasonjgw.net



Re: GNOME 3.2 / pyatspi / at-spi2-core

2011-12-17 Thread Jean-Philippe MENGUAL
Hi,

If I understood everything (note that Debian gnome team was in Cc om my
mail), gnome team doesn't want to replace Mario on atspi, as they don't
know the applications and they prefer waiting for his analysis. That's
why I think we should try experimental before thinking of sid, hoping
he'll be back (I'm sure he only is busy now).

Regards,

Jean-Philippe MENGUAL


Le dimanche 18 décembre 2011 à 10:26 +1100, Jason White a écrit :
 Jean-Philippe MENGUAL mengualjean...@free.fr wrote:
  
  - I would update the packages on experimental. Thus, even sid users will
  be able to work using experimental packages, without needing push to
  sid.
 
 Perhaps it would be better just to ask the Debian Gnome maintainers if they
 can do an NMU of the packages directly to Sid. That way, the updating and
 uploading of the packages will be done by people who do have the right
 background.
 
 The only way to make Gnome 3.2 accessible, as I understand it, is to update
 atspi2-core and Orca, and since 3.2 is on its way already, there really isn't
 a decision to be made anymore.
 
 


signature.asc
Description: Ceci est une partie de message	numériquement signée


Re: GNOME 3.2 / pyatspi / at-spi2-core

2011-12-16 Thread Michael Biebl
On 15.12.2011 23:01, Michael Biebl wrote:
 Hi Mario, hi Samuel,
 
 to unblock the situation regarding GNOME 3.2, I wanted to let you know
 that I'm planning to NMU pyatspi tomorrow and upload the current version
 2.0.2 to unstable via DELAYED/5. 

I've done the NMU a few moments ago. Attached is the debdiff.

As using static and dynamic pygobject at the same time does not really
work that well, I've pulled a fix from upstream Git for that.
I've changed the dependency on python-gobject to python-gi accordingly.

The complete changelog reads:

 pyatspi (2.0.2+dfsg-1.1) unstable; urgency=low
 .
   * Non-maintainer upload.
   * Upload to unstable.
   * Use introspection for the GLib main loop.
 Patch cherry-picked from upstream Git.
   * Depend on python-gi instead of python-gobject.
   * Use dh_python2 so ${python:Depends} is correctly set.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
diff -Nru pyatspi-2.0.2+dfsg/debian/changelog pyatspi-2.0.2+dfsg/debian/changelog
--- pyatspi-2.0.2+dfsg/debian/changelog	2011-07-28 14:34:35.0 +0200
+++ pyatspi-2.0.2+dfsg/debian/changelog	2011-12-16 15:51:54.0 +0100
@@ -1,3 +1,14 @@
+pyatspi (2.0.2+dfsg-1.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Upload to unstable.
+  * Use introspection for the GLib main loop.
+Patch cherry-picked from upstream Git.
+  * Depend on python-gi instead of python-gobject.
+  * Use dh_python2 so ${python:Depends} is correctly set.
+
+ -- Michael Biebl bi...@debian.org  Fri, 16 Dec 2011 15:40:13 +0100
+
 pyatspi (2.0.2+dfsg-1) experimental; urgency=low
 
   * Remove tests/* until upstream clarifies licensing.
diff -Nru pyatspi-2.0.2+dfsg/debian/control pyatspi-2.0.2+dfsg/debian/control
--- pyatspi-2.0.2+dfsg/debian/control	2011-07-28 14:34:35.0 +0200
+++ pyatspi-2.0.2+dfsg/debian/control	2011-12-16 15:50:43.0 +0100
@@ -7,9 +7,11 @@
 Vcs-Git: git://git.debian.org/git/pkg-a11y/pyatspi.git
 Homepage: http://live.gnome.org/Accessibility/GNOME3
 Build-Depends: debhelper (= 7),
+   python (= 2.6.6-3~),
python-dbus,
pkg-config,
python-gobject-dev (= 2.26.0)
+X-Python-Version: = 2.5
 Standards-Version: 3.9.2
 
 Package: python-pyatspi2
@@ -18,7 +20,7 @@
 Replaces: python-pyatspi
 Depends: ${misc:Depends},
  ${python:Depends},
- python-gobject (= 2.26.0),
+ python-gi (= 3.0),
  gir1.2-atspi-2.0
 Description: Assistive Technology Service Provider Interface - Python bindings
  at-spi is the Assistive Technology Service Provider Interface.
diff -Nru pyatspi-2.0.2+dfsg/debian/patches/0001-Use-introspection-for-the-GLib-main-loop.patch pyatspi-2.0.2+dfsg/debian/patches/0001-Use-introspection-for-the-GLib-main-loop.patch
--- pyatspi-2.0.2+dfsg/debian/patches/0001-Use-introspection-for-the-GLib-main-loop.patch	1970-01-01 01:00:00.0 +0100
+++ pyatspi-2.0.2+dfsg/debian/patches/0001-Use-introspection-for-the-GLib-main-loop.patch	2011-12-16 15:38:12.0 +0100
@@ -0,0 +1,33 @@
+From a48759f60b1a863f14238a5cc089eaac79d3bf2c Mon Sep 17 00:00:00 2001
+From: Mike Gorse mgo...@novell.com
+Date: Thu, 25 Aug 2011 13:18:00 -0500
+Subject: [PATCH] Use introspection for the GLib main loop
+
+---
+ pyatspi/registry.py |3 +--
+ 1 files changed, 1 insertions(+), 2 deletions(-)
+
+diff --git a/pyatspi/registry.py b/pyatspi/registry.py
+index 89a36bd..0b0130c 100644
+--- a/pyatspi/registry.py
 b/pyatspi/registry.py
+@@ -28,7 +28,6 @@ __all__ = [Registry,
+ 	   set_default_registry]
+ 
+ import os as _os
+-import gobject
+ from gi.repository import Atspi
+ from gi.repository import GObject
+ import time
+@@ -80,7 +79,7 @@ class Registry(object):
+ self.app_event_register = None
+ self.desktop = None
+ 
+-		self.main_loop = gobject.MainLoop()
++		self.main_loop = GObject.MainLoop()
+ 
+ def __call__(self):
+ 
+-- 
+1.7.7.3
+
diff -Nru pyatspi-2.0.2+dfsg/debian/patches/series pyatspi-2.0.2+dfsg/debian/patches/series
--- pyatspi-2.0.2+dfsg/debian/patches/series	1970-01-01 01:00:00.0 +0100
+++ pyatspi-2.0.2+dfsg/debian/patches/series	2011-12-16 15:38:17.0 +0100
@@ -0,0 +1 @@
+0001-Use-introspection-for-the-GLib-main-loop.patch
diff -Nru pyatspi-2.0.2+dfsg/debian/rules pyatspi-2.0.2+dfsg/debian/rules
--- pyatspi-2.0.2+dfsg/debian/rules	2011-07-28 14:34:35.0 +0200
+++ pyatspi-2.0.2+dfsg/debian/rules	2011-12-16 15:51:02.0 +0100
@@ -1,3 +1,3 @@
 #!/usr/bin/make -f
 %:
-	dh $@
+	dh $@ --with python2


signature.asc
Description: OpenPGP digital signature


GNOME 3.2 / pyatspi / at-spi2-core

2011-12-15 Thread Michael Biebl
Hi Mario, hi Samuel,

to unblock the situation regarding GNOME 3.2, I wanted to let you know
that I'm planning to NMU pyatspi tomorrow and upload the current version
2.0.2 to unstable via DELAYED/5. This will allow us to also update
gnome-shell and orca to 3.2.

We'd still appreciate having updates of pyatspi and at-spi2-core to 2.2,
so we can also update accerciser.


Rergards,
Michael
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature